[JB+][3.0.8/2.6.32 kernel] CM10.1 Android 4.2.2 for the Defy(+)

[Antiga Prime]

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

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.

 

[jassi32]

Thanks for the feedback

1.) 200 mb ram? How did you measure that? ---
2.) It should be even slightly improved
4.) Should be also improved, especially when its idling.
5.) Sounds more like a random problem. I don't think its kernel related.



1.i always see from settings -- running apps -- i had disabled few process , which where using more ram , and the part was i don't even used it ,
atm i got around 150-175 mb free .....
2.when my phone was idle at night , i got something around 11 hours of deep sleep , out of 11.30 total uptime ...
atm , got - 30 hours of deep sleep from 36 hours
4.i got 2 year old battery with skips , so overnight idle usage for me , its 3-4 % drop overnight , both with wifi + signal
5.on wifi i can't see the issue , most prob related to data ....
next report will b with screenshots ---

 

[biernus]

@Blechd0se
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!.

 

[Anton111111]

Good evening

Had some time to make another update. Short changelog;

After install 10.1 kernel, os doesn't start. I see boot animation and system doesn't start.

 

[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.

 

[frozenwaverider]

Good evening

Had some time to make another update. Short changelog;
[/HIDE]

@Blechd0se 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

 

[Proverbs2]

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.

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.

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!

 

[gkovacsp]

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

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)

 

[Proverbs2]

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)

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.

 

[gkovacsp]

Which kernel were you using? The one included in the Quarx build, or did you flash one of Blechd0se's kernels?

The one in Quarx's build.

 

[Proverbs2]

The one in Quarx's build.

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!

 

[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!

 

[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.

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.

 

[Blechd0se]

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!

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.

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.

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

 

[eliseo486]

Im going to test cm10.1 version !! XD:victory:

 

[jassi32]

@Blechd0se --
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 ......

 

[TJKV]

@Blechd0se --
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 ......

Slimbean needs a different ramdisk. What Blechd0se uploaded will work properly only on CM.

 

[jassi32]

Slimbean needs a different ramdisk. What Blechd0se uploaded will work properly only on CM.

but after 2nd boot till now , things are good , can't say about later ....
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 ......

 

[TJKV]

but after 2nd boot till now , things are good , can't say about later ....
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 ......

I'm currently testing a new build

 

[ccav2000]

@Blechd0se 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.

Sent from my Nexus 7 using xda app-developers app