In keeping with the awesome work on gps development here is a thread dedicated to audio development.
We're going to get the audio changes pushed to the sourceforge git today.
Before pushing changes back to the git, make sure they're tested
Until we get them onto sourceforge you can find them here.
Again. please DO NOT push any changes to here without checking with Vilord as we're going to be moving them to sourceforge.
http://code.google.com/p/vogue-android/source/list
Things that need to be looked over are audio routing for bluetooth
And here is the most recent Audio libs, these are for eclair and 2.1 only.
If you like my work and would like to donate me a beer you can by clicking here Beer Me
I'm merely a layman, but is this the groundwork for AD2P? (bluetooth stereo headphones)
This is getting crazy...You guys are on fire!!! This is about the only forum I've been on where there are more experts than n00bs like myself
I don't know what's required, but we should really be moving this Audio stuff to the kernel using ALSA.
Then we can use the already-maintained AndroidALSA drivers. And the BlueZ bluetooth drivers....
Less to debug that way... and we don't have to go through this with every android version.
I added the link
Hi mssmison,
Great work! I'm working on porting OpenEclair for Kaiser/Vogue/Polaris. Often I get a ton of these errors:
Code:
W/AudioTrack( 134): obtainBuffer timed out (is the CPU pegged?)
When I kill the mediaserver process and let it restart it fixes itself.
I'm not sure if this problem comes from the audio driver or the kernel, but it happens most often directly after the boot animation -- I'm guessing because that's when CPU use is the highest?
I checked dmseg for relevant errors, and here's what I found that might help:
Code:
[ 89.820245] audmgr_enable: enabled
[ 89.820287] audmgr: unexpected state 2 while enabling?!
...
[ 89.821702] rpc_write(5,0,2,3000000a,0,1,0,0,0,0,1,0,2,4,)
[ 89.821840] e,0,2,31000002,0,3,0,0,0,0,3,0,0,)
[ 89.821964] [RR] ERROR no local ept for prog 02000031 replying anyway!!
[ 89.821994] rpc_write(e,1,0,0,0,0,)
[ 89.823040] rpc_read_reply(5,1,0)
[ 89.823102] adsp: module AUDPPTASK has been registered
[ 89.823160] msm_adsp_enable() 'AUDPPTASK'
[ 89.823197] rpc_write(6,0,2,3000000a,0,1,0,0,0,0,1,1,2,4,)
[ 89.824114] rpc_read_reply(6,1,0)
[ 90.780193] adsp: module 'AUDPPTASK' enable timed out
[ 90.780278] adsp: module AUDPPTASK not enabled before write
[ 90.780313] adsp: module AUDPPTASK not enabled before write
[ 90.780343] adsp: module AUDPPTASK not enabled before write
[ 90.780373] adsp: module AUDPPTASK not enabled before write
[ 90.780399] adsp: module AUDPPTASK not enabled before write
[ 90.780429] adsp: module AUDPPTASK not enabled before write
[ 90.781509] audio_ioctl 40046100
[ 90.781564] audio_enable()
[ 90.782978] audio_disable()
[ 90.783043] 7200 Audio: Idle: using speaker.
[ 90.783101] snd_set_device 1 1 1
[ 90.783139] rpc_write(7,0,2,30000002,0,1,0,0,0,0,1,1,1,3,0,)
[ 90.784098] rpc_read_command(f,0,2,31000002,0,3,0,0,0,0,3,0,0,)
[ 90.784258] [RR] ERROR no local ept for prog 02000031 replying anyway!!
[ 90.784293] rpc_write(f,1,0,0,0,0,)
[ 90.784411] rpc_read_reply(7,1,0)
[ 90.784453] adsp: module AUDPPTASK not enabled before write
[ 90.784539] audmgr_disable
[ 90.784571] rpc_write(8,0,2,30000013,0,2,0,0,0,0,0,)
[ 90.785671] rpc_read_reply(8,1,0)
[ 90.785703] audmgr_disable: wait for disable
[ 90.816656] rpc_read_command(10,0,2,31000013,0,1,0,0,0,0,1,6,1,30,59e870,)
[ 90.816893] audmgr: DISABLED
[ 90.816941] rpc_write(10,1,0,0,0,0,)
[ 90.817034] audmgr_disable: disabled
[ 90.817084] audpp: disable
[ 90.817111] msm_adsp_disable() 'AUDPPTASK'
[ 90.817163] rpc_write(9,0,2,3000000a,0,1,0,0,0,0,1,2,2,4,)
[ 90.818864] rpc_read_reply(9,1,0)
[ 90.818943] adsp: closing module AUDPPTASK
[ 90.818998] adsp: disable interrupt
...
After that I killed the mediaserver process and let it restart. The only errors I see after that are these:
Code:
[ 162.450120] adsp: waiting for DSP write ready
[ 162.450120] audio_ioctl 40046100
[ 162.450120] audio_enable()
[ 163.040122] audpp: DMA missed
[ 163.040122] audpp: DMA missed
[ 163.052852] audpp: DMA missed
[ 163.070122] audpp: DMA missed
...
The precompiled libs work great. Any tips on getting them to compile on the latest aosp?
Sorry for stiupid question. I'm new in Android.
How to "install" those files at device?
Didn't know this thread existed. So, will this get BT Audio working on Eclair builds?
Dukenukemx said:
Didn't know this thread existed. So, will this get BT Audio working on Eclair builds?
Click to expand...
Click to collapse
I used this libs on myn's Warm Eclair Beta 2 and still no BT audio routing, so I guess the answer is "no". :/
I'm waiting for BT fix too. Not a developer so can't help much with the developing part, but I can help with testing if need occurs.
I'm waiting for BT fix to. Also not a developer but can help with testing if needed.
if anyone is looking to get BTaudio working...
check out polymod 2.1g with the BT&Wifi update. (for kaiser anyway)
it has been the only eclair that my BT headset works on.
I tried to use the update on 2.1d (which is a faster build) but no more BTaudio.
I have also tried on other builds with no success.
just for the fun of it, I went back and re-installed 2.1g+updates this afternoon and
it still works with latest nbh.
I worked on this for countless hours comparing the diff between 2.1g and 2.1d but I cant get anywhere with it.
maybe someone with more android experiance could check it out.
It's a real shame that Poly couldn't fix his Kaiser. He did post recently in the Vogue kernel thread about his Kaiser problem, but he still couldn't fix it. Since he got BT audio working in Eclair, someone could try asking him how he did it.
on a postive note...
this means that the BTaudio issue is not kernel related
and should be an easy fix once polys secret is discovered.
I have a few more development hurdles to overcome before I can attempt to
assist in any of these issues. but If nobody has addressed them by then I will
be sure to get on it.
mnjm9b said:
if anyone is looking to get BTaudio working...
check out polymod 2.1g with the BT&Wifi update. (for kaiser anyway)
Click to expand...
Click to collapse
Can you please post polymod 2.1 g BT Update I can't find it anywhere.
Millence said:
Can you please post polymod 2.1 g BT Update I can't find it anywhere.
Click to expand...
Click to collapse
here.
I think this is it. I have the file on my backup drive.
if this one doesn't work, let me know and I will upload mine.
Thanks!
Instaling right now!
Dukenukemx said:
It's a real shame that Poly couldn't fix his Kaiser. He did post recently in the Vogue kernel thread about his Kaiser problem, but he still couldn't fix it. Since he got BT audio working in Eclair, someone could try asking him how he did it.
Click to expand...
Click to collapse
Try copying your /system/libs folder from working bt audio polymod build into an androidupdate.tar, and applying it to another elair build
*M* said:
Try copying your /system/libs folder from working bt audio polymod build into an androidupdate.tar, and applying it to another elair build
Click to expand...
Click to collapse
Oh.. I wish it was that easy.
I think that was the first thing I did when poly's 2.1d came out.
I also did that with other builds as well.
mnjm9b said:
here.
I think this is it. I have the file on my backup drive.
if this one doesn't work, let me know and I will upload mine.
Click to expand...
Click to collapse
Doing a diff on this update. It contains wlan.ko libs which appears to be for the wireless lan.
The sysinit.rc changes which touch the BlueTooth references are identical to what we have in our latest Eclair Builds (SuperEclair and Warm Eclair). It appears poly's previous build was referencing bluetooth differently and he needed a fix.
With that said, I would be shocked if this fixes our BT Audio on vogue.
I got a bt headset today. It works fine on donut, tried out polymod, it pairs and connects and says its routing media to the headset but still goes through the phone. Perhaps the code is kaiser specific
Related
NOTICE: This is COMPATIBLE with ALL Vivid Rooted Stock and Custom ROMs
For frequency control use fauxclock from Google Play
Just a statement regarding kernel source: The Kernel Source is of course covered under GPL version 2. Free software does NOT mean no work or time was spent working on it. I have donated a large sum of my free time to hack this kernel. If you use my modified kernel source in parts or in its entirety, I kindly ask you mention its origins and to send me a github pull request or PM whenever you find bugs or think you can help improve my kernel hack further. This way the entire community will truly benefit from the spirit of open source. Thank you
Hi XDA members and fellow Vivid users:
This is my tenth kernel hack. I want to thank Erasmux, and several others I cannot recall for inspiring me to venture into this unfamiliar territory for me.
What is a Kernel? The Kernel is the Foundation in which everything else builds upon in any software system.
[Car Analogy]: Kernel is like the Engine, Electrical system and the Transmission to a car. The Library, Framework and the Apps [AKA ROM] are the body frame and the rest of the Car.
THIS KERNEL is BASED ON HTC Source Code. So it is COMPATIBLE ONLY WITH HTC ICS Vivid Builds.
Please DO NOT use any task killers, they DO NOT improve performance nor battery life. They INTERFERE with your phone's stability (more crashes) and App compatibilities (Forced Close).
CleanCache (via ZCache backend)
ZCACHE is a new technology I introduced to HTC Kernel. ZCACHE is a compressed cache similar to ZRAM but the similarity ends there. ZCache is meant to provide as many "cleancache" pages (non-dirty or untouched "virgin" memory) to apps that request for new memory. CleanCache is very easy to allocate and no additional penalty are required to hand them out, so having more CleanCache pages will improve performance. Under heavy memory pressure, often times the kernel will NOT have enough CleanCache pages, so the kernel has to do EXTRA work to reclaim dirty cache pages and clean them for the new apps that's requesting for them. The described process creates a performance hit for the kernel and the app, so the idea is to use compression to create more CleanCache pages available for use. Of course there's a penalty to pay for using compression, but the trade-off between compression penalty and the penalty for reclaiming dirty cache pages and allocating them after cleaning is smaller for compression, so in the end, CleanCache should add more performance.
ZRAM (aka CompCache aka RAMZSwap)
ZRAM is an updated version formally known as CompCache and RAMZSwap. It was originally designed for 2.6.38.xx kernels, I have backported to our 2.6.35.xx kernel. ZRAM allows real-time compression of memory objects in RAM thus reducing memory pressure for the Linux kernel and can keep more apps in memory longer (more apps in RAM == better performance, less fetching from slower MMC or SDCard). Compression, however, is not Free. Some CPU cycles are required to do the compress/decompression, so there's a slight penalty for it. The original CompCache / RAMZSwap required a user space binary to control its behavior which adds additional penalty to performance, but the new version ZRAM eliminated the need for a separate dedicated daemon, thus reducing the overhead and increased performance from the old CompCache by 20%. Therefore, with the newer implementation of ZRAM interface, the performance penalty is almost negligible.
Joe's RCU (Optimized for Small SMP systems)
Joe Korty has created an RCU for small SMP systems (> 32 cores). His approach is to isolate all the Garbage Collection (GC, a slow time consuming but necessary processing) to a single core, thus allowing other cores to ONLY work on real required processing. This will allow the additional cores to complete their assigned tasks as fast as possible (not bogged down by GC) then immediately go back to a suspended state (saving battery).
Fast No Hz RCU (Optimized for SMP operations)
Fast NoHz is an optimized version of the traditional Tree RCU. Many new kernels are using the Tickless NoHz design. This RCU is tailored and designed to work with the new NoHz kernel system.
SmartAssV2 Governor (Balanced)
This governor has a built-in "profile" similar to SetCPU, so screen off will use lower clock rate thus conserve more battery, but it also has a fast wake up feature so that user interaction will not see the lag when switching from Sleep to Wake state.... (So SetCPU Profiles are sorta redundant when using this governor, you can still use SetCPU to OC to higher than default Clock frequency).
Interactive Governor (Performance)
This governor is designed to put more priority to User Interface (UI aka Apps) tasks, therefore appears more responsive then the traditional OnDemand governor. So if you want the smoothest UI interaction, this governor is for you...
Brain F*ck Scheduler - (BFS)
This scheduler is designed to be simple and speedy tailor specifically for user interface type systems such as desktop/smart phone devices where user interaction is MORE important than serving 1 million web requests (CFS, the default scheduler) at the same time (think of nimble desktop workstations vs large corporate servers).
SLQB - (SLAB allocator with Queue)
This memory allocator is designed for small number of CPUs system (such as desktop or smart phone devices). This allocator is design to be simple and it is optimized for using order-0 pages as much as possible (order-0 pages are the simplest therefore quickest type of memory in a Linux system to allocate). Not all kernels are using SLQB including CM7 main line...
Fair Budget Queue (BFQ I/O scheduler)
This I/O scheduler is an improvement on top of Completely Fair Queue (CFQ). CFQ is fair in terms of time but not in terms of throughput / bandwidth, so BFQ make sure that both time and throughput / bandwidth are balanced across all requests.
Kernel Files:
******* Ice Cream Sandwich (Android 4.0.x) ******* (Linux 3.0.33)
[ CFS ] (Ultimate Edition) *** S-ON ***
The File ==> Vivid Kernel 007 (1.73 GHz, GPU @ 320MHz, ZRAM) <==
[ CFS ] (Ultimate Edition) *** S-OFF ***
The File ==> Vivid Kernel 007 (1.73 GHz, GPU @ 320MHz, ZRAM) <==
[ Optional: ]
Files to DISABLE Sweep2Wake:
http://forum.xda-developers.com/showpost.php?p=25538084&postcount=6616
[ For Kernel Devlopers ONLY: ]
The File ==> My Global VDD_TABLE for under volt patch <==
The File ==> KGSL Ring Buffer Power Management Patch for Cordy and Ninja Jump <==
Optional Under voltage: Version 0.1.4+ ONLY
Code:
[ to over volt ALL frequencies by 25000 uv (microvolts) ]
echo "+25000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
[ to under volt ALL frequencies by 25000 uv (microvolts) ]
echo "-25000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
[ to set a specific frequency (ie 1.18 GHz)
with a specific voltage (ie 1.0875 volts) ]
echo "1188000 1087500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
CPU Frequency Voltage Table Example
Code:
192000: 812500
310500: 812500
384000: 812500
432000: 812500
486000: 837500
540000: 850000
594000: 862500
648000: 875000
702000: 900000
756000: 925000
810000: 937500
864000: 962500
918000: 962500
972000: 962500
1026000: 975000
1080000: 987500
1134000: 1000000
1188000: 1012500
1242000: 1025000
1296000: 1050000
1350000: 1075000
1404000: 1100000
1458000: 1112500
1512000: 1125000
1566000: 1150000
Optional: Stock Clock Frequencies for Dual CPUs
Code:
su
echo 192000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 1188000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 1 > /sys/devices/system/cpu/cpu1/cpufreq/online
echo 192000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq
echo 1188000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq
Optional: ZRAM (Compressed RAM swap space )
Code:
su
mkswap /dev/block/zram0
swapon /dev/block/zram0
Low Voltage - Under Volt the processor, therefore uses Less Battery, but NOT ALL CHIPS can handle Under Volt.. If you experience instability, try the Stock Voltage Version.
Stock Voltage - Uses the voltage values from ORIGINAL HTC Kernel Source.
There are NO PERFORMANCE DIFFERENCE between the Under Volted and Stock Voltage versions!
Installation Instructions:
Here's a step by step instruction to install this kernel:
1. download the above file (via phone directly or to a PC)
2. copy the downloaded zip file to /sdcard/download/
3. Open ROM Manager and select "Reboot into Recovery" and select "OK"
4. Once in recovery, select "wipe cache partition", select "Yes", then select "advanced", then select "Wipe Dalvik Cache", then select "Yes" again. Once finished, click the back button to go back to the main recovery menu. On that menu, select "Install Zip From SDCad", then select "Choose zip from SDCard", then go to /sdcard/download and select the downloaded zip file and let it run its script.
5. Once the script is done, select "reboot system now"
Note: After FLASHING, the first reboot may take longer than usual, please be patient... After the first reboot, it may lag during initial load (let everything finish loading). Once everything is loaded and phone is ready for use, reboot the phone a 2nd time and the lag will be gone and everything should be silky smooth...
NEWS BULLETIN:
Ice Cream Sandwich Version 007 is out. More intelligent intellidemand! Completely free yourselves from mpdecision, thermald and now with intellidemand, complete CPU/Thermal Management by the kernel.
Please don't hesitate to talk among yourselves and help each other out... The XDA community is what inspired me to hack kernels for everyone since everyone here is nice and helpful to each other... Keep helping each other.... Famous proverb: It's better to give than to receive...
BUGS:
Not All CHIPS ARE CREATED EQUAL
TO DO:
version 1.x.x -- Haven't thought about it yet...
History:
[ Change Log ]
Standard Disclaimer: Not responsible for bricking your phone, voiding your warranty, or any other pain or suffering you may feel as result of using this kernel!!!
My Github Complying with GPL and XDA rulez
Follow me on
:
If you find this Kernel useful, feel free to hit the [Thanks] button below
Awesome!! Can't wait to try it!
Sent from my HTC PH39100 using XDA
Thank you so much.. faux123~
Faux your a god.
Sweet....
Anyone install yet and have feedback to report?
Boot Loop
No go for me.
It gave me a reason to update to the new AT&T RUU.
May try again after clean install.
Going to flash stock rooted cwm then maybe this will report back.
ismoore said:
Anyone install yet and have feedback to report?
Click to expand...
Click to collapse
Well it's fast in quadrant scores. I got like a 3560 and in that test CPU scores are significantly higher. Antutu benchmark scores with no overclock are the same as stock. All else felt the same. I'm running this kernel with WC's 3.6 Vivid ROM. Still appreciate the contribution faux! I have run your kernels on other phones and they are always the best!
Now why would Window XP forget my android 1.0 drivers for hboot? can't flash anything in hboot now...
Great, thanks for the info. May try this tonight when I get home. Thanks for your efforts faux.
brwnohno said:
Well it's fast in quadrant scores. I got like a 3560 and in that test CPU scores are significantly higher. Antutu benchmark scores with no overclock are the same as stock. All else felt the same. I'm running this kernel with WC's 3.6 Vivid ROM. Still appreciate the contribution faux! I have run your kernels on other phones and they are always the best!
Click to expand...
Click to collapse
My wifi isn't working, it just says "turning on...". Other than that, it works great
**** mines bootlooping its get the att and loops what should i dooo? I got the latest cwm, and hboot, stock rooted rom. Is it because I let it try to boot right after I flashed the boot.img and didn't flash cwm strait after?
haloXgod117 said:
My wifi isn't working, it just says "turning on...". Other than that, it works great
Click to expand...
Click to collapse
Brand New said:
**** mines bootlooping its get the att and loops what should i dooo? I got the latest cwm, and hboot, stock rooted rom. Is it because I let it try to boot right after I flashed the boot.img and didn't flash cwm strait after?
Click to expand...
Click to collapse
You shouldn't be flashing via cwm. I've included a script for pc tethered flashing. Just run flash.bat on pc with USB cable connected to the phone. You may need to run it twice if it failed to load the modules.
Sent from my HTC Sensation 4G using Tapatalk
faux123 said:
You shouldn't be flashing via cwm. I've included a script for pc tethered flashing. Just run flash.bat on pc with USB cable connected to the phone. You may need to run it twice if it failed to load the modules.
Sent from my HTC Sensation 4G using Tapatalk
Click to expand...
Click to collapse
So I could of flashed this on stock ICS? I didn't think you could OC with a non-rooted phone And I was bootlooping on the stock rooted rom not because of the your kernal I believe
iff this will help
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
D:\Documents and Settings\Noah>cd D:\Documents and Settings\Noah\Desktop\New Fol
der
D:\Documents and Settings\Noah\Desktop\New Folder>flash.bat
D:\Documents and Settings\Noah\Desktop\New Folder>adb kill-server
D:\Documents and Settings\Noah\Desktop\New Folder>adb remount
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
D:\Documents and Settings\Noah\Desktop\New Folder>adb push Modules/system /syste
m
error: device not found
D:\Documents and Settings\Noah\Desktop\New Folder>adb shell mv /system/bin/mpdec
ision /system/bin/mpdecision_dis
error: device not found
D:\Documents and Settings\Noah\Desktop\New Folder>adb shell mv /system/bin/therm
ald /system/bin/thermald_dis
error: device not found
D:\Documents and Settings\Noah\Desktop\New Folder>adb reboot bootloader
error: device not found
D:\Documents and Settings\Noah\Desktop\New Folder>fastboot flash boot Kernel-Her
e/boot.img
sending 'boot' (4348 KB)... OKAY [ 0.875s]
writing 'boot'... OKAY [ 4.984s]
finished. total time: 5.859s
D:\Documents and Settings\Noah\Desktop\New Folder>fastboot reboot
rebooting...
finished. total time: 0.188s
D:\Documents and Settings\Noah\Desktop\New Folder>pause
Press any key to continue . . .
D:\Documents and Settings\Noah\Desktop\New Folder>
can you make a aosp kernal
Nevermind Faux I figured it out! I just need to flash the boot.img that came with the stock rooted rom, then yours! I can't wait to test my battery now, games fly to!! Thanks for your support!!
SetCPU voltage tables are still nonfunctional, just like every other kernel I've tried.
come at me bro said:
can you make a aosp kernal
Click to expand...
Click to collapse
It would be easier to do so if we had a booting AOSP build right now, I think.
Having no issues here. Kernel is definitely smoother and faster than stock. Running fine on WC ROM. Hitting about 3350 on quadrant afer 5 consecutive runs. I haven't made and changes with setcpu, I'm assuming 1.5MHz from initial flash.
Sent from my HTC PH39100 using xda premium
Aus_Azn said:
SetCPU voltage tables are still nonfunctional, just like every other kernel I've tried.
It would be easier to do so if we had a booting AOSP build right now, I think.
Click to expand...
Click to collapse
thecubed's build boots but just barely and someone is working on a build right now I believe, so one day we might have working rom
Brand New said:
thecubed's build boots but just barely and someone is working on a build right now I believe, so one day we might have working rom
Click to expand...
Click to collapse
it boot loops with the proper builds , the one that boots is hacked up to hell
Introduction
This is a port of Android 4.0.X for Streak7 [WIP]
The "official" CM9 port requires you to repartition your device to use it. This is a mod that allows it to run on standard partition devices.
Any bugs in the "official" CM9 port will likely carry over, and there is a possibility of the mod creating more bugs.
Do not bug DJ_Steve or Giveen about any bugs in this version.
I will be providing support/changes for using CM9 on devices with stock partition layouts (ie Stock 5xx, HS r7 and newer users)
This version is a mod of the CM9 build by DJ_Steve/Giveen for stock rom partition users.
IF YOU ARE CURRENTLY USING HONEYSTREAK R2-R6, "NORMAL" CM9 (ICS-B4), OR HAVE USED NVFLASH: THIS BUILD IS NOT FOR YOU
If you have installed the prerelease, you are STRONGLY RECOMMENDED to do a fac reset after installing.
Click to expand...
Click to collapse
How to flash a zip:
Entering recovery mode on device -XDA wiki
Flashing an update.zip with custom recovery - XDA wiki
Click to expand...
Click to collapse
Requirements:
A custom recovery:
Clockwork Mod 6.0.1.1 (or newer)
Team Win Recovery Project 2.2.1.4 (or newer)
A compatable device (see above)
Click to expand...
Click to collapse
Install instructions:
Download: update-S7-CM9-b4-mod-2.zip
Copy update zip to SD card
Reboot into custom recovery mod
Select "update from update.zip"
Navigate to update zip
Flash
REQUIRED: Flash Gapps
Finished
Click to expand...
Click to collapse
Changes:
Removal of gapps (which will be provided in a seperate zip)
(Semi) Working /sdcard and /sdcard2 (has some bugs still, but mostly works)
Minor polish
Credits:
DJ_Steve for porting CM9
Giveen for every random thing
Click to expand...
Click to collapse
Changelog:
Aug 23 2012: Updated install script
Jul 22 2012: Released full version
Jul 21 2012: Updated instructions
Jul 20 2012: Released prerelease 1
Click to expand...
Click to collapse
2char
Introduction
I'm gonna organize everything I'm currently aware of, I'm gonna update this post as people comment.
Wifi
[-] Overall: Works fine
[-] Speed: Same as on previous roms
[?] Untested: Wi-fi tethering
Bluetooth
[?] Overall: Untested
[?] Untested: File transfer
[?] Untested: BT Headset
[?] Untested: Keyboard
[?] Untested: Mouse
[?] Untested: BT Tethering
[?] Untested: Handsfree device
Cellular data
[!] Overall: Nothing works
GPS/Sensors
[-] Overall: Works fine
[?] Unknown: AGPS support (Needs confirmation)
[-] Works: Accelerometer
[-] Works: E-Compass
[!] Bug: FM Radio does not work
[!] Bug: GPS very inaccurate/does not work
[-] Works: Light Sensor
[?] Untested: Microphone
[-] Works: Vibrator
Dock and outputs
[-] Works: Mostly works
[-] Works: Dock detection
[-] Works: HDMI out
[?] Untested: USB tethering
Mass Storage and Inputs
[-] Overall: Mostly works
[?] BUG: Internal sdcard not presented does not work
[!] Bug: USB-Hosting does not work
Battery
[-] Overall: Airplane mode: Seems Fine
[?] Overall: Cellular on: Unknown
[-] Works: Charging
[!] Bug: Usage info not available
Graphics
[-] Overall: Works fine
Sound
[-] Overall: Works fine
[?] Untested: Headphone out
Buttons and leds
[-] Overall: Works fine
Camera
[!] Overall: Nothing works
[!] BUG: Rear cam doesnt work
[!] BUG: Front cam doesnt work
[!] BUG: Rear Flash doesnt work
Screen and UI
[-] Overall: Works fine
Apps
[-] Overall: Mostly works
[-] Not a bug: GAPPs isnt included (General consensus: stock based roms: including gapps is ok, source based roms: do not include gapps)
[!] BUG: Chrome settings button causes app to crash
Feature requests:
Phone mode UI
Virtual keys (in phone mode)
Overall summary:
[-] Wifi: Works fine
[?] Bluetooth: Untested
[?] Tethering: Untested
[!] Cellular: Nothing works
[?] GPS/Sensors: Untested
[-] Dock/Output: Mostly works
[-] Mass Storage/Input: Mostly works
[-] Battery: Good
[-] Graphics: Mostly works
[-] Sound: Works fine
[-] Buttons: Works fine
[!] Cameras: Nothing works
[-] Screen and UI: Mostly works
[-] Apps: Mostly works
Conclusion:
(placeholder)
Released a prerelease version, this version uses the B3 apks as I cannot extract the B4 ones.
Once someone is able to give me a copy of the B4 apks I'll release the full version of B4-mod
I installed but it's a bit empty.(I know there is no gApps in it) Also I noticed rotation not works by default until you switch it on from Trebuchet - General Settings. While I am switching between menus on wireless part, device becomes unresponsive sometimes.(T-Mobile 4G Model)
Camera and 3G/4G Radios are still same, not working.
On the other hand it boots up and works very fast. Good Job!
I'm new to Android system but I know a bit about Linux. Also I'm a software developer. Are there any guideline for development/environment? (I'm using Windows 7 and Ubuntu both) I wanna try to contribute.
Edit: This works for me very well: http://wiki.cyanogenmod.com/index.php?title=Latest_Version/Google_Apps
Second Edit: Switching airplane mode on, locks device completely.
Cell data was never supported, and airplane mode freezing is likely related to that.
Treb locking to landscape by default isnt really a bug, as there is a checkbox and it does remember which one you pick.
Camera is known to not work. All these are carry over from ICS B4
Gapps isnt ready yet, it will be soon.
Snarg is trying to get camera to work
Sent from my Nexus 7 using Tapatalk 2
VPN is not working too. It says "Unsucessful". I'm sure credentials and other setting are correct.
Bluetooth:
General Functions and pairing with bluetooth mouse is working.
I havnt changed anything at all regarding VPN,
it's either due to:
Using the B3 apks (since I dont have the B4 apks)
A bug in B4 (which I cant fix)
Keep in mind I'm only making minimal changes, I'm not actively updating the code.
But I'll take a look tomorrow and see if it's anything fixable
iboware said:
VPN is not working too. It says "Unsucessful". I'm sure credentials and other setting are correct.
Bluetooth:
General Functions and pairing with bluetooth mouse is working.
Click to expand...
Click to collapse
I cant reproduce as I dont have a vpn I can attempt to connect to.
I'm going to need a logcat of you attempting to connect to it to look at, otherwise I cant even look at what could be the issue.
It turns out that the B4's system.img is in fact 'damaged'
It's damaged to the point that ext2explore cant read it, but linux kernals can mount it.
I will be releasing the full version of CM9-mod soon
Edit: There's a really strange bug with the B4 apks.
You must also install Gapps or the home button will not respond.
It actually responds when you're in the clock app, but not anywhere else.
I dont know why installing gapps fixes it, as I've cleanly pulled gapps out of the rom.
TheManii said:
I cant reproduce as I dont have a vpn I can attempt to connect to.
I'm going to need a logcat of you attempting to connect to it to look at, otherwise I cant even look at what could be the issue.
Click to expand...
Click to collapse
Code:
W/PrintK ( 68): dog, +tegra_wdt_set_timeout, wdt->timeout=130
V/PrintK ( 1323): <7>[ASOC-DBG]tegra_dapm_event_int_spk SND_SOC_DAPM_EVENT_ON ?
2
V/PrintK ( 1323):
I/keystore( 103): uid: 1000 action: s -> 1 state: 1 -> 1 retry: 4
I/keystore( 103): uid: 1000 action: s -> 1 state: 1 -> 1 retry: 4
I/keystore( 103): uid: 1000 action: s -> 1 state: 1 -> 1 retry: 4
D/dalvikvm( 2967): GC_CONCURRENT freed 318K, 23% free 6465K/8391K, paused 2ms+4m
s
E/BinaryDictionaryGetter( 1527): Could not find a dictionary pack
E/ActivityThread( 1527): Failed to find provider info for com.android.inputmetho
d.latin.dictionarypack
D/PrintK ( 1323): <6>wm8903_set_dai_trigger 1
D/dalvikvm( 1359): GC_EXPLICIT freed 745K, 22% free 9279K/11783K, paused 4ms+7ms
E/ActivityThread( 1527): Failed to find provider info for com.android.inputmetho
d.latin.dictionarypack
E/BinaryDictionaryGetter( 1527): Could not find a dictionary pack
D/dalvikvm( 1527): GC_CONCURRENT freed 474K, 21% free 7396K/9287K, paused 3ms+4m
s
I/keystore( 103): uid: 1000 action: i -> 1 state: 1 -> 1 retry: 4
I/Vpn ( 1359): Switched from [Legacy VPN] to [Legacy VPN]
I/Vpn ( 1359): Switched from [Legacy VPN] to [Legacy VPN]
V/LegacyVpnRunner( 1359): Waiting
V/LegacyVpnRunner( 1359): Executing
D/mtpd ( 3001): Waiting for control socket
I/LatinIME( 1527): InputType.TYPE_NULL is specified
W/LatinIME( 1527): Unexpected input class: inputType=0x00000000 imeOptions=0x000
00000
D/PrintK ( 1359): <6>wm8903_set_dai_trigger 0
D/PrintK ( 1323): <6>wm8903_set_dai_trigger 1
D/mtpd ( 3001): Received 20 arguments
I/mtpd ( 3001): Using protocol pptp
I/mtpd ( 3001): Connecting to ribbsede.getfoxyproxy.org port 1723 via wlan0
I/mtpd ( 3001): Connection established (socket = 11)
D/mtpd ( 3001): Sending SCCRQ
D/mtpd ( 3001): Received SCCRP -> Sending OCRQ (local = 39064)
I/mtpd ( 3001): Tunnel established
D/mtpd ( 3001): Received OCRQ (remote = 32984)
I/mtpd ( 3001): Session established
I/mtpd ( 3001): Creating PPPoX socket
F/mtpd ( 3001): Socket() Protocol not supported
D/dalvikvm( 2967): GC_CONCURRENT freed 336K, 23% free 6527K/8391K, paused 2ms+6m
s
I/LegacyVpnRunner( 1359): Aborting
I/LegacyVpnRunner( 1359): java.lang.IllegalStateException: mtpd is dead
I/LegacyVpnRunner( 1359): at com.android.server.connectivity.Vpn$LegacyVpn
Runner.execute(Vpn.java:569)
I/LegacyVpnRunner( 1359): at com.android.server.connectivity.Vpn$LegacyVpn
Runner.run(Vpn.java:447)
D/PrintK ( 0): <6>wm8903_set_dai_trigger 0
well, it looks like a common cm9 bug but I'm not sure : http://code.google.com/p/minicm/issues/detail?id=495
Another thread about this issue: http://code.google.com/p/android/issues/detail?id=23124
According to the posts I read, adding a kernel compatible tun.ko file will solve this problem.
It does seem to be the case, what rom were you on previously and did VPN work then?
None of our stock roms (by stock roms I mean for every dell device) have tun.ko (by default) and I havnt changed the kernel at all from ICS-B4.
If it worked in B4 then it might have been something from my end, if it didnt then there's nothing that can currently done.
Edit: I will be uploading the full version of CM9-mod soon, flash and fac reset and test against that.
As the prerelease is just that, it doesnt sound like something that would be fixed in the full version, but lets just check and confirm.
TheManii said:
It does seem to be the case, what rom were you on previously and did VPN work then?
None of our stock roms (by stock roms I mean for every dell device) have tun.ko (by default) and I havnt changed the kernel at all from ICS-B4.
If it worked in B4 then it might have been something from my end, if it didnt then there's nothing that can currently done.
Click to expand...
Click to collapse
I was on the latest stock HC and I have never installed any other rom.
If you need VPN support for anything critical (or do anything mission critical period), I would recommend staying on a stock rom.
Regardless of which version of CM9 you choose to install, they're all closer to beta then they are to release.
That said, the full version of CM9-mod is now live.
You are STRONGLY recommended to do a fac reset after installing it if you installed the prerelease.
You also MUST install Gapps as there's a strange bug that causes the home button to not work without it.
TheManii said:
If you need VPN support for anything critical (or do anything mission critical period), I would recommend staying on a stock rom.
Regardless of which version of CM9 you choose to install, they're all closer to beta then they are to release.
That said, the full version of CM9-mod is now live.
You are STRONGLY recommended to do a fac reset after installing it if you installed the prerelease.
You also MUST install Gapps as there's a strange bug that causes the home button to not work without it.
Click to expand...
Click to collapse
I have a timeout problem with marketplace on the full version. It says "loading" for ages and then "Connection timed out. [Retry]" (I did factory reset)
Are you able to connect to websites with the browser?
TheManii said:
Are you able to connect to websites with the browser?
Click to expand...
Click to collapse
Yes. I was able to connect. Today, I tried again and it's successful. I don't know why it could not connected yesterday maybe a DNS issue.
Edit: Shortcuts are displaying in wrong position(under the search icon) it needs alignment. Kindle is not working. I think pre-release version was more stable. Now, I'm back to the stock hc. I would like to try it if there is a new version.
Ive never seen a rom that you shouldnt use if you have Nvflashed before.. whats the cause, or what would happen if one did flash?
ssmr2t said:
Ive never seen a rom that you shouldnt use if you have Nvflashed before.. whats the cause, or what would happen if one did flash?
Click to expand...
Click to collapse
I was wondering the same thing.
sent from device using an app
joeclark said:
I was wondering the same thing.
sent from device using an app
Click to expand...
Click to collapse
Because nvflashed ones are changing the original partition table. if you can restore the partition table, than you can use this one as well, i think.
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.
Hi,
I clicked by accident something in the superSU settings. No idea what I have changed. Could someone tell me the defaults and especially those from the security section?
Mine at the moment are:
Enable su during boot [ ]
Mount namespace seaparation [V]
Enable multi-user [ ]
Tapjacking protection [V]
Any other critical setting that someone should be aware of?
jcur said:
Hi,
I clicked by accident something in the superSU settings. No idea what I have changed. Could someone tell me the defaults and especially those from the security section?
Mine at the moment are:
Enable su during boot [ ]
Mount namespace seaparation [V]
Enable multi-user [ ]
Tapjacking protection [V]
Any other critical setting that someone should be aware of?
Click to expand...
Click to collapse
Enable SU during boot should be ticked...
Cheers
dirlan2001 said:
Enable SU during boot should be ticked...
Cheers
Click to expand...
Click to collapse
Thank you. Is that a recommended setting or a default one?
jcur said:
Thank you. Is that a recommended setting or a default one?
Click to expand...
Click to collapse
AFAIK it's always been on on my devices.... guess that means it's a default setting. And logically, if it's not ON, it's not usefull. Some settings or apps need to be kept under control at boot.
Cheers
dirlan2001 said:
AFAIK it's always been on on my devices.... guess that means it's a default setting. And logically, if it's not ON, it's not usefull. Some settings or apps need to be kept under control at boot.
Cheers
Click to expand...
Click to collapse
Thank you. I followed your advice and set it to ON.
jcur said:
Thank you. I followed your advice and set it to ON.
Click to expand...
Click to collapse
You're welcome
Ok so this is driving me up the walls.
I got this new secondhand ( ) 3T, which had some ROM issues: on startup of the stock Oreo rom Dirac Control would repeatedly crash forcing the device to factory reset and reboot.
So I figured the issue was a bad flash by the previous owner, however I've went through a zillion roms so far without getting the phone working as it should. That is, everything works except sound and things depending on sound. Seeing this is a phone sound is kinda crucial
My expectation has been so far that it still is somehow a software issue, as an hardware issue that (outwardly) /only/ breaks sound is too odd for me (sound controller is wihtin soc).
Things I've done:
-Went back to nougat following the guides that are on this forum.
-went to lineageOS
-reflashed phone using OEM unbrick tools in Windows (MSM program), twice (both versions that could be had on the web)
-went fully OEM lock stock and flashed all the way up to Oreo using OEM updates
I suspect that somehow audio depends on a special partition which has become botched by flashing done by the previous owner. Are there any partitions that relate to the audio functions where the SOC loads some special firmware from?
Perhaps some of the data on the ESF partitions relates to the audio functions?
Anyone has any ideas or suggestions?
Attached to this post you will find for your debugging pleasures a logcat dump of me turning on the phone and turning it off again. It is quite noisy, so 1,5 meg in size uncompressed.
-update bumb-
Running OOS A3003_28_161027 build the following appears in dmesg:
wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-micbias-cfilt1-mv property in node /soc/[email protected]/tasha_codec failed
wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-micbias-cfilt2-mv property in node /soc/[email protected]/tasha_codec failed
wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-micbias-cfilt3-mv property in node /soc/[email protected]/tasha_codec failed
wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-micbias1-cfilt-sel property in node /soc/[email protected]/tasha_codec failed
wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-micbias2-cfilt-sel property in node /soc/[email protected]/tasha_codec failed
wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-micbias3-cfilt-sel property in node /soc/[email protected]/tasha_codec failed
wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-micbias4-cfilt-sel property in node /soc/[email protected]/tasha_codec failed
wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-dmic-clk-drv-strength property in node /soc/[email protected]/tasha_codec failed, err = -22
wcd9335-slim tasha-slim-pgd: wcd9xxx_slim_probe: codec type is 2
[ 5.170191]@3 IPC_RTR: ipc_router_create_log_ctx: Unable to create IPC logging for [mpss_IPCRTR]
[ 5.470344]@0 wcd9xxx_slim_probe: failed to get slimbus tasha-slim-pgd logical address: -6
[19700125_14:14:44.584697]@0 init: Unable to open persistent property directory "/data/property": No such file or directory
[19700125_14:14:44.647916]@0 init: cannot find '/system/bin/ptt_socket_app', disabling 'ptt_socket_app'
[19700125_14:14:44.647953]@0 init: cannot find '/system/bin/usb_uicc_client', disabling 'usb_uicc_daemon'
[19700125_14:14:44.654408]@0 init: cannot find '/system/xbin/perfprofd', disabling 'perfprofd'
[19700125_14:14:44.740997]@2 init: cannot find '/system/vendor/bin/seemp_healthd', disabling 'seemp_healthd'
[19700125_14:14:44.760620]@2 init: cannot find '/system/vendor/bin/qvrservice', disabling 'qvrd'
[19700125_14:14:44.760650]@2 init: cannot find '/system/bin/secotad', disabling 'secotad'
[19700125_14:14:44.768017]@2 init: cannot find '/system/bin/dts_configurator', disabling 'dts_configurator'
[19700125_14:14:45.545454]@0 wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-micbias-ldoh-v property in node /soc/[email protected]/tasha_codec failed
wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-dmic-clk-drv-strength property in node /soc/[email protected]/tasha_codec failed, err = -22
Click to expand...
Click to collapse
So it seems there are a few system bins (and maybe firmware???) missing. Though these might also just normaly not be there. Also it seems the SOC communicates with audio chip using I2C, but does not seem to be able to enumerate the device normally, which would point to either hardware failure or missing firmware/otherbinaryblobs.
I have flashed using the 'official' unbrick tool, so I would assume all data is correctly flashed onto the phone, and by that I would normally exclude missing firmwares and such as a cause of the issues.
Is there anybody here that can shed more light onto this?
-edit-
More information: normally the phone fires some events when jacks get plugged in, these are also absent. I'm planning on dissasembling the phone and cleaning everything out with alcohol, just to be sure.
Though if it is a software issue it would be nicer to keep it closed.
You having flashed with the unbrick tool, and I assume the full update zip (>1.5 GB) to get the "fully stock", would lead me to believe it is a hardware problem. Both of those methods should have properly flashed the firmware.
redpoint73 said:
You having flashed with the unbrick tool, and I assume the full update zip (>1.5 GB) to get the "fully stock", would lead me to believe it is a hardware problem. Both of those methods should have properly flashed the firmware.
Click to expand...
Click to collapse
Yes, either hardware failure or firmware files that are not included in the unbrick tool (like those resting on ESF partitions)
Doing a search on Dirac control service stopped yields quite a few results of people sharing the same problem, and for who also a downgrade to nougat did not solve the issue. They seem to have needed a motherboard swap
So either the Oreo upgrade causes hardware issues in some cases, but not all, or the Oreo update messes up some firmware files in some cases but not all.
Had same problem on my OP3. Only thing which worked was downgrading to android 6.0.1
So the audio is working like a charm on 6.0.1 except the headphone jack, when I plug in headphones i dont get the headphone logo on top and the sound plays through BOTH headphones and the speaker
fizzk11 said:
So the audio is working like a charm on 6.0.1 except the headphone jack, when I plug in headphones i dont get the headphone logo on top and the sound plays through BOTH headphones and the speaker
Click to expand...
Click to collapse
You can workaround that using an app like SoundAbout, which can force playing audio on specific route
Okay so the problem is back after a day. This happened to me in the past, phone works perfectly fine for a while after flashing a rom or factory resetting, then out of the blue, using the microphone crashes the phone and problem is back. Really makes me think this is a software issue
Did the problem fixed? I have same issues. Please help??
Hi guys, same problem here, after repairing this OP3T the phone was working great when suddenly, the sound stopped working, i have no sound through ear, loud speaker, jack 3.5 neither... i replaced the loud speaker module thinking it was broken but nope, the problem persist... I´m on Oxygen OS with nougat.
Hey, I'm sorry to post on such an old thread but did you manage to find a solution? I'm pretty much facing the same issues.