yashsingh1/xdaforums huggingface dataset:
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] deadeyed:
THX!!

Seem to be working on my machine... well I need to test a bit longer though.

THX!!
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] dodos_4:
i think the problem is back it remained for 3-4 rings until the jabra is starting to ring with my pda2k
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] kevinnugent:
Hi folks

I got a new BT headset tonight, and it's very scratchy on 3500 of BT. I can't seem to download 3900 though.

Could someone please email me a copy of BA_Bluetooth_1.0.0.3900_Upgrade

So I can try and use my new headset! :)

My email addy is ktnugent at iprimus.com.au

Thanks guys!

Kevin
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] dling1971:
on it's way 8)
[Nook HD, HD+ Android Development] verygreen:
There were some requests into forcing the charger controller in the Nooks to allow higher rate charging from non-B&N chargers, I also was constantly annoyed by how my Nooks are always discharging when plugged into my computer with screen on because of only drawing about 500mA, where as the ports would happily provide 1A (development led by Apple).

The work here is experimental and if you decide to try anything, you bear the risk of stuff frying and catching on fire (granted, I did not burn anything here yet, but who knows, this is electricity we deal with here).

The "TRM" is here for anybody interested, sadly it does not match with what the hardware actually does in some important areas (also reflected in the driver comments). It looks like there is no real way to control the charging rate much, as soon as you write into draw rate register, it's two lowest bits are reset to 0 until D+/D- detection is performed, but then the detection resets draw rate back to appropriate defaults, huh? So this leaves us with two settints: 100mA or 1.2A

Plus there's something else going on, e.g. all of my iPhone chargers that I happen to have around only provide about 1.5 Watts of power and the controller refuses to draw more than 500mA from it anyway. All the Android stuff chargers I have on the other hand work out of the box and allow Nook to draw about 1.2A from them (even the native charger does not seem to draw more than this, about 7.5W according to my Kill-a-Watt display and also according to the battery current rate reported by the battery).

Anyway, I am providing two kernels, kernel for Nook HD+ and kernel for Nook HD

Flash the appropriate one for your device.

Then there's the control app: NookChargerControl.apk

Run the app, and it will present you with the main switch at the top (ignore the second switch, it's from the earlier experimentation and currently does not do anything).

If you flip the switch on, the charging is forced at 1.2A rate, no matter where you are connected (but see my earlier note about my iPhone chargers).

In addition to whatever physical measurements you are making, thee are two clues displayed about stuff:

The registers 00 and 08. When register 00 is 0x34 - that's indication of 1.2A, 0x32 = 0.5A, 0x30 = 0.1A, 0x37 should be 3A (When connected to power).

Also a battery-reported current is shown, this is your main clue about how much power does the battery really gets, negative values = discharging.

Tap anywhere on the screen to refresh the values, the battery rate reported sometimes takes several seconds to update, so do not panic if the values appear to be stuck for some time.

If you decide to try this, please report back in the thread with your findings.

In my testing, enabling the switch (while plugged into a computer) results in as much battery charging current as I am getting from B&N charger.
[Nook HD, HD+ Android Development] dbrickg:
Flashed new kernel and installed charger app. When I first turned on the charger app, I'm pretty sure it said "Reg00: 0x37". After turning on the "Force USB charger mode", Reg00 went to 0x34, and stays there whether I turn USB charger mode off or on. The "Battery current" started at 476000 and is now at 358000, but I'm pretty sure that's because it was already almost completely charged, and now it says it's at 100%, though the LED is still orange. All of these measurements are on the Nook charger. Haven't tried anything else yet.
[Nook HD, HD+ Android Development] verygreen:
Thanks.

Using nook charger with this app is pointless, as it's already working (as are a bunch of other chargers from android devices).

So I guess it's being targeted at people who want to draw more power from their host computer or with incompatible chargers.
[Nook HD, HD+ Android Development] paaco:
Tried with a 1amp Samsung charger. It Is showing 1092000 on an HD+

Force power 2

Reg 00 0x34

Reg 08 0xac
[Nook HD, HD+ Android Development] loverppc:
is this for cm10.1 or nook original os or both of them?
[Nook HD, HD+ Android Development] dbrickg:
Now if you could just write a kernel to make the nook compatible with normal USB cables... heh.
[Nook HD, HD+ Android Development] verygreen:
That's just for CM10.1
[Nook HD, HD+ Android Development] dbrickg:
I wasn't sure if the Reg00 was originally 0x37 or not, so I reinstalled everything, and yes, it was. And for a better benchmark, when I first started charging it, with the battery at about 70%, using the nook charger, the "Battery current" was around 1670000.
[Nook HD, HD+ Android Development] paaco:
Tried with this charger and neither port seems to work. Shows right around 0 for the charge amount on both ports so no charge or discharge. http://www.amazon.com/gp/product/B0088U4YAG/ref=oh_details_o00_s00_i00?ie=UTF8&psc=1

On my nexus 4 and 7 it shows USB charging from apple port and ac from the other.

Also shows this for both ports

Reg00 0x32

Reg08 0x4c

Hope this info is useful.
[Nook HD, HD+ Android Development] verygreen:
0x32 is 500mAh, so it tries to draw this much, but if charge current in the battery is 0, that means there's not enough power left after what's used by tablet itself with screen on.

I have this problem with my iPhone chargers, not sure how the charger controller differentiates.

Big win for me is with a computer port, where with the app and a new kernel I can draw much more current and keep battery charging even with the screen on
[Nook HD, HD+ Android Development] paaco:
Ahh, I got you. It is nice having it charge from computer. Didn't know if your ultimate goal was to get it to work with as many chargers as possible so was trying to give you more info.

Either way, thanks for all the work you are doing and sharing to make our Nooks more enjoyable.
[Nook HD, HD+ Android Development] verygreen:
Yes, that was the original goal, but sadly doc does not match with the controller behavior, so current state is the best I could achieve at the moment.
[Nook HD, HD+ Android Development] Classpro:
Verygreen: I'm having a really hard time understanding what's happening with Nook charging.

When I plug into the original nook charger (and SOME other charges), the little light is YELLOW and the lightening bolt shows up in Android to indicate it's charging. However, it clearly charges slower in my portable charger (Monster cable charger) than with the nook charger.

It I plug it into apple compatible chargers (including my battery) the little light is GREEN rather than yellow. This is true even if I plug the nook cable into one of these a shorted cable (which will cause my Nexus 7 to go into high power charging mode).

http://www.ebay.com/itm/POWER-ONLY-...67?pt=Camera_Cables_Cords&hash=item58944a169b

Your system has two switches. "Force USB Charger Mode" and "Force 1A when charging". Your notes say ignore the Force 1A (second button)? I can't tell if the force usb charger mode does anything when the light is green. I get various numbers for battery current (seem to be all over the map)

In the monster charger, I get similar numbers whether Force USB is on or off, 100,000 - 200,000 current. I can't tell if it's better or not with Force USB on or off.

In the nook charger, I get around 700,000 current.

So it doesn't appear to be going into high power mode with Force USB in the Monster charger (which supports 1.5 amps).

In a windows usb port I get the green light and low charging current whether I enable or disable FORCE USB.

So, I'm confused.
[Nook HD, HD+ Android Development] Stevethegreat:
I don't know if it's connected but it is certainly a battery issue which only presents itself on CM10.1 ... I mean I had it before in both stock and other roms but not nearly to that extend. Basically the rom seems to lose battery very fast and when it reaches 0% it simply switches off. If I boot at stock I can see I have around 40% left.

In other words battery is seriously misrepresented on CM and CM alone, other roms have nowhere near this kind of problem and every time I switch to them most of my battery issues solve themselves. It practically halves the battery life of the device for no good reason (ill-reporting). So VG, I guess it's better if you can take a look at it, it's something that I have seen reported by other people too, but it's quite of a hardle.

Your rom (CM) is basically the most complete but I always have to go elsewhere in search of/for battery life. It's the last big thing that needs to be solved and I think we're set. And -no- callibration never helps, it's not 100% that is misrepresented but 0%...

Thanks for your attention.
[Nook HD, HD+ Android Development] verygreen:
I am not sure what do you mean by "other ROMs", there are only two roms out there, this and B&N stock. Everything else is based on one of the two kernels and userspaces (or sometimes combinations of thereof).

Also, is there a point in time you can think of when this problem started if it did not happen from the get go? Did 6/24 and prior exhibit premature empty battery detection?

I do not drain battery on my nooks as it takes too long and means I cannot do anything to them in the meanwhile.
[Nook HD, HD+ Android Development] Stevethegreat:
By other ROMs I mean SGT7, Carbon and stock. Using any of the three I have misrepresentation of battery life for anything below 15%, on CM I have misrepresentation all the time. It always existed as a problem but not in this level, it only became worse with the latest builds. Maybe it's hardware issue but why is it made whose by CM, basically that's what I'm asking...

I know without logs I'm not much help but for the time being I have reverted to carbon and all is well. In a few days I will retry CM and have my logs sent then. What I can safely say by looking at other people's battery graphs is that it happens to others too' maybe not as dramatically (for someone it went from 50% to 30% in one instant), but it is there...

I'm on HD+ BTW
[Nook HD, HD+ Android Development] LucaToo:
UK Car Charger

Being unable to source a B&N car Charger in the UK - I am assuming that this mod allows me to charge from any 1 or 2 amp car charger..?

Also does it only work with CM10.0 as I am currently running CarbonROM - mainly for the improved PIE controls on Expaned screen mode..?
[Nook HD, HD+ Android Development] verygreen:
I cannot promise "any".

I found that apple (and apple-devices targeting) charges generally don't work.

On the other hand chargers that target android devices seem to be working all by themselves without any tweak. My sample size is not too big, though.

depend on if the kernel support for it was added.
[Nook HD, HD+ Android Development] LucaToo:
UK Car Charger

Sorry to be a pain but do you have any specific make/model car chargers that you could recommend (as most seem to be labelled as 'universal' regardless of whether they are intended for iPhone or Android)..?

Would an HTC or Samsung branded charger work for example..?
[Nook HD, HD+ Android Development] verygreen:
I don't have any experience with car chargers.

There's a high chance Samsung charger will work, I think.
[Nook HD, HD+ Android Development] mvsroot:
Turn charging completely off

Is it possible to turn off the charging while transfering data between the Nook and a PC?

Thanks
[Nook HD, HD+ Android Development] verygreen:
That would need some more code.

Whats' the usecase, though?
[Nook HD, HD+ Android Development] starbright_:
Very useful to charge it with higher rate when connected to PC.

However - can this kernel change you mentioned be part of "standard" kernel? With this it is just the app you need and no problem with automatic nightly updates ...

To speak frankly, I didn't test it until now, but would it be good to provide the app with a few buttons with different charge rates (500mA, 1 A, 1.25 .. 1.5) so that user has the choice to select that best matching rate for the charger? (I hope I didn't misunderstand the feature of setting the rate by register values).
[Nook HD, HD+ Android Development] mvsroot:
A rechargeable battery has a limited quantity of charge cycles. I don't want to waste them during USB file transfers.
[Nook HD, HD+ Android Development] verygreen:
It is part of standard kernel now, so if you use CM nightlies or any of my recent binary drops, it's already in and you just need to install the app.

Sadly there's no real choice available here from the controller

If we do manual control, we can do 100mA or ~1.2A only (and even then some chargers like those targeting iDevices are somehow rejected from any high rate charging access in hardware).

Then if there's autodetecting, then it's again 500mA or ~1.5A (also iDevices targeting charges are discriminated against and they certainly are not utilized even for 500mA for some reason).
[Nook HD, HD+ Android Development] verygreen:
I think only full cycles count, though? As in from (almost) zero to full. I.e. if you top off a couple of percents here and there, that's not really a full circle.
[Nook HD, HD+ Android Development] mvsroot:
OK, but I also don't want to charge my battery from my laptop if I am running on battery.
[Nook HD, HD+ Android Development] starbright_:
From my experience the charge current (without any app, so just per default), is so small, that even Android isn't change to charge mode.

What I found is, that I need (Nook in standby, so almost no consumption) a night to charge - so it can't be much.

Sure, if even this is to much, than you would need this feature (if this is possible).
[Nook HD, HD+ Android Development] kmika:
cm10.2 fstrim kernel

This is sounds good but I would need an fstrim enabled / charger tweaked kernel for CM10.2 nighlies. Is such a thing exists ?
[Nook HD, HD+ Android Development] verygreen:
yes, use the latest fstrim kernel posted in the cm-10.2 somewhere, it has both.
[Nook HD, HD+ Android Development] Tom2112:
Is there any chance you could update the app to include the above information on the screen? I can never remember what the register values equate to amperages.

Also, could you identify some kind of unit for the battery-reported current? Is that miliamperes/hour or what?
[Nook HD, HD+ Android Development] verygreen:
I guess it could be trivially added, though in reality there's this battery-reported current that is the important part and is accurate.

What good is a 1.5A value in the charger register if you can only draw 300mA anyway? ;)

Which is not to say I am not going to add it if I remember about it next time I look at these apps.
[Nook HD, HD+ Android Development] kmika:
I am using that but dosent work it shows only -80000 or so and discharging.
[Nook HD, HD+ Android Development] qingz:
I am on CM10.2RC2. Do I need to flash your Kernel to support it? I ask it because my 2A car charger does not charge my Nook HD+ no matter how I set the switch.
[Nook HD, HD+ Android Development] JDMpire:
I believe so. At least with mine, before I flashed the kernel I could not get it to charge. Flashing the kernel and rebooting / wiping the caches, that made it work.

Its still a little wonky from time to time, like I need to enable and disable the changing control app, plug - unplug- plug back in the cable..ect to get it to work. I don't find fault in the app or kernel, I belive were doing the best we can with the tools at our disposal. Were using this device in ways never meant from the factory. I am quite happy with how mine runs (Carbon Rom), you just need to be patient from time to time as its slow.
[Nook HD, HD+ Android Development] qingz:
I did the same. "Flashing the kernel and rebooting / wiping the caches". "enable and disable the changing control app, plug - unplug- plug back in the cable..ect". Still not work for me on CM10.1 RC2.

BTW, after I flashed the kernel, my wifi and bluetooth can not be turned on. Fortunately, I did a backup before flash. After restore, wifi and bluetooth work again.
[Nook HD, HD+ Android Development] jbbandos:
Any chance of incorporating the kernel changes in cm11? I have an external battery that provides a 1A and a 2.1A ports, but my Nook hd+ won't charge from any, and your app doesn't seem to make a difference in CM11.

I can always try to open the battery and modify / solder something, but I am not sure of the changes that need to be done.
[Nook HD, HD+ Android Development] tebra:
Already included in CM11 kernel.

I have CM11 on my HD+ and I can charge from computer USB port at 1.2A with the NookChargerControl.apk
[Nook HD, HD+ Android Development] jbbandos:
Ok, so there is something different in the battery. It has 2.1A and 1A ports, and the Nook won't charge from it.

I guess I'll have to try to open it and see what is(n't) connected in the USB ports.
[Nook HD, HD+ Android Development] Jon Lee:
Looks to me like the code that determines "cable" type and charging current comes from

/drivers/usb/otg/twl6030-usb.c

if ((charger_type == POWER_SUPPLY_TYPE_USB_CDP)
|| (charger_type == POWER_SUPPLY_TYPE_USB)) {
status = USB_EVENT_VBUS;
twl6030_status = USB_EVENT_VBUS;
twl->otg.default_a = false;
twl->asleep = 1;
twl->otg.state = OTG_STATE_B_IDLE;
twl->linkstat = status;
twl->otg.last_event = status;
} else if (charger_type == POWER_SUPPLY_TYPE_USB_DCP) {
regulator_disable(twl->usb3v3);
status = USB_EVENT_CHARGER;
twl6030_status = USB_EVENT_CHARGER;
twl->usb_cinlimit_mA = 2000;
twl->otg.state = OTG_STATE_B_IDLE;
twl->otg.last_event = status;
twl->linkstat = status;
twl->asleep = 1;
} else {
regulator_disable(twl->usb3v3);
status = USB_EVENT_NO_CONTACT;
twl6030_status = USB_EVENT_NO_CONTACT;
atomic_notifier_call_chain(&twl->otg.notifier,
status, twl->otg.gadget);
twl->asleep = 1;
goto vbus_notify;
}

You could probably make a few changes here to force charging on non-standard chargers.
[Nook HD, HD+ Android Development] dcahoe:
Are you running CM11 with ART or with Dalvik??

I downloaded NookChargerControl.apk and when I try to install it on my HD+ with CM11 and ART it gives a parse error (says 'there was a problem parsing the package.')
[Nook HD, HD+ Android Development] tebra:
I'm with Dalvik
[Nook HD, HD+ Android Development] ST Dog:
Any easy way to tell if a 10.1 kernel has the required changes?

I have the 30 Dec kernel from bokbokan on my HD, but th app doesn't work. Says "Cannot open charger control file"

Can I flash your 10.1 kernel on that setup?

What other differences would your kernel have?
[Nook HD, HD+ Android Development] ST Dog:
Well, flashed the kernel form the 1st post. No change. Still get the same error message.

Guess I'll have to move to CM10.2 or CM11 to get it working.
[Xperia Z Q&A, Help & Troubleshooting] DrKrFfXx:
So, this is more like a general Android question rather than a specific Xperia Z thing, but since I'm always lurking this forum, I think it will be best posted here:

I have a Xperia Z, obviously, and a Sony Walkman Z, which I carry around as my mp3 player. It has Android ICS.

The thing is that I want to control at least the media player options from the Walkman from my Xperia Z, kinda like the way the Smartwatch is used to control Xperia devices.

Is that even viable? Via bluetooth or something?
[Sony Xperia ZL] danieldp1990:
Hello i just wat to know wich firmware is the best and what are heir differences, wich is newest cons and pros i will thanks.

I have the Xperia ZL (C6502) - 10.1.1.A.1.253 - Generic US 1270-7577 R7A

but how about this? 4.1.2 - 10.1.A.1.434 - GLOBAL

4.1.2 - 10.1.A.1.395 - Generic US 1270-7577 R6A Part 1 Part 2

4.1.2 - 10.1.A.1.434 - Generic US 1270-7577 R6A - Download

4.1.2 - 10.1.A.1.434 - GLOBAL - Download

Xperia ZL (C6502) - 10.1.1.A.1.253 - Generic US 1270-7577 R7A - Download

:good:
[Sony Xperia ZL] enrique71:
Go with 10.1.1.A.1.253 .. it's newer than .434. There is no change to any icons, only some performance improvements.

Buena suerte :good:
[Sony Xperia ZL] danieldp1990:
but as i know all the firmware for ZL are JB 4.1.2 not ICS 4.0....

wich of this two 253 vs 307 its newer?
[Sony Xperia ZL] enrique71:
My bad, you are correct both are JB .. from the 4.1.2 loads, .253 is newer. After .253 you'll need to upgrade to 4.2.2
[Sony Xperia ZL] danieldp1990:
wich is newer the 307 vs 253?
[Sony Xperia ZL] enrique71:
correct, 307 is an OTA and is newer. It was certified but to my knowledge not widely deployed across all Sony Z variants.
[Sony Xperia ZL] stinky73:
Stick with .253 (rock steady and best version to date) and wait until 4.2.2 is superseded by something newer (whenever and whatever that might be :D) as it is buggy and unreliable in many android devices ;)
[Galaxy S III Q&A, Help & Troubleshooting] bitpie:
Hi. I never did a backup. Can someone link ( i cant find it ) or explain how to make backup to external card ? I want to root my brothers phone ( also i9300) and install new rom CM 10.1
[Galaxy S III Q&A, Help & Troubleshooting] Glebun:
Google "how to do a nandroid backup"
[Sprint HTC One (M7)] acme64:
I need the USB tethering drivers, im on a terrible connection right now and can't download the whole 100+ mb sync manager just for that. Anyone have a link?
[Sprint HTC One (M7)] jcwxguy:
http://www.mediafire.com/download/ze6jddmp60o86m9/HTCDriver_4.2.0.001.exe
[Optimus One, P500, V Q&A, Help & Troubleshooting] Newboy1610:
Need A stable ROM which supports bluetooth headset (Plantronics backbeat 903+ )??????
[Android General] shoote:
For those of you who remember, last year we published a patched firmware for Broadcom WiFi chipsets that allows Monitor Mode and Packet Injection.

Since most of you experienced some trouble during the kernel compilation...

We worked hard during the last months to bring an easy to use solution that won’t require kernel modifications.

The new solution is a normal android APK that you can try to install on your **ROOTED** device.

Currently tested on the following devices:

GS 1 - Cyanogen 7

GS 2 - Cyanogen 9 & 10

Nexus One - Cyanogen 7

Nexus 7 - Cyanogen 9

We are currently working on GS3&4 support (which have a different broadcom chipset), we will release it “when it’s done”.

As usual:

please note that this code is experimental and you use it at your own risk and we are not responsible nor liable for any damage or loss of data. Sometimes unexpected things might go wrong and you might end up with a device that is no longer functional. Be warned and please take the responsibility yourself--it is your own risk and no one else can be held responsible.

You can download the apk from our google code page:

https://code.google.com/p/bcmon/

(Direct link: https://bcmon.googlecode.com/files/bcmon.apk)

Our slides from RECon:

https://www.dropbox.com/sh/le8zeczpddf3nx0/fdXn4LSxGI

Video of the lecture:

<coming soon...>
[Android General] NEEDHELPFOREXTERNALWIFI:
Anything new?

Hello there, would be nice to hear something new from your project, or is the project officially down?
[Android General] Gaganpreet 07:
not working in micromax unite 2

Firmware not detected

What to do??
[Android General] insider123:
Bcmon error firmware not detected on micromax a120

Is there any possiblity of monitor mode on micromax a120 or mediatek device with someone other app.
[Nexus 4 Accessories] Diz:
hey i just found a guide on making a micro usb flash drive for smartphones/tablets

be sure to take a look, it quite impressive

http://www.overclock.net/t/1409373/...o-usb-flash-drive-for-phones-and-tablets/0_30

:D
[Nexus 4 Accessories] CLTatenza:
I'd love to be able to just buy one.