yashsingh1/xdaforums huggingface dataset:
[Legend Android Development] qzem:
@ali ba

Here is the answer from mikereidis, when I asked him about putting BT to deep sleep mode:

I hope this will help yothat some in any way, so that some battery power will be saved, while listening FM radio. :)

EDIT: One little suggestion from me... I think it would be practical, if bluetooth would enabled itself automatically when fm radio is turnd on, and disabled autiomatically, when it is turned off.
[Legend Android Development] jaStrom:
That feature already exists. Hit the menu button to change the settings for the radio. You'll see that you can configure bluetooth behaviour to stop when you've disconnected headphones or when you've hit the power button (on the right) in the app.
[Legend Android Development] qzem:
Oops, didn't know that:confused:
[Legend Android Development] ali ba:
I know that this "solution" exists, but I'm not going to implement that. Try to think about whether you'd want a control delay of several seconds in FM app. I certainly don't but I don't use FM radio anyway.
[Legend Android Development] qzem:
Damn it I'm useless. I am still searching and trying to figured out if there is some better hci command. I found this code from BRF chip which is should be the same as TI WL1271 on this link.

/*
* This function is called twice.
* The first time it is called, it loads the brf script, and executes its
* commands until it reaches a deep sleep command (or its end).
* The second time it is called, it assumes HCILL protocol is set up,
* and sends rest of brf script via the supplied socket.
*/
static int brf_do_script(int fd, struct termios *ti, const char *bts_file)
{
int ret = 0, hcill_installed = bts_file ? 0 : 1;
uint32_t vers;
static FILE *brf_script_file = NULL;
static uint8_t brf_action[512];
static long brf_size;
static uint16_t brf_type;

/* is it the first time we are called ? */
if (0 == hcill_installed) {
DPRINTF("Sending script to serial device\n");
brf_script_file = bts_load_script(bts_file, &vers );
if (!brf_script_file) {
fprintf(stderr, "Warning: cannot find BTS file: %s\n",
bts_file);
return 0;
}

fprintf( stderr, "Loaded BTS script version %u\n", vers );

brf_size = bts_fetch_action(brf_script_file, brf_action,
sizeof(brf_action), &brf_type);
if (brf_size == 0) {
fprintf(stderr, "Warning: BTS file is empty !");
return 0;
}
}
else {
DPRINTF("Sending script to bluetooth socket\n");
}

/* execute current action and continue to parse brf script file */
while (brf_size != 0) {
ret = brf_do_action(brf_type, brf_action, brf_size,
fd, ti, hcill_installed);
if (ret == -1)
break;

brf_size = bts_fetch_action(brf_script_file, brf_action,
sizeof(brf_action), &brf_type);

/* if this is the first time we run (no HCILL yet) */
/* and a deep sleep command is encountered */
/* we exit */
if (!hcill_installed &&
brf_action_is_deep_sleep(brf_action,
brf_size, brf_type))
return 0;
}

bts_unload_script(brf_script_file);
brf_script_file = NULL;
DPRINTF("\n");

return ret;
}

And now I won't bother you about this any more:).
[Legend Android Development] TheGrammarFreak:
With regard to bluetooth deep sleep:

An app knows when it's in the foreground right? Would it be possible to make it so it "deep sleeps" when the app is in the background (or when the screen is off) and then awaken it when the app becomes active. As opposed to deep sleeping on after every command.

Another thought strikes me as I write this: have a button for it. Then the user just says "I'm gonna have this station of for a while, so there's no point in having the Bluetooth running"

Of course, I could be talking utter rubbish here (I fully expect that I am).
[Legend Android Development] HpX:
Wont be the First time TGF :p
[Legend Android Development] stiffmast3r:
installed CM7 RC2 and fight with big lags, broken SD (no, its not really broken, CM says...), Quadrant Score 650?

using 8gb SD class 6, once with data2ext, big lags, no without data2ext, lags again. i have ~500pics on my sd, need 10 minutes to load it.

there are lags in all menu´s, contacts, homescreens, just everywhere.

whats wrong?
[Legend Android Development] entropicamente:
It's a known problem, search this thread. Latest nightly works better...
[Legend Android Development] stiffmast3r:
found no informating things.. maybe my search is fail....
[Legend Android Development] speedyink:
Pretty much in RC1 and RC2 you'll find the system process pegs the cpu at 100%. You'll also find the other side effect of it making your battery life garbage. As mentioned the nightlies haven't had that for some time now. Either RC is in no way a true release candidate.
[Legend Android Development] stiffmast3r:
ok, thanks for answer. i flashed a nightly, and its very smooth and fast, like it.

but now, next problem:

screen off animation dont work :/

i tryed a few restarts, checking the boxes on and off, but i have no success...

any ideas?

-EDIT-

solved: spare parts -> window animation -> fast -> screen off is NOT working.
[Legend Android Development] Westi01:
Hey Guys,

I was wondering if there is a way to change notification profiles at a specific location (Work/Home). I read that there is an api for locale and tasker available but I can't find options in these two apps for that.
[Legend Android Development] qzem:
Haven't tried the latest nightlies, so I wonder if FM radio app was already modified for mdpi devices?
[Legend Android Development] namtrac:
Yeah it works fine.
[Legend Android Development] qzem:
I know it works, I was asking about the look of the app, cause it was designed for devices with HDPI display, but legend has MDPI. One more thing I've noticed that Andorid 3.0 SDK is out, does this mean Cyanogen mod will now started to work on this version, or is 3.0 only for tablets?
[Legend Android Development] namtrac:
Sorry for if it was unclear, the gui is ported to MDPI. And yes, Android 3.0 is a tablet-only OS confirmed by Google.
[Legend Android Development] TheGrammarFreak:
Given the number of emulator ports for devices including, but not limited to, the Nexus 1, Desire, Desire HD, Wildfire, G1 and Magic, I think we can safely assume that Honeycomb works on phones. Whether the big G likes it or not
[Legend Android Development] speedyink:
+1 When Google was designing it the idea was that they were able to incorporate API's for both tablets an phones in the same os, and depending on which platform your running the OS/apps pick up on that and display it in the proper manner
[Legend Android Development] PandaVoyageur:
Turn over to silence feature

CM7 on Legend runs quite well here :) I think the Sense roms days on my Legend are over now

The only problem I have so far: does the "turn over to silence" call setting work for you?

I have checked the sensor's reading with a test application and they're fine, however the phone keeps on ringing when I turn it down :( (running nightly 17 atm by the way)
[Legend Android Development] Rapier:
Yes it does work for me. Now running latest 19# build but it was ok before with 14 too. You can try to uncheck than check again the option to activate it (check Settings - Call Settings). It seems that some options need to be reselected in order to function properly (some LED notification options do that for ex)
[Legend Android Development] Lostpassword:
Actually it made me to do a poor figure when my mom called me when i was at the office, when i aswered the call all of my collegues heard "HELLOOO SWEETIEE" rumbling into all over the office -.-'
[Legend Android Development] Lostpassword:
i've a question: why when i turn on the fm radio it automatically turns on also the bluetooth? (and if i turn off bluetooth manually it turns off fm radio O_o )
[Legend Android Development] EagleTitan:
Maybe because the radio is controlled via Bluetooth? I'm sure it has been mentioned quite a few times already...
[Legend Android Development] colors:
Is there anyway to continuously update this rom to newest release without wiping/factory reset everytime? Im not so fond to type in all settings and fixing my apps after each flash.

btw, is it just for me? when i get a incoming call the answer/hang up slidefunction is over the phonenumber so i can´t see it. Just the name if it´s a contact in my phonebook.
[Legend Android Development] vasii:
Hi!

Yesterday flashed nightly18 then 12 and i have several problems.

Titanium backup didnt restore all of my apps, dont know why..

Lost all of my smss..I set that apps should be installed to external but i always have to move them manually, because they are installed to phone memory.

Also searched for this A2SD but nowhere find it, where can i download it?

GPS doesent work at all, i want to flash a new radio but where can i find it?

I used cm6.1 before. Now cant find settings for enable Only 90° rotate and 270° not. This setting is gone?

Thanks

/srry for bad english/
[Legend Android Development] m1schi:
You don't have to wipe when updating inside CM7, ever. Normally it should work without the need to wipe.. If you want to use another ROM than CM7 - then you should probably wipe, but not if you're staying with it ;)
[Legend Android Development] PandaVoyageur:
Thanks for the confirmation! Indeed I had "fixed" LED notifications this way, but this did not help for silence ringing...

I'll try again tonight with a clean install to see if some of my settings are at fault in this
[Legend Android Development] buenso80:
Have you noticed the search button here on xda :p http://xdaforums.com/showthread.php?t=841932&highlight=radio
[Legend Android Development] BAWS:
Which Radio do you guys use with CM7?
[Legend Android Development] goose2600:
people, google and the search button are your friends! :)
[Legend Android Development] qzem:
I have build #19 and the screen ON animation is not working, have tried uncheck and check it for several times, still nothing. Anyone else with the same problem?
[Legend Android Development] karl_k:
Hmm, am on Nightly18 and had an issue with the proximity sensor, the screen stayed black during the call even when i took the phone from my ear.

I was supposed to "Press 1 to stay in line" which i could not as the screen stayed off....

Just a freak incident ? Anyone else ?

(Reminds me of my GFs ZTE blade, they struggle with proximity sensor support)
[Legend Android Development] namtrac:
Happens to me with some Skype calls as well.
[Legend Android Development] stiffmast3r:
i got the same problem. do u choose a "fast windows animation"?

check "normal". thats the reason (for me).
[Legend Android Development] stiffmast3r:
hey guys!!

any way to work with a2sd+, like in blayo rom´s?

yes, i searched, found zero.

thanks :)
[Legend Android Development] goose2600:
I am using S2E (Simple2Ext), developed for CM7.

Here is the market link: https://market.android.com/details?id=ru.krikun.s2e&feature=search_result
[Legend Android Development] stiffmast3r:
thanks for fast repley?

but isnt that the same like the "real" data2ext for CM?

my phone have pretty much lags with the normal data2ext for CM.. im afraid to get the same with this.

is it recommend to wipe all and install the rom new, clean??
[Legend Android Development] qzem:
I have it on normal, funny thing is that screen OFF animation is working properly, but screen ON animation is not...
[Legend Android Development] stiffmast3r:
oh, i had the prob in an other way^^

try to reboot and check/uncheck it....
[Legend Android Development] goose2600:
I never used data2sd and I can say that S2E works fine for me (before I was using darktremor).

Don't wipe, just download and install it :)
[Legend Android Development] MaBlo:
No that's apps2sd, not data2ext. No need to wipe, however AFAIK your second partition needs to be ext3 with that one.
[Legend Android Development] HpX:
You can try Darktremor Apps2SD U find it her
[Legend Android Development] stiffmast3r:
okok, thx again guys.

but, the problem is that i (now) dont have a ext. partition.

i want to made it with rom manager. are 512mb enough? how much swap? 0mb?

so, i have to format my sd, when i made a part. -> so i have to flash CM again?

how can i do with little work?! :o
[Legend Android Development] MaBlo:
Should be enough unless you have a s***load of apps ;) you don't need swap and don't need to flash CM again. ROM manager only makes ext2 partition though, so you might want to go with darktremor unless you bother to convert to ext3 manually.
[Legend Android Development] stiffmast3r:
finally...

got issues, i installed S2E, and 1 minute after i installed darktremor :rolleyes:

got 3 bootloops after 5 try´s to uninstall S2E.

but now, darktremor working perfect!!! :)

thanks guys! :D
[Legend Android Development] Bricolo_fr:
there is one thing I miss, in CM builds, compared to sense roms: the dialer

what dialer are you guys using? I like the way sense integrates the dialer and the call history, is there something like this in CM?
[Legend Android Development] TheGrammarFreak:
Dialer one
[Legend Android Development] karlanal:
aTAKEphONE dialer
[Legend Android Development] Trekvogel:
So is there any advantage to using S2E instead of Darktremor? I'm using DT now and it works fine but if there's an advantage to it I might be interested.
[Legend Android Development] Bricolo_fr:
well, it's marginally less smooth than htc's :(
[Legend Android Development] segphault:
Build 19 user here. Have been having this problem since build 18.

With some help from TheGrammarFreak, we deduced that using browsers with the Webkit engine is the cause of crashes and subsequent reboots of my phone. Said reboots happen during general browsing. Please tell me I'm not the only one suffering this issue.
[Legend Android Development] ali ba:
The latest commit to webkit was on Jan 27 (5c1938), to v8 on Dec 31 (532f57) and the last relevant change to Browser Feb 28 (3c91b8).

Can't say I believe it's caused by changes to any of those (as there were none).
[Legend Android Development] segphault:
Well in that case, I'm entirely stumped as to what could be rebooting the phone. I'm gonna grab a logcat of the boot process when I can; hopefully someone will take a look at it.

Anything else I could do to see what could be causing problems?

On a related note, I found another issue with build 19. The keyboard settings don't seem to save for me between reboots. I've got Swype installed and have ticked it in the keyboard/language settings, and I've also selected it as my default input method, but occasionally it switches back to default input while the phone is on. After a reboot the settings are wiped.
[Legend Android Development] hitziflitzi:
What about side effects caused by other changes?
[Legend Android Development] oysteivi:
According to your signature, you're overclocking. Do you see the same problem when set to 600MHz? My own legend will crash, reboot, or develop mysterious behaviour every few days when I overclock.
[Legend Android Development] TheGrammarFreak:
With regard to the keyboard: ensure swype isn't installed on the sd card using the FroYo method

twitter.com/TheGrammarFreak
[Legend Android Development] PandaVoyageur:
Well, "turn over to silence" option definitely does not like my Legend :/

I tested a full wipe, and clean install of bare nightly 19, checked and unchecked the option a few times, rebooted the phone: no dice it kept ringing after turned face down on the table.

Checking with "Android Sensor Data" application, the pitch sensor output is OK, so it's not the sensor. Browsing through forums, it seems some people on different phones sometimes have the problem (while it works for other ones with the same phone/rom version)

Oh well my coworkers will just have to bear with the ringing a bit longer ;) I'll test that again with some more time and next rc (or 6.1 to be sure)
[Legend Android Development] segphault:
Set to 600Mhz. We'll see how it goes, even though I've not had problems with 768Mhz before now.

Rectified. Should solve that problem. ;)
[Legend Android Development] Catnap:
Due to long-winded and boring issues, CPUs aren't always able to be overclocked through their lifespan. Just because you had a "stable"* overclock for x months, doesn't mean you can hold it now ;)

* in quote marks because hardly anyone bothers to run a stress test to make sure their phone is stable at the desired speed anymore, so as soon as you get a sustained high CPU load, bam goes the phone.
[Legend Android Development] segphault:
I did run a test for about an hour on blay0's ROM using SetCPU under 768Mhz and it seemed stable enough. I guess I didn't test for long enough.
[Legend Android Development] ali ba:
There are currently over 200 projects in CyanogenMod. I think you'll understand that I'm not going to look at all of them.

V8 uses the CPU a lot more than other applications with a lot of magic going on in the JIT. V8 is not in Blay0's rom.

You are overclocking and then seriously asking for support? DIEDIEDIE and stop wasting our time.
[Legend Android Development] stiffmast3r:
yo guys.

is there a simple way to use adfree?

I'm sorry for my noobish questions....
[Legend Android Development] TheGrammarFreak:
Yes

twitter.com/TheGrammarFreak
[Legend Android Development] segphault:
Is it really all that outlandish? Hundreds of other users have OC'd without problems. Why is it so anomalous that I ask for help along with the others who've done so before me?

I asked for assistance because I've never experienced these problems before, even though I've OC'd at 768Mhz previously on many different ROMs and builds without any problems. I wouldn't have asked if I realised that V8 would've made that much of a difference.

I also asked because the problem seems extremely specific. I doubted that overclocking was an issue as a result.

As of now I'm sat back at 600Mhz, which I've stated earlier. Evidently I've taken a large performance hit which I'm not pleased about, but I guess I'll just have to deal with it.

Sorry for supposedly wasting your time.
[Legend Android Development] TheGrammarFreak:
Ignore him segphault, he's like that.

twitter.com/TheGrammarFreak
[Legend Android Development] Catnap:
I have to run at 600Mhz myself; 768 runs "okay" for a bit and then starts sporadically rebooting to the Cyanogen splash screen. I just have a CPU in mine which refuses to overclock properly. Some people get up to 800, I can only manage 600 with sufficient stability to not piss me off.

Sucks, but that's the way it goes. Apologies if I made out that it was you that couldn't be bothered; there's a metric ton of people who come in here not knowing WTF they're doing with overclocking and whinge when they can't get it stable like other people can.
[Legend Android Development] colors:
well i ask again...

is it just for me? when i get a incoming call the answer/hang up slidefunction is over the phonenumber so i can´t see it. Just the name if it´s a contact in my phonebook.
[Legend Android Development] HpX:
Yes, it's Just you;)
[Legend Android Development] ali ba:
Let me call that nonsense. A lot of users I know reported that their devices do restart after a few days - and this is not specific to the Legend. Of those few Legend users there are certainly not "hundreds" that overclock without problems. If you reboot often you just don't run into them.

Overclocking makes your device unstable. Always. It's an uncontrollable factor because it causes the CPU to not calculate reliably any more and destroys determinism through random results.

So, to sum it all up, if you report a problem with your device being overclocked the only place where people even bother answering you seems to be XDA.
[Legend Android Development] segphault:
It's fine, I don't think you did so anyway. It's not that I couldn't be bothered, it's more the fact I just wanted to get right in and start testing. Too eager. ;)

Say if I un-rooted, and returned to a stock Vodafone ROM using an RUU, then upgraded to the stock Vodafone 2.2 update... would Vodafone be able to tell at all that I've rooted? I've been considering sending my Legend in for a repair anyway as it's got a few scratches and "has been randomly rebooting", which isn't really a lie... If you know what I mean. ;)

You've made your point: you win; let's just leave it at that.

If I get any more reboots on 600Mhz then we'll know it's not overclocking which is the issue. Diagnosing the issue was the point of the post, and as of yet we can only infer what the issue is. We'll know for sure after about a week. ;)
[Legend Android Development] Catnap:
Should be absolutely fine. Do be advised that you'll get it back with HBOOT 1.01 which you can't S-OFF at all at the moment, and you'll need to go through extra steps to re-root it.
[Legend Android Development] segphault:
I'm not bothered about S-OFF; knowing my luck I'll brick the phone and Fakeflash is a viable alternative. :P

If I recall correctly I used the HBOOT 1.01 root method to root my HBOOT 1.00 Legend anyway, so it won't be anything I've not covered before. :)
[Legend Android Development] ali ba:
Oh, how generous of you.
[Legend Android Development] TheGrammarFreak:
If you have S-OFF then ad free from the market will just work. If not, take the hosts file from blay0's rom and push it to /system/etc/ while it recovery, with /system mounted

EDIT: it occurs to me that you could use Blay0's /system overlay script to "emulate" E-OFF

twitter.com/TheGrammarFreak
[Legend Android Development] namtrac:
Finally GPS signal problem seems to be nailed down! See http://r.cyanogenmod.com/#change,3895
[Legend Android Development] segphault:
Looks like the nightly with this fix in went up a little while ago: http://download.cyanogenmod.com/?type=nightly&device=legend

On another note, I've not had any random reboots. Thanks to ali ba for his facetious but helpful assistance, and to TheGrammarFreak and any others who helped me out with the problem.
[Legend Android Development] namtrac:
My GPS still doesn't lock to the signal but we'll see...
[Legend Android Development] ali ba:
Short: No.
[Legend Android Development] segphault:
Drat. I wonder if it'll ever be fixed for everyone at this rate.
[Legend Android Development] bodjor:
I would rather say how wise.
[Legend Android Development] ali ba:
Pardon? Are you actually complaining about a non-profit project? Do you have any idea what it means to reverse engineer a closed source embedded system?

GPS won't be working for everyone unless HTC releases 2.3 for the Legend. This means: likely never.
[Legend Android Development] segphault:
Not complaining at all. Just making a declarative statement. And yes, I realise what the project entails.

Any excuse to jump on my back, huh?
[Legend Android Development] namtrac:
At think it worked at some point but I might be mis-remembering. Anyhow I am glad for having CM7 on Legend already. Thanks for the good work!
[Legend Android Development] segphault:
I think I had it working a relatively early build. If I recall correctly it was either build 12 and/or 13.
[Legend Android Development] namtrac:
Should test & report! :)
[Legend Android Development] segphault:
Crap, hit the wrong button. -_-

I'll nandroid tonight, flash b12/13 and report back if I remember. ;)
[Legend Android Development] branch8:
Tried using blay0's overlay with adfree and it didn't work. Updating the host file kept failing. I was able to create a symlink in the terminal emulator though so the problem was solved. (can't be bothered to investigate further now that it works)
[Legend Android Development] commanderbaccar:
We really appreciate your efforts, which is why I think we should all have a 'grow our neckbeards even longer' month in your honour.
[Legend Android Development] lollazzo:
picasa sync works?
[Legend Android Development] ali ba:
Wow, thank you very much for contributing even more nonsense to this thread.
[Legend Android Development] branch8:
Sorry for budding in but reading the last few pages i'd almost suggest closing this thread. :(
[Legend Android Development] snowhs:
http://android.krikun.ru/pub/legend

ask less,do more.
[Legend Android Development] anran21:
OK,thanks ,my wife learn russia