yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] niksy+:
Any performance difference noticed with fresh Linaro toolchain together with Kayant's fixed flags? :)

*edit* Maybe share a Quadrant score, too? Just got 1307 on Quarx's 22/12 build together with JellyX CFS 22/12, clocked at 1.1GHz (interactive + zen scheduler)
[Defy Android Development] wskelly:
Here it is. I still have some background tasks... not sure how much impact that has.

I am at 1.0 GHz so I should OC and run again later. Would be interesting to compare all of the individual scores too perhaps?
[Defy Android Development] wskelly:
12/24 build with Kayant's compiler flags is posted at the link in the OP.
[Defy Android Development] slph:
Thanks again, will test new build today :)

Just to understand, you have a start-point-build from Quarx, and every time it needs to include his changes manualy, or every time you compiling build - all latest changes from Quarx includes automaticaly to your build?

Sorry for noob question, asking because of this commit.
[Defy Android Development] casouzaj:
Logcat for media issues with my NTFS card

Hi wskelly,

First of all, Merry Christmas!

Well, I've given your 12/24 build a try, and, as expected, the media issue (media process being killed whenever a media file (sound, video, whatever) is to be played, probably related to my NTFS-formatted 64GB card) is still present. Please, find attached the logcat file. Perhaps you can grab something there which would help you to pinpoint the issue.

Thanks, anyway,
[Defy Android Development] wskelly:
Yes, in general. The Android build system is kinda cool, I've never seen anything quite like it. Because there are so many different sources of code, basically the build manifest file dictates where all of that code comes from. Here is the manifest file I'm using:

https://github.com/skelliam/android/blob/jellybean/default.xml

You see all those tags that start with <project>, well you can see there where each individual 'project' that makes up the entire ROM comes from. In many cases they come directly from CM. In other cases I'm pointing to the repo from Quarx. In some cases (although not many) I'm pointing to my own repo.

Basically the workflow is like:

repo sync <-- this command will resync my repositories with their original sources

If I've modified files in those directories and never checked in those files, I manually have to merge my changes. If my repo is separate from the upstream one (the original maintainers) then I have to manually pull from those repos and then merge.

So right now I'm not doing a stellar job of resyncing with Quarx every day.

One thing I see missing from this system, people may agree or disagree, is some sort of method that says "all of these files belong in this build". There is nothing like that as far as I can tell. So if I wanted to reproduce the 11/17 from Quarx or the xx/xx from anyone, I don't see any way that I can make sure I have all of the files necessary to do that. There is no mechanism that *requires* all of the files to be checked in, in order to make a build. I can put whatever I want in the code, make a ROM, and then there is no guarantee that I can reproduce it. If someone has a better understanding I'd like to hear what it is....

I will resync everything and rebuild tonight probably.

Merry Christmas to all!
[Defy Android Development] casouzaj:
I understand what you mean. One thing which just came to my mind: if you picked a memory card of any capacity (i.e. not necessarily a 64GB one), and formatted it to NTFS, would you be able to reproduce the issue? Anyway, I'm afraid I'm stuck with Quarx's 11/17 build, because I posted this issue in his dev thread many times, but the most I got was another user ackowledging the issue, but no word from Quarx or any other member with a possible solution.

Thanks again, anyway.
[Defy Android Development] wskelly:
Oh casouzaj, this was not a response to you. :)

On your issue though, here is what is interesting in your log, and this is from the debugging stuff that was added:

V/MediaProvider( 2808): Attached volume: internal
V/MediaProvider( 2808): /mnt/sdcard volume ID: -1
E/MediaProvider( 2808): Can't obtain external volume ID even though it's mounted.

I am pretty sure this is exactly describing your issue:

http://epiccm.blogspot.com/2012/03/details-on-disappearing-sd-media-issue.html

So right now MediaProvider is already patched to solve one of the issues described there. Here is the patch:

http://review.cyanogenmod.org/#/c/13251/

And so the debug statements from your long CONFIRM that you have a condition that this patch was designed to fix, because the log shows that your volume ID is -1 or 0xFFFFFFFF.

The next fix to MediaProvider was here: http://review.cyanogenmod.org/#/c/13280/

One thing I did notice is that patchset #2 from this bug was NOT merged to Jellybean, however patchest #1 was merged. Both were however approved and it appears that both made it in to ICS but not JB. So, I just cherrypicked it and emailed the author. I don't think this particular patch is your issue though.

Do you have Google+ installed (looks like maybe you do based on the logcat)? It seems that the way Google+ handles one file might be implicated in this issue, if you read that entire post from blogspot.com linked above. None of this explains why the Quarx 11/17 does not have this issue though!

I am reverting a bunch of changes from around 11/17 or 11/18 that seem related to your issue, as well I've added the patchset #2 cherrypick, and resynced everything. Building now but i'm going to bed so hopefully it is done in the morning and didn't blow up.
[Defy Android Development] casouzaj:
Yes, Google+ is installed, and, by what I understood by reading the articles you linked above, it seems to trigger a full sequence of bad events. But, as you put it yourself, those bugs were identified and patched last March, still for ICS, not specificaly JB, although I think JB should have naturally inherited them, The kind of proof is that Quarx's 11/17 JB build, even with Google+ installed, simply doesn't have the issue. I may be heavily wrong, but newer CM builds seem to have lost those patches, somehow...
[Defy Android Development] wskelly:
Version 1226 uploaded, trying to fix ntfs card issue. Everything else synced with Quarx.

(Kept volume option, compiler flags, etc.)
[Defy Android Development] casouzaj:
Thank you! Downloading it right now...

EDIT: Unfortunately, the issue is still there, exacctly like always, even without Google+. Reverting to Quarx's 11/17 once again...
[Defy Android Development] ldiomedi:
Wskelly, I been using the 23th Rom for the last 2 days and for the10 first hours was really the best Rom I ever try, even the stock froyo. But after that time, some times the phone became unresponsible. Couldn't get a log yet, but I believe is something related to media server because the problem start when a sound event it's triggered. I change the kernel and for others hours the phone flies. But the problem start again. I disable almost all the sounds and the Rom is very smooth. Wiping cache and dalvik helps a lot, but just for 10 or 12 hours. I like how it works during that time, that's why still using it. When I get the log, I'll post here. And btw, very good work you are doing. Keep this way!

The thanks button doesn't bite. Try it!
[Defy Android Development] ccav2000:
Same problem related to sound has been reported by me and others in the main JB thread, it's not just in this special Linaro builds. There seems to be a problem with the sound handling, a user reported problems in interrupt handling, this is a kernel issue. I'm trying the JellyX kernel since another user claimed it is more stable.
[Defy Android Development] ldiomedi:
I'm using the jellyX kernel and I'm having the same problem. The latest kernel (22/12) doesn't work, not WiFi and signal network. I'm using the December 13 one

The thanks button doesn't bite. Try it!
[Defy Android Development] wskelly:
Okay, well I'll keep looking, at least we know what ISN'T the problem so far. :)

Thanks for the patience! If I can find a spare card I might try to format as NTFS to see if that is the issue.
[Defy Android Development] casouzaj:
Thank you very much! My part is just test each and every releases of yours. You are the one with an inifite patience, I'm afraid :D
[Defy Android Development] slph:
This bug with sound and lag famous, we have researched a bit

Short story: 48h uptime > sound lag > call lag > phone lag > outgoing call freezed phone

top:

User 0%, System 0%, IOW 100%, IRQ 0%

IOW 100%

Force reboot = bootloop,

I think, my Audio_out2 problem related to this (never seen it after)

Also, I have battery drain from nowhere. (even with your build :() But I've never has problem with sound lag (except Audio_out2 thing one time)

From my bbs log, huge increased alarms from this Kernel Wakelocks:

LD_usb_to_netmux

NETMUX_receive

GKI_LOCK_TL_MAIN_TASK_ID

GKI_LOCK_PROTOCOL_DRIVER_TASK_ID

GKI_LOCK_TL_MAIN_TASK_ID

COMMDRV_WAKE_LOCK

What is it, why it can happen on clean rom?

P.S. we have this feature?:)
[Defy Android Development] wskelly:
Well, I'm back from a nice vacation with my family over the holidays. I had my computer and had a chance to fool around a little bit, but not too much. I decided to try and incorporate the JellyX kernel from Blechd0se, but I couldn't get the result to boot. After wiping data and trying a couple of other things, I finally got it to boot, but when the battery went dead it wouldn't reboot and it was doing funny things when I tried to charge it. Performance WITH that kernel is however really quite good. I got a quadrant score and took a screenshot, I'll post later (I'm not on my phone at the moment). Very smooth response to touch actions/motions.

I found another bug with the ti wifi drivers, while at my folks' house I could not connect to a simple 3G wireless gateway device (my parents live in the middle of nowhere and this is the only option for broadband where they live). DHCP would fail and I have several logs of it happening. A couple of iPhones and other Android devices had no issues connecting to it. I was able to connect to it after multiple attempts, for whatever reason it finally worked, but then if I were to disconnect it would not connect again. So I spent some time looking at that issue but didn't get very far with it.

Other than that I have a new build based on some of the latest commits from Quarx. For casouzaj, I did exchange at least one email with the commiter of the patch that was to resolve your issue. His name is Mike Kasick. I described your issue and asked why the second part of his patch wasn't in JB. He told me that his patch wasn't needed in JB anymore. He said there were two commits that should solve the disappearing media issue:

[1] https://github.com/CyanogenMod/andr...mmit/ef9779b0e3339733c086a758a562581744da8dad

[2] https://github.com/CyanogenMod/andr...mmit/79087e4b967d8af26c488c41b8c1a087a12da84d

He also thought that the issue might be a bad/failing SD card, but I told him that was not likely since it works fine on a different built. He hasn't responded back with any other feedback but he did say this was the first time he's heard of a disappearing media issue in JB so far.

Probably my next posted build will include the JellyX kernel, or at least most of it, as soon as I can get it to boot reliably here.

Happy new year!
[Defy Android Development] casouzaj:
Glad that you have, apparently, spent terrific times during the hollydays, wskelly!

Now regarding the NTFS card bug, I'm afraid I'm not the only one facing it. Please, take a look at this post by 2Pints (and my follow-ups here and here). So, again, if you formatted a card of yours to NTFS it would be, at least theoretically, easier to pinpoint the problem.

Best regards,

Carlos
[Defy Android Development] slph:
Glad to see you :)

I can confirm what JellyX 30.12 cfs really more faster than default kernel. (more faster interface response)

I'll try to sum annoying bugs from main flood thread :) :

1) Ringtone bug, when phone uptime more than 30-36hrs - phone and sound become laggy. Flashing JellyX kernel solving this problem.

2) Somehow, people with MB525 green lense have batt drain with new Quarx's and JellyX kernels

With 31.12 Quarx build and 18.11 kernel (zImage only) - no batt drain (0.5-1% per hour), reboot then reflash to new 31.12 or JellyX kernel = battdrain 2-3% per hour. Reflash back to 18.11 - no batt drain again :) Bug started from ~05.12 and later, 28.11 can't test, 18.11 no bug.

I hope this commit will solve problem.

3) casouzaj problem with sdcard

I have only second bug (didn't tried to have 30+ hrs uptime, reflashing different kernels to find out what commit related to drain), so I can provide only #2 bug logs. They're here. /proc/last-kmsg is same with 18.11 and Jelly (strings exactly same, order a bit different, I think it related to cleanup commits)

Also, 29-30 builds have network connectivity bug, probably related to this. 'grep' command don't work when build installed with this 'new' updater-script, may be symlink problem? Be careful with merging this commit :)

Waiting your new build:)
[Defy Android Development] disadjusted:
experiences with MB526

hi folks, i highly appreciate this thread here, everything's so goal-focused :D

i'm on 12/31 build (the one from bytekiste.de because quarx server is unavailable and it's not mirrored on dhst) since yesterday and i can't confirm the battery drain issue. had mostly 0,6/0,7%h last night on wifi with full sync on (k9 & notification weather twice per hour). edit: sorry i just read it is only on green lense.

regarding the sound issues... on former builds i had not only sound issues on ringtones, but also random reboots on playing mp3s or ogg files... in combination with general poor performance while playing. and another, perhaps the most important experience: when shutter sound in camera (different apps) is on, after playing shutter sound, the preview framerate drops nearly by half and keeps. not experiencing this when shutter sound is off, perhaps this might be related to general sound driver issue or sth.?

just tried this (cam shutter sound) on 12/31 but this behaviour seems not to be the case now.

other guys (like slph here) mentioned sound issues become obvious only after 36h uptime... thought this might be due to the fact they used cam or other sound-related apps (even phone - @slph: can you confirm this?) in the meanwhile, but perhaps it's in fact just the uptime.

i even thought the whole google now lagging thing is related to this, since gnow uses both playing sound and recording voice... now on 12/31 even this is better but still not perfect.

so i can't await next linaro build with jellyX kernel... perhaps then everything will perform even better.

looking forward and both thumbs up guys! :good::good:

PS: sorry for not being able to provide logcat... won't post here furthermore unless requested...
[Defy Android Development] slph:
I didn't use sound related apps, only phone few times. Also, I use silient mode with vibro everytime.

My test: 31.12 Quarx rom + 18.11 Quarx kernel (zImage only)

0.4% per hour - bbs log for stand by period (7h)

Uptime about 35-36h, I called myself and everything ok.

Switched to sound mode - no ringtone played, but no lag

Switched to speakerphone - no speakerphone sound, but no lag

Set alarm - everything ok, alarm sound works.

(My sound tests should be in the end of logcat)

Looks like it is only ringtone\phone issue, but I didn't check ringtone after reboot, so it still uptime and alive, what can I test more?
[Defy Android Development] wskelly:
Thanks slph for the summary! I am not really following the main thread anymore.

Ok, well, we now have a build with JellyX (thank you Blechd0se) as well as Linaro-compiled everything else (kernel is compiled with Linaro 4.5.4 while everything else compiled with Linaro 4.7). When it booted I think it restarted more than once, your miles may vary. Anyway it did boot WITHOUT wiping data. I've also added the commit you referenced from Quarx to the JellyX kernel.

If it fails to boot, don't quite give up on it, try to wipe cache/dalvik again. If all fails you might try to wipe data but make sure you have Titanium backups of everything. I had one freeze during the boot animation and I had to pull the battery, then clear cache/dalvik again.

Regarding grep, it works in adb shell. I looked over that commit but I don't see a change there that would affect grep.

Carlos, nothing right now that would affect you but you're welcome to try this JellyX kernel out.

The build (cm-10-20130104-UNOFFICIAL-mb526.zip) is uploading to the OP link now. I have exactly five minutes experience with it on my phone so hopefully it doesn't introduce any major issues. :)

Also, I've branched every repo and pushed everything to github, so you want to build now basically use my /android manifest, then run the apply_linaro.sh script that Quarx wrote, after that just build. No other changes should be required.

--Bill
[Defy Android Development] wskelly:
Guys, so far this is very unstable.

Just had a reboot during an alarm, high battery drain, not good. Had to clear cache and dalvik to reboot.

Use with caution!

Curious about your experience.
[Defy Android Development] disadjusted:
Voltages?

With Default Undervolting by JellyX Kernel it was unstable for me, too. I raised the voltages to my own default values and it was better. Will try out your build soon, but perhaps that might give a clue.
[Defy Android Development] Maarren:
Red lens defy. (with normal voltages)

Installed fine, performance was fine. ROM got stuck after a few hours and could not boot anymore. Reinstalled quarx rom, but then noticed something happened to data partition. (all my setting were reset, but apps were still there). a recovery of previous data partition fixed it.
[Defy Android Development] wskelly:
I'm going to pull the build from the site; I just had a data partition issue also, not worth messing with it.

If you have it installed and everything is fine, I recommend you revert to something else asap... :(
[Defy Android Development] slph:
Installed, everything was fine (JellyX kernel really feels better at interface response).

Phone self rebooted and never boot after receiving sms :)

Clean caches and switching cpu settings didn't help, so I replaced zImage to 18.11 again.

For a temporary solution: wskelly build + kernel from 18.11 Quarx build - working correct for me, except led icon on charge, it blinking red, nothing serious.
[Defy Android Development] wskelly:
Removed kernel optimizations from Kayant and went back to plain gcc for the kernel build. I am not sure if optimizations are to blame or if the Linaro gcc is to blame for the instability but the latest version (4-Jan-2013) has so far been stable at least overnight and didn't experience anything unusual yet. I did wipe data to get it to boot, I am not sure of the reason for this but Blechd0se mentioned in the JellyX thread that this might be necessary. There is a 'kernel installation prep' script that can be flashed, I didn't try this but it seems there should be a *reason* to have to wipe data -- like a specific file or group of files that causes the issue. Maybe this kernel prep script helps with that. It comes from this thread here on XDA.

Now I will try to bring back Linaro for the kernel but won't post until I think it is stable. For now I'm using the one posted and no issues since last night.

Summary: Jan-4-2013 --> JellyX (compiled with vanilla gcc) + Quarx repo (compiled with Linaro 4.7)
[Defy Android Development] wskelly:
Success with Linaro 4.6 + JellyX

Holy crap.

@Kayant if you read this, the solution to Linaro 4.6+ with the kernel is here. I've just made the commit for this here. My android manifest includes the Linaro 4.6 toolchain as of last night, but you need to check out linaro_4_6_2 of my jordan-common repo, as well as make a symlink for the toolchain like so:

wskellenger@marquette ~/Projects/cm/prebuilt/linux-x86/toolchain $ ls -la
total 24
drwxr-xr-x 4 wskellenger wskellenger 4096 Jan 5 00:15 .
drwxr-xr-x 5 wskellenger wskellenger 4096 Dec 7 00:45 ..
drwxr-xr-x 11 wskellenger wskellenger 4096 Dec 7 00:45 arm-eabi-4.4.3
drwxr-xr-x 8 wskellenger wskellenger 4096 Dec 7 00:46 arm-eabi-4.5.4-linaro
lrwxrwxrwx 1 wskellenger wskellenger 93 Jan 5 00:15 arm-eabi-4.6.2-linaro -> /home/wskellenger/Projects/cm/prebuilts/gcc/linux-x86/arm/android-toolchain-eabi-linaro-4.6.2
lrwxrwxrwx 1 wskellenger wskellenger 91 Jan 5 00:10 arm-eabi-4.7-linaro -> /home/wskellenger/Projects/cm/prebuilts/gcc/linux-x86/arm/android-toolchain-eabi-linaro-4.7
wskellenger@marquette ~/Projects/cm/prebuilt/linux-x86/toolchain $

Prior to this commit I would get bootloops with Linaro 4.6 and 4.7 trying to boot. This time I just flashed it on top of the 4-Jan build, no data wipe, and it booted up successfully. Nothing weird yet. I'm headed out on some errands so we'll see how it goes today as far as stability.

Note this build is *not* posted yet.
[Defy Android Development] slph:
Latest build is good for me (but installed with full wipe, cleaining script, wiping caches didn't help me)

If you included this commit to 5.01.13 kernel, then, I can say it can't solve battery drain for green lense - min 2% per hour when phone untouched (18.11 twice lower, 0.5-1% more).

Here should be something, what included in kernel after 18.11... not sure what can be different with camera color, but drain reports only from people who have Defy with green lense.

Update: After manual reboot, phone got black screen and boot after wipe caches
[Defy Android Development] wskelly:
After literally HOURS of messing around yesterday, going to bed at 3a and getting up with my kids early this morning, here are the results:

Build JellyX kernel with:

Linaro gcc 4.5: boots, unstable

Linaro gcc 4.6: boots, no network available

Linaro gcc 4.7: bootloop

Gnu gcc 4.4: boots, everything works, stable

Quarx was (and maybe still is?) using Linaro 4.5 for the kernel, but his kernel doesn't have all of the tweaks that JellyX from user Blechd0se has.

So I've gone back to gcc for the JellyX kernel, they send to play nicely together. Still using Linaro 4.7 for everything else. New build just uploaded:

*Gcc for JellyX kernel

*Linaro 4.7 for everything else

*Put optimizations from Kayant back in

*Added a feature in recovery that will wipe cache and Dalvik automatically after updating from zip (I hate doing this manually). Default this feature is off but you will see "toggle cache + dalvik wipe" (something like that) next to "toggle signature verification" right before you choose zip from SD. (Of course you won't see this until after you flash and reboot.)

Carlos: just bought my wife a larger sd card so I will format her old one to NTFS and try it.

Quadrant with this build:
[Defy Android Development] casouzaj:
Thanks a ton, wskelly, for keeping attempting to solve the NTFS card issue! Eagerly waiting for a future release of yours addressing it! As Quarx's 11/17 handles my NTFS card just flawlessly, meaning that JB had the necessary patches/corrections identified last March under ICS, I suppose his newer builds (from 11/18 onwards) might have picked a different branch whilst synchronizing CM updates. I'd like to know your oppinion on this idea, if any and possible.

Thanks again, anyway!
[Defy Android Development] Fight4Music:
@wskelly, looks nice , i will try your latest Build, but which Version of jellyx should i use?

Gesendet von meinem MB526 mit Tapatalk 2
[Defy Android Development] wskelly:
@fight, JellyX is already bundled with the ROM. If you are already using JellyX, hopefully you don't need to wipe data. Make sure you have a backup.
[Defy Android Development] Fight4Music:
I used several jellyx version's, at last 30.12, but with it, i stucked in a bootloop (with quarx latest build).

So, TB is my best friend :D.

I will try and report back ;)

Gesendet von meinem MB526 mit Tapatalk 2