yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] oc2:
$ export PATH=/data/local/bin:$PATH

$df -h

Filesystem Size Used Available Use% Mounted on

tmpfs 202.9M 32.0K 202.9M 0% /dev

tmpfs 202.9M 0 202.9M 0% /mnt/asec

tmpfs 202.9M 0 202.9M 0% /mnt/obb

/dev/block/mtdblock3 250.0M 114.7M 135.3M 46% /system

/dev/block/mtdblock5 147.6M 112.8M 34.8M 76% /data

/dev/block/mtdblock4 40.0M 1.5M 38.5M 4% /cache

/dev/block/mmcblk0p2 457.4M 8.0M 424.9M 2% /sd-ext

/dev/block/vold/179:1

14.4G 8.4G 6.0G 58% /mnt/sdcard

df: /mnt/secure/asec: Permission denied

/dev/block/dm-0 2.0M 504.0K 1.5M 24% /mnt/asec/org.jfedor.frozenbubble-1

/dev/block/dm-2 2.0M 484.0K 1.6M 23% /mnt/asec/com.agilesoftresource-2
[Desire Android Development] Kali-:
sd-ext is correctly mounted but not the /sd-ext/app & /sd-ext/app-private

sames like addon is not installed

which recovery and version used?

will be useful if u come to #teamdesire
[Desire Android Development] b4bass:
the purpose of this is to fit everything on the nand so you dont need any extra storage on the SD. For exemple with a 300+ /data partition, i have plenty of space, and i dont need to use my SD as a storage device for apps anymore.
[Desire Android Development] Zobat:
touch to focus works again in latest nightly
[Desire Android Development] shyamk:
Is anyone facing gps issue with 131 nightly ? I am having a gps fix issue even when I am on Wi-Fi !

Shyam
[Desire Android Development] jun_ng_1208:
As of now, no issues with GPS so far on build# 131 :) Maybe you can try downloading an apps called 'Faster Fix' from Market, it works for me ;)
[Desire Android Development] grilopt:
Some FCs, but very, VERY nice! You got yourself a "Thanks" :)
[Desire Android Development] Jagdish84:
Scratch that...
[Desire Android Development] nachtschicht:
Did you enable it in the cam's settings? Coz it's working fine here, too...
[Desire Android Development] premler:
Im trying to flash the latest nighly (#132) coming from nightly #64 or something. It does'nt go too well. I getting stuck at the a-rev boot screen.

Tried first without wipe, and now with a full wipe without any results.

Am I missing something?
[Desire Android Development] Large Hadron:
What memory table are you using? If it's the old CM7 you'll need to either change to the new one or remove some stuff from the zip before flashing, since it no longer fits in 130 MB /system.
[Desire Android Development] premler:
Ah! I would assume that's the old one. So i need to flash a new alpha-rev(?) hboot throuth the fastboot thing right?

(I've done this before but my memory is ****ing useless :p )

Edit: I tried this alpharevx thing, but i tells me my phone is not supported. What do i have to do to get the new hboot?

Edit2: According to titanium backup, my system ROM space is 136mb. Should'nt that be enough?
[Desire Android Development] iviarck:
The clincher for me when moving to nightlies past 107 was to thin out the APK load in /system/apps (particularly the wallpapers) and to lose the whole /system/tts folder. This gave enough room for the ROM to start up properly first time in. I used Super Manager to do this before installing the new ROM. If you have a Nandroid backup to go back to, I would suggest doing so, deleting a few APK files from /system/apps and the /system/tts folder and trying the install again.
[Desire Android Development] premler:
Well, but would'nt that force me to do that everytime i wanna flash the newest nightly? It must be better just to get the new hboot.

Just have to figure out how the F I do that. :(
[Desire Android Development] iviarck:
While I am doing the Super Manager dance of deletion before every nightly install, you're quite right in saying that the new HBOOT would be a more efficient way of running the ballroom.
[Desire Android Development] Large Hadron:
I'm not sure precisely what size the current CM7 nightly is - I always strip out live wallpapers, themes etc from ROMs anyway. But I think Ti is using decimal Ms rather than binary Ms here, and you really have 130 MB space, which isn't enough.

The instructions for flashing via fastboot are on the alpharev.nl site, right under the downloads for the hboots :) You don't want AlphaRevX, as that's still in beta and you don't need it anyway for this.
[Desire Android Development] benjo:
Yep, just grab the Bravo CM7 r2 hboot from the alpharev.nl site :)
[Desire Android Development] stanleywinston:
Can someone verify that the flash works on the camera please. I've just got my desire back from repair and have no light and would like to know if its the repair that's at fault

Thanks
[Desire Android Development] ShiftyBloke:
Looks good but takes up loads of space :(
[Desire Android Development] Large Hadron:
Work for me - nightly 133.
[Desire Android Development] stanleywinston:
Thanks. Another returned phone for me then :-(
[Desire Android Development] m4rv1n_dr01d:
Hi!

I have just flashed nightly build 07162011, everythings works fine except Latitude.

When I open Google Maps, my position is always near Moscow (....I'm from Italy..)

If I turn gps on and I go where I can see the sky my position is rightly updated, but when I come back insde my avatar returns to Moscow..

I try to erase cache of google maps but nothing

Any idea?

Thank's
[Desire Android Development] SoftWord:
Hi marvin, I'm italian........I have oxygen 2.1.6 now and I have a similar problem.......

Some time, when I open google maps, it match correct position but after some seconds, gps will disconnect completely ! If I close gmaps and reopen, it fix correctly and work.

Try to open and close gmap more times.......or disable/enable manually gps.
[Desire Android Development] m4rv1n_dr01d:
I've tried but when I open gmaps I see the correct position for a millisecond, then moscow...

(gps on or off)

Works only with gps on and outside
[Desire Android Development] Z0l:
Do you have mock locations enabled in settings -> applications -> development?
[Desire Android Development] Zobat:
136 up and running here :)
[Desire Android Development] m4rv1n_dr01d:
Disabling and enabling works for a couple of minute...
[Desire Android Development] SoftWord:
can U try oxygen ? Only for test.........
[Desire Android Development] Z0l:
Can you disable it permanently and install GPS status from the market? With GPS status reset the a-gps, then download the GPS data, go outside, get a fix and see what happens.
[Desire Android Development] Zobat:
Audio Volume

Hi All,

Is there anyway to hack the audio-volume/control? I would like my sound a little louder.
[Desire Android Development] m4rv1n_dr01d:
Hi,

Thank's for reply, I try with GPS status but nothing.

Seems that after uninstalling and reinstalling maps works better....
[Desire Android Development] m4rv1n_dr01d:
:) sorry one day of work for a clean switch from leedroid...
[Desire Android Development] ssauger:
anyone got short reboots to bootscreen on latest build too? also can be that i do somthing wrong in last time.
[Desire Android Development] ssauger:
Use the DSP app included, set for headphone or speaker, turn on the settings an play with the equalizer.
[Desire Android Development] TheBlueRaja:
136 is up and running but im getting some occasional reboots with this build.

I love the ability to turn off the lock screen if you have a security screen in this build.
[Desire Android Development] Zobat:
nope, no reboots here
[Desire Android Development] grooltor:
Me too, getting some soft reboots with #136
[Desire Android Development] expl0de:
I also have soft reboots, did you try to play with volume button, is says whatever it wants (silent mode, or bluetooth enabled, the letters are completely wrong).
[Desire Android Development] Kali-:
i think u are spoking about the lock in landscape bug introduced with #136 but this bug should be fixed in #137

thank's to Richard Burton on #137 there is also a new feature for bravo "notification led during charge"
[Desire Android Development] ShiftyBloke:
Is anyone getting it where the phone goes onto emergency calls only? I have to turn airplane mode on and off and its ok

If I don't do that it'll sit at it for hours

I'm on the 30_2 radio (tried others but the problem still randomly occurs)
[Desire Android Development] Narfx:
Maybe you had a soft reboot and you didn't notice. They were quite frequent in #136. I haven't had any with #137.

(edit) Wait, if it was that you'd only have to enter the pin, no need to go into airplane mode. Probably different problem :)
[Desire Android Development] ShiftyBloke:
Yeah I don't have to enter the pin

Gone back to a previous build and it finds the network right away

Although this build did it a couple times too :o
[Desire Android Development] TheBlueRaja:
On #137 no, no reboot so far but early days.
[Desire Android Development] ShiftyBloke:
Still getting emergency calls only :rolleyes:

Wonder if a wipe will help
[Desire Android Development] aeoveu:
I'm getting soft reboots; downloading 137 now. Apparently, it's slow as hell :/
[Desire Android Development] snapilica2003:
The last nightly with the updated kernel makes my phone to stay always awake. android.process.acore shows at 100% Battery went down to 45% in 10h from full charge. Anyone else experiencing this?
[Desire Android Development] Klausi:
Everything is doing fine over here, no reboot, no stays-on, no unusual battery consumption. GPS, 2G/3G, WiFi are working.

I like the option to cancel the lookscreen, finally the use of the security pattern make sense. Maybe the devs can hide the "draw pattern to unlock" hint - everyone knows what to do.
[Desire Android Development] grooltor:
Can confirm: after flashing #137 no more softreboots. Phone is booted since 11:30 (GMT+1), System Tuner reports 3:23h in active state and 5:16h in deepsleep, so no "stay awake" problems.
[Desire Android Development] ShiftyBloke:
Went back to build 129 and no emergency calls only problems. Confusing!
[Desire Android Development] snapilica2003:
I managed to figure out what was causing it. It's the new update to GO Launcher EX. That's the app that was behind it. I've emailed the developer.
[Desire Android Development] m4rv1n_dr01d:
Hi,

I'm trying to configure USB tethering with an old xp laptop (with linux no problem).

I've installed RDNIS driver from another post in XDA, but when I flag USB tethering win xp ask for an android phone driver.

I've tried with the one included in SDK (as the wiki suggest) but it doesn't work, I have also unistalled HTC sync as suggested in many post but with no luck.

Which driver I need?

Thank's

PS. sorry:p also without phone driver tether works!
[Desire Android Development] siroj:
I am also getting reboots using the latest(137) build on my Desire.

My wife is using the latest(135) on her HTC Legend and is also experiencing reboots.
[Desire Android Development] troly:
There have been updates # 138
[Desire Android Development] TheBlueRaja:
No reboots in #137 that i was seeing in #136.
[Desire Android Development] SoftWord:
when a final cm7 ?
[Desire Android Development] niiico69:
Just came back to #126. Too much reboots with later versions...
[Desire Android Development] grooltor:
I hope NEVER :D So we can always flash new stuff ;)
[Desire Android Development] Jagdish84:
Anyone tried #138 yet?

How come we got 2 different versions today?! :|
[Desire Android Development] keyra74:
137 :	2011-07-19 08:59:34

138 : 2011-07-20 09:00:50

so no you didn't get two versions on same day

as for reboot or else i don't get any
[Desire Android Development] Large Hadron:
Been running 138 a couple of hours. All looks good so far...
[Desire Android Development] mhkhatar:
DUDE ! please do not change your Radio. it will improve more than 15 meters on your wireless , BUT WILL WIDELY REDUCE YOUR CELL ANTENA ! you will alwayse face lake of antena and blury voice .
[Desire Android Development] mhkhatar:
DEAR , DL LINKS DOESN'T WORK !!!!!!!!!:mad::(
[Desire Android Development] ShiftyBloke:
Signal seems to be OK after clearing the cache, we will see :D
[Desire Android Development] Jagdish84:
Changelog says otherwise...
[Desire Android Development] keyra74:
not so sure :) : http://cm-nightlies.appspot.com/?device=bravo
[Desire Android Development] System of a pWne!^:
I've got a similar issue, but on Windows 7. Any solutions?
[Desire Android Development] Zobat:
Which radio you are talking about?
[Desire Android Development] hawkeyexp:
Hi Guys,

is anybody in gemany und uses a exchange-account and has the behavior that the alarm of calendar entries (birthdays) starts to late ? in my case birthdays start in outlook correct at 00:00 and ends on 00:00. On the mobile the alarm comes on 1.45 not on 00:00 :-( i have testet it with 2 different exchange-server

thx
[Desire Android Development] invinciblervd:
Everytime I try a CM nightly rom, I run into space issues while restoring all my apps thru titanium backup. I thought this ROM would do it for itself instead of me having to move apps to sd card one by one going into Manage applications settings.

I am using GV 2.7 currently and have no issues about internal storage. Anyone know how can I set CM to install apps directly to sd and not fill up my internal memory ?

Thanks in advance.
[Desire Android Development] grooltor:
Install S2E from market, and choose to move app to SD-EXT (must have an EXT partition on sdcard, if you used any app2sd solution before you should already have it).

Every time you flash a new nightly without wiping, apps will remain on your SD-EXT.
[Desire Android Development] donatinho:
I just flash the A2SD script of Kali- , you can find it in first page.

This one:
[Desire Android Development] RedSkyRoad:
On #138. Had 3 reboots today...
[Desire Android Development] troly:
I used # 138 today and no reboot. Now onto # 139 and then, hopefully good.:D
[Desire Android Development] siroj:
Today i tried building a new image for my Desire, the compiling stopped with the following error and i have no idea what to do next.

I have tried a fresh sync but that didn't fix it.

Anyone can assist me with this?
[Desire Android Development] keyra74:
gonna check if mine builds
[Desire Android Development] Jagdish84:
Led notifications aint workin on #140 :\

Edit:

After wipin cache and dalvik all seems to be in order...
[Desire Android Development] edwardally:
WIFI

Wifi seems like got something wrong... it stay nothing in the list and I need to on off and on off again in order scan the SSID
[Desire Android Development] Abednego:
Probably stupid question: What do I have to do if I want to switch from Kali's version of the Darktremor A2SD to the "standard" Darktremor A2SD? Just flash the Darktremor-zip? What happens with Kali's scripts?
[Desire Android Development] Zobat:
No problem with wifi here, latest nightly.
[Desire Android Development] Jagdish84:
flash the rom again and Darktremors script right after...
[Desire Android Development] iinga:
I believe you'd have to delete /sd-ext/userinit.d too. I think kali's is better because it remains through rom flashes, whereas dt you will have to flash each rom upgrade.

Sent by Owl Post
[Desire Android Development] BaGRoS:
I can't share to many place eg.facebook, because can't scroll.
[Desire Android Development] bemymonkey:
Is anyone else having problems with WiFi Tethering (Portable Hotspot) always providing a new, incremented SSID? I.e. if the SSID is "Hotspot", Windows 7 sees "Hotspot 1", then "Hotspot 2" the next time I connect, and then "Hotspot 3" and so on. It's annoying because Win7 takes ages to reconfigure everything when it's connecting to a new, unknown network.

Any ideas how to get rid of this?
[Desire Android Development] keyra74:
something wrong with source today?
[Desire Android Development] nespresso33:
Notification blue led is no longer working since few nightly.
[Desire Android Development] Kali-:
we use some google repo which was updated to 2.3.5

cyanogen have merged 2.3.5 (GRJ90) into cm and now it build fine
[Desire Android Development] johno168:
I want to keep up with nightlys but don't have the time, and now RC's are taking too long to update hahaa!
[Desire Android Development] d0msen:
1st rule, no asking for ETAs, not even subconscious ;-) can't tell that you don't have those 2 minutes buddy :> busted! lol
[Desire Android Development] keyra74:
thx for answers, compiled without error today :)
[Desire Android Development] johno168:
you got me.....:D
[Desire Android Development] TheBlueRaja:
I was thinking that it may be a bad thing for the Reboot to recovery option being available to users before you are past the security screen, if you have one set.

Pressing the power button give you the option to go straight into recovery from anywhere even if your security pin is set.

This gives anyone who steals your phone quite an easy way to break into it, wipe it, etc that they may not have otherwise known about.

Ideally, I'd also love to see a pin code on recovery, resettable only by adb.
[Desire Android Development] bemymonkey:
You can enter recovery and the bootloader by holding down the volume down or back button when turning on the device anyway... so your complaint is irrelevant ;)
[Desire Android Development] AlxMAX:
new apn in apns-conf.xml

Would it be possible to add the following APN definition in /system/etc/apns-conf.xml right before Cosmote Internet RO?

<apn carrier="Cosmote Broadband RO" mcc="226" mnc="03" apn="broadband" type="default,supl" />
[Desire Android Development] Kali-:
ofc

http://review.cyanogenmod.com/7023
[Desire Android Development] TheBlueRaja:
Its not irrelevant at all, how many people know about the volume down and back button at startup?

Conversely, if you had just nicked a phone whats the first thing you would do to try to get into it if you did'nt really know what you were doing - hold the power button down to get it to switch off.

Then you get a really helpful menu option to take you right into "recovery".

From there, wipe data - Factory reset.

Shiny new phone.
[Desire Android Development] bemymonkey:
If you know that entering the recovery on an Android device will allow you to wipe the device, you're bound to know that you can enter recovery with a certain button during boot. For anyone else, "Recovery" is just another "Whaaaa? No idea what that is...".
[Desire Android Development] AlxMAX:
Thank you very much.
[Desire Android Development] siroj:
I yust did a fresh " repo sync" and tried to build a new image for my Bravo but it fails with the following:

I tried a second time and again it failed with the same error.

Anyone has any clue about this?

Ps: My build environment is a fresh setup (+/-1 wk old) and produced a valid image 2 days ago. I have no idea why it fail as being to large. I did not merge additional patches and because i read that some people are able to successfully build there's today it puzzles me.
[Desire Android Development] Rastaman-FB:
Lockscreen trickery

theres an issue which only affects the nightlies and gingervillain 2.3.4 builds

basically if you have your kernel as 1.4 manu havs axi and set the min cpu to 128 and lock the screen.

8/10 times when you try and unlock it it will open and close within half a second and then keel the screen lights on for the duration of time out.

it did this in gingervillain months ago so i thought it was just a one off with the cm7 commits at that point.

I moved to cm703 and the problem was not there, lockscreen worked fine

ive moved to the latest nightly and the lockscreen problem is back

the only way to fix is to set the min cpu to 256

any ideas or are cm team aware of the issue?
[Desire Android Development] Kali-:
no, and i never consirer an issue bug introduced modifying shipped rom

128mhz was never good for any android device and cant give any battery improvment
[Desire Android Development] benjo:
It would be good if someone could implement a password screen on recovery. And something that prevented people from flashing a new recovery via fastboot unless an option is enabled in recovery :)
[Desire Android Development] ziggy1001:
Even if Cyanogen had some foolproof antiwipe system what good would it do? In the incredibly unlikely event that every phone thief was aware of this then what, only 9 out of ten stolen Desires would be wipeable not much of a deterrent:(
[Desire Android Development] Z0l:
This is not a problem with CyanogenMod, it's a problem with Android. It's also a problem with iOS, if you check out what the Frauenhofer guys were able to extract without knowing the device password. My advice: take good care of your phone. If you don't want to take this risk, then switch to a dumb phone and sleep better.
[Desire Android Development] siroj:
Strange, Kali said to me that he had no problem building his image this morning.

I then reverted to a fresh install of Ubuntu and recreated my development environment. After this the build still halts with the same error:

Anyone?
[Desire Android Development] ziggy1001:
I have to agree that's the bottom line AFAIK most stolen mobile phones aren't recovered. So if no government, their military establishments, or any multi- billion$ corporation can guarantee data/network security etc how the hell can anyone
[Desire Android Development] benjo:
It would just be peace of mind knowing that the thief would be stuck with a useless phone after it being locked with wavesecure or similar :D
[Desire Android Development] Z0l:
Also, if you forget your password or input it say 10 times wrong and the device destroys itself, then what do you? Blame it on CyanogenMod that it's their fault? There is absolutely no reasoning behind your request. The device was never useful and never will be. The data can be protected, but the device cannot.
[Desire Android Development] ziggy1001:
Well unbeatable security is an oxymoron so why ask for something that's impossible to achieve;)
[Desire Android Development] benjo:
Can I make it clear that I'm not requesting Cyanogen to implement this? It's just an off topic thought.. :rolleyes:
[Desire Android Development] Rastaman-FB:
hmm while i respect your work i have to say there are devices that work on android that are made with a kernal for 128. indeed desire was not but to say it cant give any improvement is proven wrong if you check the manu thread.

Im not a trend follower or do things because other people have said "oh this is better". the manu 1.4 axi kernel when set to those values has the best battery life i have ever seen and alot of people can vouch for it.

if you have you phone on sleep with an axi kernal running with a min of 128 and a max of 246 the battery draw is the lowest ive seen.

I can understand why you wouldnt support it, i was just asking if you were aware of anything that has changed from cm7.0.3 commits on 2.3.3 to the nightlies running 2.3.4 as what ever has changed clearly doesnt agree with 128mhz.

EDIT: and its only cm7 based roms that have this issue
[Desire Android Development] zlatkowolverine:
Can anyone tell me is the 145 laggy or its jus me?
[Desire Android Development] ziggy1001:
145 fine with me
[Desire Android Development] Klausi:
sorry, just you