yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] ny73r1d3r:
Does anyone noticed laggy or stuttering scrolling when browing through very long post in xda app with recent nightlies? Scrolling down short posts is fine and smooth but whenever I encounter long ones like changelogs it suddenly becomes extremely sluggish...

Back to RC4... :S
[Desire Android Development] micheltenhove:
Did it just go final?! Looks like it on the mirrors.. :)
[Desire Android Development] nitrox1:
Yep, wonder if call delay was sorted, flashing now.

Desire is the source of all suffering.
[Desire Android Development] vr5411:
Please, report back regarding call delay.
[Desire Android Development] amitabhishek:
I am now on CM7 final. No call delay seen on the 10 odd calls that I've received since morning. *fingers crossed*.

I flashed without wiping (from RC4); working like a charm!
[Desire Android Development] kecinzer:
Looks promising. Someone else can confirm?
[Desire Android Development] MoxFulder_CH:
Upgrade is working, but now, without wiping, gmail + market (at least) don't open correctly. Open-then-close without displaying anything

EDIT : Wipe cache + dalvik and reinstall gapps. It works then.
[Desire Android Development] lazarost:
Incoming call delay is still there.

I just wiped cache & dalvik and didn't do a full wipe.
[Desire Android Development] niksha89:
What about max brightness after wakeup? Its still there for me, but I didnt wipe.
[Desire Android Development] sjgore:
Same here! :)
[Desire Android Development] nanujra:
Any kind soul cares to mirror?

It downloads as slow as hell and has died 5 times already before even reaching 2mb! I can't wait to try it out!

Edit:

scratch that. problem solved. for any others experiencing agonisingly slow download speeds, just download directly from HERE

Its way faster than the link on the first page
[Desire Android Development] nitrox1:
+1 ( only tried on 3 calls, Billy no mates here), and I have low brightness to high brightness (slowish to respond) with pattern lock screen.

Wiped cache and dalvik cache before flashing, then pushed cache to sdext.

Edit: last call no delay, so I don't know.

Desire is the source of all suffering.
[Desire Android Development] iDaddy:
Hi guys,

what's your Quadrant Score? I just tried it because Dungeon Defenders runs even worse on my device than it used to run. My actual score was 987 the first time a 1238 the second time.

P.S. Any ideas how to make Dungeon Defenders run better on HTC Desire? Even with the lowest upscale setting it's unplayable :-(

P.P.S CM7,CPU@~1075Mhz (My last stable setting)
[Desire Android Development] nitrox1:
Could try a Coutts95 .38.2 kernel,OC'd to 1190MHz.

Desire is the source of all suffering.
[Desire Android Development] crazylemon:
so, what's the next big step to look forward to? :)

what will we get in CM7.1? Any wishes?
[Desire Android Development] niksha89:
how about fixing current issues? :P
[Desire Android Development] Silence66:
issues? you mean not wanted features:D
[Desire Android Development] bemymonkey:
I'd be satisfied with that :)
[Desire Android Development] crazylemon:
:D I knew this would come up first. I just didn't want to be the first person saying it.

True. Focus should be on fixing current issues than on adding new features. Although an update to GRI54 would be nice (and maybe this update will do some of the fixes).
[Desire Android Development] iinga:
The call delay seems to be a bug on the N1 OTA 2.3.3. Something that google have overlooked :( Lets hope either google decide to fix it, or teamdouche do their magic
[Desire Android Development] jsel:
I don't have call delay bug on CM7 final.
[Desire Android Development] killall:
+1

Seems to me a lot of people have the delay......then again a lot of people don't have the delay..

could it be a carrier issue?
[Desire Android Development] kecinzer:
I tried to start topic about HW of Desire if we found any relation with call delay, but it was deleted.
[Desire Android Development] andQlimax:
How can be HW if there is no delay on froyo? :confused:
[Desire Android Development] kecinzer:
andQlimax:

I mean HW in combination with GB drivers. How else will be possible, that someone don't have delay and other have it.

I think, that people with newer version of Desire (with LCD) don't have a delay.

I can see, that you have PVT1, so do you have delay? I think you do :)
[Desire Android Development] Sylde:
I got a call delay on gb and I have a SLCD desire (a PVT3 i guess). Your supposition seem curious.
[Desire Android Development] andQlimax:
In my opinion all people with GB have the delay..But someone didn't understand what was the call delay problem (reading in other forums someone talk about delay during the conversation for example)..not all people read xda every day and know the problem..here everyone say just "call delay" :p

the problem that i noticed is that when someone call me (and not viceversa), i can't hear the other person (he hear me) for about 2-3 seconds..after that all is normal..this is the call delay..someone here doesn't have this? I don't believe if I not see it myself :D
[Desire Android Development] ssauger:
I got the same revision and without call delay since i use the "call delay patch" from market (i know it works not for all, but in my case). Try it with a clean install with CM7, wipe all. Maybe it fix the problem.
[Desire Android Development] andQlimax:
Yes, that seems to fix the problem, but randomly it doesn't work for every call during the day..don't know why

not a big problem anyway..the fix is simple, after answer wait 3 seconds and just then say hello :D
[Desire Android Development] Nekromantik:
i am very dissapointed with Google getting rid of 720P recording in GB n1 update.

we will have to wait till official Sense ROM for that.
[Desire Android Development] simonovicc:
Funny thing is that my problem with call deley is oposite than yours. When someone call me he cant hear me for about 1 or 2 seconds. I can hear him perfectly!
[Desire Android Development] mad-murdock:
Dungeon defenders is the most gpu hungry game I saw so far. Unreal tournament engine, very detailed textures, high polygon count. To be honest, it was one reason I upgraded my bravo to desire HD. The adreno 205 is much much faster than bravos adreno 200 chip and also supports open gl es 2.0 instead of 1.1

I fear dungeon defenders wont be the last game with bad playability on older gfx chip. Don't get me wrong, bravo is still a great phone and does everything very fast. But a netbook is also a great computer doing its job - yet you wont play battlefield on it, right?

Morsed by hitting a plastic pipe with my PoV mobii. Excuse typos.
[Desire Android Development] mad-murdock:
Google nexus s got call delay with stock gingerbread firmware.... that's that...

Morsed by hitting a plastic pipe with my PoV mobii. Excuse typos.
[Desire Android Development] chupchip:
Has anyone tried #39, are some weird bugs fixed e.g. notification pulldown, max brightness ?
[Desire Android Development] kecinzer:
That is realy true? I do wan't to believe this. So when I buy new Samsung S, I will have call delay issue?
[Desire Android Development] jbozic1:
Im using this rom with ext3,until yesterday i had about 70 mb free of 138 on internal storage,and i my partition had 250 mb,now ilehen i have ext3 with 512mb,i still have same free and used space,i thought that i should have more internal storage when i increase ext3 partition,and that o should see that under storage menu in prefrences or am i wrong?
[Desire Android Development] Sordep:
it did fix some notification problem(adw swap and pulldown lag)
[Desire Android Development] bemymonkey:
Anyone else having issues with WiFi on the last few builds? Sometimes, when my screen turns off and there's a file transfer over WiFi going on, the screen refuses to turn back on. SurfaceFlinger doesn't show up in Logcat when I press the power button (as it's supposed to), only *** set_screen_state.

Normally it looks like:

power *** set_screen_state 1
SurfaceFlinger Screen about to return...

Now it's just the first line, the SurfaceFlinger line is missing completely. I can still access the device via ADB...
[Desire Android Development] nitrox1:
Are you using kali's a2sd?

I am, and find cache takes up a huge amount on my phone (100MB, and 20 min to boot when I flash New Rom, also if you wipe cache before you flash you have to push cache every time)

Try going to terminal and type:

Su

/sd-ext/userinit.d/10cache2sdext-binds enable

As mentioned on page one, but you can do it from terminal.

Then you should get a confirmation message about rebooting. Reboot, and this could take 30min to reboot ( make sure you have enough battery), as cache is moved to sd-ext.

This should free up allot of you internal storage.

But not sure why the free space in your ext3 should stay the same if you've increased its size.

Desire is the source of all suffering.
[Desire Android Development] Rohaq:
Is anybody else experiencing a significant level of battery drain on 7.0 Final? I upgraded from #37, and I seem to be losing battery a lot faster now. A full wipe and flash doesn't seem to be helping, either.
[Desire Android Development] ehalai:
i also logged in to post about battery issue and here you go...

yes i m also having battery drain issue, i mean loosing double percentage when i compare it with SupeRom v2.

battery was awsum there and here it is awful...

any recomendations?

regards
[Desire Android Development] fridlack:
Have a problem with GPS since RC4, using #39 atm

Step by step to reproduce it

Try it indoors, if you lock GPS it have no problem

1- Enable GPS

2- Enter navigation aplication, GPS icon starts to blink

3- Chose a destination and after calculation route navigation icon apears in notification bar

4- hit home button and GPS stop serching signal, i need to switch GPS off and on again inside navigation to keep GPS serching signal

Anyone with this problem?
[Desire Android Development] mikbe:
I flashed CM7 yesterday after a full wipe. Everything went well until device decided to boot itself. Then again and again. That constant rebooting caused corruption in my sdcard and now I can't mount it. Won't mount in recovery either. I didn't change any settings and partition table is CM7. Now what? :mad:

E: It mounts in read only mode. Windows can't find it but all the icons on lockscreen appear correctly.

E2: Sorry wrong thread. Was supposed to go in final. And I think planets were aligned correctly because somehow I managed to fix it. :)
[Desire Android Development] belylal:
I'm not able to download #39. It gets to 99% and then stops...

Can anybody help me out?
[Desire Android Development] liquidini:
does the alarm give you a choise to choose music as ringtone?

i remember that it was possible.

no i have only the alarms sound and i cant put any mp3 as alarm tone.

thanks
[Desire Android Development] echohack:
to use mp3 as alarm, make a folder called alarms or alarm cant remember on sd card and drag the song to it. restar phone an done
[Desire Android Development] sudeki300:
i havw never used a CyanogenMod rom before and quite interested to check one out, the thing is though i'm not realy sure which one to go for. i was looking on the rom mirror network and was thinking of trying this rom"update-cm-7.0.0-RC4-Desire-signed.zip" but do i need to install a base version first something like "cm_bravo_full-39.zip " or have i just read the thing wrong.thanks for any help..........................sueki300
[Desire Android Development] RedSkyRoad:
If your phone is setup to receive custom roms, take the latest one, #39... And what works for me when installing a later one is to wipe Cache and Dalvik cache before flashing the next one...
[Desire Android Development] sudeki300:
thanks for the reply puffin will it have all the same stuff in it has update-cm-7.0.0-RC4. i also have to grab the latest gapps for the google stuff, or the other choice is back em up with titainum before flashing..................sueki300
[Desire Android Development] nyunyu:
Why install RC while final has already been published?
[Desire Android Development] sudeki300:
i don't know which way these roms are realesed, so i take it that the final version has everything from the previuos previous released roms. see at the moment i'm using the RCMIX hd port, but that is made from an orange rom and now i feel for a change.so any advice for a good setup would be greatfully accepted such as which rom and kernel is best.thanks for the replies........................sudeki300
[Desire Android Development] nitrox1:
Not trying to be rude, but best you try the Cyanogen Rom thread rather than the nightly one.

You'll find more of your answers there.

Unless you feel like your a complete crack flasher, and have to flash an update no matter how small the change, and even then, need to flash a custom kernel over the top just because you can....

This Rom is released nightly in experimental versions, other Cyanogen Rom is released by rc's and most stable, if it has a number after: probably a nightly. if it has a cm7.0.x probably a stable version. But you should be able to find the stable versions tab on web site.

Desire is the source of all suffering.
[Desire Android Development] JDima:
I'd suggest NOT to use CM7 release. It has several annoying bugs (notification etc.) that are fixed in nightly 39.

Apparently, a release version is the same as a nightly version, just some sort of milestone, and it may be even less stable than the nightly.
[Desire Android Development] nitrox1:
True some times, it is a shame that.

Desire is the source of all suffering.
[Desire Android Development] andQlimax:
http://cm-nightlies.appspot.com/?device=bravo

The nightly #39 come after the final, so is normal that fix something more, the next release 7.1 will contains that fix
[Desire Android Development] mad-murdock:
aehm, no...

for one, "notification etc..." - the notification should be it for target bravo. no etc here. also the notification drag down may be annoying, but its not show stopper.

nightlies are NOT TESTED AT ALL but automatically build from source. RC and stable release are build manually by the developer maintaining that specific device. he tests and maybe fixes stuff until it suits him.

even though i understand why you love nightlies (i do the same - bleeding edge ftw) - dont force your opinion on people looking for stable release. there are a lot of people who just wanna flash their device once every few month. for them, stable is probably the right choice.
[Desire Android Development] ShirazSuleman:
Is there a nightly #40 out?

For some reason I cannot get to the teamdouche site.

Sent from my HTC Desire
[Desire Android Development] Glotzeulor:
not yet. seems to still need some time.
[Desire Android Development] JDima:
I'm speaking of particularly the CM7 "stable" vs CM7 nightly#39. I'd say this nightly is better than the release, and probably - many would agree with me. And I hope 7.0.1 would fix all the glimpses and become a "real" stable release.

What's the use of testing if it misses the notifications bug? It's annoying enough to roll back to the previous version. And with the nightlies, testing is perfotmed by XDA members, and when a person wakes up in the morning, he would probably already know whether the ROM is stable enough :)
[Desire Android Development] iinga:
What notification bug is being talked about in CM 7.0? The gesture for ADW?
[Desire Android Development] JDima:
Just the gesture for opening the notifications bar.
[Desire Android Development] nitrox1:
Can anyone recommend a new .38.2 kernel for the bravo with cm7?

Desire is the source of all suffering.
[Desire Android Development] Rohaq:
Is it just me, or has the equalizer disappeared in 7.0 final?
[Desire Android Development] serverless:
Ok, leaked "gingersense" arrived, will cm7 take benefits from that (gpu, camera, etc...)?
[Desire Android Development] mad-murdock:
both gesture and the stuttering while dragging it open. both the same issue - wrong calculated velocity. its fixed for top status bar since #39 and i just uploaded a fix for both top and bottom status bar to finally solve this... http://review.cyanogenmod.com/4675
[Desire Android Development] mad-murdock:
now i need your help (:

friend of mine flashed 7.0.0 and got huge battery drain. he talks about 6 hours draining the battery empty on moderate usage. i didnt read about this issue here, so i wonder what might be wrong. he said, he already deinstalled most apps, but it didnt help.

i visit him this evening like usual and am going to fix this issue for him. sure i do the obvious, check battery usage, check wake lock, adb shell in and watch htop while screen off - but maybe you got any idea already (:

he used RC4 and nightlies before and never had this issue - also 6 hours empty - its not calibration or anything....

regards
[Desire Android Development] bemymonkey:
Hi Murdock, didn't notice any high battery drain on 7.0.0... most likely not a widespread issue. Battery usage, partial wake usage and htop should do the trick...

Although... maybe he activated SIP? http://code.google.com/p/cyanogenmod/issues/detail?id=2909

Because high partial wake usage causes maybe 40mA of drain => empty in 1400mAh/40mA=35h... not 6h. 6h is something like 200+mA, and that's the usual drain for screen on + loading something over WiFi...

-edit- Oops, linked to the wrong issue.
[Desire Android Development] ed.dark:
Maybe check the radio installed. I used to get a massive drain on CM6 with the newest radio (5.14.05.17). Then I reverted to the previous one (5.11.05.27). Double the battery life! I'm now on CM7 and have no issues with the latest radio.
[Desire Android Development] mikeandjaimie:
So outta curiosity, does the continued release of nightlies mean these are towards 7.1? I'll be flashing eitherway as I love the latest new features (and bugs).

scribbled across a screen from somewhere mobile..
[Desire Android Development] Ahalex:
Can anyone help me with bluetooth issue please? Can´t pair with any devices although they´re found. :(

Not working with RC4 and latest nightly.

Edit:

Solved it with this tip: http://xdaforums.com/showthread.php?p=12846830&highlight=bluetooth#post12846830

and changing system/etc/bluetooth/auto_pairing.conf and data/misc/bluetooth/auto_pairing.conf from

// Blacklisting by Exact Name:
ExactNameBlacklist=Motorola IHF1000,i.TechBlueBAND,X5 Stereo v1.3,KML_CAN

to

// Blacklisting by Exact Name:
ExactNameBlacklist=Motorola IHF1000,i.TechBlueBAND,X5 Stereo v1.3
[Desire Android Development] nitrox1:
Talking about this drain on nexus one on gigglebread, but they have said it was fixed. Said it was a notification causing phone to come out of sleep state and stay out draining battery. Could be this.

Desire is the source of all suffering.
[Desire Android Development] marinierb:
I find setting my phone to "GMS Auto (PRL)" reduces battery drain.
[Desire Android Development] f0xy:
Is it me or is the app drawer really laggy?
[Desire Android Development] :
Try using launcher pro its noticeably faster then adw and has some pretty good transition animations on the home screen.
[Desire Android Development] f0xy:
Yes thank-you I like lpp. But I prefer adw. I've opted to remove adw and use adw ex. Which oddly is smoother. Although I use cm7 on the wildfire which is very smooth.
[Desire Android Development] ididnt:
for what its worth, i was getting unlockable lock screens with 39 and went back to stable cm7
[Desire Android Development] Black1982:
Guys I could really use your help! I was about to update my gf fone from RC4 to nightly but after I made nandroid backup the phone doesn't recognise any sd card. Her card works in my phone and her phone doesn't recognise my card either.

Sorry fot the offtopic but I need a thread with some brains!

Thanks for your help!
[Desire Android Development] nitrox1:
Is it mountable in recovery? Cmw or amon-ra?

Desire is the source of all suffering.
[Desire Android Development] Black1982:
No, when I choose flash zip from SD it responds: can't mount /sdcard
[Desire Android Development] iinga:
If you turn the phone on without sd card in, does it recognise sim? can you turn bluetooth on?

Sounds like it could be a usbbrick (simple enough to solve). Is the phone s-off? If so what version?
[Desire Android Development] bemymonkey:
Yep, sounds like USB brick.
[Desire Android Development] Furma:
has 2sec call delay been fixed? tnx
[Desire Android Development] Black1982:
I certainly hope it's its easy to solve! My weekend will not be so good if I brick my gf fone! :rolleyes: My own device is a Desire HD so I'm not to familiar with the Desire's ins and outs.

.

It is still s-on. It reads the simcard but I can't turn on bluetooth. Another strange thing is that it can only get an G connection but if I select G/3G it cuts the connection after a minute. Don't know if that's related?
[Desire Android Development] bemymonkey:
That's another symptom of the USB Brick. Don't worry though, it's just called a USB brick, it's actually easily fixed, the device isn't bricked at all.

Follow the instructions here: http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/ - start at step 2 (reactivate SD card via Fastboot), then flash the supplied update.zip file through your recovery (CWM/AMonRA, whatever you have installed is fine) - done.

Should be up and running in 10 minutes or less ;)
[Desire Android Development] Black1982:
Great! I'll give it at try when I'm home!

Thanks for your help!
[Desire Android Development] dbolichowski:
I've had this issue even while using CM6, so I'm not sure if it's common among other users or just me.

Basically when I go to type/reply to an SMS, I click on the 'Type to compose' field to open the keyboard. A keyboard ALWAYS comes up, but sometimes I cannot type on it. I know there is an issue because when this happens, there is no :) Key on the keyboard, and there is a 'Return' arrow. If I back out of the SMS and re-open it, the proper keyboard is loaded and I can type.

Anyone else ever run into this, or know of a fix? The obvious full-wipe/reflash has been tried many times.
[Desire Android Development] iinga:
Even faster with an s-off phone :)

Is the recovery amonra 2.0.1?
[Desire Android Development] bemymonkey:
How so? Do you rewrite the MISC partition manually instead of flashing? :p

One Fastboot command and flashing a single ZIP file isn't really slow :D
[Desire Android Development] Black1982:
S-off is the next thing I'm doing!

It's the latest Clockwork Recovery with ROM manager.

To b sure: I need to execute the fastboot command from android-sdk dir and I need HTC sync installed?
[Desire Android Development] bemymonkey:
The HTC USB Driver package from developer.htc.com would suffice instead of HTC Sync as well, but yes, that will work just fine.
[Desire Android Development] Black1982:
Succes! Thank you for saving my gf's desire and my love life:p

Now for s-off!
[Desire Android Development] bemymonkey:
Glad we could help.

You should keep that update.zip file somewhere on the SD card, in case the USB brick happens again - still have no idea what causes it, happens during ROM flashes and/or Nandroids sometimes.
[Desire Android Development] iinga:
fastboot flash misc mtd0.img

Makes life more convenient for those usb bricks
[Desire Android Development] iinga:
its interesting and weird at the same time. I only seem to have encountered it whilst doing something to do with nandroids.
[Desire Android Development] Black1982:
Ok I will! My girl is happy running the nightly! Here biggest problem wkth RC4 is the 2 second call pickup bug, but i get that's not fixed yet.
[Desire Android Development] madman_cro:
It s got to be nandroid. I changed 100 + roms and never did nand backup or restore and i never had brick
[Desire Android Development] bemymonkey:
The weird thing is that it happens during the backup, during which nothing should be changed. Why is the backup process writing stuff onto the misc partition? :confused:
[Desire Android Development] CharlieCharlie24:
Anyone got issues with Video playback? Tried playing some mp4 videos but it's unwatchable. Got #39 the latest leaked radio and 0.38 couttstech kernal.

What effects video playback? Kernal? Or ROM?