Database Develop

Compass and Accel sensors not working, Please Help!

I seem to be having an odd problem with my new G1.
In any Cupcake build (JF 1.51, TheDude's 1.2, Official ADP) I flash, neither the compass nor the accelerometer sensors work at all. I have flashed between them several times, with an Alt+W each time, so I know it's not a bad flash.
The strange thing is, when I jump back to an official RC29 build, both sensors work fine. I haven't tried RC30 or anything else, but I know the sensors are physically functional.
I have re-flashed the latest radio as well, as it is currently using 2.22.19.26I.
If anyone can help me with this problem, I would greatly appreciate it.

gigawatts said:
I seem to be having an odd problem with my new G1.
In any Cupcake build (JF 1.51, TheDude's 1.2, Official ADP) I flash, neither the compass nor the accelerometer sensors work at all. I have flashed between them several times, with an Alt+W each time, so I know it's not a bad flash.
The strange thing is, when I jump back to an official RC29 build, both sensors work fine. I haven't tried RC30 or anything else, but I know the sensors are physically functional.
I have re-flashed the latest radio as well, as it is currently using 2.22.19.26I.
If anyone can help me with this problem, I would greatly appreciate it.
Click to expand...
Click to collapse
I think your using the pre-cupcake apps. Did u download the apps after you updated or did you install them from a back up?
Best way to check, You should got to settings and then sounds&display and check off orientation. You phone should switch from portrait to landscape when you rotate any program (except homescreen). If that works then nothing is wrong with your phone. If it doesn't then something happened somewhere weird

any apps i have installed have been after i flashed a rom (after a wipe) and not from a backup. Plus, something as simple as Google Maps or the Browser App should just rotate without opening the keyboard.
Best way to check, You should got to settings and then sounds&display and check off orientation.
Click to expand...
Click to collapse
By that I assume you place the check mark (lit green) next to the option, not "check it off" (not lit green). I have tried both checked and unchecked in pre-installed apps like maps and browser, and still nothing.

Small update. I just flashed JF's v1.43_RC33 with root, keeping the same more recent radio, and both sensors work there, as they do in RC29. It seems to be ONLY cupcake based roms where they don't work.
Any other suggestions anyone has for me? I might try a hero build next, to see if they work there, but I'm not sure how stable they are yet.
Any help/suggestions would be greatly appreciated!

Accelerometer fix
http://forum.xda-developers.com/showpost.php?p=4081673&postcount=4885

I tried your suggestion, and it did not work. Unlike the other user reporting that the sensors would work for a short time after reflashing, mine has never worked after a cupcake flash. Only after a pre-cupcake flash.
Although ideas like that are what I am looking for, possible corrupt config files that need to be cleared or maybe a mod probe command of some sort to activate or wake up the sensors.

Upon some more inspection, I get the feeling something is wrong with my akmd process, or whatever executable generates the akmd_set.txt compass and accelerometer calibration data. I tried to follow some instuctions to purge the akmd_set.txt file to clear any bad config, but the file is no where to be found. My phone doesnt seem to generate one at all when it's booting.
The akmd process does remain running in the background, as here is its ps output:
Code:
# ps | grep akmd
compass 77 1 1320 328 c020d268 afe0c45c S /system/bin/akmd
This is the output I get from logcat when I try to manually run the /system/bin/akmd process or when it restarts automatically after being killed:
Code:
D/AKMD ( 362): akmd 1.6.4 START
D/AKMD ( 362): library version: 1.2.1.1129
D/AKMD ( 362): Compass OPEN
D/AKMD ( 362): No calibration data
D/AKMD ( 362): Can not initial compass parameters error: -5
and this is the output I get when I run a program like Orienteer:
Code:
I/ActivityManager( 90): Starting activity: Intent { action=android.intent.action.MAIN categories={android.intent.category.LAUNCHER} flags=0x10200000 comp={com.deafcode.android.Orienteer/com.deafcode.android.Orienteer.Orienteer} }
I/ActivityManager( 90): Start proc com.deafcode.android.Orienteer for activity com.deafcode.android.Orienteer/.Orienteer: pid=363 uid=10041 gids={}
D/SensorManager( 363): found sensor: AK8976A 3-axis Accelerometer, handle=0
D/SensorManager( 363): found sensor: AK8976A 3-axis Magnetic field sensor, handle=1
D/SensorManager( 363): found sensor: AK8976A Orientation sensor, handle=2
D/SensorManager( 363): found sensor: AK8976A Temperature sensor, handle=3
D/dalvikvm( 363): GC freed 920 objects / 64320 bytes in 92ms
D/LocationManager( 363): Constructor: service = [email protected]
D/Sensors ( 90): sensors=00000005, real=00000005
D/GpsLocationProvider( 90): setMinTime 2000
W/IInputConnectionWrapper( 145): showStatusIcon on inactive InputConnection
I/ActivityManager( 90): Displayed activity com.deafcode.android.Orienteer/.Orienteer: 1313 ms
D/dalvikvm( 145): GC freed 795 objects / 45896 bytes in 165ms
D/GpsLocationProvider( 90): TTFF: 7203
Maybe this will give someone some more insight as to the problem I am having.

hello,
i me french and i have the same problem.
No akmd_set.txt on my phone.
If you are a solution could you partage it ?
I think it's a driver problem but i'm not sure.
JEEP

Unfortuantly I have still not found a solution, but continue to look for one. I will let you know here if I do manage to solve it.

I am also having the same problem. Wiping does not fix it and the method stated by Cyanogen didn't work either. I don't know if this will be any help, but I do know the accelerometer issue started about 3 or 4 days ago for me. Maybe if I list things I've done to my phone in the last few days, it might help narrow down the cause if others with the same issue compare their experiences to each other.
I have a US T-Mobile G1 and I have been rooted since February. Since that time I have upgraded to (and currently use) the latest radio from HTC, Haykuro's SPL, and a class 6 4gb card. I've also been through more roms than I can count in that time, all without an accelerometer issue till now.
Now that I've got all that out of the way here's the more relevant stuff:
Within the last week I have upgraded to Cyanogen's 1.3.1 recovery boot and installed the latest JAC Hero build. I repartitioned my card into 3 partitions with the directions given in JustAnotherCrowd's thread using parted in the recovery's console.
Code:
#parted /dev/block/mmcblk0
rm 1
rm 2
mkpartfs primary fat32 0 3420
mkpartfs primary ext2 3420 3932
mkpartfs primary linux-swap 3932-3964
This is the first time I've ever used apps to sd. After using that rom for about a day, I switched to Cyanogen's build and wiped my user data without wiping the ext partition of my sd card and I continued to use the swap partition on my Cyanogen build. I'm fairly sure but not 100% certain that the accelerometer was still working at this point. Soon after installing this rom, Cyanogen released an update including the compcache modules to replace the linux-swap setup. I installed the custom userinit.sh script to system/sd to activate compcache. Then Cyanogen released another update (immediate bug fixes) almost as soon as I got this rom working. I flashed the update.zip, but then it started to boot loop. I wiped the phone (not the ext partition), still boot looped. I took out the sd, still boot looped. I put the sd card back in wiped again, reflashed, and then clicked "repair ext file system". STILL BOOT LOOPED! (Don't say I just wasn't giving it enough time to boot because I acctually watched the boot animation flicker in and out for a second and start over.) Next, I used fastboot to restore only the user data from a nandroid backup of an older Cyanogen rom. This time it worked. Next, I installed the audio resources to system/sd/media and linked them using the userinit.sh file. The next day, I realized that the accelerometer was no longer functioning.
I hope this description helps to figure this out.

I'm having the exact same issue.

testing567, can you post the userinit.sh file you are currently using, and possibly you or someone else post their userinit.sh of a phone with a working accelerometer and compass here?
I am thinking that one of my init scripts may not be calling the akmd service properly, as in not with the correct permissions or something, and thus not calibrating itself on boot. I was planning on upgrading to the latest cyanogen update today, as i am running 3.6.5 right now. I was also considering upgrading my SPL to a dev SPL so i can use nandroid to backup (getting a little tired of loosing everything when attempting different roms to fix this issue).

I got my userinit.sh from this post.
http://forum.xda-developers.com/showpost.php?p=4140826&postcount=74
I also decided to take advantage of the media symlinking already in this script and pushed the audio resources to system/sd/media/.

I've always had the same issue when upgrading to a cupcake based rom. Nobody else until recently seemed to share my misfortune (sorry for everyone else). There is an exception though, JF 1.5 (T-Mobile) build the sensors work (although miscalibrated). I haven't found any other solutions or any other way to generate the settings file. My process output appears to be the exact same as you've posted.
I'll keep trying some things but I just want to keep this alive incase anyone else needs a fix and one of us comes up with a solution.

RemoteDJ, I may actually have a solution to your miscalibrated problem. In the process of going through and trying to get my sensors working, I created an empty akmd_set.txt file with chmod 777 permissions (just so it wouldnt ***** about some user permissions when trying to edit it), and then rebooted the phone. Upon looking at the file after reboot, it was filled with calibration data.
Although this has not fixed my problem, it may help you. Also, the application "Bubble" has a calibrate sensors menu option, which may help you too. I may have to try reverting back to JF 1.5 to see if I have better luck there. Was that JF 1.51 you were using? If not, please advise.

Yes it was JF 1.51, it's funny because I just got done making a blank chmod 777 akmd_set.txt lol. Of course i'm on the latest stable cm-3.6.8.1 currently and the sensor doesn't work at all.
Just so we stay up to date with each others findings, I also pulled the akmd app from Haykuro's ION, JF 1.43, JF 1.51, Official RC33 and the current CM build. I have only tried replacing the current one with the ION app (in recovery), so far no change, but I think the only file difference I noticed out of the files I pulled was that the JF 1.43 and Official RC33 seemd to be the same (haven't hashed them to verify) and different then the others which seem to be the same but since I haven't hashed any of them to verify yet I can't say for sure.
I am calling it a night right now but will let you know if I find anything tomorrow.
Just a followup with the hash info.. looks like I was correct:
517a87a4e6caa5e66f0520c68dcb7c0e - Official RC33
517a87a4e6caa5e66f0520c68dcb7c0e - JF 1.43
c3a80124ab072f9bf12cc9e4155a0f9f - JF 1.51
c3a80124ab072f9bf12cc9e4155a0f9f - ION
c3a80124ab072f9bf12cc9e4155a0f9f - CM 3.6.8.1
Another Edit: I am apparently not good at going to sleep.. Good News! (semi).
I left the akmd_set.txt in place (it got filled with data just like yours)
replaced ion/cm akmd with jf 1.43 and now the sensor appears to be working (although still miscalibrated for me, this might be a hardware issue.. lots of drops).
step by step.
copy jf1.43 akmd to sdcard (i just pulled it out of the update zip).
reboot recovery
mount /system
rm /system/bin/akmd
mount /sdcard
cp /sdcard/jf1.43_akmd /system/bin/akmd
then umount (probably not required)
reboot.
It still didn't work, but I deleted the akmd_set.txt via adb and then rebooted and voila!
Let me know if any of that works for you
Edit: I was able to fix my calibration by reverting to the rc30 akmd, I have absolutely no idea why my device is so picky, but it only has ever had correct calibration with accelerometer on the rc29/30 builds (this includes all official t-mobile ota releases). Anyway just wanted to through that out there incase anyone else uses the jf1.43 and is miscalibrated.

RemoteDJ,
Thank you so much for that suggestion! That totally worked for me! I flashed cm-3.6.8.1 tonight and replaced its /system/bin/akmd binary with the one from jf 1.42. After messing around with some permissions (I failed to realize the akmd binary was not set as executable when i moved it over ) i was able to create a blank akmd_set.txt, chmod 777 it, and then restart the akmd service (stop akmd, followed by start akmd).
I can not thank you enough for this suggestion! Guess it just took another similar brain bashing away at the same problem to solve it. I just wonder why this is not a problem for a lot of other people out there. It's the same hardware, so you would think everyone upgrading to cupcake would have an incompatible akmd binary. Strange...

Sweet, I'm really glad it worked for you!
I can't imagine for the life of me why other people don't have similar problems, but then again I've had a few problems that seemed indivualized to my device lol. Its only recently that I discovered a few other people were having problems with the accelerometor.
Oh well, all in all just glad this worked.
Maybe we can get Cyanogen to include this in his FAQ as an alternative for sensor repair for the people like us. I might reply on the latest build thread later, anyway have a good one.

So far I haven't had any luck with this. I'm actually tempted to send my unit back to HTC with the ota 1.5 cupcake on it and see what happens. I'm not sure if it was working when they sent it to me or not. It doeswork with the rc29 though.

I'm having the same issue, no compass apps seem to work, google sky maps doesn't work , the level app doesn't work, all are froze.
How can I fix it?

[ROM][ICS][IML74K] teamhacksung's CM9 ALPHA for Vibrant (BUILD 17)

Introduction
Teamhacksung (the rest of them really!) has been porting ICS (to be CM9) for the Galaxy S and they feel that it has reached a state where it would benefit from public testing. However this is still a very early versions and there will be bugs. Bug reports are allowed in this thread only. Please check the known issues section before reporting a bug. The most minor bugs are welcomed (we'd love to know them, but we may not fix them instantly).
Download
ROM: BUILD 17: androtransfer.com / Mediafire
Google Apps: Download from ROM Manager. (Or http://goo-inside.me/gapps/gapps-ics...213-signed.zip)
Google Apps Fixer: MultiUpload / tux-head.net / faramir.eriador.org (md5: af8bcaf5f8158e8e1be7097fc86b6b28)
Google Apps Fixer will fix your problem with not being able to add Google Account or Calendar Sync, but will also reset your Google Apps data. Only flash if you're having problems. If Google Apps Fixer does not work for you, do a factory reset from CWM (or Android Settings) and do not restore system data via TitaniumBackup.
Older Downloads
ROM
Build 16B: Mediafire
Google Apps
v7.1: MultiUpload / tux-head.net / faramir.eriador.org (md5: 8bf66137f18de45657f29c129a8f4d52)
v7: MultiUpload / tux-head.net / faramir.eriador.org (md5: 1888fbb15f36a076cb3908acaf1bd15a)
v6: MultiUpload / tux-head.net / faramir.eriador.org (md5: 6f51ded731d173c31b8c47395ca580b7)
v5.3: MultiUpload / tux-head.net / faramir.eriador.org (md5: e7d69d98a633b646e4f14e6a43208e66)
v5.1: MultiUpload / tux-head.net (thanks! Kaik541) (md5: 87415730a1db2e90d3588bc895f239e5)
v5: MultiUpload (thanks! Kaik541) (md5: 8667c9ddca581a98867fc02db29a2326)
v4: MultiUpload (thanks! Kaik541) (No longer include apps downloadable from Market.) (md5: 8b2dad009bc2f8724d27f78bca162495)
v3: internal
v2: MultiUpload (thanks! koush)
v1: MultiUpload (thanks! koush)
Installation
- First time flashing ICS to your Vibrant (or coming from another ROM)?
Root your device and install ClockworkMod Recovery.
Reboot into Recovery using 3-button-combo
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
WIPE again or Calendar Sync will not work.
- Upgrading from CM7?
Do a Nandroid Backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
- Coming from onecosmic's ICS build?
Do a Nandroid Backup!
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
Reboot into recovery and WIPE (wipe data/factory reset + wipe cache partition)
If radio doesn't work, go back to Samsung ROM and flash from there.
- Upgrading from another build of ICS by teamhacksung?
Do a Nandroid Backup!
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
Note: The upgrade process from CM7 to ICS is automatic, but downgrading from ICS to CM7 (or restoring Nandroid) requires flashing twice. Once from ICS and again from CM7's recovery.
Source
Kernel Source: https://github.com/teamhacksung/samsung-kernel-aries
Userspace Source: Patches are being integrated into CM's mainline tree. Device tree is available on teamhacksung's GitHub, but may not be buildable. No support for the source code, do not post that you are not able to build it.
Known Issues
Camera does not support scene modes
Phone unnecessarily gets data connection on device encryption password enter screen.
Cannot format external SD *
Android OS battery usage display higher than normal.
Sometime wrong SMS selected for forwarding
Format internal instead of external SD when requested to format ext. SD
Transfer speed slows down when screen off
Screenshot shutter sound
TV Out using HW-decoding (probably won't be fixed)
Sim Toolkit (probably won't be fixed)
No camera focus mode setting
Compass doesn't work in Google Maps v6
Unable to dial "0001" in some regions
Slow USB transfer speed for some people
Camera still photos problem after recording video
Top of widget selection selector says "Select screen lock"
Note: there are a lot of new options in Settings, but many of them are not implemented yet. DO NOT REPORT THEM AS BUGS. Additionally, some users has reported boot failure after disabling boot animation.
Empty wifi icon when using juice defender / sometimes on boot
Unused bottom bar in landscape dialer
Send contact to voicemail doesn't work
911/E911 is unknown, one report of weirdness
Fixed Issues
BUILD 17
Top of widget selection selector says "Select screen lock" (Upstream fix)
Chrome not working
Various other upstream fixes
BUILD 16
Regression in BUILD 15: Superuser application crashes
Regression in BUILD 15: Data Roaming enabled by default
Back camera does not record geotagging
Camera crashes when changing resolution
New: WM8994 Extensions (aka "Voodoo Sound") is now configurable from DSP Manager
BUILD 15
Duplicate entries in MediaScanner (will only prevent new duplicates, need to clear data to get rid of old duplicates)
Regression in BUILD 14: Screen flicker while turning off
Regression in BUILD 14: adb turns off every reboot
Mute-unmute needed on some calls (hopefully)
Notification power widget uncustomizable (now integrated into Settings)
Reboot into recovery on crash (it will still reboot, just not into recovery)
Unreliable Wi-Fi on screen off (hopefully)
Gallery face glow FCs
BUILD 14
Laggy video recording in low light
"sin" does not work in calculator in Spanish
Laggy playback of some video in .mkv container (same video works in the .mp4 container) (Recommendation: Dice Player from market. Does its own mkv extraction and has hw decoding support)
New Feature: Gamma tuning (equivalent to Voodoo Color's "v1 gamma hack")
BUILD 13
720p Video Recording laggy
No camera zoom
Timelapse video recording crashes
TV Out broken on sleep
TV Out black video
Broken encryption (regression in BUILD 11) (WARNING: users with already encrypted phone will have their data cleared (for real this time))
BUILD 12
Compass, accelerometer broken in certain apps
Random force closes (hopefully)
Missing camera touch to focus (thanks to havlenapetr)
GPS does not work (regression in BUILD 11)
Off-charging does not show progress
/datadata cache not cleared when space is low
Slow mass storage transfer speed
Automatic brightness not working
GApps v7.1
Network location broken
GApps v7
Market purchase broken
BUILD 11
Encryption not working without a data wipe (WARNING: users with already encrypted phone will have their data cleared)
Cannot authenticate new apps for root
Data sometimes get disabled on boot
GApps v6 / Face Unlock v6
Updated: based on IML74K
Face Unlock not working on BUILD 10+
BUILD 10
No hardware composition (but hardware acceleration works)
Video recording does not work.
Video playback is not hardware-accelerated.
The front camera produces distorted preview.
Photo taking does not work with the front camera.
Some camera options FC. (The camera is a temporary hack, when the Nexus S ICS source is released, there will be a proper fix.)
Movie Studio does not work.
WiFi automatically turns on after quitting airplane mode if WiFi was used during airplane mode.
Data Roaming is enabled by default
Can select widget on launcher without being on the widget screen *
GApps v5.3
Updated: Market apk
Removed: unneeded GoogleLatinIME
BUILD 9
WPA Wifi Tethering broken (regression in BUILD 8)
Audio recording by android app crashes (phone calls still work) (regression in BUILD 8)
Phone crashes in landscape with T9 enabled
Reboot to recovery by default even though recovery not selected.
Slow T9 speed
CPU rarely scaling up to 1000 MHz
GMail sometimes fills up /datadata with attachments
BUILD 8
USB Tethering on Windows requires the user go to to driver update and manually select the RNDIS driver.
Sketchy wifi tether (breaks if data connection comes up while tether is active) (it will still error, but you can now re-enable it)
Mounting external SD via USB broke in BUILD 7
Cannot accept many file types via bluetooth
Data activity icon sometimes gets stuck even data is off.
New feature: T9 Dialing by devatwork (Enable in Dialer Setting)
BUILD 7
Cannot encrypt phone after restoring data.
Wi-Fi problems for Iran users
Market download temporarily goes to /datadata
Support for TV Out (in Galaxy S Setting application)
Screen appearing for a split second after screen off animation
BUILD 6
Persistent "Removed SD card" message on external sd card removal.
Missing library for Android Open Accessory
Support for USB Mass Storage (see FAQ)
BUILD 5
VPN does not work
Regression in device encryption
BUILD 4
Large photos cannot be edited.
Missing Live Wallpapers
Bluetooth Reverse Tether does not work
Wi-Fi Direct not supported (it's supported in settings now, but apps are needed to use it as ICS does not come with any use-case for Wi-Fi direct)
Sometimes wifi strength won't show after boot if wifi is enabled. Toggle once to fix. (fixed, hopefully)
GApps v5.1
GApps: Missing TTS libs
GApps v5
GApps: Missing Picasa Sync
GApps: Unable to purchase apps
Build 3
Device encryption does not work. (Note: temporarily broken again in BUILD 4, works on BUILD 5)
User does not have write permission for external sd
A2DP bluetooth headsets do not work.
GApps v4
GApps: More missing libs for GoogleTTS
Build 2
Superuser.apk does not open.
Installer does not work on Samsung ROMs.
Factory reset (from settings menu) does not clear /datadata.
GApps v2
GApps: Missing voice chat, maps, text-to-speech libraries
GApps: Android Keyboard appears twice in Settings.
Frequently Asked Questions
My calendar sync isn't working!
Install the latest build and gapps and gapps fixer. If it still doesn't work, wipe your data.
App X isn't working!
Check the list at http://forum.xda-developers.com/show....php?t=1402210 (unaffiliated with teamhacksung) first and check if it works on other ICS phones. Most likely, it's the application's problem, not ours.
Can I mount the phone as mass storage via USB?
Starting from BUILD12, mass storage is the default configuration (might not apply to existing installations). The below command can be used to change into USB Mass Storage mode. USB Mass Storage mode is always used in recovery.
Code:
setprop persist.sys.usb.config mass_storage,adb
If you want to switch to MTP mode use
Code:
setprop persist.sys.usb.config mtp,adb
Please reboot after executing the command.
I can't adb into the phone!
Please install Nexus S drivers from Google. (Or Galaxy Nexus's driver in MTP mode)
Can I flash other modems?
You may flash modem packages designed for CM7.
How do I take a screenshot?
The screenshot taking function is built into ICS. Hold volume down + power.
Can I use CM7 kernels?
No, the kernel has modifications to make graphics, camera, data counter and data limit work.
Can I disable LED Notification?
Yes. Untick Settings -> Display -> Pulse notification light.
Maps keeps asking me to sign in even though I'm signed in!
Ignore the sign in dialog and pull down the notification menu. Answer the request for permission. Do this a few times and Maps will work.
How do I enter Galaxy S Settings (Device Settings)?
Type "am start com.cyanogenmod.AriesParts/.AriesParts" from adb. Or starting from BUILD 7, it is available as an icon in your launcher.
Is there a Captivate version?
A captivate build from the same source (but with captivate config) is available here.
What's working? Why is there only a list of issues?
Everything else not listed are supposed to be working (aside from the usual CM7 bugs). If they're not listed, please post so that they can be added to the list of issues. A list of issues is far more useful from a development standpoint.
Why am I getting notified that my data partition is getting full when I have 1+ GB free?
Your /datadata partition, a smaller partition, is getting full.
I want to install gazillion apps on my phone and /datadata is too small
Run the following and datadata will no longer be used on next reboot. Your phone might become slower though.
Code:
touch /datadata/.nodatadata
IRC?
#cmsgs on freenode
My adb shell isn't root!
Run "adb root" to restart adb in root mode.
Why is "Android OS" battery usage so high?
It's just a reporting change in ICS. Android OS now includes battery usage from more components than in Gingerbread, the actual battery drain is the same.
What is "Random Offset" during installation?
It's just a harmless message given as a verbose logging due to the new ASLR security feature in ICS. It is not an error.
How do I get the latest version of Rom Manager without market?
If the bundled version doesn't work, update from http://download.clockworkmod.com/rec...RomManager.apk.
I would like feature X
This thread is not the place for it. Submit it to the CM bug tracker once an official RC is released.
Thanks
syndtr: Updated touch and graphics driver
onecosmic: Being the first to successfully build the AOSP tree
Kaik541: GApps from v3 onward
ancdix: For hosting on tux-head.net
nikademus (_renaud_): For hosting on faramir.eriador.org
SysTem-X: For hosting on ics.haxer.org
sixstringsg: For hosting on androtransfer.com
CyanogenMod team: Setting up the infrastructure and being a great help in the porting process.
sixstringsg, TkGlitch, and Skitz: Helping me get GPS going on ICS.
Team ICS Passion: This build uses a gpsd blob they found for their ROM from older versions of CM7.
and everyone else involved in this port or CM7 for SGS.

Reserved. *10 char*

thanks FaultException. was waiting on six to bring us Build 16, going to give it a try later when i get home, thank for this and the good work you are doing on cm7.

thanks will try tomorrow

Thank
Thanks FE and wish you all best.

Thanx man...will flash this.

What is the stock kernel the rom comes with???

krackerjac said:
What is the stock kernel the rom comes with???
Click to expand...
Click to collapse
It's the standard Aries CM kernel.

Thanks again FaultException for your time and effort which I know the Vib community here appreciates it 800% !

Fault Exception is there any way you could committ the yagf2 GPS fix in to this rom. It makes a huge difference in GPS lock speed over stock.

hurtz777 said:
Fault Exception is there any way you could committ the yagf2 GPS fix in to this from. It makes a huge difference in GPS lock speed over stock.
Click to expand...
Click to collapse
The what? You'll have to give me a link.

FaultException said:
The what? You'll have to give me a link.
Click to expand...
Click to collapse
I think this http://forum.xda-developers.com/showpost.php?p=19869399&postcount=1

Yeah that is the link to it. It makes a world of difference on GPS locks and accuracy.

the usual gps problem....
it works good first time...then no more and doesnot go in ds too...
damn vibrant first stock!

daffyno said:
the usual gps problem....
it works good first time...then no more and doesnot go in ds too...
damn vibrant first stock!
Click to expand...
Click to collapse
From what rom you came from.i came from cm7 and ended up in a bootloop..wander what im doing wrong.
Edit* if you end up in a bootloop all you have to do is pullthe battery.enter the clockworkmode useng three button combo.reinstall.done.
Sent from my SGH-T959 using XDA App

daffyno said:
the usual gps problem....
it works good first time...then no more and doesnot go in ds too...
damn vibrant first stock!
Click to expand...
Click to collapse
Can you try using yagf2 + http://forum.xda-developers.com/showpost.php?p=22119563&postcount=80 ?

nuwanmw1988 said:
From what rom you came from.i came from cm7 and ended up in a bootloop..wander what im doing wrong.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
another ics rom
chui101 said:
Can you try using yagf2 + http://forum.xda-developers.com/showpost.php?p=22119563&postcount=80 ?
Click to expand...
Click to collapse
the same...

hurtz777 said:
Yeah that is the link to it. It makes a world of difference on GPS locks and accuracy.
Click to expand...
Click to collapse
I'll look into it. If it does make that much of a difference, and I have permission from the authors, I'll throw it in CM9 and 7.

Dougfresh said:
Thanks again FaultException for your time and effort which I know the Vib community here appreciates it 800% !
Click to expand...
Click to collapse
+1 that's right
Sent from my SGH-T959 using xda premium

chui101 said:
Can you try using yagf2 + http://forum.xda-developers.com/showpost.php?p=22119563&postcount=80 ?
Click to expand...
Click to collapse
If u flash that file it works on this rom. I am using this rom and I flashed the GPS fix and I get a GPS lock.
Sent from my SGH-T959 using XDA App

Cell signal lost

Some people (like me) loosing the signal to the provider. WiFi is ok, but to get back the mobile connection I had to reboot the phone (1-2 times a working day. I never had this problem over the weekend).
I could pin down this behavior to a fast switching between mobile connection and no mobile connection. If the connection is just reestablished and in the next moment it is lost again the phone hangs. I take the underground to reach the office. That is the reason why I only have this issue on working days
So the solution is clear: Stop working. Enjoy the free time
I used "How to get useful logs" from tonyp with the App: SysLog and found in the modem.log the following error: (full log attached)
( 98): dlc[12] atchannel: at_send_command_full() at handshake fails, err - 12. Restarting rild
( 98): lge-ril: handle Cp Reset (CP Reset Cause - 1, RIL recovery activated flag - 0, dlc - 12)
( 98): [0485]< DEACTIVATE_DATA_CALL fails by E_RAIDO_NOT_AVAILABLE
( 98): dlc[12]: lge-ril - requestInterface: Exiting DLC handler, thread - 22231000. s_dlc_handler_create_tracker - 0x6013f
( 759): Exception processing unsol response: 1054Exception:java.lang.RuntimeException: Unrecognized unsol response: 1054
( 759): Unrecognized RIL errno 16
Click to expand...
Click to collapse
I tried a lot of different basebands but could not fix the problem. The only difference was the RIL errno changed from 16 to 14 ???
The basebands I tried are: V30b, V30a, V30c (SU660 - because the sticker under the battery says: Made in Korea), V20m, V20s. In the end I tried different RILs but that only made the problem worse. Now I am back on the original cm10.1 RIL.
Losing the IMEI in the phone is not the problem. I already checked this.
I am pretty sure it is not ROM related because I experienced the same thing on cm7.2 and now on cm10.1 from tonyp on the old and new Boot loader
Regards
Fidi

Possible solution
Hi,
it looks like I found a solution for the loosing signal problem.
After trying all kinds of differnt basebands I switched to an old not recommended baseband. No signal lost for 4 working days in a row :fingers-crossed:
I am now on Baseband 0823-V21b and using ROM tonyp cm10.1 (04)
For the baseband have a look at the P990 Complete Baseband Overview Thread from tonyp: http://forum.xda-developers.com/showthread.php?t=1658047
Cheers
Fidi

Thanks for your informations, i think i have the same problem. Please respond if you have further informations!

I keep you updated:
Over the weekend: Everything worked fine and stable. I used the phone "normal" over the last three days. Including running with Endomondo Sports Tracker and some other parts. The phone is still stable. No reboot since the downgrade to Baseband 0823-V21b.
If I don't get any issues over the week I think that's the solution.
trampi did you downgrade your baseband too? I hope it's a working solution for you too.
Cheers
Fidi

Thank you Fidi!
I have the same logs when my data connection drops, currently with tonyp's T-Build 4 and Kowalski 125 and baseband 0725-V10d.
I will try this out, and report back.

Well I had this data drop issue but when using tonyp's T-Build I started having drops in the whole mobile connection (no voice as well). So I followed his recommendation and flashed BB V30a but that did nothing. Then I tried his Paranoid Android and it's working great!

Bad news here:
7 hours after flashing the baseband 0823-V21b (tonyp T-Build 4, kowalski kernel 125 exp), I got the same error again, and no data, no voice. And only reboot will fix it.
As soon as I see
## AT COMMAND TIMEOUT ##
in the radio log, I'm in the same situation again.
then at the moment of the connection blackout, always followed by:
E/RILJ ( 584): Exception processing unsol response: 1054Exception:java.lang.RuntimeException: Unrecognized unsol response: 1054
and
D/RIL ( 98): dlc[5]: lge-ril - requestInterface: Exiting DLC handler, thread - 7126560. s_dlc_handler_create_tracker - 0x611df
Only with this baseband I don't see this anymore:
E/GSM ( 593): Unrecognized RIL errno 16

I've found a workaround to restore the connection without rebooting:
first kill the /system/bin/rild process
then kill the com.android.phone process
They will both restart automatically.
So this looks like a problem with the ril. Is the ril not compatible with the baseband?
This is also suggested by the "Exception processing unsol response" messages: ril is not able to handle certain baseband commands, although this could also be a corruption on the baseband side...
Now creating a script to automate this workaround will at least give back the connection immediately.

Hi gios_
I am running on the same configuration: 0823-V21b (tonyp T-Build 4, kowalski kernel 125 exp)
If you could provide the script that will check for the error and kill the two services that would be gorgeous. That will solve the problem even if we don't find a "real" solution :fingers-crossed:

Here's the script to fix the connection:
Code:
#!/system/xbin/sh
ps|grep phone|cut -c10-14|xargs kill
ps|grep rild|cut -c10-14|xargs kill
To quickly execute it, you can use gscript (then leave out that first line).

do you guys already check with this solution?
Code:
http://forum.xda-developers.com/showthread.php?t=2075564

antec123 said:
do you guys already check with this solution?
Code:
http://forum.xda-developers.com/showthread.php?t=2075564
Click to expand...
Click to collapse
I did not try that solution because their problem seems to be something else: transition from wifi to data not working; whereas our problem is connection dropping (not only data) at a random moment.
Also my IMEI number is transmitted correctly, so I doubt changing it will do any good.

gios_ said:
I did not try that solution because their problem seems to be something else: transition from wifi to data not working; whereas our problem is connection dropping (not only data) at a random moment.
Also my IMEI number is transmitted correctly, so I doubt changing it will do any good.
Click to expand...
Click to collapse
i used that solution, and with kowalski kernel exp 125 i haven't gotten any data loss. up time already 4 days. using kowalski kernel exp 124, i always get data loss and need reboot.
i use bb v30b ics, and ril (default). rom is using tony bulid 4 cm10.1 newBL. and using 2G always.

Yes, I tried this. But I never lost my IMEI and the solution did not help me
At the moment I am happy with my old baseband (no drops over two weeks). But It looks like that's only a solution for my phone. Maybe we should create a script, that scans the logs for the error and if the connection drops we could restart it with the solution from gios_

FidiS said:
Yes, I tried this. But I never lost my IMEI and the solution did not help me
At the moment I am happy with my old baseband (no drops over two weeks). But It looks like that's only a solution for my phone. Maybe we should create a script, that scans the logs for the error and if the connection drops we could restart it with the solution from gios_
Click to expand...
Click to collapse
yeah i think that true. I'm also confused why some people still have data loss with kowalski exp 125 and some people don't, so wierd

I will stick with baseband 0823-V21b. Still there is no real issue.
There is only remaining thing. In the situations when I formerly lost my connection now the phone rarely heats up for a short time with can drain the battery about 3%. After that the connection is reestablished and everything works as it should
Cheers Fidi

Open Source CM10.1 for Dell Streak 7 continuation

First you need to have giveen's original port installed: http://goo.im/devs/giveen/jellystreak (via the old thread: http://forum.xda-developers.com/showthread.php?t=2130081). The most important thing this does is installing the TWRP "recovery" bootmenu thingy. You can use it when powering on/restarting the dell streak 7 and then keeping power+volup pressed and then choosing "install update from sdcard" or so.
With AOKP there is one install image that wipes /system and an ota update. I have not tested the ota update.
Download for the AOKP 4.2 build for the Dell Streak 7: http://w3studi.informatik.uni-stuttgart.de/~haagch/aokp/
The non-ota update wipes /system. So you have to reinstall gapps every time too, preferably before rebooting (android deletes settings for apps that are not installed I think).
The "official" gapps package uses neon instructions that don't work on tegra2. You'll see the keyboard, tts, etc. crashing all the time. "tonyp" has created a gapps package that uses "old" libraries that work without neon instructions. So you should use this instead of the official gapps:
Download for non-neon gapps: http://goo.im/devs/tonyp/non-neon-gapps
Gesture typing on the keyboard doesn't seem to work for me, but tts works and it doesn't seem to be crashing.
Known issues for me:
[*]sensors don't work: rotation, accelerometer, gps (I think), magnet field (Sensor driver is sensors.p3.so for now, maybe later giveen gets open source drivers to work)
headphone jack doesn't mute/transfer for some headsets like ones with built in microphones
bluetooth keyboard
Performance problems. Especially when the ram gets full. You can use a ram manager like https://play.google.com/store/apps/details?id=com.jrummy.apps.memory.manager with the Aggressive or Extreme preset to make that problem go away with the cost of background apps being killed very quickly.
Here is the repository: https://github.com/ChristophHaag/android_device_dell_streak7
And here is how to build it on Archlinux:
AOKP: https://gist.github.com/ChristophHaag/6334554
Cyanogenmod: https://gist.github.com/ChristophHaag/6078249
I'm new to android but maybe some other people know something, so I post whatever I come about. Maybe someone else wants to get started too and finds this helpful.
If you want to engage in bug finding and fixing yourself:
Remote debugging c works like this:
On the android device you do
Code:
gdbserver --remote-debug :5039 --attach 1
Which will attach gdbserver to the process with pid 1 and listen on port 5039 on all interfaces.
For a gui debugger I tried nemiver:
For $ANDROID I use the path where the cyanogenmod was checked out.
Code:
nemiver --remote=<STREAK7-IP>:5039 --gdb-binary=$ANDROID/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gdb --solib-prefix=$ANDROID/android/system/out/target/product/streak7/symbols/ $ANDROID/android/system/out/target/product/streak7/symbols/init
And in edit-preferences for sources I added some paths like symbols/, symbols/system/lib and the android/system directory.
There's also a statically compiled gdb that you can use over ssh or so: http://dan.drown.org/android/howto/gdb.html
Obsolete first look into the CyanogenMod adb bug:
I think the problem is in line 1068 in init.c
Code:
if (!action_queue_empty() || cur_action)
timeout = 0;
each time I looked when it comes there the cur_action->name was "property:sys.usb.config=none".
Maybe it is connected with the adb issue. When I googled for the
Code:
E/UsbDebuggingManager( 367): Communication error:
E/UsbDebuggingManager( 367): java.io.IOException: No such file or directory
E/UsbDebuggingManager( 367): at android.net.LocalSocketImpl.connectLocal(Native Method)
E/UsbDebuggingManager( 367): at android.net.LocalSocketImpl.connect(LocalSocketImpl.java:238)
E/UsbDebuggingManager( 367): at android.net.LocalSocket.connect(LocalSocket.java:108)
E/UsbDebuggingManager( 367): at com.android.server.usb.UsbDebuggingManager.listenToSocket(UsbDebuggingManager.java:79)
E/UsbDebuggingManager( 367): at com.android.server.usb.UsbDebuggingManager.run(UsbDebuggingManager.java:115)
E/UsbDebuggingManager( 367): at java.lang.Thread.run(Thread.java:856)
issue I found surprisingly many people having issues with this, but few answers.
But I also found e.g. this: https://gist.github.com/steven676/5...c-remove-obsolete-ro.debuggable-1-trigg.patch
so the problem may be in https://github.com/ChristophHaag/an...lob/master/prebuilts/root/init.streak7.usb.rc
but I didn't have time to really read documentation to that.
I think this file complements $ANDROID/system/core/rootdir/init.usb.rc
I'll either play around with that or I'll add debug output in android.net.LocalSocketImpl.connect(LocalSocketImpl.java:238)
Code:
connectLocal(fd, address.getName(), address.getNamespace().getId());
Then I would at least know what it's trying to do and it would get easier.
Many of the results I saw from googling mentioned that it might have to do with netd.
On the streak 7 I get this:
Code:
cat /dev/socket/netd
cat: can't open '/dev/socket/netd': No such device or address
I'm not sure if this is how it should behave...
An observation is that adbd run from a command line seems to start without an issue and listens on a port specified with
Code:
setprop service.adb.tcp.port 5555
but the access over adb connect <STREAK7-IP> does only say "unauthorized". And "start adbd" does nothing. None of the programs seem to have --help or -h, so I have to look closer into whether they can be started directly.
I'll change "[ro.adb.secure]: [1]" in /default.prop to 0 and see whether that does anything.
In the other thread from giveen I said that I don't see the log spam. This was with debugging in the developer settings disabled. When I enable it, the logspam starts. But whether it is enabled or not, init still eats 100% cpu. The trouble with the debugging is that each time it is enabled and I want to disable it, the streak 7 immediately reboots.
Now that I had logcat via ssh running I caught this when the reboot happened:
Code:
W/dalvikvm( 367): threadid=50: thread exiting with uncaught exception (group=0x40b0e930)
E/AndroidRuntime( 367): *** FATAL EXCEPTION IN SYSTEM PROCESS: UsbDebuggingHandler
E/AndroidRuntime( 367): java.lang.NullPointerException
E/AndroidRuntime( 367): at com.android.server.usb.UsbDebuggingManager.closeSocket(UsbDebuggingManager.java:125)
E/AndroidRuntime( 367): at com.android.server.usb.UsbDebuggingManager.access$200(UsbDebuggingManager.java:46)
E/AndroidRuntime( 367): at com.android.server.usb.UsbDebuggingManager$UsbDebuggingHandler.handleMessage(UsbDebuggingManager.java:177)
E/AndroidRuntime( 367): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 367): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 367): at android.os.HandlerThread.run(HandlerThread.java:60)
Looks bad.
For looking at the android code I just use grep and ls with globbing for the c and config files and for the java part I imported it in eclipse via this method: http://source.android.com/source/using-eclipse.html
This is a build I haven't tested yet: http://w3studi.informatik.uni-stuttgart.de/~haagch/cm-10.1-20130820-UNOFFICIAL-streak7.zip
This is giveen's original nvflash that I am not sure I am allowed to put there as giveen has not put any license information in there: http://w3studi.informatik.uni-stuttgart.de/~haagch/JB_Beta2.1.zip But then it's all apache code and there are no notices in reagards to the apache license or changed files anyway. If not, you can just tell me and I'll remove it.
------------------------------------------------
So the call to connectLocal() that throws the exception has as parameters
fd: FileDescriptor[263]
address namespace: RESERVED with address name space id: 1 and address name: adbd
That doesn't help me much yet, but there are frequent calls with FileDescriptor[263] and namespace RESERVED, id 1, name rild (radio service) that don't throw an exception.
So it's a "valid" file descriptor... But I think the problem is still that adbd is not started by init...
The whole UsbDebuggingManager.run method is
Code:
public void run() {
while (mAdbEnabled) {
try {
listenToSocket();
} catch (Exception e) {
/* Don't loop too fast if adbd dies, before init restarts it */
SystemClock.sleep(1000);
}
}
}
where listeToSocket() is ultimately throwing the exception.
I have also read a bit about how adbd is supposed to work. Apparently in android 4.2.2 they introduced rsa encryption. It looks very similar to ssh. You have your authorized public keys on the device in /data/misc/adb/adb_keys (like ~/ssh/authorized_keys) and on your computer you have your public key in ~/.android/adbkey.pub
So I put my ~/.android/adbkey.pub in /data/misc/adb/adb_keys on the streak 7 and started adbd from the command line on the device. And indeed, when I connect with "adb connect <STREAK7-IP>" I get "<STREAK7-IP>:5555 device product:cm_streak7 model:Streak_7 device:streak7" with "adb devices -l" and adb shell works. It's a bit unrelated, but this applies: https://code.google.com/p/android/issues/detail?id=48126
But the actually important part, the "start adbd" still doesn't do anything.
It really must be somethin with /init.streak7.usb.rc. The stuff in /sys/class/android_usb/android0/ seem to be set all wrong...
------------------------------------------------
I'll just keep posting random things I discover that I find strange or interesting and if anyone knows anything about any of those, they can just chime in.
In /init.streak7.usb.rc there is the line
Code:
write /sys/class/android_usb/android0/iProduct $ro.product.model
"getprop ro.product.model" says "Streak 7" but /sys/class/android_usb/android0/iProduct apparently doesn't seem to be able to take a string with a space because "cat /sys/class/android_usb/android0/iProduct" returns "Streak". You can write directly to it with "cat "Streak 7" > /sys/class/android_usb/android0/iProduct" but it only saves up to the space. I don't think that's really a problem but strange anyway.
I have googled for another tegra 2 device and looked at its usb init rc: https://raw.github.com/CyanogenMod/android_device_samsung_p4-common/ics/init.p3.usb.rc
Adding a section with on property:sys.usb.config=adb did nothing and it seems I haven't been able to google what should be in /sys/class/android_usb/android0/idProduct for the streak 7.
I think I'll just look into how init on android works and how the triggers work. Then it shouldn't be too hard to figure out what exactly it is trying to do and why it is failing.
------------------------------------------------
I was trying to get my head around why "getprop sys.usb.config" would always return "none" and the system wouldn't respond to "setprop sys.usb.config adb,mtp" in any way. So I got to suspect that /init.streak7.usb.rc was not used at all. Then I compared the imports and found that /init.streak7.rc did use a relative path for /init.streak7.usb.rc while all the other init*.rc were using absolute paths.
So I'm not sure if it this is really the thing that fixed it, but it's the latest thing I tested and now init's 100% cpu and adb are fixed: https://github.com/ChristophHaag/an...mmit/eee0625e11cfafd510c3bada6ae67a133766c0f4
Edit: Wait, it happened again. Maybe not. :/
Hm, no, definitely not it. Can't even reproduce it. It worked after adb sideload and wiping the cache and the dalvik cache.
At least it's clear now that init's 100% cpu usage and adb not working and the dalvik crash when disabling debugging are all the same issue.

Good luck. I'll give you a hint as a parting gift. The USB issue is not kernel related.
I really dont care to licenses anything so you are free to do with as you will. Personally, I will continue to develop in private and if there are kernel changes, as per the GPL, I will make those updates available.

[moved to hidden section in first post]

[moved to hidden section in first post]

[moved to hidden section in first post]

If you really want to help, let me know. I'll let you in on my secret.

giveen said:
If you really want to help, let me know. I'll let you in on my secret.
Click to expand...
Click to collapse
Do I want to help? Does this thread look like I don't?
As I've said I'm new to the android code so I'm not really sure what I'm doing yet.
After rebooting with debugging enabled and adb sideloading an image it works for some reason (until you disable debugging in the developer settings, then it loops on sys.usb.config=none again) but it's all clearly not like intended by /init.streak7.usb.rc. /sys/class/android_usb/android0/idVendor is 18d1 and android_usb/android0/idProduct is d002 which is set in init.usb.rc for on property:sys.usb.config=adb...? I just don't get it yet. The init readme says declaring an action or service twice is an error but this is from upstream, so adb is supposed to always be 18d1:d002?
So if you know something I don't I would obviously greatly appreciate it if you told us. In fact you can directly push to the repository now if you wish to do so.

ccxxx said:
Do I want to help? Does this thread look like I don't?
As I've said I'm new to the android code so I'm not really sure what I'm doing yet.
After rebooting with debugging enabled and adb sideloading an image it works for some reason (until you disable debugging in the developer settings, then it loops on sys.usb.config=none again) but it's all clearly not like intended by /init.streak7.usb.rc. /sys/class/android_usb/android0/idVendor is 18d1 and android_usb/android0/idProduct is d002 which is set in init.usb.rc for on property:sys.usb.config=adb...? I just don't get it yet. The init readme says declaring an action or service twice is an error but this is from upstream, so adb is supposed to always be 18d1:d002?
So if you know something I don't I would obviously greatly appreciate it if you told us. In fact you can directly push to the repository now if you wish to do so.
Click to expand...
Click to collapse
The problem is CM.
I switched to AOKP which is close to Google's AOSP, and the problem solved itself. Something in the way USBManager is programmed in CM screwed things.

I got around to download aokp today.
The build system is slightly different, but easy enough to set up. I first just did an "update" to it, but the adb/init problem persisted, acore kept crashing (but deleting data for the contacts app "solved" that).
So I decided to finally make a factory reset. Not really sure what happens there, but that didn't delete the apps in /system/apps I think so I just wiped everything except sdcard etc. with twrp and installed the image again. This time it works better it seems. adb seems ok for now, cpu usage is okay.
The 4.2.2. google apps for that are these: http://goo.im/gapps/gapps-jb-20130812-signed.zip
Now I'm not sure: Would a factory reset/complete reinstall have helped with cyanogenmod too?
aokp is missing a few features cyanogenmod has, most notably the performance settings where you can overclock and set up zram with the gui.
Keyboard still crashes. Not really surprising that illegal instruction hasn't changed.
There doesn't seem to be recent apps when long pressing the home button. Strange.
Not sure how much I like it yet and whether I'd rather use cyanogenmod.
Here it is: http://w3studi.informatik.uni-stuttgart.de/~haagch/aokp_streak7_unofficial_2013-08-23.zip
Thanks, giveen.

No problem. AOSP keyboard burns RAM like nothing else. If you switch to an 3rd party keyboard , you will no longer crash. This problem is common on a lot of low memory devices. ZRAM doesn't really work. I have a script that I want to test out that DJ_Steve had originally wrote. Also, I will send you the sensor files you need to modify to get them to work.

google has this keyboard in the play store https://play.google.com/store/apps/details?id=com.google.android.inputmethod.latin and I got it from http://dl.androidnext.de/com.google.android.inputmethod.latin.apk. Works ok, but has issues like you can't disable the "ducking" blocking of "offensive" words...
The sensors changes you commited work well. Rotation/acceleration/magnet/light seem to react normally.
It's almost usable now.
For people building it from source: If you get a weird error like "ERROR: couldn't find <type 'property'> in build.prop" and can't find anything useful with google... I deleted out/* and did a complete rebuild and then it worked.
Plugging in a headset still doesn't turn off speakers but it seems only like a minor issue since it seems to be detected just fine:
Code:
V/WiredAccessoryManager( 374): Headset UEVENT: {SUBSYSTEM=switch, SWITCH_STATE=1, DEVPATH=/devices/virtual/switch/h2w, SEQNUM=2006, ACTION=change, SWITCH_NAME=h2w}
V/WiredAccessoryManager( 374): newName=h2w newState=1 headsetState=1 prev headsetState=0
W/AudioPolicyManagerBase( 103): checkOutputsForDevice(): No output available for device 0004
V/WiredAccessoryManager( 374): device h2w connected
Google tts is crashing like the keyboard (
Code:
F/libc ( 6525): Fatal signal 4 (SIGILL) at 0x5dc80738 (code=1), thread 6525 (gle.android.tts)
) but pico tts seems to work, at least with english.
A Google search gave me this:
http://stackoverflow.com/questions/7102606/sigill-in-android-ndk-code/7104177#7104177
And further this might be worth looking into: http://forum.xda-developers.com/showthread.php?t=2186251
Not sure whether it's simply neon instructions or register usage of 16+ since I haven't looked that close into the build system yet. But probably ILL_ILLOPC means it's a neon instruction.

So sensors work now? I've been at that for months and I wasn't sure if I got it right. If I got it right, that was months of work there that I wasn't even sure was going to work.
Headphones and microphones need to be adjusted in mixer_paths.xml

Months of untested work that just works? Impossible! :good:
I haven't done a really thorough test, but they all seem to be doing something. https://play.google.com/store/apps/details?id=imoblife.androidsensorbox seems to have a little problem with the directions with the rotated screen though. But in general it all does something that seems related to what I do to the device.

The AKM8973. is a chip that is normally found on qualcomm devices. So I had to track down the right HAL and then modify to work with Tegra sword ices. It's a terrible hack/slash, modify and pray it works job. I had Just finished. Does the screen rotate?

giveen said:
The AKM8973. is a chip that is normally found on qualcomm devices. So I had to track down the right HAL and then modify to work with Tegra sword ices. It's a terrible hack/slash, modify and pray it works job. I had Just finished. Does the screen rotate?
Click to expand...
Click to collapse
Yes, the screen rotates. And even more impressively, it rotates correctly!

Good. Now i can focus my energy on the camera.

Hm, having difficulty with my compiles booting. Chris, if you compile and upload the zip, I can give you my goo.im information and you can push it as an auto-update. Don't forget to include your name in there somewhere for credit as well as you are now part of the team.

giveen said:
Hm, having difficulty with my compiles booting. Chris, if you compile and upload the zip, I can give you my goo.im information and you can push it as an auto-update.
Click to expand...
Click to collapse
I have edited my first post.
http://w3studi.informatik.uni-stuttgart.de/~haagch/aokp_streak7_unofficial_2013-08-25.zip
http://w3studi.informatik.uni-stuttgart.de/~haagch/aokp_streak7-ota-eng.c-builder.zip
giveen said:
Don't forget to include your name in there somewhere for credit as well as you are now part of the team.
Click to expand...
Click to collapse
Yea, maybe if I contribute something substantial instead of cosmetic changes.

OH yeah, bluetooth keyboard, I see that as one of your issues. I'll upload a bunch of idc files that should at least address that issue, not sure though.

Are you missing any commits? I noticed your update has sensor working but my build does not.

NFC Firmware for HTC Desire C ROMs with NFC Enabled

Hi everybody !
In the attachment you will find nfc.golfu.so which is the firmware for HTC Desire C with NFC (phone model PL01110). I get it from RUU_GOLF_U_ICS_40A_H3G_UK_1.45.771.3_Radio_10.11.98.09H_1.06.98.13M2_release_266089_signed.exe that you can find on the net.
I upload firmware here because I have spend 3 weeks to get it working with [STABLE][ROM][4.1.2][JZO54K] CyanogenMod10 | BUILD #3.
On this rom, we see the NFC option but it can not enable it and we get the error hw_get_module() failed with logcat and the option stick unchecked.
With the attachement to this post, NFC is working (at least with JZO54K CM10 build#3), see logcat :
I/NfcService( 477): Enabling NFC
D/NFCJNI ( 477): Start Initialization
I/dalvikvm( 315): Jit: resizing JitTable from 4096 to 8192
D/NFCJNI ( 477): NFC capabilities: HAL = 8150100, FW = a76d0c, HW = 620003, Model = 10, HCI = 1, Full_FW = 109, Rev = 12, FW Update Info = 0
D/NFCJNI ( 477): phLibNfc_SE_GetSecureElementList()
D/NFCJNI ( 477):
D/NFCJNI ( 477): > Number of Secure Element(s) : 1
D/NFCJNI ( 477): phLibNfc_SE_GetSecureElementList(): SMX detected, handle=0xabcdef
D/NFCJNI ( 477): phLibNfc_SE_SetMode() returned 0x000d[NFCSTATUS_PENDING]
I/NFCJNI ( 477): NFC Initialized​
So what to do do with this nfc.golfu.so ?
Uncompress file nfc.golfu.zip and you will get nfc.golfu.so
Put the file (nfc.golfu.so) on /system/lib/hw/ on your phone.
chmod 644 /system/lib/hw/nfc.golfu.so
Then reboot your phone and now, you can check NFC option and you can use it (at least with phone having NFC AND rom having NFC enabled)

roms2000 said:
So what to do do with this nfc.golfu.so ?
Uncompress file nfc.golfu.zip and you will get nfc.golfu.so
Put the file (nfc.golfu.so) on /system/lib/hw/ on your phone.
chmod 644 /system/lib/hw/nfc.golfu.so
Then reboot your phone and now, you can check NFC option and you can use it (at least with phone having NFC AND rom having NFC enabled)
Click to expand...
Click to collapse
And the phone is not working, now. I tried to reboot, it's never completing the bootstrap. I can use the recovery console, I tried to fix permissions but it's always the same. How can I remove that file from recovery console?

fankool said:
And the phone is not working, now. I tried to reboot, it's never completing the bootstrap. I can use the recovery console, I tried to fix permissions but it's always the same. How can I remove that file from recovery console?
Click to expand...
Click to collapse
It doesn't work for me
Bootstrap? Is that stuck on boot animation?
If so:
You can reflash the current rom. That removes all the installed mods but not the apps or any sdcard data.
/*Worked for me, maybe not for you...*\

julian6457 said:
It doesn't work for me
Bootstrap? Is that stuck on boot animation?
If so:
You can reflash the current rom. That removes all the installed mods but not the apps or any sdcard data.
/*Worked for me, maybe not for you...*\
Click to expand...
Click to collapse
Yes, there's always the boot animation. But If I reflash the current rom I'll loose the data saved on phone and I have to reinstall the applications.

fankool said:
Yes, there's always the boot animation. But If I reflash the current rom I'll loose the data saved on phone and I have to reinstall the applications.
Click to expand...
Click to collapse
As I know flashing a new rom witout a /system wipe will not delete the applications.
You can also remove the micro SD (If you have one) there are multiple ways to cpoy the files to a pc from like micro>usb
Flasing roms only disable xposed modules and reinstall the stock apps.
Maybe a backup will come in handy the next time

julian6457 said:
As I know flashing a new rom witout a /system wipe will not delete the applications.
You can also remove the micro SD (If you have one) there are multiple ways to cpoy the files to a pc from like micro>usb
Flasing roms only disable xposed modules and reinstall the stock apps.
Maybe a backup will come in handy the next time
Click to expand...
Click to collapse
My recovery is not finishing backup for 4 months. Before it works perfectly.. so, I have only old bakcup (fbefore the last rom flashing).
I tried by adb to remove nfc.golfu.so from /system/lib/hw/ but the phone still stucks on boot, so I'll not try to copy file by memory card (it will not be useful).
I reflashed the rom without erasing anything and the phone was rebirth. Thank you!
A strange fast blinking on the screen is annoying me now, why? It's like the old crt monitor using 60Hz frequency. I restarted the phone but it's still blinking, from the white screen after switch on. Can anyone help me to understand what's happening?
---------- Post added at 11:31 AM ---------- Previous post was at 11:25 AM ----------
fankool said:
A strange fast blinking on the screen is annoying me now, why? It's like the old crt monitor using 60Hz frequency. I restarted the phone but it's still blinking, from the white screen after switch on. Can anyone help me to understand what's happening?
Click to expand...
Click to collapse
Replying to myself: I only disabled "developer options" (my phone is in italian language, I suppose this is the translation), restarted the phone and removed the battery and now works perfectly. But still I don't know why it was blinking.

Well roms2000,
thank you for your job (even if it's not working on my phone) if you are interested now I can continue the tests on my mobile phone to use NFC, I know how to quickly recover my phone (I also updated my cwm and now the backup works perfectly).
I'm wondering why it stucks (I disabled boot animation at start so I can't say exactly when it freezes) and what is the logfile I can read to understand what's happening (obviously my phone has NFC, is the O2 version).
I'm using NOPE kernel v2.6 850MHz (but at 800MHz) on miniCM v6 (a derivation of cm10). I just followed the instruction, I copied nfc.golfu.so in /system/lib/hw using x-plore and with the same application I changed the attributes to 644 (maybe, but it's difficult, I could set a wrong attributes, but in this case I think android simply ignores the library).
Also removing the file (by adb from recovery) the phone always stucks.

Sorry for long response, I did not check this post, so i couldn't received notifications.
@fankool : do you have the NFC version of HTC Desire C ? If not, you can't enable NFC, and the file won't do anything for you.
For NFC, I have simply take the module on the official rom to get it working, if your rom is base on android 4.1.2, it should work. Try to use logcat to see some message about error and NFC.
--- Edit :
I don't think MiniCM has NFC soft enabled : check on your phone : Settings / Wireless & Network (More...) / NFC
If you have a check box for NFC, rom embed NFC soft, else, it is not and I don't think firmware / module will do anything.

my desire c has NFC (it's an O2 desire c, and with stock rom and the revolution 4.0.4 it worked), but the option to enable NFC disappeared, also trying with prometheus or nope. I installed many different roms based on 4.1.1 (cm, minicm, miui..) but always NFC was not working. How can I use logcat?

Can you try this rom : JZO54K CM10 build#3, like I did ?
For logcat, it will not be useful if you do not have the option to enable NFC.

htc desire c nfc
roms2000 said:
Hi everybody !
In the attachment you will find nfc.golfu.so which is the firmware for HTC Desire C with NFC (phone model PL01110). I get it from RUU_GOLF_U_ICS_40A_H3G_UK_1.45.771.3_Radio_10.11.98.09H_1.06.98.13M2_release_266089_signed.exe that you can find on the net.
I upload firmware here because I have spend 3 weeks to get it working with [STABLE][ROM][4.1.2][JZO54K] CyanogenMod10 | BUILD #3.
On this rom, we see the NFC option but it can not enable it and we get the error hw_get_module() failed with logcat and the option stick unchecked.
With the attachement to this post, NFC is working (at least with JZO54K CM10 build#3), see logcat :
I/NfcService( 477): Enabling NFC
D/NFCJNI ( 477): Start Initialization
I/dalvikvm( 315): Jit: resizing JitTable from 4096 to 8192
D/NFCJNI ( 477): NFC capabilities: HAL = 8150100, FW = a76d0c, HW = 620003, Model = 10, HCI = 1, Full_FW = 109, Rev = 12, FW Update Info = 0
D/NFCJNI ( 477): phLibNfc_SE_GetSecureElementList()
D/NFCJNI ( 477):
D/NFCJNI ( 477): > Number of Secure Element(s) : 1
D/NFCJNI ( 477): phLibNfc_SE_GetSecureElementList(): SMX detected, handle=0xabcdef
D/NFCJNI ( 477): phLibNfc_SE_SetMode() returned 0x000d[NFCSTATUS_PENDING]
I/NFCJNI ( 477): NFC Initialized​
So what to do do with this nfc.golfu.so ?
Uncompress file nfc.golfu.zip and you will get nfc.golfu.so
Put the file (nfc.golfu.so) on /system/lib/hw/ on your phone.
chmod 644 /system/lib/hw/nfc.golfu.so
Then reboot your phone and now, you can check NFC option and you can use it (at least with phone having NFC AND rom having NFC enabled)
Click to expand...
Click to collapse
can i flash this zip file with stock rom

Stock rom should have it.
If you flash with stock I don't know if it will enable NFC.

roms2000 said:
Stock rom should have it.
If you flash with stock I don't know if it will enable NFC.
Click to expand...
Click to collapse
Well, this firmware enabled NFC on Cyanogenmod 11 - confirmed working by one of users, so thanks for this.

I've flashed Stock ROM and deodexed ROM, neither had NFC working (although it's meant to be) so it could be in boot if it works or not as my handset is 100% known to have NFC but my Bootloader is 1.31 and not 1.28
Sent from my B1-730HD using XDA Free mobile app