yashsingh1/xdaforums huggingface dataset:
[Legend Android Development] m1schi:
I'm going to update to RC2 in a moment, but I am experiencing problems with Wi-Fi / Mobile Internet with RC1 already. Sometimes it won't change to mobile when going outside the Wi-Fi radius / turning Wi-Fi off.

Going to see, with a wipe, if the problem is gone in RC2 for me :O
[Legend Android Development] lalamaus:
is rc2 the same as the actual nightly build or is the rc2 newer then the nightlys?
[Legend Android Development] Skardy:
Same here (installed from rc1 without wipe), it worked in rc1 :(

Rockplayer finally working :D

No issues with wifi on my legend
[Legend Android Development] ali ba:
RC2 is the newest release you can get. Nightly building is broken at the moment.
[Legend Android Development] Sckank:
Who got the best performance? New HTC's froyo or CM6.1? :-)
[Legend Android Development] g0dshead:
I recon sence consumes more recources , giving that i would have to say cm6.1 has better performance but why not try both and find out yourself:)
[Legend Android Development] tauk2mi:
where can i find the changelog for cyanogen's nightly builds. thanks for your help.
[Legend Android Development] ali ba:
Yes. I included the new libhtc_ril for testing purposes.

My choices are

Break searching for carriers

Break roaming info and MNVO reporting

Because I'm using an MNVO and never search for carriers I went for the 1st option. Data roaming is very expensive and I don't want to watch my device and deactivate it every time I'm near the border.
[Legend Android Development] Catnap:
Gallery app is amazing compared to standard non-nightly rc1. What the hell did you do to it?

Many thanks!
[Legend Android Development] Sckank:
Oh I have indeed. Been using CM for a long time. I think the performance of CM is better. I can really see a differance when I run more apps at the same time. But theres more to it than just that. The wifi, for one thing is better with the new htc rom. Or if you just cant live without FM-radio there's no competition. So thats why I ask what YOU think gives the best performance! ;-)
[Legend Android Development] Messatsu:
Same problem here...had this problem in RC1, now in RC2 ( after wipe ) still the same auto focus problem.

( For example if i'm making a video with cam app and i'm moving my phone, there's a focus every 3 seconds ), don't know if that's normal ?
[Legend Android Development] deimdos:
wiped, fresh install and I still have problems with RC2 status bar power widget, switching from 3G to 2G without problems but from 2G to 3G takes a life to activate data... with RC1 no problems at all

FSM bless Nandroid
[Legend Android Development] beggar23:
So, with RC2 I would not be able to use it abroad? :-(
[Legend Android Development] greenolive:
Notification power widget bug

I 've posted about this before but did not get any response. Perhaps my post was just overlooked but hey, I'm not the one to give up ;)

I can't for the sake of my life get rid of the GPS-switch in my notification power widget. It's there by default and if I actually tick it in the settings, I get two of them. Im going crazy right about now...
[Legend Android Development] Catnap:
Same. Today I took a bunch of clips when out for a walk and just ended up turning the autofocus off in the video options.
[Legend Android Development] snakehult:
Seems that you messed up your romlist on phone.

I suggest that you take look in folders in sdcard an maby delete some that belongs to rommanager, /clockworkmode. DO save your licensefiles :)
[Legend Android Development] snakehult:
pretty cool isn´t it :)

But I am so nice and good looking :cool:
[Legend Android Development] kabler:
Same as most of the folks here - try different roms and give feedbacks. That's the least we could do the help the dev ;D
[Legend Android Development] snakehult:
Absolutely.l ;)

Have you test any "3:e part" version of cameraapps?
[Legend Android Development] Rapier:
Did you wipe before flashing? I was using nighties, than RC1, than nighties again and now flashed RC2. With none I had this problem, I even tried to reproduce it now but for me it works OK.

Also no issues with the camera (as mentioned above). I've tried now to make a film and it works OK... Of course it is auto focusing IF I move the camera. If you have the focus setting set on "auto", "continuous" or "infinity". Set it on "touch", press on the screen where you want to focus, and here we go...no more auto focus during shooting.
[Legend Android Development] Tserppa:
Should I wipe when flashing from nightlies to RC2?
[Legend Android Development] Skardy:
Not if you currently have RC1/recent nightly
[Legend Android Development] Rapier:
Theoretically not...but if you have problems, this could be first option to try
[Legend Android Development] Tserppa:
I'm not having any problems, just thinking about the gallery and it's speed. I'm not experiencing "blazing fast" gallery and just thought should I try wiping and reflashing RC2. Maybe I wipe for the next version.

Thanks.
[Legend Android Development] Catnap:
Well, same... but what use is a video camera you can't move around? That's kinda the point of shooting video.
[Legend Android Development] greenolive:
Yes, I did wipe when flashing rc1 from nigthlies. No wipe rc1 ---> rc2. Problem started with rc1 though and still persists.
[Legend Android Development] tauk2mi:
can someone redirect me to the changelog please? thanks
[Legend Android Development] TheGrammarFreak:
There isn't one for the nightlies. Look at the gerrit review section, and @cmsrc

Swyped from my Galaxy Tab
[Legend Android Development] Rapier:
"Blazing fast" is a relative thing...I'm considering it fast, but I don't know what you will consider. We don't have a way of comparison between our points of view right? For me, gallery is moving OK (I don't know if "blazing fast" is the best description), that means the movements are smooth and instant when I slide that wall for example, or when slide the photos, when zooming and so on. This is enough for me.

Not quite...If you're selecting "touch" as the focus type, you can also move around and focus DURING the movie by pressing on the desired zones. There will be no auto-focus and if you press the screen only once at the beginning of recording, that will be the only focus the camera will have for the whole film...despite your movements. What else do you need, cause I don't understand? You want the auto-focus work but on the other hand you don't want this happen during recording...well then, I don't think that's possible with any ROM. When set to "auto" (or the other "dynamic" modes) the camera will focus as soon as it detects ANY movement. If you want not to do it, just select "touch", that is the "manual" mode.
[Legend Android Development] Tserppa:
Well that's true. I also think it's OK. I just read this thread and someone said it's somehow amazing or blazing.. :D For me the gallery is moving and scrolling fast but I have to wait for the preview pics. But I have to say now that I'm testing this, the gallery is reacting faster and faster. Maybe it takes a bit longer when used for the few first times. Maybe it creates somekind of a cache or something?

Now it certainly is faster!
[Legend Android Development] Catnap:
How about focusing without zooming in and out of the picture?

Don't know about you, but I like things to just work, and work properly. I'm not having a go at the author of the ROM, more venting frustration that all my video clips from one particular day a while back have the zooming in and out effect throughout. Whoever wrote the camera application must have been on drugs.
[Legend Android Development] EnhancerFIN:
Word of a warning, the latest nightly, build 66 caused friend Legend to freeze on the htc boot screen, and not get past that, no matter what. Build 62 worked fine, so leave the 66 uninstalled (or prepare to unbrick your phone).
[Legend Android Development] TheGrammarFreak:
Cyanogen himself wrote that

Swyped from my Galaxy Tab
[Legend Android Development] Rapier:
Then you shouldn't "play" with nighties or RCs...wait for a stable release or switch to stock. Or, if you seek perfection, buy a professional camera instead.

My understanding is that the developers here try to offer us more ROMs to choose from, each having particular settings, apps or godies included...or not. Did you thought that maybe this ROM is not for what you're looking? Also not for FM Radio freaks or profi camera shooting? It's a phone after all for Christ's sake, not a one-thing-perfect-for-all. There are a lot of good (or say better) things in this ROM for many of us, including performance and applications and I'm sure things will go better in time.
[Legend Android Development] ali ba:
You are not able to select the correct setting in a menu so don't expect anyone to feel sorry for you.

Moreover you were using nightly builds (which are clearly labelled as being unstable), so there's no justification for your stupidity.

If you are whining around and insulting people (who do a great job

for free

) like that then I've got one nice advice for you:

Upload a patch that fixes your problems. Or get lost.
[Legend Android Development] Catnap:
Cyanogen wrote the stock 2.2 camera app?

Really? Come on...
[Legend Android Development] TheGrammarFreak:
He wrote the auto focus part of it.

Swyped from my Galaxy Tab
[Legend Android Development] ali ba:
He wrote the fix to use 2.1 camera libraries in 2.2.

He wrote touch-to-focus.

He wrote continuous auto-focus.

He wrote the sliders for image settings.
[Legend Android Development] Catnap:
That's a real nice attitude you have there. I came in here praising the speed of the Gallery app and asking why the video camera keeps zooming in and out, debated the logic in having that setting on by default, and that's stupidity?

Well pardon me. Seems I struck a nerve.

Wasn't whining, wasn't insulting you or any of the other homebrew coders. I assumed (however wrongly or correctly) that the person who wrote the stock 2.2 Android camera app was, you know, from Google. Please do correct me if I'm wrong, because I'm not seeing any evidence to the contrary.

Kindly take a deep breath before replying in a poisoned manner; I and may others are tremendously grateful for the work that you and other people do.
[Legend Android Development] Catnap:
Fair enough, I stand corrected.

Perhaps you'd see fit to disable the continuous auto-focus in a future build?
[Legend Android Development] TheGrammarFreak:
There's a setting...

Swyped from my Galaxy Tab
[Legend Android Development] Catnap:
By default.
[Legend Android Development] TheGrammarFreak:
I doubt it.

To answer an earlier question:

The auto focus changes the zoom slightly because of what focus does: it moves lenses to sharpen the image. In bigger cameras this motion has a very small impact on the zoom, but in a camera this size the motion causes a much larger change in zoom. It sucks, I know.

Swyped from my Galaxy Tab
[Legend Android Development] BlaY0:
@pjgodd: Maybe he will, maybe he won't. Stay tuned...
[Legend Android Development] Catnap:
Thanks for the reply. I'll try to remember to turn that off if I wipe in the future. :)
[Legend Android Development] Rapier:
That was considered to be mostly used. But if your needs are different you can easly change it to "touch" and it'll stay like this.
[Legend Android Development] BlaY0:
Yeah, but he wants it to be hardcoded ;)
[Legend Android Development] Catnap:
Fair point; I'm just viewing this from the POV of usability and "it just works", with the option of fiddling with geeky stuff as we like to do via a menu.

I work for a small IT firm who regularly supply pre-configured PCs with custom software loads on them and if we were to take a step back from thinking through the end-users' eyes, there'd be hell to pay ;)

So yeah, I guess from my POV, I see things from a "works out of the box" perspective, rather than "needs some fiddling".

Do hope I haven't ruffled too many feathers today.
[Legend Android Development] TheGrammarFreak:
You're not a part of XDA until you've ruffled feathers. :P
[Legend Android Development] ali ba:
OK. Back to topic, now that we've all agreed on the fact that there are people who don't want to change settings to their needs because it should simply work the way they want.

Searching for networks with newer libhtc_ril.so should be fixed soon. I've got a patch done, it only needs to be uploaded and reviewed.
[Legend Android Development] Rapier:
Just one, small amendment...nobody's paid here. Considering this, I think we can make the little effort to tweak the settings by our needs.

Great news Ali ba, that is indeed needed. It'll be released through RC3 then or it'll be included in the nighties as well?
[Legend Android Development] norashers:
[OFF TOPIC]

Sadly there's an inconsistency in your logic, flashing roms and using nightlies are inherently "geeky". Arguing that it might be a non-optimal configuration is a different argument; and one which may be valid. However I have no measured opinion since I don't use the video camera.

[/OFF TOPIC]

[ON TOPIC]

Interesting, does that enable channel/frequency detection? I noticed with the current version I'm unable to distinguish channels. Only distinguish mind you, wpa_supplicant is still happy to connect me to my router no matter the set channel.

[/ON TOPIC]
[Legend Android Development] Catnap:
I never stated I didn't consider myself geeky though, did I? I kinda wouldn't be here if that were the case. There's no harm or crime in striving to be better than the next.

That was precisely my point.
[Legend Android Development] Catnap:
Fixed that for you. I honestly can't understand why you're so upset about this. Surely end-users providing feedback is a good thing, no?
[Legend Android Development] Baanbi:
Hi all,

i have a problem with the last nightly version. When i install her on my legend, my phone stay on HTC logo when i power on my device.

Can you anwser me about how install correctly this rom ?

Thank you.
[Legend Android Development] ali ba:
GSM network is not WLAN. They use different drivers, firmware and software stack.
[Legend Android Development] Rapier:
Could you tell more details? From what ROM you've migrated, did you wipe before? Also have you read the previous posts in this topic? There was someone getting our attention that build 66 may brick our phone. Is this 66 what you've flashed?

Also ali ba stated one day ago that nighties build is broken...don't know if it's fixed already
[Legend Android Development] ali ba:
Don't use nightly builds if you are not able to fix such problems yourself. You should know that. It's written everywhere. Several times. And repeated in every board that offers links to nightly builds.

Once again, to make sure you understand the importance of that statement: Don't use nightly builds. They are not made for end-users.

RCs are unstable too, but tested on at least one device. If you are smart then you don't even use RCs. I know you guys always want the latest and greatest stuff but you always forget that those releases are unstable. And full of bugs.

You have been warned (again).
[Legend Android Development] norashers:
Sorry, I thought the drivers were for wifi. I am well aware of the differences between gsm/wlan hardware/software, but not the naming system of gsm drivers.
[Legend Android Development] ali ba:
libhtc_ril.so: http://en.wikipedia.org/wiki/Radio_Interface_Layer

It's not that far fetched to assume you confused GSM and WLAN because that's what 20 users already did in this thread.
[Legend Android Development] kugel.:
with blazing fast gallery I meant that the speed of thumbnail loading isn't a PITA anymore (it's now comparable to the speed of the stock gallery, I.e. a set of thumbnails now loads within 3 seconds), while it previously took a couple seconds *per* thumbnail and half is them didn't load at all. same situation with viewing photos.

this is my experience.its entirely possible that the gallery always worked fine for you(or still doesn't) so you don't feel the difference.
[Legend Android Development] Sckank:
I think its just fun to try out all this firmware and talk about'em. And the RC releases are surprisingly stable and bugfree. And if there's bugs in them, I must say of kinda gives me a trill. :-) Damn am I geeky or what?!?!
[Legend Android Development] norashers:
I didn't notice the ril while reading on my phone; not that it's really important in the scheme of things.

Thank you.
[Legend Android Development] copponex:
Please release an official something something soon :(
[Legend Android Development] ricky007:
I have now tried nightly build 44 & 48, RC1 & RC2 and i still cant get the wifi to work. Im now using Azure 1.01 and it works.

As i wrote earlier it tries to connect to my router and then disconnect over and over again. The problem is not my router becouse it disconnect even if i dont chose i wifi to connect to.

Yesterday i tried whitetigerdks froyorelese and the wifi worked perfectly.

Is there anyone who knows a solution for this problem?

I love the rom and all the work on it you guys do so i would like to keep using it.
[Legend Android Development] Neon87:
Same problem here.. solved with a wipe.. you have to know that google save ap information (online?) and so you have to uncheck the backup checkbox during first boot, after the wipe.. you have noticed that if you wipe the password remains?
[Legend Android Development] ricky007:
Thanks for the quick reply but i always wipe data/factory reset and cache before installing from sd.

I use cyanogenmod recovery when i do it and not the rom manager if that make any difference.
[Legend Android Development] Rapier:
Did you check the no of channels to use? Some routers have by default 13 and I saw in CM that was set on 11. If your router is set on channel 12 or 13, it won't connect
[Legend Android Development] ricky007:
I have tried that as well with no luck.

But i dont think the problem is with the router because when i turn wifi on it scan for wifi and then suddenly it disconnect, in a few seconds it start to scan again and then disconnet and thats before i even choose i wifi
[Legend Android Development] le_dek:
Same problem for me :(

The Wi-Fi is perfect with Azure, but unusable in CM6.1 RC1/2.
[Legend Android Development] pik1:
i have...

...no problems at all with my legend.

thx for the great work!
[Legend Android Development] kugel.:
Is that a WPA 2 enterprise network? I'm having problems with these as well (e.g. eduroam). if yes, you need to delete the configuration for it and re-add every time it disconnects.
[Legend Android Development] Sckank:
WPA working excellent here
[Legend Android Development] le_dek:
WPA2-PSK on a WRT54G which runs OpenWRT.

(I think it's tuned on channel 11, I'll check tonight)
[Legend Android Development] BlaY0:
This is wpa_supplicant.conf example for EDUROAM network here in Slovenia:

network={

ssid="eduroam"

proto=RSN

key_mgmt=WPA-EAP

group=CCMP TKIP

eap=TTLS

identity="***@mf.uni-lj.si"

anonymous_identity="anonymous@mf.uni-lj.si"

password="******

ca_cert="/data/misc/wifi/ca_mf.der"

phase2="auth=PAP"

}
[Legend Android Development] Justinvanorsouw:
First time poster!

Thank you all for all the fun i got from playing with the Legend.

I am also getting the same issue after installing the 66 and also the 67 build.

This was no clean install, but that wasnt an issue before.

Ive installed build 67 today and it is possible to connect with a shell to my phone. So ive attached a bugreport to this message to help analyse.

It appears the following message error causes my hang:

Unable to dlopen(/system/lib/libandroid_servers.so): Cannot load library: link_image[2033]: failed to link libandroid_servers.so

The same error is described on the following page, but im not sure if it helps.

http://xdaforums.com/showthread.php?t=704561&page=6

Regards,

Justin
[Legend Android Development] Rapier:
Justin, maybe you missed the first post in this thread. Allow me to remind some parts of it (quoted from that post), mostly the bits in red:

That is, don't know if your bug report will be good for something. Maybe just to be considered in a stable release
[Legend Android Development] Justinvanorsouw:
Fully aware of these guidelines, just was replying to an earlier post reporting the same symptom.

And as we are all trying to support the development process of this nice mod, I would just like to enhance the awareness of possible issues.

Regards,

Justin
[Legend Android Development] TheGrammarFreak:
It was probably one of the more constructive posts.

Swyped from my Galaxy Tab
[Legend Android Development] maximus1965:
do this:

http://xdaforums.com/showthread.php?t=719164

(Darktremor)

work on CM 6.1 RC2 ?
[Legend Android Development] TheGrammarFreak:
If you want apps2ext do this: http://krikun.ru/en/2010/10/28/app2sd-for-cyanogenmod-6-x/

Your phone would perceive the ext partition of the SD card as internal memory, so when you move the apps to the internal memory they are in fact installed on the SD card
[Legend Android Development] maximus1965:
ok, thank you, i will try this tomorrow.

I have to flash both files, if i want to move the dalvik-cache and the apps ?

cm-app2sd

cm-app2sd-dalvik
[Legend Android Development] le_dek:
So, my AP was broadcasting on channel 9, I've changed it for channel 11 without any effect : with RC2 I can't connect to it.

I've also tried different things in Wifi advanced settings and in proxy settings (on the phone), unsuccessfully.
[Legend Android Development] ArchiFleKs:
Hi. Did someone manage to run builds 66 or 67 ? I got stuck in htc bootscreen too.
[Legend Android Development] greenolive:
What are your recommendations on partioning the sd-card?

Minimum/maximum and so on?
[Legend Android Development] gyroing:
cm-app2sd-dalvik is for both.
[Legend Android Development] maxq1:
er..i use dt's (darktremor) apps2sd on b62. been using it since azure actually. i have my 8gb sd broken down to 512mb ext3, rest fat32. moving apps and davlik to sd just requires issuing out commands from terminal. cl4 & up sd is required though
[Legend Android Development] maximus1965:
Thanks, i will try it as soon as i get my new transcend 16gb class 6 sd card.
[Legend Android Development] plicto:
I'm wondering if anyone else notices that Launcherpro isn't working very well with the rc2-release?

The problem is that 3d app drawer simply doesn't work (it is as though it doesn't register touches correctly) and the usual app drawer seems incredibly choppy. It doesn't matter if I wipe or not.

Has anyone else experienced the same thing?
[Legend Android Development] beggar23:
Nope. Seems to work well at my RC2.
[Legend Android Development] torrre:
I have the same problem with RC2 and launcher pro.

Nightlies -> wipe -> RC1 -> no wipe -> RC2.
[Legend Android Development] qzem:
Yes me too, but I did wipe when going from RC1 to RC2
[Legend Android Development] Westi01:
I have exactly the same problems. With wipe from RC1 to RC 2 and without. I am now using normal drawer. Not the 3D one. This works well.
[Legend Android Development] xryan007:
Quick question, has anyone noticed that with this rom that they do not get a notification of receiving a voice mail? I get a text message, but not a notification in my notification bar...

Just wondering if I'm alone..

thanks!

Ryan

EDIT: to be clear by "this rom" I meant either nightly 34 or 41. I'm pretty sure I had this in the azure stable as well. I just happened to notice this today. I am not trying to ruffle feathers.
[Legend Android Development] AllWin:
I can't answer to your question since i'm not using voice mail at all, but i believe that many things has been changed since v41... Current "Nighly" build is marked as v68. Go with the times ;)
[Legend Android Development] xryan007:
Yes, well aware of that :p I am going to try RC2 now. I was just curious if it was only me.

Thanks for the reply.
[Legend Android Development] speedyink:
Build 68 doesn't boot for me at all, just stuck at htc screen. No wipe from RC1
[Legend Android Development] xryan007:
Update if anyone is curious too.

Just tried RC2. Same thing :( Bell shows the text for the VM being delivered to my phone, nothing shows up though on my end. All other text/data services work great.
[Legend Android Development] thejust:
Same here using rc2 no voicemail notification