yashsingh1/xdaforums huggingface dataset:
[Legend Android Development] gyroing:
When some user same as me had problem for booting developers prepared new "testboot.zip" , this boot had been reduced the size of boot.img and have 2 module for aufs.ko & cifs.ko that each one bigger than 2 MB & 3 MB but in B39 both of the boot.img & modules size reduced . what items in B39 are removed? is it aufs.ko & cifs.ko? these module are updated as testboot.zip do? :confused:
[Legend Android Development] oysteivi:
39 runs perfectly for me, just as 35 did. Had to wipe when flashing from azure to 35, or gapps wouldn't work properly on first startup, but I guess that's to be expected.

I've noticed some increased battery drain lately, but for my part it mostly seems like the battery drains faster if I play Angry Birds compared to when the phone is in my pocket with the screen off ;)
[Legend Android Development] Sckank:
Testing it now. Seems like I finally can put away SuperFroyo :-)
[Legend Android Development] qzem:
Anyone tried overclocked build 39? I did with dumfuqs oc kernel v4.0 with 768MHz, but my system always stops responing when desktop lunches. It strange casue it worked on previous builds. Now I tried to overclock it with v3.5 same frequency, and works.
[Legend Android Development] HpX:
im useing dumfuqs oc kernel v3.5 787MHz, works good for me.
[Legend Android Development] TheGrammarFreak:
Ah, but V4 is where it's at. Lol
[Legend Android Development] HpX:
Well i dont see the point in switching to v4 when 3.5 is working gr8.. and if u read a few posts over, somone had a issue with the v4 on B39..
[Legend Android Development] TheGrammarFreak:
I know. We were told that everything stops when the desktop has lunch.

Swyped from my HTC Legend
[Legend Android Development] BlaY0:
Well, why R U guys even bother to use dumfaq's kernel with nightlies? His frequency table was pulled into CM Legend's kernel source anywayz! As if U would buy a brand new Peugeot 207 and then install engine of 206 into it...

Sent from my HTC Legend
[Legend Android Development] Knight77:
Please can anybody answer to this? Thanks
[Legend Android Development] ArchiFleKs:
Sorry but could you be more specific about why it's not necessary to use the dumfaq's kernels ? The nightlies are not overclocked by default, are they ?
[Legend Android Development] Badger2point0:
Running 39 with 806OC and getting great battery life. Made a 2h21m call and only drained 13%, much better than what I was getting previously.
[Legend Android Development] andrekua:
I've revert back to B34. It seem like the battery drain is more severe than initially thought.

1hr from power-up and with some light surfing, battery drain was a staggering 25%. I did not wipe, as I did when upgrading from RC1 to B34.
[Legend Android Development] kabler:
People won't bother or entertain this kind of basic question when you're in fact trying to run nightly. You're considered to have already covered the basic stuff like flashing nightly update/rom when you join this thread.

Read 1st post for do's and don't's.

Just my 0.02.
[Legend Android Development] qzem:
Well first a question, is there anything special I have to do, to use higher frequency? Like put some command with adb shell into some files. I use SetCPU, and set it on 768. Then run a Quadrant test, and nothing has changed. Ali ba said that legend is still locked on 600. With dumfuqs kernel everything runs smoothly, and like someone else mentioned, I get longer battery life too.
[Legend Android Development] liltbrockie:
I'm getting force quit on the mail app when trying to forward messages. (Exchange active sync, build 40)
[Legend Android Development] BlaY0:
The nightlies kernel can go straight to 864 MHz coz it uses the same frequenc table as dumfaq's. U just need to set that in SetCPU.

Sent from my HTC Legend
[Legend Android Development] Sckank:
I have great battery life too. 5h running, 10-12 sms, 15min online, max br/con screen, and still got 95%. 804mhz OC and 245 standby.
[Legend Android Development] ali ba:
Not that I care too much about what you do with your devices, but I'd advise everyone not to flash that update.

As gyroing said, the difference is tiwlan.ini.

I took a look at this file and it's clear that it was certainly not made for the 1273 used in our phones. You can tell that for example by the fact that it enables 802.11n.

I'm using the proprietary files that can be found in the 2.10 updated released by HTC. So if you really want to test then take the 2.06/2.05/2.03 update and copy the files (tiwlan_drv.ko, sdio.ko, tiwlan.ini, Fw1273_CHIP.bin) from them.

There are differences between said releases and files and there might very well be a setting (like desiredPsMode or QOS_wmePsModeVO) that affects performance for you.

I did not pull any tables from dumfaq. If I had done so I would have given credit. I do not copy the work of others and label it as mine. In fact I cherry-picked the updates from the espresso kernel (committed by Steve Kondik).
[Legend Android Development] BlaY0:
I don't actually care who was the first who constructed the table itself and I don't care whos credits are for that, the fact is it's the same table.

Sent from my HTC Legend
[Legend Android Development] :
B39 keeps boot-looping on me, any time I try it...
[Legend Android Development] deimdos:
You definitely shouldn't be thinking of messing with this stuff before reading/learning something more about this like you were told before.

Of course you can flash this ROM as any other ROM, but keep in mind that it's still an alpha release ;)
[Legend Android Development] maxmax0:
We don't really care whether you care, but if you start spreading bull**** about who copied what you can expect people to set you straight, and quite rightly so.
[Legend Android Development] andrekua:
B39 would appear to be the most zippy rom I ever used, but its definitely not stable.

I ran into some trouble with Gallery crashing everytime with live wallpaper on, kaki memo stop working correctly and severe battery drain.

B40 is out and waiting...
[Legend Android Development] ali ba:
Absolutely true.

That community thing can only work if we give credits. If someone practically says I'm not doing so then I have to correct that. This is very important to me and I'm not going to insult people who are doing a great job by copying their work and saying it's mine.

Background info:

Steve added the frequency tables made by dumfuq and the corresponding commit message for the espresso device target reads "Disabled perflock, added Dumfuq's OC patch (864MHz). No OC by default.".
[Legend Android Development] JonasDroid:
B40 is working great for me.

Until I was so stupid to set the clock speed to 864 and didn't uncheck the set on boot causing a freeze and I wasn't able to get back in the settings without my phone freezing.
[Legend Android Development] Sckank:
More ppl tried out B40? :-)
[Legend Android Development] marclh1992:
Is it not possible to have the custom notification bars? I'm not a fan of the stock one.
[Legend Android Development] kabler:
1 here, already running for 1/2 a day.

Running stable so far, 787MHz. Linpack and Quadrant scores are as good as build #33 I used previously. Battery life I cannot tell the difference yet, might need a couple more days of observation :)
[Legend Android Development] Sckank:
Sounds very good indeed :-) Please keep us updated?
[Legend Android Development] TheGrammarFreak:
What's with the question mark? "Please keep us updated" is a statement. The question would be "could you keep us updated?" :D

Swyped from my HTC Legend
[Legend Android Development] Sckank:
Thanks for the grammar correction :-) I will try to express myself in proper form in the future ;-)
[Legend Android Development] BlaY0:
So all of a sudden it is so damn important whether Steve or Alex made that commit but nobody except me is telling ppl how to set it up and how to use it. Every now and then there is someone coming here who obviously needs to remind ppl whos work is what and tell them they should be grateful. That's actually very egocentric and doesn't really fit OS scene. So better care to teach ppl how these all work and not to beat your chest too often...

Sent from my HTC Legend
[Legend Android Development] BlaY0:
Care to read my statement again? Where exactly did I write that U pulled that table into Legend's kernel source? U wrote U didn't pull it (don't know why it was so damn important to expose that) and I wrote I didn't cara who did o didn't pulled it, just that it was there and it was being used and more important (latter on) how ppl could have used it. But U didn't care about that, U just ripped my post of an actual context and drove ppl's attention somewhere else...

Sent from my HTC Legend
[Legend Android Development] maxmax0:
Well Ali set that straight as far as I'm concerned, so whatever, dude.
[Legend Android Development] TheGrammarFreak:
Enough! It really doesn't matter guys. :D

Swyped from my HTC Legend
[Legend Android Development] Sckank:
Agreed! Guess the buggy night-builds makes us frustrated.
[Legend Android Development] JonasDroid:
Back on topic. Anyone who knows if the framework-res changed since B26?

If I knew how to compare it I would check it myself but I'm still a noob trying to learn as much as I can.

EDIT: They are both 2.100.834 bytes Guess they are the same :p
[Legend Android Development] Sckank:
How does B40 feel do far?
[Legend Android Development] maxmax0:
Hey, they are not that bad, not at all. Well at least not for me :D

But still, I can't wait to get my hands on 6.1 :D:D
[Legend Android Development] HpX:
Just an update on the B39. I have now used it for a while and have not yet had any problems with it. When it comes to battery consumption, I think it is not too bad. Screenhot is from a full-day use.

Translation from Norwegian

Skjerm - Screen

Telefonsamtaler - Phone Calls

Trådløsnett - Wireless Network

Cell-Standby - Cell-Standby

Telefonen ikke i bruk - Phone is not in use
[Legend Android Development] norashers:
There is no need to be so rude. If you had read carefully everything instead of shouting off mindlessly you would see Blay0 is indeed correct.
[Legend Android Development] maxq1:
@ alex/all other gods here...

from what i've searched here so far, seems cm6 (both stable & nightlies, i guess), as is, does not support ext partitions. if this is correct, please continue on...otherwise, anything from this point is junk :o so kindly disregard

would it be possible to integrate the script/s (or any other thingies) from the attached file to cm6 (nightlies and future builds) for legend? the objective would be to have native support for ext & swap partitions on sd.

i've tried the said file on azure 1.0.1 (w/ the intention of installing dt apps2sd and Blay0's system overlay, both of which need an ext3 partition for other functionalities - such as moving both dalvik-cache & system overlay to sd). everything works, including apps2sd & overlay! now i've got about 160mb on internal even with so much stuff installed on my gizmo (<-- Blay0's term :D ; > 'device')

if it helps, my gizmo setup: azure + dumfuq's 3.5-825 oc kernel w/ class6 sd (512mb ext3, no swap, rest fat32)

NOTE: can't remember where i got the attached file. if you're the author, kindly advise so proper due can be given.
[Legend Android Development] CfYz:
B40 here, no problems so far, installed with full wipe. After setting two profiles in Setcpu (profiles mentioned earlier here) battery life back to normal, at least in feeling of use.

And if I'm not wrong - gapps was included in B40(?)

Huge thanks for CM Team! Again :-)
[Legend Android Development] Sckank:
Sounds good! Any rumors about RC1?
[Legend Android Development] BlaY0:
Basically it is not correct. As you can see from Legend's default kernel config ext[23] are supported by default.

It is possible. It is plain shell script that mounts ext partition. But this actual script U attached might and also might not work. Actually there's a possibility that script won't find any ext partitions. Why U ask? Because it first creates block device files in /dev and just right after that it wait for them to appear. But since the script just created them, they are already there (the dev files) but actual devices weren't attached (by kernel) just yet. They might have been attached if you have fast sdcard, but slower cards are available (initialized by kernel driver) only after 2 to 3 seconds and by that time this script would be long finished. What I would do in this case is removing those mknod commands from script alltogether.

But since you are using dt app2sd and overlay scripts you actually don't need this one because earlier ones do exactly the same job.
[Legend Android Development] maxq1:
now i'm confused :eek: how is it w/ a clean install of azure, i get a blank sd or unrecognized format on my notification bar even with my sd partitioned (in every way possible, CW recovery, standard 'droid recovery or parted) w/ ext3 prior? pulling my sd & checking it in linux confirms i've still got my partitions right though...after flashing said file, like i said, got my gizmo to recognize ext3 then proceed w/ installing apps2sd & your overlay
[Legend Android Development] maxmax0:
By now everyone made their point regarding this topic, so there is no value add in discussing this further. Let's get back on topic.
[Legend Android Development] maxmax0:
After some testing with #39 I can confirm it runs very smoothly indeed. Great job! :D
[Legend Android Development] BlaY0:
@maxq1: By supported it means kernel has the right drivers to recognize these file systems. It doesn't mean that framework would mount them on its own. Framework only mounts first partition and this partition should have fat32 files system on it.
[Legend Android Development] Skardy:
http://forum.cyanogenmod.com/topic/8455-when/page__pid__82944#entry82944

RC1 will officially go out later today

I'm so happy :D
[Legend Android Development] liltbrockie:
http://forum.cyanogenmod.com/forum-112/announcement-5-61-release-candidates/
[Legend Android Development] liltbrockie:
I have a question... is the nightly builds that I have been installing recently..(B39, B40, B41 etc etc) anything to do with 6.1 RC or are they still the old 6.0 ?
[Legend Android Development] JonasDroid:
RC is a Release Candidate. CM6.0 is already stable.

It's a Release Candidate for CM6.1 it will be based on the nightly builds
[Legend Android Development] b4bass:
Is the curent nightly fixing things for 6.1 rc2 or its a different branch.

I just like to find the most stable 6.1 based rom.

Thx
[Legend Android Development] maxonite:
Sweeeeeeeeeettttt! Bring on RC1.
[Legend Android Development] ali ba:
I don't know what you all are expecting or why you are so excited.

RC1 won't be any different from the nightly builds. So if it is built today then it's basically nightly build #41.
[Legend Android Development] liltbrockie:
I think the people who are getting excited are the people who haven't been risking the nightlies?!
[Legend Android Development] kuklux:
build 41 is ready now downloading
[Legend Android Development] curto:
oi ali ba man i just got onto these nightlies and omg man after using this one uhh whatever it is the nov 2nd one, yeah its f%^$@!# awesome!! just wanted to thank you for your hard work. it seems perfect and so fast! i love everything about it. i got something like 1064 in that quantum whatever benchmarking thing compared to the usual of like 300 - 400. cheers mate
[Legend Android Development] BlaY0:
It's because nobody obviously never explained to them that Alpha7, Beta3 or RC1 are or were all basically nightly builds. CM 6.1 will also be a nightly build. It's a simple rule of declaration... devs can declare nightly build #67 to be RC2 because it fits the profile of stability for RC2.
[Legend Android Development] maxonite:
I get excited because nightlys keep getting new features, which in turn can bring new bugs. In theory RC1 is feature frozen and we can hope for bugs to be progressively fixed.

Is that a wrong assumption?
[Legend Android Development] BlaY0:
Nope, it is not.
[Legend Android Development] ali ba:
For a project like Firefox for example this would be correct but in CM all changes are on hold until 6.1 is out officially. The only commits that are merged now are bug-fixes and translations. So the feature freeze also affects the nightly builds, as there is no master branch.
[Legend Android Development] maxonite:
Ok,

So in the nightly a little while back, 30 something when you changed the kernal to remove perflock or whatever cool thing you did, is that not classed as a feature?

I take your point though, and have been happy with the nightlys, I guess it will just be nice to have the official rubber stamp :-)
[Legend Android Development] ali ba:
That was a "bug-fix". :D

No, a few features were already tested quite well and then merged (which in fact breaks the code freeze).
[Legend Android Development] maxonite:
Cool, thanks for setting me straight, keep up the good work :-)
[Legend Android Development] grandioso:
I haven't been following this thread so far. Could anyone help me catch up ? What's new in azure compared to 1.0.1 ? When is the next stable release coming out ?

Sent from my Legend
[Legend Android Development] nbite:
Hello devs! i have been using nightly since v27 and id like to say that since build 38 everything seems to be more or less stable. 3g and wifi seem to be working ok now, no random reboots and although i had some issues with music-player (right channel stops working with equalizer), but after skipping few tracks or selecting new file, or unticking equalizer everything is back to norm. And to talk about the quadrant score.. :)

Updating to build 41 now. Thank you for your tremendous work!
[Legend Android Development] gyroing:
B41 works great . but if i want speed more than 600 mhz what is the best clock speed considering perfomance of device?
[Legend Android Development] nbite:
768 seems to be perfect for legend
[Legend Android Development] TheGrammarFreak:
I'd say 787
[Legend Android Development] xryan007:
I've been running 806 for 2 weeks just fine also. I'm not saying i'm right.. but that is my personal experience.
[Legend Android Development] xcrew:
Been using 844 since it came out without problem.
[Legend Android Development] qzem:
I don't think so, my legend can't handle this frequency and there were others having problems too. But 768Mhz seems to be the one that can be handled for sure.
[Legend Android Development] nbite:
mine hangs occasionally on 87, 68 is perfectly stable. I think it goes for most legends, more than that should be benched before used. Besides, what does extra give u? Just a bit more battery drain imo.

Also i tested on one of the nightly those two kernels and i get less score on 87... :S

Please pm me if any help with cyanogenmod is required, i want to offer my help anyway i can.
[Legend Android Development] slovenec88:
How long your battery lasts with that kind OC?
[Legend Android Development] kuklux:
806 works fine for me...whats diff. Between dumq oc 806 v3.5 and b41? Dumq run interactive
[Legend Android Development] TheGrammarFreak:
1, maybe 2 days. Depends what I do with the phone
[Legend Android Development] JonasDroid:
Why is everybody giving a specific frequency? It depends on the chipset.

Just try it out with SetCPU (but be sure to uncheck set on boot)

See what is the stable for you and I like to pick one less then the one that's stable I'm running 806 I can run 825 without problems(tested for a day) and I can run 844 for a benchmark but it'll freese or reboot after a while.
[Legend Android Development] nbite:
because flashing oc kernel is easier than testing, and benching and getting there yourself
[Legend Android Development] JonasDroid:
Why would you flash an OC if your using build 41? preflock has been disabled since b30 or so. I think installing SetCPU is quite a bit easier then flashing an OC (which is an older kernel)

EDIT: the CM kernel even uses the same frequency table (that's where all the hustle was about a few posts ago)
[Legend Android Development] nbite:
i never said im using it now. Although i did on earlier nightlys and it did give 200+ more score in quadrant. But why would i need that extra, it doesnt give me any advantage. So i use stock.

Was talking about the majority mainly, and why it is (seems to be) easier in general. Sure installing SetCPU aint hard, but that's not all u have to do, right?
[Legend Android Development] Phycopat:
any1 else have problems with GPS??
[Legend Android Development] xryan007:
You should probably include the proper information. You may also want to read the first post.

I am using nightly 34, GPS is working just dandy for me.
[Legend Android Development] oysteivi:
Perhaps a stupid question, but does the power drain increase for every frequency step upwards? Is there any way I can know by how much without disassembling the device? Anywhere I can read up on this? I tried searching, but came up blank -- I guess qualcomm doesn't hand out that sort of information unless you're planning to buy a few thousand units..
[Legend Android Development] Phycopat:
Sorry...

Using nightly 41.. GPS is the only thing i'm missing ? Cant find anyplaces to turn it on ?! Did make WIPE before install like allways..
[Legend Android Development] deimdos:
of course the more the "power" (frecuency) the less the battery life... 1+1=2, on the other hand I don't think there's a stay-in-one-piece way to measure processor consumption in our phones.
[Legend Android Development] kugel.:
The calculation is not that simple. it depends on the governor and how often you actually run at that frequency. Eg I set the ondemand governor so that it only runs and full speed of it really needs to. Also if the phone can sleep more often and longer because tasks are completed more quickly you could even end up with better battery life.
[Legend Android Development] norashers:
One way to check power consumption is to use battery graph from the market. That can record the battery charge over a day or two. Then compare different frequencies. It can also export the data so you can look at the first derivative for the power consumption.
[Legend Android Development] suilow1991:
hi, so flash OC kernel or use SetCPU? which one has advantage as it's quite trooublesome to flash the OC kernel after flashing an update everytime but some replies that there are some problems regarding SetCPU. Can anyone help me clarify this?
[Legend Android Development] andrekua:
It seem like I'm getting very good battery drain on b41. What did they do?

With b39, its really bad. With b40, better but b41 seem to be the best.
[Legend Android Development] Sckank:
41 is good indeed :-) But what about 42? =-O
[Legend Android Development] BlaY0:
42 is, as we all know the answer to the ultimate question of life, the universe, and everything. And you should know that to :D
[Legend Android Development] knsai:
updated to b42. battery drain seem better in b41. and I am having this problem in b42, no more multi touch for me. anyone else having this problem as well or is it just me.
[Legend Android Development] Sckank:
Damn thats true! :-D Lets see if The Guide hits the target! ;-)
[Legend Android Development] Likemike24:
I always get a FC with B42 when starting Gallery und LWP on.
[Legend Android Development] liltbrockie:
I don't have that problem.
[Legend Android Development] andrekua:
I never really tried LWP until b39 and the gallery FC everytime I had LWP on.
[Legend Android Development] grandioso:
So is there anything new compared to 1.0.1 stable except perflock ?

Sent from my Legend
[Legend Android Development] Corra:
my legend automatically activates usb file transfer from sdcard when connected to pc. This is quite annoying. I'm using #40, anyone are experiencing the same issue?
[Legend Android Development] slovenec88:
Do you have winamp installed? That is function of winamp or maybe some other program..
[Legend Android Development] ali ba:
Are you seriously asking that question?

https://github.com/CyanogenMod/android_vendor_cyanogen/blob/froyo/CHANGELOG.mkdn

Or look at all the tweets since mid August. You could call this a Changelog too.
[Legend Android Development] Corra:
you're right!! tnx