[Kernel][AOSP][2.6.35.9][UV][OC] PureGinger Kernel 25-DEC-2010 - Nexus One Android Development

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?

Related

HTC Desire Wi-Fi Problem

Had a wi-fi problem on my htc desire for a while now..
One time I went to turn wi-fi on and it just said "Unable to start wi-fi". It had worked totally fine up until that point.
I've tried doing a factory reset, rooted, updated rom but it's still not working.
When the problem happened I had not rooted the phone or changed anything really.. it just happened.
In logcat it says:
flg=0x10200000 cmp=com.android.settings/.wifi.WifiSettings bnds=[124,404][236,531] }
D/SettingsWifiEnabler( 548): Received wifi state changed from Enabling to Unknown
W/SyncAllWidget( 151): activeSynch is null false
I/ActivityManager( 79): Displayed activity com.android.settings/.wifi.WifiSettings: 495 ms (total 495 ms)
I/WifiHW ( 79): wifi_load_driver enter
D/SettingsWifiEnabler( 548): Received wifi state changed from Unknown to Enabling
D/dalvikvm( 1805): GC freed 3806 objects / 257536 bytes in 97ms
D/NetworkLocationProvider( 79): onCellLocationChanged [1363,22890]
I/WifiHW ( 79): wifi_load_driver end error 2
E/WifiService( 79): Failed to load Wi-Fi driver.
D/SettingsWifiEnabler( 548): Received wifi state changed from Enabling to Unknown
Anyone got any ideas on how to fix this?
h2o pete said:
Had a wi-fi problem on my htc desire for a while now..
One time I went to turn wi-fi on and it just said "Unable to start wi-fi". It had worked totally fine up until that point.
I've tried doing a factory reset, rooted, updated rom but it's still not working.
When the problem happened I had not rooted the phone or changed anything really.. it just happened.
In logcat it says:
flg=0x10200000 cmp=com.android.settings/.wifi.WifiSettings bnds=[124,404][236,531] }
D/SettingsWifiEnabler( 548): Received wifi state changed from Enabling to Unknown
W/SyncAllWidget( 151): activeSynch is null false
I/ActivityManager( 79): Displayed activity com.android.settings/.wifi.WifiSettings: 495 ms (total 495 ms)
I/WifiHW ( 79): wifi_load_driver enter
D/SettingsWifiEnabler( 548): Received wifi state changed from Unknown to Enabling
D/dalvikvm( 1805): GC freed 3806 objects / 257536 bytes in 97ms
D/NetworkLocationProvider( 79): onCellLocationChanged [1363,22890]
I/WifiHW ( 79): wifi_load_driver end error 2
E/WifiService( 79): Failed to load Wi-Fi driver.
D/SettingsWifiEnabler( 548): Received wifi state changed from Enabling to Unknown
Anyone got any ideas on how to fix this?
Click to expand...
Click to collapse
I have the same problem on a ROM i have made... That's just for Tattoo not Desire... But it's the same logcat... So can somebody help us??
Yeah I'm pretty stuck on what to do :/.
Added some information about my software to the first post.
i have same problem on my htc dream
BUMP...
-------------------------------------
Sent from my übercharged HTC Tattoo
Fixed it by setting a static IP address.
Wi-Fi > Menu Button > Advanced > Use static IP
i had yesterday the same problem on my desire,
i fixxed this with flash a "older" stock rom and update it with the build-in updater....
same problem with my desire. how to fix it?
It's broke again. Setting a static IP doesn't fix it any more. Any ideas?
got the same problem here
can any one help???
Bump
Sent from my HTC Desire using XDA App
seems like wlan.ko is not available in /system/lib/modules/
I've had similar problems in the past, but was unable to solve them. You can check several things though.
1) wlan.ko in /system/lib.modules <-- has to match up with the kernel that you are using
2) any entries for wifi and/or dhcp in the init.rc and init.devicenamehere.rc files that are in the ramdisk in the boot.img
3) wifi settings in the build.prop
4) files in /system/etc/wifi
5) I'm not sure about this one, but even some of the files in /system/etc/firmware might have something to do with wifi.
6) files in /system/etc/dhcpd
7) any files in /system/bin and/or /system/xbin that are called by *.rc from #2.
Just take a working ROM (stock is usually what I use), and compare the files with the corresponding files in your build. I use either WinMerge or N-way Folder Compare or just plain old 'diff' in Linux.
I had the same issue.
Flashed a new ROM with full wipe etc. Wifi OK.
Flashed a kernel update on top of the ROM. Wifi broken. Turning wifi on it would error and turn off again.
The only way I could fix it was to flash a full ROM and make sure I wiped everything from the recovery.
Any more info you can provide? Current ROM +version +any other mods applied like status bar or OC kernels?
Did anyone fix this?? I am stuck here, G1 Dream
CM 5.0.8 DS
Please help!!!
Are you getting the same error in logcat as others have? If so, I think .mak fixed it, but he never let us know how.
Same Issues...
Ive tried Reverting to CM 5.07, 5.07 and now the beta 6.0 and all have yet to fix the wifi issue. I also tried switching between the radio's and doing a full format/partition and wipe. Any fix to this yet?
That was Lovely Bro...Really Useful...I got my DESIRE today and could connect to WIFI but was unable to browse...This tip helped me...Thx a lot... Keep up the good work..
Trying to replace bcm4329.ko
I did the OTA update for my Desire today, and of course have the wi-fi problem.
However, when I enable wi-fi, I see the following appear at the end of dmesg:
Code:
<3>[ 8197.511535] bcm4329: version magic '2.6.32.15-g6a358a9 preempt mod_unload
ARMv7 ' should be '2.6.32.15-gf9c0527 preempt mod_unload ARMv7 '
The update zip (via thread 778852) contains a bsdiff patch file patch/system/lib/modules/bcm4329.ko.p... and from some examination of that file it appears just to patch the vermagic field of the .ko file.
I tried to use a hex editor to 'fix' bcm4329 and used adb pull/push to replace it, but I get
Code:
failed to copy 'bcm4329.ko.fix' to '/system/lib/modules/bcm4329.ko': Read-only
file system
Can anyone help me with this?
Update: I am a fool. I was using the wrong goldcard! Once I put the right goldcard in, then sdcard:update.zip applied correctly and wi-fi started working again.
@dleonard, could you please make step by step instructions of how to fix this wifi issue?
thanks
Mixu

[Guide] How to provide a LOGCAT

Here's how to use logcat..There are two main ways to do a logcat, within android, and through adb. Logcat within android can be done one of two ways, through a Logcat app..Here are two good examples are either aLogcat or CatLog I prefer catlog, because in my opinion it has a little bit nicer UI. Both of these programs can dump their logs to a txt file, which is very useful for debugging. Or, you can do it in terminal emulator (same rules as running through adb.
On the other hand, using adb to run logcat, in my opinion is much more useful, because you can start using it when android boots (i.e. once the boot animation appears.)
The code for logcat to output to a file is
Code:
adb logcat > name of problem.txt
you can also do
Code:
adb logcat -f name of problem.txt
how I prefer to do it is this way:
Code:
adb logcat -v long > name of problem.txt
with the -v flag & the long argument, it changes output to long style, which means every line of logcat will be on its own line (makes it a little neater, imo)
Note: When outputting to a file, you will see a newline, but nothing printed, this is normal. To stop logcat from writting to a file, you need to press ctrl+c.
Here's where using logcat (via adb makes life really easy)
Lets say you find a problem you're having after looking at a logcat.
For example:
When I was trying to use a different ramdisk, wifi wouldn't work so I got a logcat that's almost 1300 lines long (a lot of stuff happens in the background)
So if you are searching for an error in the logcat file (it's always e/ for error, f/ for fatal. Those are the two main things that will break a system.)
Code:
D/dalvikvm( 871): GC_CONCURRENT freed 472K, 6% free 10224K/10823K, paused 1ms+6ms
V/AmazonAppstore.DiskInspectorServiceImpl( 871): Available blocks: 21981, Block size: 4096, Free: 90034176, Threshold: 5242880, withinThreshold? true
D/AmazonAppstore.UpdateService( 871): Received action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
W/AmazonAppstore.UpdateService( 871): Confused about why I'm running with this intent action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
D/dalvikvm( 890): GC_CONCURRENT freed 175K, 4% free 9375K/9671K, paused 2ms+3ms
V/AmazonAppstore.ReferenceCounter( 871): Reference (MASLoggerDB) count has gone to 0. Closing referenced object.
E/WifiStateMachine( 203): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
V/AmazonAppstore.UpdateService( 871): runUpdateCommand doInBackground started.
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateCommand( 871): Not updating key: digitalLocker from: 1334228488057
V/AmazonAppstore.UpdateService( 871): Finished UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: serviceConfig
V/AmazonAppstore.MASLoggerDB( 871): performLogMetric: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
V/AmazonAppstore.MASLoggerDB( 871): onBackgroundTaskSucceeded: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
W/CommandListener( 118): Failed to retrieve HW addr for eth0 (No such device)
D/CommandListener( 118): Setting iface cfg
D/NetworkManagementService( 203): rsp
D/NetworkManagementService( 203): flags
E/WifiStateMachine( 203): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg eth0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
W/PackageParser( 203): Unknown element under : supports-screen at /mnt/asec/com.android.aldiko-1/pkg.apk Binary XML file line #16
D/wpa_supplicant( 930): wpa_supplicant v0.8.x
D/wpa_supplicant( 930): random: Trying to read entropy from /dev/random
D/wpa_supplicant( 930): Initializing interface 'eth0' conf '/data/misc/wifi/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
D/wpa_supplicant( 930): Configuration file '/data/misc/wifi/wpa_supplicant.conf' -> '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): Reading configuration file '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): ctrl_interface='eth0'
D/wpa_supplicant( 930): update_config=1
D/wpa_supplicant( 930): Line: 4 - start of a new network block
D/wpa_supplicant( 930): key_mgmt: 0x4
(mind you, that's 29 lines out of 1300ish, just for example)
I then could do the following with logcat:
Code:
adb logcat WifiStateMachine:E *:S -v long > name of problem.txt
and this will only print out any errors associated with WifiStateMachine, and anything which is fatal, which makes it about a million times easier to figure out what's going on!
In WifiStateMachine:E, the :E = to look for Errors, the full list of options is as follows:
V — Verbose (lowest priority)
D — Debug
I — Info (default priority)
W — Warning
E — Error
F — Fatal
S — Silent (highest priority, on which nothing is ever printed)
You can replace the :E with any other letter from above to get more info.
In order to filter out anything other than what you are looking for (in this case, WifiStateMachine) you must put a *:S after your last command (i.e. WifiStateMachine:E ThemeChoose:V ... ... AndroidRuntime:E *:S)
Sources: http://developer.android.com/tools/help/logcat.html
http://developer.android.com/tools/help/adb.html
Please do NOTE: : I am just sharing. Original post is Here.
Don't be a noob. Be a newbie..!!
Details here.
Great guide! I am glad that I can help you by logcat. Thanks.
Sent from my E10i using xda app-developers app
How long take the. Logcat?
Sent from my E10i using xda premium
ruben21 said:
How long take the. Logcat?
Sent from my E10i using xda premium
Click to expand...
Click to collapse
Whatever you want.
Sent from my E10i using xda app-developers app
Well and how I finish the logcat because I leave them all the night and still run
Sent from my E10i using xda premium
ruben21 said:
Well and how I finish the logcat because I leave them all the night and still run
Sent from my E10i using xda premium
Click to expand...
Click to collapse
Just press CTRL + C
Thanks bro.
☜ Sent from my X10 MP U20i ☞

[DEVS]Lets fix cm9!

All dev related posts for fixing cm9 will come here.
All ideas are welcome but dont post for eta and stuff like that..
Currently fixing: Bluetooth
ToDo:
Camera
Internal memory
Graphic flickering
Audio(partially working)
Anything else?
Fixed:Wifi
My device tree: https://github.com/hell-lock-xda/android_device_htc_protou
If you manage to fix anything then send me a pull request.
prototype-U said:
All dev related posts for fixing cm9 will come here.
All ideas are welcome but dont post for eta and stuff like that..
Currently fixing: WiFi
ToDo: Bluetooth
Camera
Internal memory
Graphic flickering
Audio(partially working)
Anything else?
My device tree: https://github.com/hell-lock-xda/android_device_htc_protou
If you manage to fix anything then send me a pull request.
Click to expand...
Click to collapse
Fixed:
Camera atis 112 fixed it (if permissions were granted )
Internal Memory ( same as above )
I'll try ti fix graphical glitches
And wait have you tried using stuff from lliors device trees/ github?
The Android Manual said:
Fixed:
Camera atis 112 fixed it (if permissions were granted )
Internal Memory ( same as above )
I'll try ti fix graphical glitches
And wait have you tried using stuff from lliors device trees/ github?
Click to expand...
Click to collapse
Where is the fix??
BTW @all the above device tree is not working properly.. pls dont compile it.. I will soon make a working device tree
prototype-U said:
Where is the fix??
BTW @all the above device tree is not working properly.. pls dont compile it.. I will soon make a working device tree
Click to expand...
Click to collapse
In atis112's guthub his cm9 build has a functioning camera and internal memory
The Android Manual said:
In atis112's guthub his cm9 build has a functioning camera and internal memory
Click to expand...
Click to collapse
I have his tree forked and camera is nt working.. dunno abt internal
Good news and bad news for ya all!
Bad news:Wifi is still not working properly
Good news:WiFi drivers are loading properly! But its showing probs with supplicant. I was able to replicate such problems on stock rom too so we are pretty close to fixing it!
Code:
23:26:55.120 Error WifiHW 294 Supplicant not running, cannot connect
23:26:44.093 Info logwrapper 4398 /system/bin/wpa_supplicant terminated by exit(255)
23:26:44.093 Error wpa_supplicant 4401 wlan0: Unsupported driver 'nl80211'
23:26:39.065 Error WifiStateMachine 294 Failed to setup control channel, restart supplicant
23:26:24.107 Error wpa_supplicant 3977 wlan0: Unsupported driver 'nl80211'
23:26:24.107 Info logwrapper 3974 /system/bin/wpa_supplicant terminated by exit(255)
Adding the commit to github and will work on that driver..
prototype-U said:
Good news and bad news for ya all!
Bad news:Wifi is still not working properly
Good news:WiFi drivers are loading properly! But its showing probs with supplicant. I was able to replicate such problems on stock rom too so we are pretty close to fixing it!
Code:
23:26:55.120 Error WifiHW 294 Supplicant not running, cannot connect
23:26:44.093 Info logwrapper 4398 /system/bin/wpa_supplicant terminated by exit(255)
23:26:44.093 Error wpa_supplicant 4401 wlan0: Unsupported driver 'nl80211'
23:26:39.065 Error WifiStateMachine 294 Failed to setup control channel, restart supplicant
23:26:24.107 Error wpa_supplicant 3977 wlan0: Unsupported driver 'nl80211'
23:26:24.107 Info logwrapper 3974 /system/bin/wpa_supplicant terminated by exit(255)
Adding the commit to github and will work on that driver..
Click to expand...
Click to collapse
can you upload the built you made??
mhb92 said:
can you upload the built you made??
Click to expand...
Click to collapse
I hate posting here, but if you want the build, check out the sources.
Sent from my awesome, stock, Nexus7!
i will be able to check source from my main pc next week..thats why i want the built rom...i wanna check something about supplicant file
mhb92 said:
i will be able to check source from my main pc next week..thats why i want the built rom...i wanna check something about supplicant file
Click to expand...
Click to collapse
I will upload it in few hrs from now..
new build is compiling
Ok..! Waiting for link
Sent from my HTC Desire X using xda app-developers app
So guys here is the latest build. Sorry I cant put it on d-h.st cuz my connection is slow and I will prefer github until we fix all the bugs.
https://github.com/hell-lock-xda/cm9-packages
Just click on zip.
And the kernel is here..
http://d-h.st/zSS
prototype-U said:
So guys here is the latest build. Sorry I cant put it on d-h.st cuz my connection is slow and I will prefer github until we fix all the bugs.
https://github.com/hell-lock-xda/cm9-packages
Just click on zip.
And the kernel is here..
http://d-h.st/zSS
Click to expand...
Click to collapse
https://raw.github.com/hell-lock-xda/cm9-packages/master/cm-9-20130505-UNOFFICIAL-protou.zip
Error: blob is too big
BTW:
init.rc, that loads the wpa_supplicant service, also specifies nl80211.
WiFi almost fixed. It gets turned on but still few errors left to fix(scanning and stuff not working till now).
Code:
18:47:17.788 Info wpa_supplicant 2988 rfkill: Cannot open RFKILL control device
18:47:17.898 Info wpa_supplicant 2988 WPS: Converting push_button to virtual_push_button for WPS 2.0 compliance
18:47:18.007 Error WifiConfigStore 298 Error parsing configurationjava.io.FileNotFoundException: /data/misc/wifi/ipconfig.txt: open failed: ENOENT (No such file or directory)
18:47:18.007 Error wpa_supplicant 2988 wpa_driver_nl80211_driver_cmd: failed to issue private commands
18:47:18.007 Error WifiStateMachine 298 Failed to set country code in
18:47:18.007 Error wpa_supplicant 2988 wpa_driver_nl80211_driver_cmd: failed to issue private commands
18:47:18.007 Info wpa_supplicant 2988 wlan0: CTRL-EVENT-DRIVER-STATE HANGED
18:47:18.007 Error WifiStateMachine 298 Failed to set frequency band 0
18:47:18.007 Debug CommandListener 137 Clearing all IP addresses on wlan0
18:47:18.007 Info wpa_supplicant 2988 wlan0: CTRL-EVENT-TERMINATING
18:47:18.224 Debug SoftapController 137 Softap fwReload - Ok
18:47:18.224 Debug CommandListener 137 Setting iface cfg
18:47:18.224 Debug CommandListener 137 Trying to bring down wlan0
When I press on "ON", it turns on and then off... this keeps on happening.. so we did something productive today
Wifi fixed!!!!!!!!!!yeyeyeyeyey!!
YEAAAHHHH!
prototype-U said:
Wifi fixed!!!!!!!!!!yeyeyeyeyey!!
Click to expand...
Click to collapse
I love you lol Lets apply it on PA! What do you say?
The Android Manual said:
I love you lol Lets apply it on PA! What do you say?
Click to expand...
Click to collapse
tomorrow :highfive:
prototype-U said:
tomorrow :highfive:
Click to expand...
Click to collapse
Copy That :highfive:
so is wifi fully working now???
mhb92 said:
so is wifi fully working now???
Click to expand...
Click to collapse
Yes

SUPERNEXUS 2.0 Build 4 : Wifi Tethering, may be the workaround found...

Dear all,
I wish share my experience, with Supernexus 2.0 Build 4.0 on my gs3, more especially with the wifi tethering.
Like most of people, i encountered the issue with the last version where wifi tether did not work, although in the release note, it is indicated as fixed.
So, like others guys, second device was properly connected to the wifi hotspot (it had an IP adress).
Ping to gateway OK... For me, all should be ok to provide internet to second device, but never.... :crying:
I decided, after many tests, wipes, re-install, to check logfile with logcat tools, and i found this :
05-06 08:29:14.255 D/Tethering(2264): notifying tethered with iface =null
...
...
05-06 08:29:20.775 D/libgps (2264): agps_ril_update_network_state: Waiting for IPC connection - timeout
05-06 08:29:20.775 E/libgps (2264): GpsiClient: Can't write to closed pipe
05-06 08:29:20.775 E/libgps (2264): IPC Communication Error, /tmp/11980989/proprietary/deliverables/android/gps_interface/../gps_interface/gpsi_client/GpsiClient.cpp:1143 agps_ril_update_network_state
05-06 08:29:20.775 D/libgps (2264): proxy_agps_ril_update_network_state: called
05-06 08:29:20.775 D/libgps (2264): agps_ril_update_network_availability: Waiting for IPC connection...
05-06 08:29:21.780 D/libgps (2264): agps_ril_update_network_availability: Waiting for IPC connection - timeout​
Where id 2264 is regarding the tether process in activity for my test.
So, when i read logfile, I found this very weird :
05-06 08:29:20.775 E/libgps (2264): IPC Communication Error, /tmp/11980989/proprietary/deliverables/android/gps_interface/../gps_interface/gpsi_client/GpsiClient.cpp:1143 agps_ril_update_network_state
So, by curiosity, i enabled GPS by the toggle, and a miracle appear, the wifi tethering has worked perfectly.....
My second device connected to the hospot, can browse and get data from internet.... :victory:
May be, someone (an expert) can explain this, but for the moment I wish share this workaround with all.
See you,
Manuxme.
May be relevant to us, don't know. But should be noted the ROM you mention is for the international, just in case someone gets eager and tries using it.
We have hotspot unlocked for the most recent builds of TW.
He is posting in the wrong g forum
Transmitted with a portable device using Xparent Blue Tapatalk 2
edfunkycold said:
He is posting in the wrong g forum
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
You are right.... Sorry for that, it was my first ppost altough I follow many subject since few weeks....
DO not hesitate to move the post to the good one
Manuxme.
Is the post can be move to this area :
Samsung Galaxy S III I9300, I9305 > Galaxy S III Q&A, Help & Troubleshooting (and not Sprint Samsung Galaxy S III > Sprint Galaxy S III Q&A, Help & Troubleshooting ).
Sorry for the inconveniences.
Manuxme.
Manuxme said:
Is the post can be move to this area :
Samsung Galaxy S III I9300, I9305 > Galaxy S III Q&A, Help & Troubleshooting (and not Sprint Samsung Galaxy S III > Sprint Galaxy S III Q&A, Help & Troubleshooting ).
Sorry for the inconveniences.
Manuxme.
Click to expand...
Click to collapse
You can report the thread (from the browser) and just say you want the thread moved, or PM a mod
CNexus said:
You can report the thread (from the browser) and just say you want the thread moved, or PM a mod
Click to expand...
Click to collapse
Done
Transmitted with a portable device using Xparent Blue Tapatalk 2
All,
About the workaround indicated yesterday by enabling the GPS, actually, it does not work !!!!
I do not why yesterday it works. When GPS turn UP wifi tether works when turn down, it does not works. A strange luck ??!!
BTW, I continu investigations, tests and founds the really root cause (already found by people on other forum) :
Code:
AccountRecoveryService$Receiver }
05-07 13:06:28.145 D/dalvikvm(2725): GC_CONCURRENT freed 360K, 5% free 9328K/9784K, paused 1ms+1ms, total 14ms
05-07 13:06:28.320 D/ConnectivityService(2268): handleInetConditionHoldEnd: net=0, condition=100, published condition=100
05-07 13:06:30.230 D/ConnectivityService(2268): ConnectivityChange for mobile_dun: CONNECTED/CONNECTED
05-07 13:06:30.270 E/SecondaryTablController(1907): [B]ip route add failed: /system/bin/ip route add 0.0.0.0/0 via 10.221.59.1 dev rmnet1 table 60[/B]
05-07 13:06:30.270 W/FrameworkListener(1907): Handler 'interface' error (No such device)
05-07 13:06:30.275 E/ConnectivityService(2268): Exception trying to add a route: java.lang.IllegalStateException: command '182 interface route add rmnet1 secondary 0.0.0.0 0 10.221.59.1' failed with '400 182 ip route modification failed (No such device)'
05-07 13:06:30.275 E/ConnectivityService(2268): Exception trying to remove a route: java.lang.IllegalStateException: command '183 interface route remove rmnet1 default 0.0.0.0 0 10.221.59.1' failed with '400 183 Failed to remove route from default table (No such process)'
05-07 13:06:30.295 W/NetworkPolicy(2268): shared quota unsupported; generating rule for each iface
05-07 13:06:33.300 D/Tethering(2268): TetherModeAliveState.processMessage what=3
05-07 13:06:33.300 D/Tethering(2268): chooseUpstreamType(true), preferredApn =4, got type=4
05-07 13:06:33.335 D/TetherController(1907): setDnsForwarders(0 = '192.168.10.110')
05-07 13:06:33.335 D/TetherController(1907): Sending update msg to dnsmasq [update_dns:192.168.10.110]
Everytime, Wifi tethering is enable; this issue apear :
05-07 13:06:30.270 E/SecondaryTablController(1907): ip route add failed: /system/bin/ip route add 0.0.0.0/0 via 10.221.59.1 dev rmnet1 table 60
So, with a terminal emulator in root acces on the phone (example below in the screenshot), i launch exactly the same command line, and it works ?! :
Screenshot explanation:
1 - Check the new entry, added by the start of wifi tether process.
In orange, the exact command line launch on the terminal, in the history command line number 10.
Now, i sure, with this manual intervention, it works , the wifi tether allow other device to reach internet.
But why it failed everytime by the the normal way ? Is someone know ?
FOr the moment, i am going to try to write a shell script to add/remove the entry when necessary.
Thanks,
Manuxme.

[Q&A] [DEV-only][WIP] ALSA BCM21553 Audio libs built from source - BroadcomCM

Q&A for [DEV-only][WIP] ALSA BCM21553 Audio libs built from source - BroadcomCM
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [DEV-only][WIP] ALSA BCM21553 Audio libs built from source - BroadcomCM. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Same Kernel but Cm 7 vs cm 9 have opposite Audio bug. Help?
Hi guys, just recently moved from Glass kernel modding and realized that my old Galaxy Y s5360 needed a fix. Ace and Y share same chipset so I'm writing to the most knowledgeable thread.
I see that you guys have got the BT a2dp working. I flashed bieltv rc4 kernel + cm 9.2 rc 5 and my bluetooth a2dp audio was fine but no mic / speaker working with normal phone call. Although phone music plays fine.
Also noticed that the ported ics rom from cm made phone slow + gms / vending didn't recognize device. So i decided to revert back to gingerbread using same kernel with customized hyperion 2015 rom.
With this the phone and all other audio fine + faster using gingerbread but the Bluetooth audio didn't work even after successful pairing with beats pill (thus worked before using cm 9.2).
So basically
cm 9 based ics rom works bt audio but not phone call.
Vs
CM 7 based gingerbread works phone and play service but not Bluetooth.
I understand that broad com stopped support and many devs moved to Alcatel-Lucent based libs and merged them.
Currently the rom I'm using is great except the bt audio. Which you guys have fixed in cm 9.
So my question is since both are running off biel last kernel, it would be possible to rewrite some of the cfg and libs on my current os to get it fully working (on gingerbread).
There are lots of threads and many git repo shared by all devs so basically I'm unclear which one had the right combo of libs.
I hope you can take few mins tui reply me back. I'm not a very active forum user but I am an experienced modder working for Google Glass QA Testing team, so hopefully if you can just show me the way i will be able to fix the rest without bothering you.
Thanks in advance
RK
 @AUGmedix
nvsetup said:
I've created this thread to join developers into the final audio fix for android 2.3.7. Although the prupose of this thread is to fix Audio on Android 4.0.4 we first need audio drivers source.
On all our based Android 2.3.7 ROMs we fixed audio using some AOSP Alcatel .so files (to remove Samsung lib dependency) and some Samsung .so libraries too, this is the whole list:
Our device uses ALSA audio system, which is also used on stock ROM. This is related to software more than hardware, although we are not planning at the momnt to "change" this audio way. To activate ALSA audio some changes need to be done on kernel, that samsung provide to us on their kernel sources. Mostly we need to enable ALSA on device .config file:
Code:
CONFIG_BRCM_SOUND_ALSA=y
CONFIG_BRCM_SOUND_ATHENA_ALSA=y
That's not an issue as prebuilt alsa libs work, so new libs should work too. Ramdisk needs some edit too, as ALSA audio system is stored on dev/snd, and this is well defined too on our ramdisk, ueventd.rc
Code:
/dev/snd/* 0660 system audio
We realised after that that actually CyanogenMod 7.2 Sources include ALSA lib sources, what we didn't know if those sources could work with our devices. This sources build the following libs, as releated to its Android.mk files:
We can found inside /android_hardware_alsa_sound/tree/gb-release-7.2"]hardware/sound_alsa the following sources to build
libaudio
libaudioflinguer
hw/alsa.default
hw/acoustics.default
On
libasound
And apart from that, some other audio libs such as libaudiopolicy are built inside framework/base repository, but they doesn't make any conflict. Other libs are included on Android source files.
To enable the build of those libs, using ALSA software instead af "Android default (not sure about that)". I've enabled on Boardconfig.mk the following configs:
Code:
# Audio
BOARD_USES_GENERIC_AUDIO := false
BOARD_USES_ALSA_AUDIO := true
BOARD_PREBUILT_LIBAUDIO := false # even not writted.
BUILD_WITH_ALSA_UTILS := true
This configs enable the building of those libs on their Android.mk files.
Also, I've added on device_cooperve.mk the following lines to build those hw modules releated to audio:
Code:
# Audio
PRODUCT_PACKAGES += \
alsa.default \
acoustics.default
After the build finished, and fixed some errors, AUDIO WAS WORKING, but not as expected. There were issues on Audio Routing:
Headphones are detected through system, but audio is not reproduced on headphones (speakers does)
When you make a call, sometimes you can't and phone freezes, or when you hangout the call, phone freezes.
Everything else apart from that seems to be working, even microphone, although this bugs are pretty weird, I took a look to logcat.
Code:
[COLOR="Gray"]D/AndroidRuntime( 1419): CheckJNI is OFF
I/ ( 1420): ServiceManager: 0xad50[/COLOR]
[COLOR="Red"]E/ALSALib ( 1420): external/alsa-lib/src/control/control.c:882:(snd_ctl_open_noupdate) Invalid CTL AndroidOut[/COLOR]
W/AudioHardwareALSA( 1420): Unable to attach mixer to device AndroidOut: No such file or directory
[COLOR="Red"]E/ALSALib ( 1420): external/alsa-lib/src/control/control.c:882:(snd_ctl_open_noupdate) Invalid CTL AndroidIn[/COLOR]
W/AudioHardwareALSA( 1420): Unable to attach mixer to device AndroidIn: No such file or directory
D/AudioHardwareALSA( 1420): openOutputStream called for devices: 0x00000002
D/ALSAModule( 1420): open called for devices 00000002 in mode 0...
I/ALSAModule( 1420): Initialized ALSA PLAYBACK device AndroidPlayback_Speaker_normal
I/AudioHardwareALSA( 1420): buffer size (bytes) to AF = 16384
D/AudioFlinger( 1420): setParameters(): io 1, keyvalue routing=2, tid 1593, calling tid 1420
I/AudioFlinger( 1420): AudioFlinger's thread 0x1d978 ready to run
D/ALSAModule( 1420): route called for devices 00000002 in mode 0...
I managed to fix those errors (E/) by moddifying asound.conf, found on system/etc, adding this lines on the top and deleting old ones:
Code:
ctl.AndroidOut {
type hw
card 0 # Can replace with drivers name from /proc/asound/cards
}
ctl.AndroidIn {
type hw
card 0
}
Now logcat shows this at the moment
Code:
[COLOR="Gray"]D/AndroidRuntime( 1425): CheckJNI is OFF
I/ ( 1426): ServiceManager: 0xad50[/COLOR]
D/AudioHardwareALSA( 1426): openOutputStream called for devices: 0x00000002
D/ALSAModule( 1426): open called for devices 00000002 in mode 0...
I/ALSAModule( 1426): Initialized ALSA PLAYBACK device AndroidPlayback_Speaker_normal
I/AudioHardwareALSA( 1426): buffer size (bytes) to AF = 16384
D/AudioFlinger( 1426): setParameters(): io 1, keyvalue routing=2, tid 1604, calling tid 1426
I/AudioFlinger( 1426): AudioFlinger's thread 0x1d960 ready to run
D/ALSAModule( 1426): route called for devices 00000002 in mode 0...
Actually that's the actual logcat, using headphones, and sound goes through speakers:
Code:
D/dalvikvm( 1926): GC_EXTERNAL_ALLOC freed 324K, 49% free 3317K/6471K, external 571K/579K, paused 58ms
V/HeadsetObserver( 1607): Headset UEVENT: {SUBSYSTEM=switch, SWITCH_STATE=2, DEVPATH=/devices/virtual/switch/h2w, SEQNUM=1335, ACTION=change, SWITCH_NAME=h2w}
W/Vold ( 1415): Ignoring unknown switch 'h2w'
V/HeadsetObserver( 1607): Intent.ACTION_HEADSET_PLUG: state: 1 name: h2w mic: 0
I/HeadsetService( 1907): Headset plugged: true
I/Effect-DRC( 2115): Compression factor set to: 1.000000
I/Effect-BassBoost( 2115): New strength: 0
D/SurfaceFlinger( 1607): Layer[1c62e0] [2] non-RGB565 reloads
I/Effect-Equalizer( 2115): Setting band 2 to 0
I/Effect-Equalizer( 2115): Setting band 2 to 1
I/Effect-Equalizer( 2115): Setting band 2 to 2
I/Effect-Equalizer( 2115): Setting band 2 to 3
I/Effect-Equalizer( 2115): Setting band 2 to 4
I/Effect-Equalizer( 2115): Setting loudness correction reference to 100.000000 dB
D/AudioFlinger( 2115): setParameters(): io 1, keyvalue routing=8, tid 2117, calling tid 2115
D/ALSAModule( 2115): route called for devices 00000008 in mode 0...
D/ALSAModule( 2115): open called for devices 00000008 in mode 0...
I/ALSAModule( 2115): Initialized ALSA PLAYBACK device AndroidPlayback
D/dalvikvm( 1926): GC_EXTERNAL_ALLOC freed 323K, 49% free 3327K/6471K, external 571K/579K, paused 44ms
We must take a look if that is kernel relevant or not, as we really need this libs to work, to then start working on CyanogenMod 9.1 / Android 4.0.4 audio. Any suggestions are welcomed, although if they are from newbie or developer, don't want this thread to be spammed as others
Click to expand...
Click to collapse

Categories

Resources