yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] woodman:
CM10.1 13-07-09 V2 full changelog

As usual, here is the 07-09 V2 Quarx's build changelog from github (global CM10.1 updates and kernel updates) :

* Misc translations

* [AeroKernel] :

- fix compile

- tracing: Fix undeclared ENOSYS in include/linux/tracepoint.h

- tracepoints: Add check trace callback type

- remove cpcap audio spam

- clean defconfig

- LOAD_FREQ (4*HZ+61) avoids loadavg Moire

EDIT: - Revert "Revert disable SWAP, can cause data loss(test)"

* [android_device_moto_jordan-common]

- update egl configs

- update overclock config

- disable 2nd-boot-uart mode for public builds

- update OC script

* [android_frameworks_base]

- NotificationManager : Fix security exception

- Merge "Don't consider input restricted when the lockscreen is disable…

- Merge "Add option to hide music controls in lockscreen."

* [android_system_core]

- Merge "Fixed reversed output in netstat Recv-Q Send-Q columns"

- lolcat

* [android_frameworks_opt_telephony]

- Merge "Revert "CallTracker: Add delay to reduce cpu load""

- Merge "CallTracker: Add additional check for pendingMO to verify that…

* [android_packages_apps_Settings]

- Merge "Settings: privacy Guard enhance app logic"

* [android_packages_apps_Phone]

- Phone: Disable accelerometer sensor while in-call and screen UI is off

- Merge "Add android.permission.INTERCEPT_SMS permission."

* [android_frameworks_av]

- Merge "Camera: Add more htc parameters"

- Fix includes for media-caf

* [android_external_bootmenu]

- fix OC settings, add SCHED option, resort options, remove unused opti…

- clean code

EDIT for 2013-07-09 V2

* [android_frameworks_av]

- again fix memory leak for old codecs
[Defy Android Development] Quarx:
CONFIG_SWAP affect on zRam/zCache...

I disabled CONFIG_SWAP, this option has some problem which can cause random data loss, infinity cyanogen logo etc.(even when swap not used).

Who want use ZRAM and other experimental features, can install [MENTION=4855459]Blechd0se[/MENTION]'s kernel. Until it's not will be stable.

I re-uploaded today build. Again some cyanogen commits broke our codecs, but fixed in "v2".
[Defy Android Development] ccav2000:
Ok boss, will do!

---------- Post added at 03:17 PM ---------- Previous post was at 03:12 PM ----------

By the way, this nightly has the new Privacy Guard manager under the Security settings. [MENTION=513620]Quarx[/MENTION], does this nightly contain the security fix from Google for the latest hacking with the master key? I read in Android Police that it was to be merged in CyanogenMod yesterday or today.
[Defy Android Development] Quarx:
This build contain latest Cyanogen changes :)
[Defy Android Development] Kayant:
Yup it's there ---> https://github.com/CyanogenMod/android_libcore/commit/fe70e697810a7a8b9ce47325f53d16fdbc19f1f8
[Defy Android Development] rol525:
I have the last nightly "v2" ,the games work very good.Excellent work Quarx.
[Defy Android Development] playitlouder:
Anybody noticed any stability or data loss problems on Blechdose's new Kernel?

The problems Quarks is refering to can only happen if the phone is inproperly shut down i guess?

Oh and funny thing is, i had one strange stability issue on my Sammy Galaxy SII. I was scrolling trough the settings and all of the sudden the phone froze.

Well a battery pull later I was stuck at the CM screen :laugh:
[Defy Android Development] ccav2000:
I see no reports for the new build yet, hopefully that means users did not encountered problems (or they didn't get around to install it yet...).

Anyway, I think [MENTION=513620]Quarx[/MENTION] should delete item 5 in the OP (delay on wake up), this seems fixed for me for a while now. The problems with bluetooth remain.
[Defy Android Development] woodman:
Flashed "2013-07-09 V2" 2 hours ago, no problem so far. I need more time to do a good feedback.
[Defy Android Development] okij:
Update about memory leaks

+1

[MENTION=513620]Quarx[/MENTION]: Also item 3 (Video recording is not good) and item 4 (Memory leak after some days) must remain for now, since they are not fixed yet.

About the memory leak: I had an eye on it with the 07-02 nightly and unfortunately, the available memory still got less by about 20-30 MB per day, which leads to too little available memory after a couple of days, so that only a reboot helps.:silly:

To have quite consistend and comparable testing conditions, I look at the available memory right after using the Killing Tasks feature of the TrustGo Antivirus & Mobile Security app, so that all non-system-apps and tasks get kicked out of the memory.

I tried the same also with zRAM and KSM turned off (to check if they were the culprits for the memory leak) and got the same results.

Since this afternoon I am using 07-09 V2 nightly with Blechdose's kernel from 07-08 with zRAM 18% and KSM turned on and will still keep an eye on memory. Maybe the recent changes on the kernel improve this issue... :)

It would be great if someone else, who is using the plain Quarx kernel from today's build, could also keep an eye on the memory leak issue to see if totally disabling ZCache/Zram/Swap (like Quarx did for now) maybe has a positive influence on the memory leak.

Anyway, it would be great if the memory leak could be solved (with zRAM, Swap and KSM working), since our Defy's just have those 512 MB of RAM and we have to make the best of it! :fingers-crossed:
[Defy Android Development] ccav2000:
[MENTION=4916555]okij[/MENTION], that's exactly my thoughts too, we only have 512 MB of RAM, 477MB user available, and technologies like zram were developed exactly to help in conditions of limited amount of memory. Memory leaks obviously make matters worse.
[Defy Android Development] Shubhamqweasd:
delete
[Defy Android Development] Blechd0se:
The following is my personal oppinion, feel free to correct me.

Thanks for testing! I appreciate it :) Btw. the only difference between Quarx Kernel and mine is zram (= swap) and zcache.

I already contacted Quarx, because as [MENTION=3344838]ccav2000[/MENTION] suggested we will [should] leave this features optional. The problem for now is swap

or at least something inside swap which causes according to Quarx data loss.

Thats exactly my oppinion. I will explain some of my thoughts based on your statement :)

At least some parts of it, because we know how android handles memory. It tries to keep as much in memory

as possible, thats probably why android performs quite well on devices with more RAM. Now to the "real" problem here; sooner or later

we have to use some sort of swap (doesn't matter if pure swap or zram or something else), because android apps will have a larger

memory footprint and there isn't anything we can do about this. The reason for this is simple; app developers try to support a huge bandwith

of devices and newer devices usually have something around 1GB RAM (not counting those very low end devices), so they try to develop for

the lowest device (and "low" is relative). Low today means something totally different as low in some years. Yes android tries to fix this problem

from the OS-side, but we have to improve this more.

You are right, those technologies were developed to help in such conditions, but there is some sort of "huge" lack. Before my patches to zram

the swap space was just like normal ram visible for the OS and this causes some problems obviously it wasn't anybodys fault,

because nobody could assume that some day a device uses a very old kernel with a very modern mobile OS.

The worse part of this? We wont have complete freedome here thanks to some libs and the locked bootloader and furthermore i for myself don't use the defy

daily and that means i am doing things more theoretically (sometimes this turns out to be very efficient like the changes on interactive).

Some final words; I don't want to split the community here, unfortunally i published a new nightly right before Quarx did, so obviously the changes

haven't been tested much. Quarx builds should be known to be very stable (thats why he disabled some of those new features) on the other hand

my builds are more experimental not in terms of instability but rather in terms of new features.

So if you don't know which build/kernel you should flash, flash Quarx one. Its meant to be as stable as possible and Quarx does a great job here.

If you are some sort of advanced user and know how to give feedback, then flash mine (but don't forget to report!)

One last request; if you post something in this thread, try to post something usefull with which either Quarx or i can work with (not talking to the usualy

suspects, you are giving great respones!), just read this and you understand why even android developers like it that way :)
[Defy Android Development] ccav2000:
[MENTION=4855459]Blechd0se[/MENTION] the Defy is an old device and has limitations, zram is one remedy for the limited RAM but obviously we cannot tradeoff its benefits with loss of stability and even severe data loss. I guess the only solution is for the swap problem to be addressed, but you and Quarx already know that.

For the time being, the ones who just want their phone stable should stay away from all this, the restless ones (myself included) will try your nightlies looking for that bit of extra performance!
[Defy Android Development] Sivaguru:
Using [MENTION=4855459]Blechd0se[/MENTION] 08.07 Kernel, Enabled zram(18%) yesterday evening and noted the snappiness in the interface. It rebooted now while unlocking the phone.

Been using quarx's build 02.07
[Defy Android Development] serpent_rider:
Unable to flash the new nightly.

I am unable to flash the new nightly 9/7.

It also breaks my 2/7 installation.

I tried twice and everytime I have to start from scratch by flashing SBF.

I have checked the MD5 of the downloaded file and it is correct.

The error comes in TWRP. It says failed to flash. And after that if i try to restore my backup that also failed.

Do we have any changes in the folder structure or file structure when we flash the new 9/7 nightly.

I am doing wipe cache/dalvik cache --> install zip --> wipe cache/dalvic cache.

Any other user also facing the same issue.

Even when I am flashing the 9/7 over the SBF it is giving me the same error. So I am now running the 2/7 and it is working fine.

So maybe some file structure I have to care of before flashing 9/7 but I am not sure.
[Defy Android Development] slaphappy76:
Clean Install not Possible?

Good morning,

I have the problem that it is not possible since the 16.06.2013 build a cleaner install with a full wipe.

When I start the phone lacks the function of the home button and the Quick Menu.

Does anyone have the same problem or a quick solution?

At the moment I intsall the 16.06.2013 and after a start I intall the new version without wipe over it.

Thanks

slappy
[Defy Android Development] okij:
[MENTION=4855459]Blechd0se[/MENTION]: Yesterday evening I also got a sudden reboot, in my case I was just copying files with MyPhoneExplorer, which usually isn't a problem. Maybe somehing got less stable in your latest kernel? :confused:

edit1: I just saw, by checking the uptime and also by seeing that currently the IMEI number is missing, that there must have been another sudden reboot tonight. I'm sorry, but for stability (and for testing) reasons I'm now switching to the kernel of [MENTION=513620]Quarx[/MENTION] 07-09' nightly.

BTW: Isn't there anything that can be done against the missing IMEI numbers? At the moment, it's missing about every one out of two reboots. I know that this problem exists since CM10 (at least since the first custom kernels), but I would be happy if it could be fixed. I would vote for adding it to the Problems/ToDo list! :)

edit2: Interestingly, using Quarx 07-09' nightly (with zRAM turned off by default) I get just about 15-20 MB less available memory than with 18% zRAM (I both checked it after a fresh reboot and using "Killing Tasks" of TrustGo). I thought that 18% zRAM would lead to about 80 MB more free memory... :confused:
[Defy Android Development] ccav2000:
Almost 17 hours uptime now with the 09/07/2013 ROM and [MENTION=4855459]Blechd0se[/MENTION]'s kernel, 26% zram enabled, no reboots, no FCs. Note that I deleted my overclock.conf before upgrading so now I'm using the recommended VSELs that are higher than usual and the recommended CPU and IO schedulers.

If I get a sudden reboot I report it immediately here though.
[Defy Android Development] okij:
Thanks for your feedback! :)

I had my Vsels at my usual, still quite conservative, settings when testing [MENTION=4855459]Blechd0se[/MENTION]'s latest kernel. Those are: 300@25, 600@35, 900@50 and 1100@60. I didn't have reboots because of this for the last couple of weeks, the reboots normally start to occur after a few days of uptime when the available RAM becomes too little.
[Defy Android Development] ccav2000:
Ideally we shouldn't get any reboots unless something goes completely wrong, but theory is far from practise. All I can do is to use the phone normally until something happens.
[Defy Android Development] ccav2000:
Passed the 24hr uptime mark, still not reboots or anything abnormal using [MENTION=4855459]Blechd0se[/MENTION]'s kernel.
[Defy Android Development] niksy+:
+1 :) I'm at 36h currently (although CM10.1 itself is still the previous build) and it's working veeery nice :) It's smooth and snappy, apps load noticeably faster and games do indeed work quite a bit better (fps I'm getting in Minion Rush with the latest kernel changes is much better - the minion is running faster on lower scores now than it did on higher ones before :D It's completely playable! :cyclops: )

Thanks Quarx and Blechd0se for the improvements you keep bringing :) I just love how good all of this tweaking is turning out to be!

Oh, yeah I should mention the set-up, I guess - running on deadline scheduler and with zRam set at 18%!

[MENTION=3344838]ccav2000[/MENTION] You mentioned that you're running yours at 26% zRam? Noticed any differences between 18 and 26% or not really? :)
[Defy Android Development] ccav2000:
Nothing much noticeable, I just figured I should give it as much space as possible to compress data to leave more usable RAM free, perhaps in higher uptime where memory leaks start to form there will be some difference. What VSELs are you using?
[Defy Android Development] niksy+:
Okay, guess I'll stick with 18% for now, then, might test the higher settings some time later..! :good:

My clocks and vsels are the default ones from the previous build(s) - 300/30, 600/42, 800/54 and 1000/58. But that's only because this build has a problem with saving clocks and vsels, or else I'd be on the same settings I've been using for the past year and a half - 300/17, 600/32, 800/42 and 1100/54. I must say that I don't think low vsels have anything to do with the data loss problem or the RIL bug... But maybe that's just because I never had the RIL bug, on any ROM. But I did have one random reboot that brought about some data loss - about 2 weeks ago (so it was before this build that I'm on now) and when the reboot happened I wasn't doing anything stressful for the phone, I was just going through some menus when it went off, I don't think (moderately?) low vsels were the culprit... I'm no expert, though, I'm just sharing my experience and what I could make out of it. :)
[Defy Android Development] walter79:
Sounds very good. Thanks for your work. What about 720p encoding?
[Defy Android Development] YaPeL:
Re: [JB+] CM10.1 Android 4.2.1 for the Defy(+)

Will be able to decode my 10bit chinese cartoons?
[Defy Android Development] ela1103:
Quarx has a grand master king for the moto defy developer.good news quarx 720p decoding, full hw decoding.quarx pls enable the usb otg function and sweep 2 wake
[Defy Android Development] Quarx:
Driver for camera not added. Can't say about enc.:)

Camera will not easy here,
[Defy Android Development] theclaytons:
How about wifi, data and 3G? Is this able to get working? I can live with phone and no camera....
[Defy Android Development] Shubhamqweasd:
i think kfazz is working on RIL and WiFi , lets c how it goes :D
[Defy Android Development] Quarx:
Sholes has cdma ril, not wrigley. I'm waiting czechop answer.

First we need detect modem as usb device.

Wifi has some strange problems.
[Defy Android Development] drunk_ryder24:
quarx this may sound stupid or irrelevant,i've managed to merge drivers into p-android omap 3.1,the cross compiler assembles the kernel properly but i get an arch/arm/include/linux/asm/atomix.h error(function already declared here include/linux/atomix.h;btw in this project ive got all defy's drivers shown up even gpu recognized
[Defy Android Development] Quarx:
Which drivers you tried to port?

You should update sources of driver, to use new define.

We have almost all drivers in 3.0 kernel. Camera not exist only.
[Defy Android Development] premaca:
Re: [JB+] CM10.1 Android 4.2.1 for the Defy(+)

New build coming up. Quarx does it include RIL also, can we have working signal and 3G?

Great work thanks!
[Defy Android Development] drunk_ryder24:
well most of the drivers you commited to kernel 3.0 are merged in my test p-android-omap-3.1 build,cpcap is there,display,pvr sgx 530,board type mapphone defy mb526,so when i initiate make maphone_defconfig i get it done without errrors and makemenuconfig is ok but after make -jx it bumps at atomix.h saying that the statement was allready made in include linux,tried diferent gcc but gcc4.4.3,4.6 and 4.7 bumps on that problem
[Defy Android Development] Kayant:
Trying a different gcc won't help because the problem is not with gcc is with the code...... You need to fix the code first and from what you're saying it seems that there is duplicate code..... once you have done that you can use any gcc compiler you like ;) since Quarx fixed it for gcc 4.6 and up.....

Could you post what the error says exactly.....
[Defy Android Development] drunk_ryder24:
im not home on my pc now but will provide more info about the make error,yes its a merge fault probably but i tried different merges and with no luck but this one eems more promising because under terminal it shows up everything needed for defy since mostly its based on quarx 3.0 and omap 3.1 project(i mean its capable displaying something on our moto)
[Defy Android Development] Blechd0se:
How about deleting one statement if its already declared? However i think its more usefull to bring one kernel to a stage where it could be called "stable" instead of having many versions which are all quite buggy.

@Quarx, so no drivers for camera? Do we need to port them from 2.6.32?
[Defy Android Development] drunk_ryder24:
agree with you,but thats why i asked the forum so i dont screw up the entire code XD,will provide later more info since im out of town.

Yes,having many unstable versions would not be a great experience for our device but having less isnt an option either,instead we could tryparalel works on what we know so when we need it,it wont be too hard to make a step forward
[Defy Android Development] Quarx:
I want use drivers not from .32 kernel, because i want use opensource camera lib from omapzoom... else camera will use old api, which not good (as we can see in 4.x on .32 kernel)
[Defy Android Development] d3xt3r:
Re: [JB+] CM10.1 Android 4.2.1 for the Defy(+)

Change log of new build???
[Defy Android Development] niksy+:
Full hw decoding (720p, too), that's pretty much it, but it's impressive, nonetheless! We haven't had 720p playback ever since CM7 :) Other than that, some minor code fixes, you can always check Quarx's github - https://github.com/Quarx2k?tab=activity

Quarx, could you, or anybody else, please explain what kind of improvements could we hope for from the use of omapzoom camera libs? Better picture quality? Faster operation? Problem-free (720p?) video recording? Just curious :)
[Defy Android Development] Quarx:
OpenSource camera libs will fix problem with video encdoing.

It's laggy in 4.x because we convert colors in realtime... old libs can't use new formats of colors.

Explain: just see how works playback, in 4.1 .32 and 4.2 3.0 and diff:) in 4.1/.32 we have color convert.
[Defy Android Development] Kayant:
Oh I see ;)

Is that also why you're going to be using opensource libs and drivers I guess for fm and audio stuff since you recently deleted the proprietary ones from vendor tree?? or is it just easier to work with?
[Defy Android Development] ccav2000:
[MENTION=4442286]niksy+[/MENTION] I was only curious about your VSELs because I'm suspecting that increasing them may have cured some random reboots that I had. Never had the RIL bug the last year either anyway.
[Defy Android Development] soyusado:
I'm having a problem after flashing the 07-09_v2 nightly:

I can't connect to my career signal, I changed the baseband into the one that I've been using (America>Argentina>Claro 3.4.2-107-9) and after the phone has finished the reboot I still get no signal, then I checked the baseband again and it has been changed to unknown.

I had the same problem with 07-02 nightly but I manged to fix it by changing to a different baseband and then choose the correct one, but today that didn't work.

I'm trying Blechd0se kernel as well, but I don't think that the kernel might be the problem.
[Defy Android Development] Matzemink:
[MENTION=513620]Quarx[/MENTION] I would appreciate the following tiny little change: The lowest display brightness 0% isn't really the lowest value. In the old CM versions I had to change the lowest value from 20 to 2 (value 1 was completely dark).

I noticed that because the screen gets darker after some time of no activity.

So you see how perfect the ROM has become when I'm complaining about such little things :D :good:

Edit: Ok I've searched in the code on github and found out that the lowest value is already 10.So just a cosmetic change. Sorry about that.
[Defy Android Development] atulclassic:
flash defy baseband switcher..posted somewhere in this thread
[Defy Android Development] Bleak3993:
I have a problem, I flashed the latest v2 nighlty, I tested it for a while and then I decided to install the blechd0se kernel, now I'm stuck on... I don't know, after the blue led, shows a green led (wtf) and black screen, and I cannot access to the TWRecovery... any suggestions?
[Defy Android Development] pgreed:
A very BIG problem a week after installed the 02-07 version. I've reboot the phone and ... ALL my data and installed application was gone and system appear like after a factory reset. This problem appear from now at every reboot - system start with all data erased. That's no good!
[Defy Android Development] mikrom.cz:
Restore backup, there is some strange bug which corrupt data. Happened to me week ago.
[Defy Android Development] trurl3:
You can go to recovery only during blue light. When green light on is to late. Catch the moment and when blue lite goes on push VOL- to enter recovery, then flash Quarx's ROM once more.
[Defy Android Development] mikrom.cz:
Rsd lite? I flash new build + kernel + gapps + mytweaks as one batch in TWRP yesterday in the pub, all works fine.
[Defy Android Development] pgreed:
For the app I have bkup but some telephone numbers was not synced...
[Defy Android Development] trurl3:
+1

Random reboots & factory reset. For me ROM is unusable...

EDIT: In my case this issue was sourced by problems with /cache partition. From reason unknown (for me) after cleaning caches this partition doesn't want to mount and produce error. After 'three finger salute: (sbf, root, 2ndinit) all is rihgt for now. System works good and is quite snappy. Will see..

EDIT2: On reflection i must confess... likely cause of the problem was cleaning cache in stock recovery...
[Defy Android Development] :
testing latest version everything seems ok,

my only doubt is about BL.. is BL4 good enough for this rom? It doesnt matter? Should I upgrade to BL5 or BL6 or BL7? If yes, which one you recccomend and from which thread? I have nordic sbf and so but cant seem to find the way to upgrade BL
[Defy Android Development] prateekranka:
+1

Any suggestions?