yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] nickpj:
I've been wanting to ask: Why is that? I've been trying to using CMCompiler, trying to download the source, using up any few gigs data left spare at the end of the month, and so far after 3 months of trying, it's up to 12 GB of source, and it's not even close to done downloading. I have no idea how much space will be needed all up, but let's guestimate it's 30 GB. How can ~ 30 GB of data possibly be required to build an 80 MB ZIP file? That's around 500:1 source:binary ratio, which seems so ridiculously inefficient that I must have misunderstood what's happening. Perhaps there is a huge amount of redundancy & duplication in that data? I had assumed it would be a core cyanogenmod tree, with a series of tiny diffs against that for each device (e.g. device XYZ has a hardware quirk with its camera, so apply this 2 KB diff to the standard driver for that camera to get it to work). Would I be right in saying that each device has an entirely separate source tree, reproducing essentially the same files over and over? Or if not, why does CM seem to need so much space? Is it taking a belt-and-braces approach, and building everything from scratch?

/me is baffled
[Miscellaneous Android Development] wbrambley:
What branch are you downloading? Also the source will have changed a bit in that length of time.

Sent from my U8150
[Miscellaneous Android Development] Hetfield666:
@aorth

i talked with ac1953, really a good dev who's rewriting part of audio backend.

in the meanwhile i kindly ask you to build a temporary libaudio with should fix all the remaining headset issues.

AudioPolicyManager.cpp ~line 126

case STRATEGY_SONIFICATION:

device = mAvailableOutputDevices & AudioSystem::DEVICE_OUT_SPEAKER;

if (device == 0) {

LOGE("getDeviceForStrategy() speaker device not found");

}

if (mPhoneState != AudioSystem::MODE_IN_CALL)

break;

just add the two lines.

99.9% of credits go to ac1953 :)

good thing is that you can make it upstream easily because it's our "private" lib.

asap you post the lib i'll test it.

thanks man!
[Miscellaneous Android Development] aorth:
Hmm. I tried building last night but I'm having problems with my build box. Didn't get a chance to fix it yet.

btw, what's the behavior in stock? I would assume notifications would go to the head phones?

It's just the way git works, unfortunately.

The CyanogenMod project is comprised of dozens of sub projects and has support for 50-100 devices. Each one of those projects has an associated git repository. When you clone the CyanogenMod repository you get the history of ALL the repositories involved in the CyanogenMod project.

See the CyanogenMod manifes to get an idea about information about just how many projects we're talking about: https://github.com/CyanogenMod/android/blob/ics/default.xml

The "manifest" is a list of projects which are in the CM project itself; it helps the repo tool manage all the ~100 individual git repositories.
[Miscellaneous Android Development] Hetfield666:
With headset plugged in

a) if in call, notification output in the headset (of course it means you're talking!)

b) else via speakers (you may be far from phone)
[Miscellaneous Android Development] psyke83:
@aorth & others,

Can you do me a favour? I'm trying to troubleshoot some potential battery drains with the kernel, and some output from a U8150 phone may help.

I need you to do this:

1. Enable wireless on your phone.

2. Find out the IP address used by your phone: adb shell ifconfig wlan0

3. Enable "ADB over network" in Settings -> Applications -> Development.

4. Make sure to close any open apps and leave the phone on the home screen.

5. Disconnect your phone from any USB source (very important).

6. Connect to your phone via ADB over the network. To do this, enter the following, where <address> is the IP address you discovered in step 2:

adb connect <address>

7. Begin to capture data from the kernel log*:

adb shell cat /proc/kmsg >suspend.log

*Make sure to run this command verbatim. Capture the log directly to your host - don't capture suspend.log from inside a phone shell (e.g. to the /sdcard/). Using the latter method would interfere with proper suspending.

8. While the logging is taking place, turn off the screen and wait 10-20 seconds, then turn the screen back on.

9. Repeat step 7 over a few iterations.

Please send me the resulting log via pastebin. I would also recommend that you do a run and view the kmsg log yourself (i.e. remove the >suspend.log), so you can see the behaviour of the phone while suspended. Keep an eye out for suspicious and repeating messages. You may also want to plug in a USB cable and see if the behaviour is different (but I need logs taken without a USB source).

Thanks!
[Miscellaneous Android Development] acejoker68:
LCD density

I love this rom its the fastest i have used so far but the lcd density at 120 is to much for my tasting i want it at 100 but putting it at 100 the status bar FC and so does half my program and ideas?
[Miscellaneous Android Development] aorth:
Alright, I misunderstood the point of the patch, but I'm still not sure what the default should be. Also, I haven't had time to observe the current behavior.

btw, I'm lending my IDEOS to someone for a week, so I won't be able to test much. I can still build, though (my build box should be fixed).

I'll do this tonight hopefully (seeing as nobody has helped you yet hahaha).

Try to get a logcat while it's crashing. Do you know how to capture logcats using adb?
[Miscellaneous Android Development] mitulvohra:
request for a .csv

can somebody please create a .csv audio filter having audio and sound quality of audiofix11 but without the pop sound...the new one has a lot of treble which doesnt sound good..and for that too i have to set dsp equalizer which eats up memory..i would have done it myself but as i have never done it before i am a little skeptical about doing it...also i am afraid that i may end up breaking my sound..
[Miscellaneous Android Development] aorth:
adb logs, for battery drain analysis

Hey, psyke. Here you go: http://paste.pocoo.org/show/583748/

That's ~1 minute of testing after a fresh boot (after everything settled). I turned the screen off after a few seconds, left it off for 30 seconds or so, then turned it on and swiped around the home screen for a sec.

All using the my latest (April 5th) nightly, which uses your old U8160 kernel source.
[Miscellaneous Android Development] May_11:
log for subpsyke

Hello.

I've made some logging as subpsyke asked.

pastebin.com/jm7Csua6

I didn't reboot before the test so it can be a bit messy.

Tested with the latest (April 5th) nightly.
[Miscellaneous Android Development] psyke83:
Thanks, it confirms that your phone is having the same issue.

First there's the "get_smem_clock: invalid start state 10c29" spam - maybe it's only cosmetic, I'm not sure.

What's more important, however, is that your kernel seems to be exhibiting signs of incorrect suspending. Look at lines 958 - 1046. Something is causing the kernel to continuously enter and exit suspend, even though it's clear that the phone didn't need to wake up (it does after line 1046, when the screen turns on).

I did some tests with the stock Huawei code, and this problem exists. After some trial and error I discovered that the constant suspend/resume behaviour seemed to be mitigated by TinyRCU, but I'm not sure if the problem is completely solved.

What's odd is that your kernel is already using TinyRCU (I think), so you shouldn't be seeing the bug manifest. Maybe if you also suppress the get_smem_clock kernel spam, it will prevent the kernel from waking from suspend needlessly. See: https://github.com/psyke83/codeauro...mmit/59d1f9d6df22c2d10de72e12045c04b07e037d5b

P.S. This kernel seems quite stable now, and battery usage is good (but I think can be improved even further).

---------- Post added at 09:16 PM ---------- Previous post was at 09:10 PM ----------

Thanks for running the test. Your log shows the "get_smem_clock" spam but not the suspend/resume bug.

I do notice something odd in your log:

<3>[4, events/0] [45534.582005] Setting EBI1 min rate to 160000000 Hz failed!
<3>[4, events/0] [45534.582049] Last successful value was 65000000 Hz.
<4>[4, events/0] [45534.582070] Setting AXI min rate failed (-22)
<3>[4, events/0] [45543.541702] Setting EBI1 min rate to 160000000 Hz failed!
<3>[4, events/0] [45543.541744] Last successful value was 65000000 Hz.
<4>[4, events/0] [45543.541767] Setting AXI min rate failed (-22)
<3>[0, swapper] [45544.784222] Setting EBI1 min rate to 160000000 Hz failed!
<3>[0, swapper] [45544.784222] Last successful value was 65000000 Hz.
<4>[0, swapper] [45544.784222] Setting AXI min rate failed (-22)

I think you may be using under/overclock values that are simply not working for your phone. You may want to change them if that's the case.
[Miscellaneous Android Development] nickpj:
Ah, yes, of course, because it's distributed, you need the full history for everything, and even if that's compressed, it's still a huge amount of data. And it is potentially useful if you want to find out who or when or what or why a change was made, and it does so without talking to a central server. Okay, fair enough.

I ran into this problem with the March version of this ROM. I plugged the headset in, called my brother overseas, and he was in the middle of another call and said he'd call me back. I put the phone down and walked away to the next room (and I didn't even think about it at the time, but of course I had left the headset in). Hours later I came back and found 9 missed calls, all from my brother trying and trying to call me back, but had not heard a single one, because it had rung into the headset. So I for one am strongly in favour of changing the behavour, so that it rings on the speaker if there is no ongoing call, or into the headset if there is a call in progress. That is what it "should" be, IMHO.
[Miscellaneous Android Development] itachilinux:
Hello, i wanna try to debugging battery drain as subpsyke asked...

I've connecting my phone to USB and i launch adb...

D:\kerja\adb>adb shell ifconfig wlan0

* daemon not running. starting it now *

* daemon started successfully *

wlan0: ip 192.168.2.103 mask 255.255.255.0 flags [up broadcast running multicast

]

OK it working... now i copy my IP address to connect and...

D:\kerja\adb>adb connect 192.168.2.103

unable to parse 192.168.2.103 as <host>:<port>

what should i do?
[Miscellaneous Android Development] acejoker68:
LOGCAT

This is my results from the force closures at LCD density 100

i uploaded the whole file the code below is just the pieces i think our the cause.

E/AndroidRuntime( 2300): Caused by: android.view.InflateException: Binary XML file line #21: Error inflating class <unknown>

E/AndroidRuntime( 2300):	at android.view.LayoutInflater.createView(LayoutInflater.java:518)

E/AndroidRuntime( 2300):	at com.android.internal.policy.impl.PhoneLayoutInflater.onCreateView(PhoneLayoutInflater.java:56)

E/AndroidRuntime( 2300):	at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:568)

E/AndroidRuntime( 2300):	at android.view.LayoutInflater.inflate(LayoutInflater.java:386)

E/AndroidRuntime( 2300):	at android.view.LayoutInflater.inflate(LayoutInflater.java:320)

E/AndroidRuntime( 2300):	at com.android.systemui.statusbar.powerwidget.PowerWidget.setupWidget(PowerWidget.java:126)

E/AndroidRuntime( 2300):	at com.android.systemui.statusbar.powerwidget.PowerWidget.<init>(PowerWidget.java:83)

E/AndroidRuntime( 2300):	... 23 more

there is a lot more but u will have to look through the log i dont want to take up all the forum. Any idea? also if you see any other issues let me know
[Miscellaneous Android Development] tulangabol:
Sorry...

May be we don't need key 164...

In stock rom huawei C8150 and U8150. Only have key 226, key 163 and key 165.

key 11 0
# begin BU5D02300 modified by liuyongming00163001 20100203 add headSetHook key value
key 226 HEADSETHOOK WAKE
# end BU5D02300 modified by liuyongming00163001 20100203 add headSetHook key value
#/* < BU5D09842 weixinghai 20100513 begin */
key 163 MEDIA_NEXT WAKE
key 165 MEDIA_PREVIOUS WAKE
#/* BU5D09842 weixinghai 20100513 end> */

key 158 BACK WAKE_DROPPED

I'm only add that line/value in qwerty.kl

key 11 0
key 226 HEADSETHOOK WAKE
key 163 MEDIA_NEXT WAKE
key 165 MEDIA_PREVIOUS WAKE

key 158 BACK WAKE_DROPPED

Thank you

This is my log:

Suspend1.log

http://pastebin.com/HY8jA8nj

Suspend2.log

http://pastebin.com/LAd3XLKR

suspend3.log

http://pastebin.com/K78TF9mK

suspend4.log

http://pastebin.com/hwQX8iBD

May be suspend2.log good for me ( I can read clearly than other).

Thank you
[Miscellaneous Android Development] acejoker68:
i was also wondering compcache does it do more harm then good when playing a game say angry birds i have V6 supercharger setup so shouldnt i be able to run with out compcache? giving my cpu less load so it can use it more for the game? or does the compcache help angry birds or anyother game run better?
[Miscellaneous Android Development] tulangabol:
That script suggest to disable compcache if you got lag. But ideos have little ram.

May be you can set compcache to 10...

I set vm heap size to 32 or 48...

I think that good for me...

Sorry for my bad English
[Miscellaneous Android Development] acejoker68:
ill have to try running it at 10. with it off loading at the begining is painful but after that its speedy. I was thinking of a swap file any ideas good or bad on that? i currently have everything i can on my ext partition through s2e like cache and apps. that its self seems to run faster for me because yea that apps load last but the system dont get stressed at the begining. I have class 6 sd card
[Miscellaneous Android Development] tulangabol:
I have swap too. If i write 'free' in terminal emulator. That swap always eat my memory (i suspect swap are running)

I'm modified with another script too. Modified read_ahead_kb in:

/sys/devices/virtual/bdi/179:0/read_ahead_kb;

Default this port are 2048. I change to 512

(I think this can booster my sd card)

And

/sys/devices/virtual/bdi/253:0/read_ahead_kb;

/sys/devices/virtual/bdi/7:0/read_ahead_kb;

/sys/devices/virtual/bdi/7:1/read_ahead_kb;

/sys/devices/virtual/bdi/7:2/read_ahead_kb;

/sys/devices/virtual/bdi/7:3/read_ahead_kb;

/sys/devices/virtual/bdi/7:4/read_ahead_kb;

/sys/devices/virtual/bdi/7:5/read_ahead_kb;

/sys/devices/virtual/bdi/7:6/read_ahead_kb;

/sys/devices/virtual/bdi/7:7/read_ahead_kb;

/sys/devices/virtual/bdi/default/read_ahead_kb;

Default this port are 128. I change to 512

(I think this can booster internal memory)

I think 512 enough for me (i have sd card class 4)...

Sorry for my bad English
[Miscellaneous Android Development] ntnlzr:
did you try to setup overclock min freq. to 122 or similar value(normally there is 60mhz) ?
[Miscellaneous Android Development] trekker99:
Cool! Just one thing, the downloads seem to be only served on fileserve who has taken file sharing offline. Are there any mirrors? Thanks.
[Miscellaneous Android Development] GJSmith3rd:
I haven't noticed a problem with capacitive keys except I wish they had haptic response for tap and press.
[Miscellaneous Android Development] aorth:
Hmm, what you're describing is related to this patch: https://github.com/alanorth/kernel_huawei_u8160/commit/209786f5b7b2d7dc45b2918c8a49e554f322f78f

It adjusts the position of the "Home" softkey. If you have time (I don't right now), you could look at playing with those values ;)

Hmmm, not right now. I should upload it to more sites, you're right. I'm currently out of town on business (all week), so I'm limited in what I can do. Maybe someone else can upload it for you? Check the md5sum!!
[Miscellaneous Android Development] trekker99:
I have mirrored some of the files aorth had online here: http://www.mediafire.com/?8q2p44sx456pr

The Dec 5 one should appear soon (still uploading at this time).

If you require any other files from what aorth has been sharing, let me know, I will see if I can upload them. Give me 24 hrs though as I can only do this in the evenings.
[Miscellaneous Android Development] Trekker56:
Thnx.

We have similar nicks :p
[Miscellaneous Android Development] trekker99:
Actually I was referring to the splash screens veer1238 has in his threads. Sorry for the confusion. Well I hope my links (apparently for myself haha) will benefit someone anyway.
[Miscellaneous Android Development] Hetfield666:
what about battery usage and headphones bug?
[Miscellaneous Android Development] trekker99:
Oh and aorth, I am willing to continue maintaining a mediafire mirror as long as I still use this phone. Your mirrorcreator link for the jan17 nightly is still okay (that probably explains why the jan17 upload was so quick while the dec5 is slow). Your minus.com link is rather confusing. The only way I could grab CWM was to download your whole folder (clicking on other links just bring me back to the download page?? Or I am just not clicking on the right things).
[Miscellaneous Android Development] ALESSIO94x:
Only a word for describe this ROM... Amazing!

Just a little question... is there any way to disable the unlocking feature by touch menu button?
[Miscellaneous Android Development] trekker99:
Battery usage seems fine to me. I do use JuiceDefender Plus though. As for the headphones bug, which one are you referring to? As aorth mentioned in the first post, there are a few "lost" bugs as the previous thread got a bit too big and some less serious bugs has fallen through the cracks.

My $0.02 to anyone asking about resolution of old bugs which is not mentioned in the first post to give a summary of the bug.:)

---------- Post added at 04:14 PM ---------- Previous post was at 03:52 PM ----------

Yes, this happens to me too.

I can also confirm the change in LED behaviour (I hesitate to call it a bug). It remains always on when there is a notification waiting (I don't remember what it should be) and always off when there is no notifications (it should be blinking green). I just started using these builds, so I have no idea whether it has always been a problem or did a patch for something else broke this. Anyone with any idea?
[Miscellaneous Android Development] Giogts:
no no, i love this feature

you can disable it only in your rom, search in build.prop

------------------------

Please someone can test headphones during call and say if they works?
[Miscellaneous Android Development] ALESSIO94x:
Where exactly? I also tried to disable/enable the "Menu unlock" feature into Cyanogenmod settings but it doesn't work. Can someone tell me how to disable this feature? Thank you ;)
[Miscellaneous Android Development] aorth:
Hhaaha no, Hetfield666 is an old timer in this thread. He has a bug with his headphone audio, I can't reproduce it... :( I actually think it only affects some phones...

Thanks for mirroring it. In the future I'll upload to a few different sites, I don't mind doing that.

I agree Minus.com is really confusing. I swear that link for CWM 5.0.2.7 used to be a direct download... I think they changed it. I've updated the first post with an updated link that should direct download.

I haven't done any extra work on audio so I bet the bug is still there. As for battery, it's not as good as stock yet, but I haven't looked into it any more than a few "optimized" kernel patches...
[Miscellaneous Android Development] tilal6991:
Hey Alan:

Just wondering if you are going to stick to developing gingerbread or you are going to move to ICS. ;)
[Miscellaneous Android Development] aorth:
Hehe, I think I'll stick around at least until CyanogenMod 7.2 comes along. I'm pretty busy at work lately, but I'm still around. :)
[Miscellaneous Android Development] tilal6991:
Good good. I've been doing more work on it and I think its fairly stable now. Fixed the final major bug of phone crashing. Basically just camera to go :)
[Miscellaneous Android Development] Hetfield666:
yes right!

i'm monitoring releases cause i need headphones

bug for me is easy to reproduce: plug stock headphones, make a call, bla bla bla, hang up, try another call, no output from headphones.

plug/unplug doesn't fix, a reboot does. of course you can understand that rebooting each call is not feasable.

some reinit must be called after hangup. actually music app work fine.
[Miscellaneous Android Development] trekker99:
Ahh ok, I vaguely remember some discussion on the previous thread... I don't have the stock headphones, but I do have the headphones from my Galaxy Tab 8.9, I might try it this weekend if I remember :p
[Miscellaneous Android Development] smashman42:
I had the same bug tho my u8150-D (synaptic/multitouch) is "retired" now, was hoping to learn GIT & stuff & maybe help figure it out but hasn't happened past getting a working build environment.

Both the OEM headset & aftermarket ones have the bug for me & I think it happened for the first time on my P990 today too, this bug on the GP0 sounds similar except for me the first call works ok through the headset, then all call audio is broken but music still works (as per Hetfield666 I think?)

Edit: this is a pure CM7.x bug, wasn't present in the Gingerman builds so Tilal must have done something differently with the audio from then to now.

Also I'd noted in the other thread that the headset button no longer pausing/unpausing the music player arrived at the same time as the headphone glitch so they may be related
[Miscellaneous Android Development] mayurh:
help boot loop

guys i downloaded april 5 update

isntalled,worked fine, installed gapps, updated apps

all was going well decided to do a reboot

and then it got stuck in a loop at the cm7 boot screen

? why?

booted into recovery

wiped and installed again, now it will not go beyond "touch the android " to continue

it doesnt accept my touch, and after few seconds cm7 bootscreen appears again?

:confused:

help please
[Miscellaneous Android Development] veer1238:
Did you flash gapps that are for our device? Mdpi version?

Just go to recovery wipe-data/factory reset

Then go to advance and WIPE SYSTEM PARTITION. And flash rom again.
[Miscellaneous Android Development] mayurh:
hi there

thanks

yes i do have the mdpi version but didnt even get a chance to flash it

anyways

an update

i did wipe system partition and then install again and its now ok

thanks dude

not sure why cwm didnt wipe it with wipe-data factory reset

all ok now :)
[Miscellaneous Android Development] veer1238:
Glad it worked out for you! :)
[Miscellaneous Android Development] aorth:
Test this boot image

Can someone try to boot this for me? It's the same as what we're using now, but the kernel is compressed with gzip instead of lzo. lzo is faster, blah blah blah, but I think it's causing the CM7 build system to fail (I believe it expects gzip-compressed kernels). I just compiled it but I don't have my phone this week so I can't test it.

Download: MediaFire (md5: 530144f50bf8a580962a4313d634d2f8)

Flash: fastboot boot april19_gzip_boot.img

You should flash with your phone in bootloader mode (Volume down, Red, Power). "boot" will just boot the kernel once, btw (as opposed to "flash" which rewrites the boot partition). So if it doesn't work you'll be fine!

Thanks!
[Miscellaneous Android Development] Hetfield666:
@subpsyke

in aorth's log i see several oops in the kernel too.

did u address those in u8160 kernels?

plus i see, at startup, some init error on i2c and gps modules...
[Miscellaneous Android Development] nico202:
Hi aorth,

First time using fastboot, however, it booted. It returned:

< waiting for device >

downloading 'boot.img'...

OKAY [ 0.205s]

booting...

OKAY [ 1.954s]

finished. total time: 2.160s

And the phone is running. Don't know the boot time, however.

uname -r gives: 2.6.32.9-perf, if it does matter.
[Miscellaneous Android Development] itachilinux:
i can't get the different... o_O
[Miscellaneous Android Development] itachilinux:
to aorth, i've using your april19's kernel... this is my screenshot...
[Miscellaneous Android Development] acejoker68:
BUMP
[Miscellaneous Android Development] aorth:
Good, thanks. :)

That's the point, there is no difference in the kernel itself. I only changed the compression of the kernel from lzo -> gzip.

Looks good. :)