yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] hotdog125:
The audio cutoff is more pronounced in CM10.1 though. I tested the camera JB+ app with a 7 minute video with different ROMs. On CM10.2 the audio got cutoff no matter what I tried.

In CM10 the audio stayed till the end with no cut (Camera JB+ with overclock). With CM10.1 I could reduce the cutoff to a minimum, not fully.

Another small thing about Slimbean 7.8 and 8.1. Switching from the normal notification bar to the quick settings is not smooth. In the first Slimbean version it was perfect like CM10.1.

I have to agree with you about the video problem though.
[Defy Android Development] Blechd0se:
Good evening :)

Had some time to make another update. Short changelog;

* changed the behaviour of interactive in terms of scaling up to max_freq instead of hispeed_freq

* patched in google's sync driver for android

* backported the cgroups timer slack controller

* some little fixes, check out github

* (and of course all previous changes in case you missed it.)

Yep, the last change is quite interesting. It also requires a modified ramdisk, so this update contains a modified ramdisk by me.

I attached both CM10 and CM10.1 zips. The one for CM10.1 should also work for CM10.2, but keep in mind i have only tested

it with CM10.1.

The following is confusing and can cause headaches. Be warned.

So you are probably asking yourself "what about ion?". Well ion is tough. Everything looks, it compiles, it boots up, it

registers the ion_device properly. The funny part is the initialization; on our 3.0 branch we use module_init(ion_init) to

load the ion driver like a module. On 2.6.32 we have to use subsys_initcallion_init) otherwise it wont even boot and we

have no clue why. Now the subsyscall has some special thing; its order of execution and because of that the ion_device

can't allocate its memory and can't use anything.

So here is what i assume; because of the very early init the ion_device tries to allocate memory thats not ready yet and

therefore fails. With module_init(ion_device) this is probably no problem because it gets way later initialized. Now we have some

other devices that gets memory allocated that early, namely our gpu or the be more precisely vram. In fact it gets allocated

right before the ion stuff is happening. Also i assume the problem is not related to our driver/gpu/ion driver instead i think

the problem is in our platform code namely in arch/arm/mach-omap2.

To put even more questionmarks in your heads; the current nexus 4 kernel head uses ion too. But they init it with subsys_initcall.

As i said, pretty tough.
[Defy Android Development] woodman:
Good evening :)

Thanks Blechd0se, I'm going to flash this for cm10.1 and I will do a feedback if I can notice something interesting.

EDIT 1: Flashed and 1st boot OK. Very responsive so far.

EDIT 2: Everything is still working fine. Good battery life, google's sync OK, cpu scaling behaviour OK. No wake up delay.

Sent from my DEFY green lens

CM10.1 ROM by Quarx (2013-07-09 build)
[Defy Android Development] TJKV:
Are the ramdisk changes the ones described in this commit message?
[Defy Android Development] slaphappy76:
Hello,

my Defy + with 4.3 would only start to boot animation with the latest Blechd0se Kernel.

I hope there will be a solution :)

Slaphappy
[Defy Android Development] ccav2000:
Exactly the same problem here with CM10. Unable to get past boot animation (green led never goes off). Cannot boot with this.
[Defy Android Development] niksy+:
+1 I must say, [MENTION=4855459]Blechd0se[/MENTION]. ON CM10.2 it's stuck in an infinite boot animation with the red led turning on every 4-5 seconds... I guess it's actually in an infinite reboot-loop :D
[Defy Android Development] yogesh324:
[MENTION=4855459]Blechd0se[/MENTION] i m using this kernel right now but after flashing it option to change zram disappeared i m using illusion rom by [MENTION=4173406]Kayant[/MENTION]
[Defy Android Development] Blechd0se:
No, on github are only kernel changes :)

For those with anything expect cm10.1, where can i find your logs? Its probably the ramdisk, but logs would be helpfull.

I disabled swap and zram in this release.

Send from my Nexus 4
[Defy Android Development] woodman:
I'm just wondering, for those with bootloops issue, zram which have disappeared from performance parameters could be a clue. I don't know what should happen if we flash last BlechdOse's kernel over a ROM which have zram or swap activated.

As I said in my previous post, I had no problem with cm10.1, I flashed it over the last PURE Quarx rom (2013-07-09).
[Defy Android Development] Blechd0se:
I disabled zram&swap because i have to talk to Quarx about this topic and because i haven't recieved any feedback

regarding those features in the past.

Like i thought the problem was the ramdisk, so i just updated my earlier post with proper ramdisk changes for all CM-Versions.
[Defy Android Development] ccav2000:
What kind of feedback? I have already stated that my belief is that for our device to be usable with the latest android versions technologies like zram are necessary. It has to be a fast type of compression otherwise lags are introduced. For swap, I wouldn't use it, would wear out my SD card fast.
[Defy Android Development] hrk:
I agree with you, adding that I like KSM more than ZRAM :)
[Defy Android Development] Blechd0se:
The only reason why Quarx disabled swap is because of /data corruption. My past releases had all swap&zram enabled to prove,

that this /data corruption has nothing to do with swap&zram, however if none of you post something like "i have no /data corruption

with your kernel" then we won't flip the switch.

I like to enable, because of my recent patch-series, but i don't want to read something like "halp my device wont boot".
[Defy Android Development] ccav2000:
There was one time in the past month I had issues with /data failing but I was using stock Quarx's kernel, had no zram or swap on. And I'm convinced it happened because I tried to reboot the system too early before it had settle down from the previous boot.

My personal observations suggest that zram / swap have nothing to do with the problem. But that's just me.

Btw, the kernel with the fixed ramdisk works.
[Defy Android Development] trurl3:
Is there any fix for lack of voice in telephone connections when BT is ON? The telephone rang, but after that is only silence... It looks like nobody have problems with it. Is it only me? I tried several ROMs either CM10.1 and CM10.2. On Cm10 all is OK. I think I will have to downgrade albeit very reluctantly.
[Defy Android Development] ccav2000:
It's a known problem and no, no fix currently. To make or answer phone calls BT must be off in CM10.x.
[Defy Android Development] Proverbs2:
I have been using your 29.07-cm10.1_V2 kernel with Quarx's July 9th nightly since it was released, with zram enabled at 26%. I only had the data corruption bug once, when I intentionally let the battery drain to 0% to test if that would cause the problem (which it did). The zram made a noticeable performance improvement, and I'd love to try using it with your latest kernel. If you would make a version with zram enabled, I'd be grateful.

By the way, I flashed your 25.08-cm10.x kernel last evening, and it has been working very smoothly so far. 12 hours uptime, and it still seems fast and stable, with low battery consumption.

Many thanks for your work!
[Defy Android Development] sterankin:
Hi - I flashed CM 10.1 on my wifes Defy+ to try and improve speed and stability.

Unfortunately she has call issues (which I have just found out is due to BT being on!).

I don't yet see a fix for this. But I was wondering if there was a stable ROM that could be used as a daily driver.

Link would be great (and to the necessary gapps also).

Thanks
[Defy Android Development] hotdog125:
MS2Ginger, CM7.2 or to a certain extent even CM9 is good enough as a daily driver.
[Defy Android Development] GuustFlater89:
I use CM10 for several months now as daily driver without issues. Specially 3july13 and most recent Unofficial build of this August are good! I do not see problems to use CM10 as daily driver....
[Defy Android Development] bone101:
Installed Kernel .....

Boot up .... fine...

Android 4.3 Cm10.2 quarx last build
[Defy Android Development] sdrawkcab3:
I'm testing the 10.2 version on a Bravo running the most recent 10.2 build. So far so good, except for soft button coordinates. Anyone know if there's a simple way to edit those coordinates, or would that take a recompile? (I'm not set up for that...)
[Defy Android Development] Anton111111:
Does "BT Headset" work with this kernel on 10.1 ?
[Defy Android Development] eliseo486:
question

work deep sleep in this build??? kernel_25.08-cm10.1.zip of Blechd0se
[Defy Android Development] hotdog125:
BT Headset will connect but audio won't be good. This isn't fixed yet.

Yes, latest kernel gives deep sleep.
[Defy Android Development] bonedriven:
Google plus is not compatible with my phone? Why?

I can't fix it by

1.changing dpi

2.apply a multi dpi patch (both white and inverted) which include:

1). flash patch

2). clear play store and google service frame data, reboot

3) clear play store data again, not working

4) delete google account, reboot, add google account, delete play store data, reboot

---------->Still, "google plus is not compatible with your phone" in the end.
[Defy Android Development] signs23:
Searched for it but didnt find a solution,flashed this build after 4.3 but same problems, the home button isnt working, also the statusbar have some problems, cant open settings etc.. would be nice to know what do to against not useable home button, i did a full wipe befire flashing cm10.1

Gesendet von meinem GT-I9001 mit Tapatalk 4
[Defy Android Development] bonedriven:
Flash it again sometimes sovle various problems. I had weird problem after the first flash, then I flashed it again, especially you are from other ROMs. Just my 2 cents.
[Defy Android Development] atulclassic:
try to reduce the size of zip before flashing and use minimum gapps by tejus.

---------- Post added at 04:26 PM ---------- Previous post was at 04:24 PM ----------

which phone you are using?
[Defy Android Development] bonedriven:
Defy? It's a green lense defy but I accidently flashed a defy+ full sbf, and then get it rooted and installed CM10.1. But that's another story.

I wonder what is the cause of "Google plus is not compatible with your device". I have tried most things I can find but it's still there" Google plus is not compatible with your device". I am planning to flash another ROM, if no solution is available any more.
[Defy Android Development] Antiga Prime:
Booted up fine with [MENTION=4148153]TJKV[/MENTION]'s Slimbean 8.1.
[Defy Android Development] TJKV:
Slim ramdisk has a few differences from CM ones. Will boot fine but there might be problems, no idea what kind though. If [MENTION=4855459]Blechd0se[/MENTION] can tell me what modifications he made in the ramdisk I can upload a proper one :)
[Defy Android Development] Blechd0se:
No problem; update init.rc with the following;

mount cgroup none /dev/cpuctl cpu

becomes

mount cgroup none /dev/cpuctl cpu,timer_slack

and add the last line to the following;

write /dev/cpuctl/apps/bg_non_interactive/cpu.shares 52
write /dev/cpuctl/apps/bg_non_interactive/cpu.rt_runtime_us 700000
write /dev/cpuctl/apps/bg_non_interactive/cpu.rt_period_us 1000000
[B]write /dev/cpuctl/apps/bg_non_interactive/timer_slack.min_slack_ns 100000000[/B]

In my ramdisk i also changed rights for /proc/last_kmsg to 0771 in 4.2 and 4.3, because i want to fix that feature.

However the point with the new timer slack controller is; it may get you better battery life, but the thing is

i can't mount it in userspace and i have not clue why (mount -t cgroup -o timer_slack none /sys/fs/cgroup).
[Defy Android Development] jassi32:
[MENTION=4855459]Blechd0se[/MENTION] -- i tried your latest kernel on Slimbean 8.1 --

following r the observations ---

1.opened around 12 apps and kept them running in background overnight to see , ram n any performance issue , all was fine , same free ram around 200 MB, no lag at all in morning , switching between all apps was smooth

2.Deep sleep is perfect as it should be ..

3.I was on deadline earlier , when switched to SIO , i felt more smoothness in apps opening and multitasking thing ....

4. Battery drain is normal as it should be

5. Uptime is around 25 Hours ,

POINT -- when i saw battery stats , I saw strange loss of signals , marked with red line and in between white line , this happened only when i enabled DATA (2g)

i never used data(2g) before , just used coz i had a prob with my router .....

thanks
[Defy Android Development] TJKV:
Thanks a lot :)

Are these changes considered as "experimental" or will they be present in all future builds? If it is permanent then I'll push it to the system_core branch so I won't have to edit the ramdisk every build.
[Defy Android Development] Blechd0se:
Thanks for the feedback :)

1.) 200 mb ram? How did you measure that?

2.) It should be even slightly improved :)

3.) Its really rather a personal thing than a observation. I just like deadline on all my devices.

4.) Should be also improved, especially when its idling.

5.) Sounds more like a random problem. I don't think its kernel related.

Consider those as stable i like the controller :), maybe i do more ramdisk-changes in the future. I probably have to make a pull request for Quarx Repo.

Btw. if you find a way to mount it from userspace, let me know :)

[MENTION=4280775]bonedriven[/MENTION]

Did you consider a full wipe?

[MENTION=4672331]signs23[/MENTION]

You said you flashed 4.3 and then you said you flashed cm10.1. Whats true?

Some users reported of a none working homebutton, you can post a logcat/dmesg output if you have done

a full wipe.

And if you are on 4.3 (aka cm10.2) keep in mind that its still in a early CM-stage, where bugs are granted.
[Defy Android Development] Antiga Prime:
I know that you weren't asking me, but since you did ask someone, I generally always have at least DS Battery Saver, Nova Launcher, Whatsapp, Setvsel and Touchpal Keyboard running with 188mb free of RAM. If I kill Touchpal and use the inbuilt AOSP 4.2 keyboard it goes up to 200mb of free RAM.

I must add my Whatsapp process uses about 40-60mb of RAM, which in itself does seem weird since I've seen other people's use A LOT LESS, but it might be due to the fact that I have lots of active chats.
[Defy Android Development] biernus:
[MENTION=4855459]Blechd0se[/MENTION]

I upgrade your newest kernel on newest ver. of quarx firmware CM10.2 (i know its experimental) but... before install your kernel i dont have problems with "showing number when calling". I have this problem few monts ago on early version of 10 or 10.1. Problem is when phone lies on table (lcd off) and somebody call - of course - i have this person in contact list. First... lcd is on (im sure! its more laggy then before your kernel) then i see number but 'name' is on after sometimes 10 second of ring!.
[Defy Android Development] Anton111111:
After install 10.1 kernel, os doesn't start. I see boot animation and system doesn't start.
[Defy Android Development] Arathon:
hi i noticed a strange behavior with the latest CM10.1 rom on my Defy Red (with or without Blechd0se kernel) after some time (fron 2 hours to 12 max) the phone will remain frozen and i can't wake him (screen black but sometimes the phone is hot), so i decided to do a logcat and here it is (it's the first time i do this so i hope everything is fine).

EDIT: couldn't upload the log because it exceeded the file size limit so here my google drive link:https://docs.google.com/file/d/0B8qd5ysy8H-cZVFhUFQ2bVlNVEk/edit?usp=sharing

EDIT sorry i forgot to set the link to public, btw i had another 3 freezes and a reboot, I'm now recording with Logcat so for the next freeze i'll upload the new file.
[Defy Android Development] frozenwaverider:
[MENTION=4855459]Blechd0se[/MENTION] thank you for your new kernel, I have been running it for 2 full days now and my ph seems a lot more snappy, not just because of cache wipes as I do them about every 2 weeks to help stop slow downs and had done this in the weekend

Funny thing though, in the first few hours I had 4 random reboots(2 in a row, no data loss) and a RIL notification which I ignored as I was on the web and sending/receiving texts at the time so it was a false notification

After that it has settled down and is very stable with same battery life(I am on CM10 sunnyqeen unofficial build from quarx git with excellent battery life) but better performance! :)

Thank you

MB525 Red lense
[Defy Android Development] Proverbs2:
I just encountered the corrupted data partition bug again, this time on the latest kernel (25.08-cm10.x), which has zram and swap disabled. So, I don't think the problem is related to zram or swap. In both cases where I encountered the problem, I used a CPU-intensive app (Firefox with a streaming video website) to run the battery down to 0%. After the phone shut down due to low battery, it wouldn't restart: stuck at the bootanimation. I tried pulling the battery and restarting, still stuck at the bootanimation. Wiping cache and dalvik and re-flashing the rom didn't help; I had to restore a TWRP backup.

EDIT: The problem appears to be reproducible. I just got the data corruption bug again, after running the battery down using StabilityTest.

If there is anything I can do to help with debugging this issue, please let me know. Meanwhile, I'd love to have zram back again, especially since it doesn't appear to be related to the data corruption issue. Your latest kernel is really fast, and zram would make it even better!

Thanks again!
[Defy Android Development] gkovacsp:
Funny you say that. I just had 2 data corruptions in the past two days. I had no idea about the reason, but my battery was pretty close to 1% both times.

I've never had such a problem before, although I never allow the battery level to be so low.

Running the last Quarx release (07/09)
[Defy Android Development] Proverbs2:
Which kernel were you using? The one included in the Quarx build, or did you flash one of Blechd0se's kernels?

Edit: By the way, I've never had the problem when the phone was powered down manually. A simple workaround for now would be to create a script that powers the phone off when the battery reaches 3 or 4 percent.

Edit2: In case this helps with debugging the issue: the last two times that I ran the battery down, I noticed that it stayed on 1% a lot longer than it did with earlier roms like CM7. I wonder if the low battery isn't triggering shutdown like it's supposed to, and the phone just gets stuck on 1% until it dies. If that's the case, maybe pulling the battery will have the same effect. I'll give it a try and report back.

Edit3: The phone booted normally after a battery pull, even though I had both Firefox and StabilityTest running. At least in my experience, the data corruption problem only happens when the battery dies.
[Defy Android Development] gkovacsp:
The one in Quarx's build.
[Defy Android Development] Proverbs2:
That's what I suspected. More evidence that the data corruption bug has nothing to do with zram or swap. Maybe it's not even a kernel problem?

Would anyone here be able to create a script (or a patch, or an Xposed module) to power off the phone before it reaches 1% battery (say at 2 or 3%)? That might serve as an acceptable workaround, but I don't know how to do it. I'd be happy to test the script if someone else can create it. Thanks in advance!
[Defy Android Development] sukano1:
Data corruption happened to me twice already when the phone crashed without an empty battery, so I guess 0% battery is not the root cause.

Also consider that some after-market batteries reach 0% after about 40% of the actual runtime due to battd issues, so any such script should be optional!
[Defy Android Development] Arathon:
Maybe i founded the cause of the freeze, i deactivated GreenPower Premium and since that i didn't have any freeze, but the reason why this happens is unknown for me.
[Defy Android Development] Blechd0se:
I guess its kind of the root. In some of my test cases i could reproduce it when the device was inappropriate shutted down, but thats really

hard to tell and not easy to debug.

Last time i checked you logcat i couldn't find any suspicious on the first sight.

That's what I suspected. More evidence that the data corruption bug has nothing to do with zram or swap. Maybe it's not even a kernel problem?

Its probably kernel related, because its corrupting something. I did enable a safety flush a while back for kernel panic,

maybe i have to check it again.

Anyway, new nightly today!

Nothing really special, except for TRIM-Support :)

Changelog;

* Trim-Support for ext3/ext4, therefore enabled discard in ramdisk (e.g: fstrim -v /data )

* enabled back swap&zram because of popular demand

* small cleanups and fixes (check github for more)

I am tired so no more infos today, as always only tested on 4.2. Happy flashing :)
[Defy Android Development] eliseo486:
Im going to test cm10.1 version !! XD:victory:
[Defy Android Development] jassi32:
[MENTION=4855459]Blechd0se[/MENTION] --

Flashed you latest kernel on SB 7.8

wiped cache/dalvik ( this time only , else i just flash and it works too)

On start up , everything was laggy , and suddenly everything , nova , G+ , weather widget , gmail etc etc , crash -- all were stopping (error) and cant go ahead

after that i restarted - still LAG on start up for 1-2 mins , after that it works fine

Interactive + Sio , no other setting enabled ......
[Defy Android Development] TJKV:
Slimbean needs a different ramdisk. What Blechd0se uploaded will work properly only on CM.
[Defy Android Development] jassi32:
but after 2nd boot till now , things are good , can't say about later ....:confused:

i will use it , and will report , how it goes .....

so can you do something about the ramdisk for SB , as its under you ...... whenever you get the time ...... :):):):):):)
[Defy Android Development] TJKV:
I'm currently testing a new build :)
[Defy Android Development] ccav2000:
[MENTION=4855459]Blechd0se[/MENTION] I cannot use the new kernel in CM10 unless I use the ramdisk from the older nightly. With the new ramdisk the system is very unstable even if I wait 10mins after boot, many times even freezing while in sleep forcing me to pull the battery. Assuming the trim call was the only change you did to it, I guess it's not a good idea to do it at boot.
[Defy Android Development] Blechd0se:
Its not done at boot, its done when the OS thinks its the right time. I only activated the discard option, nothing else.

Had the problem the first time too, but i forced fstrim on /data and got rid of it.

Trust me its worth it doing this one time for your device.

By the way check dmesg/kmsg if you get a kernel panic. If thats the case you need to wait after reboot until all bytes were trimmed :) Or as i said you force it one time without my ramdisk.

I know that people will always complain about everything, but what really pisses me off is the fact that nobody reads.

I posted the changelog, you should flash this only if you know what trim does, whats its like to help debugging and

overall you should know what you are doing (not talking to you in person, but took the opportunity to point this out).

In my oppinion the only statements that should be posted in this section are either code snippets or code discussions/suggestions. The first question you should ask yourself before posting something here is "has my post something usefull in it regarding development?"

I hate to post something like this...

Send from my Nexus 4
[Defy Android Development] ccav2000:
In that case, how can I force it manually? Also, as far as I know the OS will do it on its own only in Android 4.3. Since I'm in 4.1.2 currently, should it cause such issues?