yashsingh1/xdaforums huggingface dataset:
[Nexus One Q&A, Help & Troubleshooting] RogerPodacter:
Well your voltage readings are perfect, but the capacity is pretty high. I bet you have the 1600 mah battery which is the same size as stock battery physically, so you might not tell the difference. Did you buy the phone brand new?
[Nexus One Q&A, Help & Troubleshooting] stuff:
Yeah I got it brand new. I thought the batteries were 1400mAh?
[Nexus One Q&A, Help & Troubleshooting] khaytsus:
Yep, 1400mAh. Lithium's are fully charged at 4.2V, if it's saying it's charging more "power" than that, you might just need to calibrate the system. I think Google has "official" documentation on this, otherwise I've seen it here. Something like charge it all the way to green, turn off phone, re-plug the charge, leave it for several hours.
[Nexus One Q&A, Help & Troubleshooting] stuff:
I actually recently "calibrated" it that way, and it worked perfectly. I don't think it could become uncalibrated.
[Nexus One Q&A, Help & Troubleshooting] RogerPodacter:
The stock batteries are 1400, but I was implying that you got the 1600 one based on those readings. Are you sure you didn't somehow get the 1600 one? I don't think this is a calibration issue. The OS is hard coded with basic mah numbers that cannot be changed no matter what, even if you delete the battery stats file.
[Android Software Development] rogershroed1991:
I have a navigation/dvd/music/etc system in my car, it's nice but I had an idea to buy another Android phone and put it in the glovebox, put a touchscreen monitor in the dash and hook the phone up to it and use the display output on the phone to broadcast it to the monitor, so it's basically like having a separate phone with a huge screen built into your dashboard. Then you could make calls and listen to music, watch videos, Google Navigation, go on the internet, whatever, using the screen in your dash.

Is there anything like this already out? Would it be possible to do that or would the monitor not be able to send your input/touch back to the phone? Would it be able to stretch the display to the size of the monitor? I'm not very technical so I'm just coming up with ideas and I'm not really sure if it's possible or not.
[Android Software Development] eweo911:
Why not look into the APAD. I believe it takes a sim card so you can hook up to the internet and make phone calls, it also has a 7in screen. It's only on 1.5 I believe but it should work for what you want.

Or this:

http://chinagrabber.com/7-android-tablet-pc---apad-irobot-eken-tablet-pc-w-google-android-wifi-webcam---apad-m003.aspx

Does NOT have GPS.

Here is one review of the iped:

http://www.product-reviews.net/2010/06/01/apple-ipad-vs-china-iped-apad-which-one-is-better/

These guys are selling one for $189.00

http://www.androidostablet.com/

I have not tested any of these but I might do exactly the same thing as you are talking about.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] derylmccarty:
Chefs and Devs give us pretty up to date ROMs to flash and test and I for one am most grateful. But I have noticed that, compared to say a year ago, new ROM builds are coming slower and slower. We have had the more leading edge 23569 now for a few weeks and the 21xxx series has gone from only 03 to 11. The Max and Cookie builds are going faster as is the Sense core.

My questions are:

Am I really seeing a slowdown in Micosoft builds and therefore a slowdown or tapering off of attention paid to 6.5.1 and 6.5.5.

Does that mean they have gotten most of the testing done for those series to apply to 7.0 or some "final" version of 6.5+.x

Does that mean that you guys are gonna start working a 7.0 (minus) beta build for even some of our "less capable" phones.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] steviewevie:
New OS releases might be a lot slower coming out these days (23569 has been around a lot longer than a few weeks), but I don't see any slowdown in terms of ROM releases with different packages/fixes/tweaks etc - I use EnergyROM, I can't comment on other ROMs.

Don't think there's any way we're going to be seeing WM 7 on our TP2 though.
[Desire Android Development] zeussn:
One note, I've a Desire with Mac 38:E7 and I can confirm that with the HTC Leaked the wifi is always on (as I set it in the Wifi Policy) but with the screen off, yes I've higher pings.

But, with the AOSP (AOSPDesire/OpenDesire) even setting the Wifi Policy to Never, it falls at the time that the screen goes off.
[Desire Android Development] meLIanTQ:
for me it's perfect :00:23

check too this file: WifiService.java

/home/meliantq/aospdesire/system/frameworks/base/services/java/com/android/server/WifiService.java

already try to force stay on = ko

maybe change the wake lock :confused:
[Desire Android Development] PaulW21781:
Differences between how the MAC addresses react, could be related to a possibly firmware bug for the driver too... Who knows...

I have also tried building an AOSP build around the new firmware files from the leaked HTC 2.2 ROMs, but these failed to connect at all too.
[Desire Android Development] mon@diac:
I thank you for your great work..I hope you can fix it.. and I hope i can use AOSP rom

meliantq - je te remercie pour ton travail formidable...
[Desire Android Development] meLIanTQ:
paul for me too is not really perfect ...

when screen off ping don't work

here is good:

Ping when screen off ok
[Desire Android Development] sjauquet:
I have MAC who starts with 38:E7

I also have network who became to state "disabled" after a long sleep time

I ave to re connect to the network.

It seems it happens only to secured networks

with richardtrip roms versions 2.0a b c and d It seems this problem disapeared.

edit: probably also because the rom had sleep problems as the battery consumption was high... so maybe it was as simple as no sleep measn also no wifi disconnection....
[Desire Android Development] mon@diac:
but why? why doesn't it work for me? Ok i changed my mobile package and i buyed origami jet package (internet mail&wifi, calls, tv, sms&mms etc unlimited).. I want to use AOSP rom and downloaded froyo-desire 0.1b...ooo la la
[Desire Android Development] meLIanTQ:
@Paul:

check the framework/base/wifi
[Desire Android Development] PaulW21781:
Looking

Also, in the same folder, check out lines 922 onwards for file WifiManager.java

Infact, the whole function (843 to makes some interesting reading...

Also, 1094 on references to Multicast locks, could be related...

May be worth looking into this also...

I'll have a proper look over the weekend when I get time (joint birthday bash tomorrow with me and a friend), and been to the pub tonight so not the best time to start sifting though code & make changes lol!
[Desire Android Development] PaulW21781:
Rawr

Also... References in WifiNative.java

/**
* Start filtering out multicast packets, to reduce battery consumption
* that would result from processing them, only to discard them.
* @return {@code true} if the operation succeeded, {@code false} otherwise
*/
public native static boolean startPacketFiltering();

/**
* Stop filtering out multicast packets.
* @return {@code true} if the operation succeeded, {@code false} otherwise
*/
public native static boolean stopPacketFiltering();

public native static boolean setPowerModeCommand(int mode);

Possibly disable the Start & Stop Packet Filtering routines, and override the setPowerModeCommand function too (which you already pointed out)

Further down WifiStateTracker.java too... line 2256... It's admitted in there it causes issues!! WTH?!?!

/*
* There are problems setting the Wi-Fi driver's power
* mode to active when bluetooth coexistence mode is
* enabled or sense.
* <p>
* We set Wi-Fi to active mode when
* obtaining an IP address because we've found
* compatibility issues with some routers with low power
* mode.
* <p>
* In order for this active power mode to properly be set,
* we disable coexistence mode until we're done with
* obtaining an IP address. One exception is if we
* are currently connected to a headset, since disabling
* coexistence would interrupt that connection.
*/

hazaa
[Desire Android Development] sjauquet:
tested with this rom for 1/2h and the problem seem not happening.

Now I'm back to defrost 2.1 and still the problem
[Desire Android Development] Peve:
Hey guys signed up to the forum just to say thanks for looking into this :).

Biggest problem with the current ROMs for me is losing WiFi when sleeping, so keep up the good work.
[Desire Android Development] joshjzx:
I have 38:e7 network too but I haven't had that issue on dj droid

Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
[Desire Android Development] mon@diac:
Wifi issue is valid for froyo non-sense roms.. Djdroid and Official Froyo are froyo sense roms..
[Desire Android Development] Westcliff1979:
I can confirm this. Same Mac-Address an no problems with leaked Sense-Froyo. With defrost I have still the problems. So the bug seems to be fixed on sense-based roms.
[Desire Android Development] zeussn:
People, all the NON-Sense Froyo (OpenDesire/Defrost/OASPDesire...) Rom have this problem and All the Froyo Sense Roms (HTC Leaked/HTC Official HK) don't have this problem, that is a Fact so please stop say it over and over.
[Desire Android Development] PaulW21781:
meLIanTQ - I'll work through that code tomorrow, see what I can pull off...

Just for the record, I've tested a N1 running FRF91 (official google build + kernel) completely unmolested... MAC is 38:E7... And it suffers from the EXACT same issue, so it's not just the Desire that this affects... So I will also be building a passion ROM to test on my friends N1 aswell if we manage to sort something for the Desire...
[Desire Android Development] meLIanTQ:
Drivers bug or froyo bug? if its a offcial bug maybe google work on ... and get a patch in futur update ;)
[Desire Android Development] zeussn:
It's a froyo bug however htc have manage to fix it because the froyo versions with sense works just fine.
[Desire Android Development] ghiki:
I'm not sure, I have 00:23 MAC Adress and I have this bug, at 20-30 minutes of inactivity the wifi disconnects (in sleep policies have selected "Never")

ED: I have DJDroid v1.1
[Desire Android Development] zeussn:
The bug isn't that the WiFi disconnects after 15 minutes, the bug, at least this bug, is that even setting the Wifi Policy to Never, every time the screen goes off the wifi does the same and apparenly it happens only to the people that have a mac address that starts with 38:E7 using the AOSP roms (On the HTC Leaked works just fine).
[Desire Android Development] davedgd:
I wish I could post links, but on the BGR story about the N1's WIFI issue (this same issue the Desire experiences), there is an update with a .git for new driver for the Broadcom chip, on the code site (provided by Broadcom developers). Anyone able to try this?
[Desire Android Development] hi2u2:
Here is the link dave was referring to; I have been following the thread over at google too.

http://www.boygeniusreport.com/2010...users-experiencing-wi-fi-connectivity-issues/
[Desire Android Development] sjauquet:
problem solved on defrost 2.4d !!! :D:D:D
[Desire Android Development] lambrospower:
how can we apply the fix ????? is there any flashable zip we can use from the recovery ?
[Desire Android Development] sjauquet:
Ask Richardtrip...
[Desire Android Development] dnlgee:
Applied in the kernel.
[Desire Android Development] Seronez:
I've got an Froyo Sense Rom but the Problem still occurs. Mac Adress is this crappy 38:E7 is there an easy solution available??

MfG
[Desire Android Development] bemymonkey:
Same here. Looks like nobody's interested any more though...

WiFi Fixer helps a little (pingableness etc.) but doesn't solve the actual problem - for the first 30 seconds or so after the screen's turned off, there still isn't really a connection (as stated in the first post of this thread), which makes VoIP impossible... :(
[Desire Android Development] Myshkinbob:
http://xdaforums.com/showthread.php?t=752856

Modified wifi module for HTC 2.2 based roms, fixes the standby lag/disconnects/bandwidth restrictions. Basically uses a different wifi power management mode when the phone sleeps.
[Desire Android Development] bemymonkey:
Seen it, it's for a different kernel. I'm guessing flashing that on current AOSP ROMs will blow something up...?

Please correct me if I'm wrong :(
[Desire Android Development] xeren:
oops -

deleted
[Desire Android Development] bemymonkey:
Guess you read the other thread? Myshkinbob has pretty much solved the problem ;)
[General Topics] conflikt:
I don't own an iphone but it looks like not just the iphone suffers from the death grip. Also apple is giving user free cases or bumpers which is cool of apple to do. Source link....http://www.engadget.com/2010/07/16/apple-to-give-away-free-bumpers-to-iphone-4-users/

Confernce... http://www.engadget.com/2010/07/16/live-from-apples-iphone-4-press-conference/

Sent from my fully rooted HTC EVO running damage control 3.2.3
[General Topics] orb3000:
Do we really need to have a new iphone thread for this?

Having more than 20:confused::eek:

Respectfully,
[General Topics] conflikt:
Ehh as said. I don't own one nor did i see any posts about it at the time that i did create this post.

Sent from my fully rooted HTC EVO running damage control 3.2.3
[General Topics] hungry81:
So its "cool" of Jobs to do what he should have done in the FIRST place and give away parts that fix the phone? After ignoring the issue for months? Something tells me he should have done that in the first place.

If your EVO came without a battery cover (Optional accessory $29.95!) and the battery "occasionally" fell out interrupting your calls, would it be "cool" if because of negitive publicity ( consumer reports) they started giving it away for free? or would you have expected the cover to have come with the phone in the first place?

But hey coolaid is great and the cups are soooooooo shiny mmmmmmmm
[General Topics] leftkats:
Just couldn't resist using photoshop today!
[General Questions and Answers] krakenus:
Hi, I have XPERIA X1 with Touch It Experience (ROM from Itje, with Windows Mobile 6.1). When I connect cable or BlueTooth handsfree and want to make a call, the phone speaker is switched on. I can hear sound both in handsfree and from speaker. Microphone on handsfree doesn't function, only microphone on mobile itself is switched on. I have tried many handsfrees so there has to be problem in Xperia or in settings of phone or windows.

Please help me - is there any thread with this problem? or some fix? I have tried to find it but was not successfull.

Thank you!
[myTouch 3G, Magic General] Cryofuse:
Hi,

Phone : HTC Magic 32A

Firmware : 2.1

Country : Denmark/Europe

I'm trying to install the MLIGN 3.3 Hero ROM on my HTC Magic 32A (Denmark model). It is already rooted and I have ClockworkMod's ROM Manager installed. I think that I am correct in saying that the following procedure is how I should flash the new ROM.

1. Power on to the 'Recovery mode' (Home + Power)

2. 'Factory Reset' the phone.

3. Reboot to 'Recovery mode'

4. Install/flash the 'Radio' zip file.

5. Reboot to 'Recovery mode'

6. 'Factory Reset' the phone.

7. Install/flash the 'eng spl' zip file.

8. Reboot to 'Recovery mode'

9. 'Factory Reset' the phone.

10. Install/flash the 'ROM' zip file.

11. Reboot the phone and continue to 'Phone setup'

12. Enjoy.

Now the problem I have is trying to find the CORRECT and LATEST compatible versions of the 3 files (Radio, SPL and ROM). I already have the 'MLIGN 3.3 Hero ROM' which I think is compatible with my phone but I don't know which 'Radio' and 'SPL' to use or where to find them, as when I search for them I get so many results which often do not have any links to the files.

I would really really be grateful if anyone (especially if you have the same version phone and ROM) could reply with the links to the relevant files (Radio, SPL and ROM) which I am seeking and let me know if the install procedure I mentioned above is correct (and if I need to partition my SD card).

Many thanks in advance. :confused:
[Droid Eris Android Development] jcase:
Do not install the new update, if you have or can get the link to it please provide it so we can take it apart. If you did install it, please try the root trick and let us know if it works.
[Droid Eris Android Development] tbonepitt:
Re: URL for OTA

8e3b63f96149.OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip

I couldn't get any of the URL's to work...

android.clients.google.com/updates/partner/8e3b63f96149.OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip

and

android.clients.google.com/updates/partner/OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip

they both didn't work
[Droid Eris Android Development] Stonent:
I wonder if google is checking the user agent? Or if not that, maybe just making sure the IP is coming from Verizon. Remember someone noted this will not work over WIFI, so I would try the URLs within the Eris's browser with wifi off if that is the case.

If you're using your home internet connection, it won't show up to google as Verizon wireless.
[Droid Eris Android Development] tbonepitt:
I just tried the URL's using 3G --- that didn't work either.
[Droid Eris Android Development] Stonent:
Well damn.

Ok I wonder if they are caching the zip on your sdcard. You could try running the freeware program called "Recuva" on it which will recover deleted files and see if the file is still there.

http://en.wikipedia.org/wiki/Recuva
[Droid Eris Android Development] bugger561:
I tried installing the update but there was some type of error in the recovery menu or something. These are the stats I have now

Software Information:

Firmware version

2.1

Baseband version

2.42.00.01.22

Kernal version

2.6.29

zanfur@gandalf #46

Build number

2.36.605.1 jcase release-keys

Software number

2.36.605.1

Browser version

WebKit 3.1

PRI version

2.11_002

PRL version

51866

ERI version

3
[Droid Eris Android Development] Stonent:
Probably explains it right there.
[Droid Eris Android Development] tbonepitt:
Software Info

Firmware 2.1

Baseband version 2.42.01.04.27

Kernel version 2.6.29-8a03cb9a htc-kernel@and18-2 #1

Build Number 2.37.605.4 CL185970 release-keys

Software number 2.37.605.4
[Droid Eris Android Development] thenestor:
Is it still in your cache?
[Droid Eris Android Development] gr8grumpy:
Here is a link that will work.

"https://android.clients.google.com/packages/desirec/OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip"

I can't post an actual link being a new user.
[Droid Eris Android Development] thenestor:
That works! Thank you!
[Droid Eris Android Development] Sjflowerhorn:
im pretty sure this is something i as a rooted user do not want to do however, are there any major bugfixes in this update?
[Droid Eris Android Development] Stonent:
This is the only thing in the patch script that makes me nervous.

assert(package_extract_file("recovery.img", "/tmp/recovery.img"),
write_raw_image("/tmp/recovery.img", "recovery"),
delete("/tmp/recovery.img"));
show_progress(0.016179, 1);
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "boot"),
delete("/tmp/boot.img"));
show_progress(0.016179, 1);
write_firmware_image("PACKAGE:radio.img", "radio");
[Droid Eris Android Development] t2noob:
I tried flashing on PlainJane which is the OTA update with a few changes and well it didn't work( On RA I modified the update script so it wouldn't flash recovery,boot,or radio and signed it give me an error and on the first assert). So I flashed the recovery that came with the update to see if it was the RA recovery giving problems and then tried to flash the OTA as is and still got the same error, so You probably have to be on a true no root, no nothing OTA for it to work. If anyone is willing to do it let me know so i can incorporate this OTA into PlainJane.
[Droid Eris Android Development] Stonent:
The radio should be safe. It's the other I'm worried about.
[Droid Eris Android Development] t2noob:
I wouldn't be to sure they can lock the nand with the radio if they wanted, doubt they would do it thought. but if you have 1.49200 the engineering hboot you're good because you can flash anything with that.
[Droid Eris Android Development] bftb0:
"OTA 2.1plus" 2010-07-17 System Image

Here is the fully patched /system partition image (yaffs2 format) for those of you that want to start using the patched files.

http://www.megaupload.com/?d=3UBCFTHP

(see below for MD5 and file size)

This system image was created by running the 2010-07-17 "OTA2.1plus" OTA update against a FR'ed Leak-V3 ROM on the Eris

1) Start with a rooted Eris w/ 1.49.2000 S-OFF bootloader and Amon_RA

2) Wipe /system and /data

3) Install (via unyaffs or flash_image) system.img, userdata.img, boot.img, recovery.img from (unpacked) Leak-V3 PB00IMG.ZIP

4) Boot phone and let it configure itself

5) Move OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip to SD card root folder and rename as "update.zip"

6) Perform FR of Eris

7) Reboot, skip activation calls, shutdown

8) Boot (Vol-Up+End) LV3 Recovery, and perform sdcard:update.zip update

9) Finish update, reboot, skip activation, shutdown

10) Re-install Amon_RA via fastboot

11) Make Nandroid Backup

For disambiguation purposes only, I renamed the resulting system.img file

63a06b50ca291e62a9a7f6c8761a5284 ota21+_system.img (172,675,008 bytes)

I could have culled only the patched files into a zip, which would have reduced the size considerably, but I'm still rebuilding my dev station, and don't have everything I needed set up yet.

bftb0

PS Yes, I suppose I have a new radio on my phone now. Que sera, sera, sera.

PS2 Now you can stop worrying :)
[Droid Eris Android Development] Stonent:
Well I'm saying I feel safe because I already have that radio. I've had it for a few months. It was extracted from the Sprint Hero.

BFTB0: FR?
[Droid Eris Android Development] n8thegr8:
Here's an edited update.zip i made. It patches everything and leaves the bootloader and recovery untouched.

http://www.multiupload.com/NUFVZNVDGD

I had to fix permissions on su afterward, but that's fairly easy with adb shell:

mount -o remount,rw -t yaffs2 /dev/mtd/mtd3 /system

chmod 06755 /system/bin/su

I TAKE NO RESPONSIBILITY IF YOUR PHONE GETS HOSED
[Droid Eris Android Development] bftb0:
FR Factory Reset

Probably not needed since I was starting from images in the leak-V3 PB00IMG.ZIP, but wanted folks to have confidence I was working with a "clean" /system

Hell, now that I think of it, a FR doesn't even touch the system partition - LOL.
[Droid Eris Android Development] amoeller:
I just did the update and everything seems to be working. I'm using my own ROM Official Obsession. I flashed the update.zip 1st then reflashed the root files (su and superuser) and then reflashed my overclocking kernel. The update.zip made me reboot into a recovery flasher to flash the radio. My service is noticeably stronger now.

My info is now:

Firmware version
2.1

Baseband version
2.42.01.04.27

Kernel version
2.6.29
zanfur@gandalf #46

Build number
2.37.605.4 CL185970 release-keys

Software number
2.37.605.4

Browser version
WebKit 3.1

PRI Version
2.11_002

PRL Version
5120

ERI Version
5

Oh and thanks for the update n8thegr8!
[Droid Eris Android Development] kzoodroid:
I just installed this update with no problems. I have a rooted ruu (leak 1.49 s-on) phone, no custom rom installed just rooted and overclocked with setCPU. I used ROM Manager to boot into recovery then used Clockwork Mod Recovery to apply update from sdcard. After reboot I ran the commands to reset su permissions and was back in. Didn't have to re-flash the overclock kernel again as setCPU just worked without flashing it.

Thanks to everyone who worked on this.

My Code:

Firmware version

2.1

Baseband version

2.42.01.04.27

Kernel version

2.6.29

zanfur@gandalf #46

Build number

2.37.605.4 CL185970 release-keys

Software number

2.37.605.4

Browser version

WebKit 3.1

PRI Version

2.11_002

PRL Version

65144

ERI Version

5