yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] Husi10:
New build is very unstable here too. After some time it starts to lag then it will freeze. The only solution is to remove battery.

Can't post log, I will if I have more time tomorrow.

I'm back on 15/05 one.

Keep going Quarx and other devs, your work is awesome.
[Defy Android Development] bone101:
No reboots or lags here , last build works fine

I set flight mode before boot in recovery

Wiped caches

Deleted some apks from system app folder and some stuff from system media folder

MB525 red lens
[Defy Android Development] mosta00:
+1, only wipe cache and dalvik cache..really great!:good:
[Defy Android Development] niksy+:
Installed new build and been setting it up for the past half hour - no freezes, no lags, no problems of any sort :) The amount of free ram is incredible :D (not sure if it's higher than in the previous build, but it's awesome, anyway!)

Here are my standard installation steps since we got TWRP, if anyone's interested:

1. Advanced Wipe > Dalvik + Cache + Data + System

2. Install > CM10.1.zip + cache_wipe.zip + gapps + cache_wipe.zip (a 4 zip queue)

Reboot after that and rock on :cool:

*edit* Soft reboot did happen for me, too, after oppening 4 or 5 apps one after another. :/
[Defy Android Development] nostupidthing:
i cant believe that you'd consider trying another custom kernel, which are all still at 2.6.32, on this new build, with 3.0 kernel.

that's the whole point!!! :p
[Defy Android Development] KairosDev:
I got it to work on my Defy (MB525) Red Lens. You have to wipe data though, and when restoring a backup, wipe data too.

Also, Quarx isn't wrong when he says Experimental: it's a pretty early build.
[Defy Android Development] pjgowtham:
Re: [JB+] CM10.1 Android 4.2.1 for the Defy(+)

Can anyone point out the difference in 3.0 kernel other than sd mount will work on 4.2 only with 3.0 kernel, thanks

And does flashing gb/froyo stock kernels contribute something to the performance?
[Defy Android Development] mato_d007:
I was misunderstood, i was not saying that i dont like the new 3.0 kernel... i just asked if someone has the same curiosity as me to flash another kernel and see what happens, just for testing purposes...
[Defy Android Development] tngjs1230:
Re: [JB+] CM10.1 Android 4.2.1 for the Defy(+)

Quarx fixed sd problems :D
[Defy Android Development] nostupidthing:
you still don't get it... to use a car analogy... it's like you change from a honda to a ferrari, and you ask to use the engine from the honda.

ok, it maybe exaggerated, but that's the logic.

edit: @tejus: no it doesn't, to follow the same car analogy above, yes, you can try running the ferrari "frame" from the honda engine, and maybe test if the doors can open, the lights can turn on, but then it is "essentially" meaningless.. it may even run but then when you put the real ferrari engine there, you'll have to test and change many things again... and if at the end of the day you only have a ferrari with a honda engine, well... well, you, you can test everything, like jumping down a tall building and test the various ways your body will hit the pavement and resulting mess, you can call yourself "curious" as well... i wouldn't call these people "clever" though... see my username.
[Defy Android Development] mato_d007:
You are the one who still dont get it: testing something can give you useful and insteresting and even unespected information. Im not saying "use this kernel" im saying "test this kernel and see what happens" because thats testing spirit... (and i have curiosity)
[Defy Android Development] TJKV:
To be honest your suggestion does make sense. If it boots after flashing the old kernel, it would be nice to check out CM10.1 features in a more stable environment (albeit without sdcard access).
[Defy Android Development] kangi26:
Alright guys, please take a break from the bickering and get back on topic

Cleaned thread

Thank you
[Defy Android Development] bone101:
AW: [JB+] CM10.1 Android 4.2.1 for the Defy(+)

After testing the beast ;) and go back to 4.1.2 q.10.1.13 , phone have some lags with display response after touching the glass and sometimes it freeze , but not often.

Locking and Unlocking the phone helped.

Thank you Martin , Quarx

MB525 red lense
[Defy Android Development] TJKV:
Re: [JB+] CM10.1 Android 4.2.1 for the Defy(+)
[Defy Android Development] rodrigojfuentes:
I do call this people clever. I´m definitely convinced that having a functional kernel would serve as a base, where you can find functioning code, and merge or replace it in the 3.0 kernel if it has some unfunctioning features.

In other words, I think that for the new 3.0 kernel, having 2.6.32 kernel as a base at least is better than nothing.
[Defy Android Development] bone101:
AW: [JB+] CM10.1 Android 4.2.1 for the Defy(+)

1.Sorry for non OP relatet posting

You can also implement working things from 3.xx kernel into 2.xx

It would take the same effect or not ?

MB525 red lense
[Defy Android Development] rodrigojfuentes:
I believe it can be done, but the goal is to have a stable 3.0 kernel in a near future. So I don´t think anyone will try to port 3.0 features into 2.6.32
[Defy Android Development] Kayant:
It is true it can be done in some cases with some changes it may not be possible but it's not really worth it because the amount of changes necessary to port features we need to the 2.6 kernel is huge and because the Linux kernel has matured a lot over those years with lots of changes in different places. I think the effort needed to backport stuff is a lot higher than working with a higher version of the linux kernel but I maybe wrong ...... I recently tired to port the drivers needed for the new wifi driver to work for our 2.6 kernel but failed because I underestimated the amount of changes needed and for one I don't really have near enough knowledge on the linux kernel to start doing what I did lool ;) .... In the end I was close but still far away :p I had cherry-picked about 100+ commits but am sure there was a shorter way around it but I just don't know how :( Now compare that to working with the 3.0 kernel where all Quarx has to do is enable it in the defconfig then debug wifi to get it to work ( which is not an easy task anyway) now compare that to using 2.6 as base where he would have to port over the drivers first then debug it and get it working.
[Defy Android Development] pjgowtham:
Re: [JB+] CM10.1 Android 4.2.1 for the Defy(+)

So it's like changing the engine of our device. And I find lots of lags in defy where other devices don't get much. Hope our new kernel blasts out all the lags and provide remarkable optimization.thanks
[Defy Android Development] fryta22:
Odp: [JB+] CM10.1 Android 4.2.1 for the Defy(+)

4.1.2 is unfinished and never will be.
[Defy Android Development] xdaid:
Yea it hurts, it's hard to believe :crying:

Sorry for the sarcasm but i just can't find a "WTH" button for your pointless post.
[Defy Android Development] nostupidthing:
the problem is, most of you who thought that was clever has never compiled the kernel, do backports or ports, or merge patches from another version... (yes, i did it before) if you have done that, you'll realise that, as Kayant said, it's just not worth it.

ok, this is not stupid, just ignorant.

besides, cm10 and 10.1 isn't that much different, and we've a very much working cm10 now, if you're so desperate to have cm10.1 or JB 4.2, perhaps you should get a newer phone like the Nexus 4 or learn a little patience.
[Defy Android Development] pjgowtham:
Re: [JB+] CM10.1 Android 4.2.1 for the Defy(+)

Hey wanna clear a doubt. We have experienced the power of custom kernels and is the Motorola s bootloader policy still affecting our development in any way?
[Defy Android Development] przemal:
I always wipe caches after update and my phone froze while I was trying to answer incoming call, however i left it (without rebooting) and after few minutes it was responsive again :).

Before that incident it was working quite well, not as well as 16/05 one but still.
[Defy Android Development] Alan Miranda:
I guess i'm having boot loop, i tryed to install it now, but it is taking 5 minutes o CyanogemMod logo, cai i back to the Quarx 4.1.2 only doing all wipes?
[Defy Android Development] Persechini:
Getting the same behavior already described:

Interface lag at startup, gets better after a few minutes

When doing anything that seems a bit more memory intensive I get a temporary freeze and a lot of lag, and/or interf sist crashes, or it goes straight to soft reboot

But:

I reduced vsel levels (old x/20+2, no overclock) and it seems very swift and stable for now. Will leave it with wifi on to check performance and battery drain in the morning (PS: got a black unresponsive screen again while navigating rom toolbox, buttons light up indicating something is happening, but couldn't do anything but pull the battery and reboot. root problem maybe?)

Installed over previous CM10.1, some system apps removed (apollo, calendar, email, exchange, cm and live walpapers) and flashed a zip with a different version of the 4.2 camera and keyboard for working picasa/google+ photos integration in gallery (never mind the keyboard as I use swype)
[Defy Android Development] ccav2000:
So it seems Quarx has caught up with the issues, he created a new branch with the kernel of the previous nightly tagged. Until he releases an updated version or an updated kernel, I will just report what I remember from the kernel dmesg before I removed the nightly.

Most of the errors I was seeing were something like: "ashmem: negative number of objects to be cleaned" and a couple of other lines. This could be pointing to failures in the memory management subsystem. But it's not for me to say, I am not a developer, considers this a wild guess.
[Defy Android Development] okij:
Feedback for 05-22 nightly: unstable and still high battery drain

After using my Defy+ yesterday evening (with a couple of freezes and reboots / battery pulls) I unfortunately have to confirm ccav2000's statement of yesterday: Even waiting the mediaserver to do its work still doesn't lead to a stable system. :(

Even more: also battery drain hasn't improved since 05-16 nightly: I left my phone after a clean boot for the rest of the night and this morning, Battery Monitor Widget still reports about 39 mA/h (which is about 2,5%/h) consumption during the night (with WiFi on), which is exactly the same as before. Main consumers, according to the battery settings of Android, being Android OS and android.process.media. :eek:

With 04-15's nightly (as well as with CM10 before) I had about 1% consumption at night with the same settings.

Sorry I have to report this, but for now I will roll back to 05-16 nightly for stability reasons and charge my phone a bit more often...

edit: Just as an additional information: deep sleep wasn't a problem here and restoring just "system" of my TWRP backup went smooth.
[Defy Android Development] mrcurly:
I had the exact same issue, infact when i tried updating from 05/16 to 05/22 my phone restarted during the process and didnt boot past the moto logo after that, so had to reflash sbf etc and do a clean install. For some reason my phone didnt auto enter deep sleep mode, and cpy spy showed it stayed on 300mhz for the 5hrs it was off.. Any reasons why?

Screenshots attached.
[Defy Android Development] vic160890:
CPU clock

Hi guys,

I was curious about how the latest version of kernel works with the CPU clock.

What I noticed going to Performance -> CPU is that the clock changes at least once every 1 second between 300Mhz and 600Mhz.

As I believe (working with electronics hardware) this might lead to a higher battery consumption and as I recall from what Bleachd0se (sorry about misspelling) wrote in his post, it is not recommended for the clock to switch so many times from a value to another.

What I suggest is finding an event to trigger the change in CPU speed that is a bit more stable (appears more rare). Or at least setting the clock to 300 (or deep sleep) when screen is off and to 600 minimum when screen is on. I think holding the 600 mark and starting from there shouldn't raise the consumption in comparison to switching between 300 and 600 back and forth every second.

Apart from this, just a night after installing 22-May version, the CPU usage in standby was about 4.38, and if I would turn on the screen it would go slowly down to 0.9. After going back to standby it would go back up. (I assume this could be the media server running, because Android OS had 41% of battery consumption) Now it's back to 0.0 in standby. So don't panic people the battery consumption should go lower after a few recharges.

Regards.

Victor
[Defy Android Development] niksy+:
[MENTION=4511529]vic160890[/MENTION] Improvements of interactive done by Blechd0se include that 300 is the max clock while screen is off and that the clock state before screen-off is the clock that CPU will go to when you turn on the screen.

I can't confirm the CPU going from 300 to 600 and vice versa all the time... Are you sure haven't got something running in the background? Because here I got the (touch) impulse that boosts it to 1000 on touch and then it takes ~2 seconds to get down to 600 and ~3-4s more to get to 300. :cowboy: (Using Trickster MOD app to see the current CPU state, while flinging the notification drawer up and down, for example)

[MENTION=4800644]mrcurly[/MENTION] Yeah, that happened to many on the previous nightly as well and all that was needed was a simple reboot and then deep sleep was working again :)

I've had one soft-reboot, too, so +1 on stability issues :( (I was going through apps one by one setting them up and the phone rebooted while starting up 5th or 6th... Must be memory management problems, as suggested already :( )

And +1 on the improved battery drain, it's really going down with this nightly :cowboy:
[Defy Android Development] bbllaazzee:
IN interactive the switch between 300-600 is pretty frequent, may be even less than a sec. I changed it to BOOSTED and it

is stable at 300 in idle. Let me check and report the battery status with WIFI on all time.
[Defy Android Development] mrcurly:
[MENTION=4442286]niksy+[/MENTION] well i had tried rebooting as well, cause at first my baseband wasn't set to my area. But still i'll try it again see if it happens today. Thanks again for the tip & especially [MENTION=513620]Quarx[/MENTION] [MENTION=4855459]Blechd0se[/MENTION] for such amazing work.
[Defy Android Development] niksy+:
You can try adding a cache and dalvik wipe to that reboot, that's what fixed deepsleep for me on one of the kernel updates (the ones when we were still testing interactive edits), it never hurts :laugh:

Cheers, everybody :highfive:
[Defy Android Development] vic160890:
Please check what is cpu freq is shown in Settings-> Performance -> CPU. Side apps can always read only once a second or slower. I guess built in method will always be the fastest.
[Defy Android Development] niksy+:
First I couldn't because every option in Settings silently force closed Settings :rolleyes: Now, rebooted and...

lol :D it's constantly going 300 ->600 ->300 ->600 ->300... [MENTION=4855459]Blechd0se[/MENTION] Have you noticed this? Trickster MOD indeed doesn't show this behaviour... :confused:

Still, this couldn't be the cause of DeepSleep drain :rolleyes:
[Defy Android Development] vic160890:
Yes, that is true, but I strongly believe that the deep sleep drain can only be stated as "high" after the time that the ROM needs to settle(I'd say a minimum of 2 recharges, making it at least 2-3 days).
[Defy Android Development] xinrag:
Suddenly Welcome Message appears

Hi!

I am wondering! I just played around... switched in airplane mode... did a reboot... than again in recovery menue and just another dalvik + cache wipe... reboot... in airplane mode I switched the baseband to 3.4.x and did another reboot and then I got big eyes:

A google welcome message appeared! I was pleased to enter my name and decide if I would grant the google location service or not...

Why did this dialog appears suddenly after reboot? Any ideas?

Btw: Mooving from quarx CM 10 to 10.1 (linux 2.6.x) I did a data, cache and dalvik cache wipe. During my updates between the different 10.1 releases I just cleared the dalvik and cache.

Best regards, Stephan
[Defy Android Development] Blechd0se:
I can't really reproduce the problem. It stays for me at 300 in settings, but i am running a older build and while i tested the new gov features

i added debug messages and never saw it jumps between 300 and 600, don't know how accurate the cm-implementation is.

However, you are right, it shouldn't raise up and down the frequency and i don't want to limit min_freq to 600 while screen is on.

If you are just reading something on your screen you won't need 600 and the gov should have the ability to go back to 300 in this case.

Maybe i need to increase min_sample_time, have to investigate it, because gov should only change speed when its really needed.

If this is only happening on the latest nightly then fault is somewhere else, because i haven't touched interactive since my last changes.

Last time i asked you guys over here about my concept with 300 limit at suspend and the feedback was pretty well.

So i thought i do it the same way with my new idea;

Many of you are overclocking your phone, while i don't like the idea of overclocking to get a reasonable performance, it may be a nice addition

in some cases.

We have 4 frequencies at the moment (300, 600, 800, 1000). I want to add a 5. one (1200), but only activate it on a very high and longterm load.

It's like the turbo-boost concept you see on some intel CPUs but on our device. Of course this sort of dynamic overclocking will have some

sort of on/off-switch (if you don't like it), but what do you think about it? Just wanted to hear some oppinions :)

But don't expect anything too soon, exams are around the corner... :eek:
[Defy Android Development] frullewulle:
might be a good idea but we should be careful for overheating in case that there is a process that hangs at full load ...
[Defy Android Development] AnTerNoZ:
+1

I think the idea is great, cause if the phone had 1200 at 4th vsel it need to much battery for me, if it runs all the time with this high vsel. that's why I set it manual every time I really need it, that as automated boost option would be great.

yea, a kill switch are a good idea too. like vol+ and vol- or something, maybe a graphic overlay.
[Defy Android Development] TJKV:
It's happening on the 16th May CM10 as well. I was planning to flash the latest (22nd May) but changed my mind because of the rebooting reports.

Good luck for your exams (:
[Defy Android Development] vic160890:
I could send you some feedback printed by dmesg in terminal if it's relevant.

Unfortunately I did not check this out on 16th-May version.

About the 5th frequency i'd say it's a great idea if it's posible. (i've seen that Samsung Galaxy S runs the exact same CPU and goes nearly as low as 100Mhz and as high as 1400Mhz or more when overclocked, even though I know that there is the locked bootloader problem on our side )

Good Luck with exams :) (I have one today :( )

Victor
[Defy Android Development] disadjusted:
I don't like the concept of limiting frequency to 300 or whatever at all.

It is always most power saving getting as much done in as least time as possible.

So 3sec in 1GHz should consume less power than 10sec in 300MHz.

Regarding screen on behavior: why not keeping it at min 600MHz for 10, 15 or 20 sec after the last touch? That might keep it responsive even when just reading and will settle when hands seem to be off the device...

And I don't think we need a turbo mode, that might complicate frequency management even further.

Have overclocked to 900/1100, but I think 1200 might be too much in terms of heat... We have a plastic case and no cooling possibility at all, especially not when in pocket!

Max frequency should really be a decision of the user himself!

But thanks anyway for your efforts and good luck with your exams!

Sent from my hands using my brains
[Defy Android Development] d3xt3r:
Its a new build update...:D
[Defy Android Development] sepp.:
0522

Short patience span: stepped back to 0415 after 2nd reboot today

details:

approx double battery drain during the night compared to 0415

1st reboot after ~ 5 mins unresponsiveness after authentication via Browser on the company (5GHz) WLAN

2nd reboot around noon - starting camera app - ~5mins .. reboot
[Defy Android Development] niksy+:
Can anybody figure out the changelogs for yesterday and today's build? I know the battery drain fixing is being worked on, but is that all? (I know ION is has not been implemented and enabled yet.)

Downloading the new build, anyway!

[MENTION=4855459]Blechd0se[/MENTION] That actually sounds like a good idea! But implementation must be done carefully :) Because, for example, if we're gaming the CPU is likely to be used 100% most of the time, but switching to Turbo mode during the whole gaming session would be too much... (I'm not sure on this, but, whatever, the point is - it should be implemented in a way that it could not stay in Turbo mode for a long period :) )

P.S. AMD has got Turbo modes, as well :p
[Defy Android Development] wadb:
That's depend on the game, in Subway Surfers I need full speed :D
[Defy Android Development] ccav2000:
So I tried today's ROM. I tried the usual stress test, Chrome browsing. Managed to have it freeze the device in 2 minutes. Soft-rebooted a couple of minutes later on its own. Sorry, but it's not fixed.
[Defy Android Development] Shubhamqweasd:
same here , soft reboots while the system is in stress ( high ram usage ) ..:(
[Defy Android Development] Quarx:
Oops, sorry guys, forgot to change branch of kernel in manifest:(

In cm10 ok, cm10.1 will be reuploaded.
[Defy Android Development] casouzaj:
Media contents keep failing with NTFS card!

Just reporting (as always) that in buid 05/22 the issue of media contents failing (process.android.media has stopped) whenever a NTFS-formatted card in in place is still present. Hope it gets fixed any time soon. Once again, I'm back to Quarx's 11/17 build.
[Defy Android Development] ccav2000:
Damn, we were trolled! (Just kidding of course). Awaiting the reuploaded version!

---------- Post added at 05:28 PM ---------- Previous post was at 05:23 PM ----------

quarx2k.ru seems down right now. [MENTION=513620]Quarx[/MENTION] please let us know when the new CM10.1 will be ready, and from where to download.
[Defy Android Development] biernus:
Uuuu this ver from 22 for me is bad mean problematic. Early ver. works like a charm (exept battery drain and wired behevior on incoming call lock). This new ver. make my defy freeze only grab a battery help (first time in my life grab batt. from my defy+ :). I think i go back to some older one and wait for some change. Also in my opinion nothing change on + in batdrain problem :(

::. Tapniete
[Defy Android Development] Blechd0se:
Yeah i know, i already have some sort of pseudo code;

If current_load > 99% and cpu_load_history_average >= 100% and current_freq = max_freq then go up to 1.2ghz.

But i guess i need here some sort of time thing, to let it stay (for 10 seconds or similiar) at 1.2ghz and check again

if still needed.

It should only go there if load is really high and scale down as quick as possible :)
[Defy Android Development] Harishsudharsan:
[BUG]

I just found a bug. Unable to mute phone calls. Found it in a real nasty way.
[Defy Android Development] disadjusted:
reducing any delay by increasing clock

are you sure that your phone doesn't do anything other than playing music while screen is off? what about synching? media scanner? scheduled backups or other related stuff?

as far as i understood how touches are recognized the already small "input lag" (or delay) of 300MHz will reduced by the half at 600Mhz, so it is able to jump twice as fast to 1GHz (or 1,1/1,2 if overclocked) as soon as you touch the screen.
[Defy Android Development] configuration:
I see what you did there.
[Defy Android Development] mohan vinay:
+1 every thing works fine