yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] perdurabo2:
ADB works fine here on Windows 7 x64 with the latest patches from Microsoft applied. I have no information on its functioning on 32-bit, though.
[Nexus One Android Development] lolittle:
Works fine here Win7 Ultimate 32bit :)
[Nexus One Android Development] stshannon:
I run Windows 7 Ultimate 64bit, with latest updates from Microsoft, and ADB works fine for me. I'm still fairly new to this, only about a month in, and unfortunately, i do not remember the steps i took to get ADB to work properly when i first rooted my nexus one. Wish i could help more.
[Nexus One Android Development] phreaker18:
Can i beg forgiveness for the crappy laptop i have ... we all now know that adb works with Win 7 64 bit & 32 bit ... :D
[Nexus One Android Development] flomid:
I tried searching for this to no avail so I hope I don't get chewed out on the issue if its been brought up before, but...

I noticed that ever since I unlocked/rooted and flashed to CyanogenMod that my MMS messages haven't been received on the recipient's phone. On my phone it says they are sent successfully with the envelope and clock icon showing up and then going away as if it were sent properly, however whenever I ask the recipient if they have received the MMS they never have. I called T-Mobile regarding the issue because I had searched and found that it might have been my APN settings but they confirmed that they were properly configured. I tested sending MMS to friends of mine that I know are on different networks (Sprint, AT&T, Verizon, & T-Mobile) and none of them were receiving my MMS. While I was on the phone with T-Mobile they had me send a test MMS to myself to see if I was able to receive that and I was...

I have read that there is an issue regarding varying file size limits for MMS across the different carriers and how CyanogenMod ROM might have altered that limit so the images are not being compressed to a file size that is compatible with other networks, is that the possible issue? At this point I am not sure what to do. I think I have pinpointed the problem to be somewhere with the CyanogenMod ROM because I was successfully sending MMS that were confirmed received before I flashed and was on stock OEM google ROM.

Any help would be greatly appreciated (other than suggesting Handscent, please)
[Nexus One Android Development] krumb:
http://www.google.com/support/forum/p/android/thread?tid=728949efd681db72&hl=en

this worked for me.
[Nexus One Android Development] djmcnz:
Edit: lol, try that ^^^ :)

Fair enough. I don't recall hearing about this specific issue.

What about sending a really small mms (text only) to a friend that hasn't received your other ones? Does that work? If so it is likely a resizing issue. If they don't receive it then I'd ask your carrier to have a look at the call detail records - typically a CSR can see the last 100 or so - to determine was it received by the network, was it carried by the network, was it delivered (including handed over) by the network. I'm disappointed they couldn't tell you that the first time! They should be able to do this large or small message... if they have no record whatsoever then the messages are not leaving your phone. Wipe and reflash I think in this case...
[Nexus One Android Development] flomid:
Yeah I saw that and tried it out, but still the same issue. Also when I talked to T-Mobile on the phone they went through all the apn settings line by line to make sure they were correct...
[Nexus One Android Development] flomid:
Just sent a small text only mms and it was received... so is there a way yo configure the file size of images after they are compressed for mms?
[Nexus One Android Development] craigacgomez:
any idea when CM 5.0.6-N1 will be released... I see some nice changes in the changelog...

http://github.com/cyanogen/android_vendor_cyanogen/blob/eclair/CHANGELOG
[Nexus One Android Development] stshannon:
I hate to sound like a broken record, but until Cyan (or someone) codes a resizing option into the mms.apk, there's another alternative.

Download (for free) "Handcent (NEW)" from the marketplace. In addition to a TON of other features you wont see in the stock sms/mms application, it allows you to set your maximum MMS size to either 200k, 300k, 500k, or 1m.

This might solve your issue if it is solely a resizing issue.
[Nexus One Android Development] jblazea50:
i'm waiting for 5.0.6 so i can do a complete wipe and move to this again
[Nexus One Android Development] djmcnz:
I forgot to ask, is your messaging user agent set correctly? You could try playing around with them to see if your network varies their rules by agent?
[Nexus One Android Development] izmar:
To each their own I guess.:rolleyes:
[Nexus One Android Development] Harry454:
One small request, anyway to get divx/xvid on Nexus one? :D
[Nexus One Android Development] djmcnz:
Yep, easy too see here
[Nexus One Android Development] psylink:
i had stock messenger, handcent, chompsms

chompsms personally is the only one that resized the pics properly

handcent made them way too small

so to stshannon, check out chompsms as well
[Nexus One Android Development] craigacgomez:
hahaha... lol!! good one... there's talks going abt this on the Google forum... but from wht I see, I guess we're just waiting for the NDK to mature enuf...
[Nexus One Android Development] yostral:
1. Make sure the FOURCC is "DX50"

2. Ré-encode the audio in AAC (or any other codec compatible with the mp4 container)

3. Mux the video (DivX/XviD) stream with the audio stream in a mp4/m4v container

And it should work...
[Nexus One Android Development] stshannon:
+1 to this for sure.

Currently I'm using Xilsoft Video Converter to convert my Divx movies down to a compatible format... but if i could take my movies, and just copy them to my SD card, that would be ideal.
[Nexus One Android Development] ttieder:
is there 5.0.6 because it says there is on his change log or was that a aprils fools joke to
[Nexus One Android Development] jblazea50:
it's not released yet, don't know the estimated release time; just have to wait
[Nexus One Android Development] SiNJiN76:
yeah...can't wait to see if this change means what i think it means...

* Ability to move installed applications between internal storage and SD (from ChrisSoyars)
[Nexus One Android Development] fitsnugly:
Install the trackball unlock mod and you'll get this function early :)
[Nexus One Android Development] thejron:
Ok, this is my second N1 and my second time rooting. When booting into recovery I get the exclamation point and android screen. I think it was volume up and power that brought me to "Android system recovery <2e>" with options to reboot system, apply update.zip, wipe/factory reset, and wipe cache partition. I also get

Cant open cache recovery command". I'm trying to do a backup and flash recovery image before i go to CM.

HELP! thanks in advance
[Nexus One Android Development] craigacgomez:
That is the stock recovery... flash Amon_RAs recovery for the nandroid backup...
[Nexus One Android Development] SiNJiN76:
nevermind.
[Nexus One Android Development] RiNo808:
anyone expiriencing there batt draining faster then ussual? any ideas on how to conserve the batt...or what is a good over clock settings? just wondering what you all got your n1's clocked at, before i install setcpu...thanks in advanced....
[Nexus One Android Development] andonnguyen:
Stock settings without setCPU works pretty well. I found that setting your screen brightness too high will drain the battery very fast. I just set it to automatic brightness, and downloaded the program "dimmer" from the market and enable it during the nighttime (it sets the minimum brightness from 30 to 10).

If you install setCPU, set the max to 998 and min to 245. Make sure the governer is set to "on demand". Enable "set on boot" and "auto-refresh" as well. I have the following profiles as well:

Charging:

Max: 998

Min: 245

Standby:

Max: 245

Min: 245

Battery < 100%:

Max: 998

Min: 245

The current CM kernel is slightly undervolted, but you can also download the UV or UV/OC kernal by pershoot/persiantown which work pretty well for further battery savings.

If all that doesn't work, you might want to recalibrate your battery. Let it drain all the way down until you can no longer turn it on. Charge it for 4-5 hours with the phone off. First boot into recovery and wipe battery stats. Reboot and let the OS boot. Then Reboot again.
[Nexus One Android Development] RiNo808:
thanks andonnguyen...thats awesome...i got another question that has to do with the track ball notifications...i know that its built into the 5.0.3 rom, but i also have the "trackball alert" from the market place...for some reason the lights are all messed up...i have green to blink for sms, mms...but for some reason it blinks blue..then sometimes it blinks green...i tried both to disable one and the other...should i just remove the trackball alert from the phone? I also have "missed call" also from themarket place, it alows you to set a tone and repeat duration whenever you miss a call, sms, etc...my problem is that it alerts me only sometimes...im wondering if it conflicts with the CM rom mods...does anyone know of anyother mod that has that repeat alerts??? or do any of you know of a fix or maybe the repeat alert can be implemented in the next rom update...thanks in advanced...
[Nexus One Android Development] thejron:
it worked, thanks guys
[Nexus One Android Development] mgorman:
---- 5.0.6-N1

* Latest code from AOSP from Google as of 3/31/2010

* Ability to move installed applications between internal storage and SD (from ChrisSoyars)

* Added libncurses, irssi, htop, bash, nano and powertop.

* Added option to disable USB Debugging notification.

* 5 column launcher drawer (from Kmobs and ChrisSoyars)

* Animated GIF support in the browser

* Updated translations

* Yahoo mail can be used over wifi (from Invader@AllDroid)

* Kernel is now built from source and installed properly by the Android build system (from Android-X86, tweaked by Wes Garner and Chris Soyars)

* New camera features (antibanding, focus mode, jpeg quality) from CodeAurora

* Battery percentage meter fix from ChainsDD

* Fixed some bugs in Dropbear and added dropbear-keygen to generate host keys

* New ARM NEON optimizations from ARM and 0xlab (http://0xlab.org)
[Nexus One Android Development] jean1190:
For those having batteries issues, I got another problem two days ago, and I never could have solved it without Spare Parts. Indeed, who could have imagined that the problem was Doodle Jump sucking the battery life with the sensor even after being closed by TasKiller...

I have no idea why... But I just uninstalled it, and now battery is back !
[Nexus One Android Development] McAndrew73:
Incredible!

Good job in discovering it. :)
[Nexus One Android Development] pzumk:
it's not Doodle Jump.. it can't use battery after being closed by Taskiller..

show us screenshots of spareparts!
[Nexus One Android Development] asci:
Please can you be more precise and explane me what you did exactly? I searched for Doodle Jump but I didn't find anything...

What is it?

Thanx a lot!
[Nexus One Android Development] mikroN1:
You would of had to of installed Doodle Jump to have a problem. If you don't know what it is obviously you haven't downloaded it.
[Nexus One Android Development] peadarog:
I LOVE this ROM, but the battery issue is very real.

I tried all sorts of things -- task-killers, setcpu, removal of batterystats.bin with further recharging etc., etc. I managed to improve my battery life considerably. However, moving to Enom's ROM, with no task killer and no setcpu profiles running my battery has returned to normal again.

Other people have reported the same behavior. For me, the biggest anomaly was how much battery got used up while on airplane mode overnight. 8-10% without setcpu and task killer, 3-5% with setcpu profiles and task-killer turned to automatic.

After switching to ENOM, last night I lost less than 1% without taking any special precautions.

Something is definitely up.

When 5.0.6 comes out, I'll try again and maybe see if I can catch any rogue processes in the act. FYI, I have not now, nor have I ever installed Doodle Jump :)
[Nexus One Android Development] jean1190:
If it's not, then Spare Parts is wrong ;)

I tried again, just for you !

1- I re-installed Doodle Jump (from Market, not even from Titanium Restore)

2- I pressed "Exit" in the game and killed it with tasKiller 5 seconds after.

3- I checked on Spare Parts, sensor usage. Doodle Jump = ~10sec

4- As you can see on the screenshot, there is no Doodle Jump icon in the task bar widget. (neither in the tasKiller black list, I checked..)

... *Wait 5 minutes*

5- Doodle Jump usage sensor = 6m44 (screenshots)

It stopped increasing when I plugged my phone in my computer to upload the screenshots.

:rolleyes:
[Nexus One Android Development] jlevy73:
I definitely agree. Even with SetCPU set to 384/245 during standby/sleep the ROM snarfed down 45% of my battery during 6 hours of absolute no usage (while I was sleeping). The funny part is display accounted for 40% of that and it was off the whole time.
[Nexus One Android Development] Andrewtst:
I never face such issue, I set to 384/245 as well during standby/idle time.

After wake up from sleep, normally only around 5% battery drop. I know it still quite consuming, but at your said down to 45%? if from 100% (you never mention) that means is around 55% drop. This is crazy!
[Nexus One Android Development] stewart1988:
Not an issue for me...

A full night charge can last 14+ hours with heavy use throughout the day. Thats calls, texts, email and browsing.

With the stock ROM I had to charge my phone by lunch (5-6hours after charging)

I don't use any task killers because I found they kill my battery more and I just let Android do its thing with killing tasks etc. I don't have SetCPU or any over clocking or battery saving tweaks etc.

Try checking battery usage to see what is killing your battery.
[Nexus One Android Development] peadarog:
That's the problem, really. It's not an issue for everybody and that's what's going to make it difficult to track down. I still come back to losing 8% overnight on CM, to losing less than 1% on ENOM with the same set of applications installed (from titanium backup).

There's GOT to be something running that disagrees with this ROM, but what? Maybe those of us who are having the problems -- and we're probably a minority -- should list what apps we have installed and maybe we'll get to the bottom of it. So, here's mine:

[morimhaire@localhost tools]$ ./adb shell ls system/app

AccountAndSyncSettings.apk LiveWallpapers.apk

ApplicationsProvider.apk LiveWallpapersPicker.apk

Bluetooth.apk MagicSmokeWallpapers.apk

Browser.apk Maps.apk

BugReport.apk MarketUpdater.apk

Calculator.apk MediaProvider.apk

Calendar.apk MediaUploader.apk

CalendarProvider.apk Mms.apk

Camera.apk Music.apk

CarDock.apk NetworkLocation.apk

CertInstaller.apk PackageInstaller.apk

Contacts.apk PassionQuickOffice.apk

ContactsProvider.apk Phone.apk

DeskClock.apk PicoTts.apk

Development.apk Settings.apk

DownloadProvider.apk SettingsProvider.apk

DrmProvider.apk SetupWizard.apk

Email.apk SoundRecorder.apk

EnhancedGoogleSearchProvider.apk SpareParts.apk

Gallery3D.apk Street.apk

GenieWidget.apk Superuser.apk

GlobalSearch.apk SystemUpdater.apk

Gmail.apk Talk.apk

GmailProvider.apk TalkProvider.apk

GoogleApps.apk TelephonyProvider.apk

GoogleBackupTransport.apk Term.apk

GoogleCheckin.apk TtsService.apk

GoogleContactsSyncAdapter.apk UserDictionaryProvider.apk

GoogleFeedback.apk Vending.apk

GoogleGoggles.apk VisualizationWallpapers.apk

GooglePartnerSetup.apk VoiceDialer.apk

GoogleSettingsProvider.apk VpnServices.apk

GoogleSubscribedFeedsProvider.apk YouTube.apk

HTMLViewer.apk googlevoice.apk

HtcCopyright.apk gtalkservice.apk

IM.apk kickback.apk

LatinIME.apk soundback.apk

LatinImeTutorial.apk talkback.apk

Launcher2.apk
[Nexus One Android Development] Pochemuchka1977:
I have the same problem too and usually reboot fixes things. What i have noticed, that every time i have my slider stacked, bluetooth was enabled on the phone
[Nexus One Android Development] SubyWill:
maybe it's a hardware issue for you guys? like, the battery taking a crap or something.

i get over 20 hours of battery with mine.
[Nexus One Android Development] nathanzachary:
The only thing that makes me wonder about the battery is that mine drops approximately 4-5% per hour when not in use (no messaging, phone calls, browsing or anything). My battery is still lasting as long as I need it to, but it would be nice to do more and not worry about it making it through the day.
[Nexus One Android Development] djmcnz:
Well I don't actually have a problem with my battery but... check this out, it may mean something.

CPU and memory usage whilst the phone is in airplane mode over night. Memory is yellow, CPU is green.

I have no idea what's causing the crazy memory behaviour since there's hardly any CPU usage.

Happens every night.
[Nexus One Android Development] jlevy73:
Wow, what program or app is that. Very informative chart.
[Nexus One Android Development] djmcnz:
aiSystem Widget from the market... well worth the price... top left wdget on the first screen launches the main app.
[Nexus One Android Development] mikroN1:
Could you list all the widgets on your home screen djmcnz? I'm only aware of the two top right quick boot icons.
[Nexus One Android Development] DarkSi08:
I can confirm this issue. I have the exact same anomaly - caused by Abducted! though, not Doodle Jump. I just thought to check Spare Parts because of this post. I played Abducted! for about 5 minutes this morning, at most. It's currently showing 11hr and 43min of usage on the sensor.

Thanks Jean - you've definitely pointed out a problem, even if it's not what's causing everyone's battery issues. I uninstalled Abducted!, hopefully my battery will last a little longer tomorrow. We shall see!
[Nexus One Android Development] RaQHoliday:
... I don't see this link?

Edit: Ok, i see, this is info from the change-log. Gotcha. [/slowmoment]
[Nexus One Android Development] zidane:
i think i have a problem with the automatic brightness

heres the situation. when in a completely dark room, shouldnt the brightness go down to the lowest? (the room is pitch black)

however my screen never seems to dim all the way down, it does change brightness if im outside in a sunny days or in indoors, but i think it never went to its lowest possible brightness even if in a completely dark room
[Nexus One Android Development] stshannon:
The lowest setting is 30 (as allowed by default android), which isn't quite dim enough for a dark room.

Quote from andonnguyen in post 6494:

"I found that setting your screen brightness too high will drain the battery very fast. I just set it to automatic brightness, and downloaded the program "dimmer" from the market and enable it during the nighttime (it sets the minimum brightness from 30 to 10)."

Hope that helps
[Nexus One Android Development] jean1190:
It's good to know I am not the only one. Actually, I am pretty sure a lot of people have problem with the sensor usage but just don't see it.

Yesterday evening, my phone was at 80% battery life, so I decided to give it a shot. I opened a few apps and then closed everything with tasKiller.

This morning, what a surprise !

Sensor Usage :

Doodle Jump = ~4h

Abduction! = ~4h

ShootMe = ~4h

WTF ?!
[Nexus One Android Development] paulk_:
I thought it was standard for the battery to drop around 5% per hour? Not sure if that has anything to do with me having autosync on all the time though.

I don't have any problems with games which use the sensor not closing themselves, running 5.0.5.3
[Nexus One Android Development] djmcnz:
No worries:

2x2 aiSystem Widget

2x1 Mini Info

2x1 IP Address Widget

1x1 Settings Profile

1x1 Cachemate

And the two Quick Boot shortcuts you mentioned. All from the market.
[Nexus One Android Development] distortedloop:
Is it possible that the aisystem widget itself is what's causing that memory and cpu fluctuations? The fact that it's running must impact the system, unless it's just reading some standard log info that Android's already collecting...?

There are only 10 comments for the the widget on the market and two of them complain of it using too much memory and a third complains of it draining the battery quickly.
[Nexus One Android Development] distortedloop:
There might indeed be some sensor usage weirdness going on.

My N1 with 5.0.5.3 has only been off the charger for 48 minutes this morning. It's down to 93% battery, 87% of that is from the screen, which has been on 15 minutes (per settings/about)

re: the sensors, though, Spare Parts sensor usage reports the following SINCE LAST UNPLUGGED:

Gallery 21m 32s

pocketBLU 21m 32s

Android System 20m 35s

When I first checked before writing this post, the phone had been off charger for 36 minutes, and Gallery/pocketBLU were both reporting 17m usage, so in 12 minutes they both sucked up another 4 mins of sensor time. Odd.

I haven't touched Gallery this morning, though I just opened a task killer and it shows Gallery is running, and I did use it last night before docking the phone.

I haven't used pocketBLU (a DVD remote control for PS3) since Friday afternoon, and here's what's interesting, two different task killer apps both show it's not even running.

Interesting that the Gallery needs to check sensor input (tilt for the 3d effect?) while backgrounded and that an app that's supposedly not even running also checks the sensors.

What we really need at this point is for someone to load up a different ROM, preferably not even CM, and see if they can reproduce this; that would really tell if it's a CM problem or not, right?
[Nexus One Android Development] mikroN1:
Thanks a lot
[Nexus One Android Development] andonnguyen:
5 percent battery drop per hour isn't standard...I've gone 7 hours with my battery dropping to 85 percent

Sent from my Nexus One using the XDA mobile application powered by Tapatalk
[Nexus One Android Development] myn1:
Guys. Try log off your Google Talk. Or turn off the Auto-login option and reboot your N1. I found that app eats up a lot of battery.
[Nexus One Android Development] prettyboy85712:
Do you have the same apps installed as him? Did you use your phone for the same amount of time or in the same way with the same settings? If you not then it's not an apples to apples comparison.
[Nexus One Android Development] paulk_:
I don't think it's possibleto have only a 15% drop in battery life over 7 hours if autosync is on, even if you don't touch your phone and you're using a UV kernel with CPU speed set at the lowest.
[Nexus One Android Development] hondaguy:
Has anyone else tried this? I had done this on my milestone and I found that my gmail accounts stopped pushing emails reliably. I would get messages late or in groups and once I allowed gtalk to do its own thing the issues went away.

Thanks
[Nexus One Android Development] typ_ex:
i sent my self a couple of emails to test, works fine.
[Nexus One Android Development] hondaguy:
That is good to hear but I said reliably because it was an intermittent issue. It would work fine for an hour, then not so well. You have to pay attention to the times on the emails to notice it.

I hope you are right as any increase in battery life is welcome
[Nexus One Android Development] cedricj:
Funny GPS problem

Hello,

Using the latest and greatest CYA 5.0.5.3.

Everything is a perfection.

I have a funny problem with GPS.

GPS only works in my country.

If i am travelling abroad (france, nederland Ireladn so far), then i cant get any GPS app to work. A max of 2 sat is found.

I just landed today from Dublin where i could not get any GPS sats at all and got immediately 9 sats aftre landing??!

Any ideas?

Is there a file i could delete that caches sats?

Le me know if you have an idea on how to fix this?

TX:)
[Nexus One Android Development] paulk_:
Weird, I always disable the auto login for Google Talk and I've never had that problem. The only time I have problems receiving push Gmail is when I am at work where the data signal is atrocious.
[Nexus One Android Development] Stea1thmode:
+1

same here