yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] --Rob--:
*up*

Is there an option/methode to set the minimum voltage of the battery to a specific level? A shutdown at 3.5V is too high. An Lipo can be discharged to 3.1 or 3.0V without hamring it...
[Android Q&A, Help & Troubleshooting] gomme600:
I was just wondering the same for the ultimate battery saving app !!! :confused:
[Android Q&A, Help & Troubleshooting] xjack03:
Have you find out something? I have tested my old battery and found out, that after my phone shuts down, there is almost 800mAh in battery left. Battery capacity 2400mAh. My phone uses only aboout 1000mAh of 2400mAh capacity :/
[Android Q&A, Help & Troubleshooting] timjosten:
For the whole Android history (9 years) this has never been investigated. That's silly!! No one even knows whether it's hardcoded in the kernel or in the ROM itself. This is astounding! The battery is the second important thing after the CPU in mobile devices. It should be examined far and wide.
[Android Q&A, Help & Troubleshooting] lucasfxd:
aaaaaaaaaah..... nothing about this yet? my phone is dying at 30%... with a lot of charge, since I changed the ROM............
[General Questions and Answers] shashidhar125:
When i hit back button in the android market app,it doesnt show the latest app i have seen. I shows the first app in the list. It's troublesome to navigate in the market.
[Android Q&A, Help & Troubleshooting] AliensDroid:
how to use tools ported in dsixda kitchen?

I plan to ported rom cyanogenmod 7 hero to my x8 devices

anyone can help?
[Android Q&A, Help & Troubleshooting] grayn0de:
I haven't messed with the porting tools in dsixda's kitchen, yet, but I am pretty sure the best way to port CyanogenMod to an unsupported device is by forking the master and implementing the drivers and build scripts for the device in question. You will have to modify a lot of source code to get any bugs ironed out and get the kernel configured properly for your device. After that, you'd compile from source.

My want to check in the CyanogenMod forums for some advice, as well. Also, the CyanogenMod wiki has a LOT of information on the project and how to build kernel ports.
[Android Q&A, Help & Troubleshooting] droople:
Hi

I bought an android tablet which has around 12GB available internal storage and a 16GB class 4 micro-sd card.

I'm planning to install apps and put some music/video/map data into my tablet.

How would you suggest me to arrange the space?

All apps to internal-sd and others to external-sd?

How about gps map data internal or external?

Best regards
[Android Q&A, Help & Troubleshooting] Ratlegion:
If I were you, I'd just put all the music and video on the external and everything else on the inside.
[Android Q&A, Help & Troubleshooting] droople:
ok, thanks a lot
[Samsung Galaxy Nexus] nyijedi:
Does anyone else's power button feel a little different than the volume rocker? It's perfectly responsive, but it feels a little less "clicky" than the volume rocker. It seems to be a little more recessed. It's not a problem, I'm just wondering if everyone else's feels this way.
[Samsung Galaxy Nexus] Luxferro:
Yeah, mines the same way. That's probably how it was designed. The power button is most likely recessed to keep from waking the screen by accident - in pockets, ect.
[Samsung Galaxy Nexus] nyijedi:
Cool. Thanks a lot for the response. I just wanted to make sure I didn't have some type of latent defect that could cause problems down the road, especially with such an annoying warranty process.
[Samsung Galaxy Nexus] king23adrianc:
Yes I feel the same too. Hope it last long though =\
[Samsung Galaxy Nexus] IvanDobskey:
Yeh, was wondering the same here. It works fine, just feels a little squishy and not as tactile as the volume rocker.
[Samsung Galaxy Tab Plus] rEVOLVE:
Wifi connectivity seems to not recover well when waking the device. In fact, i have to keep it from going to sleep when it's mounted on my dash in the car so i don't lose the wifi link from either my RAZR or MiFi while driving. i have WiFi sleep policy set to never and it still does it.

In regards to Bluetooth it's much better than my original Galaxy Tab, where when i tried to do music via BT to the car's stereo (BT FIPO adapter to 30-pin ipod dock adapter on car's cd changer input), plus connection to an OBDII Bluetooth adapter (Torque app) - it would have frequent stutters.

With this 7 Plus, i can be SIMULTANEOUSLY connected to both BT devices and switch between Spotify, Mortplayer, Navigation, Torque w/ no stuttering or lag. Also nice that now my car's steering wheel controls actually work better going through the BT on the FIPO to the ipod adapter (only track next/last toggle).

I wish Navigon and CoPilot didn't crash/lag so much, though.

Also the Stowaway folding bluetooth keyboard i used to use with my old UMPCs works well with this tablet.
[Samsung Galaxy Tab Plus] jsapp:
My wifi would disconnect constantly when I was in a different room than the router. I used a wifi analyzer to view the channels and had the router use a channel that wasn't as busy. Works a lot better now. But I had no issues before hand with any other device.
[Samsung Galaxy Tab Plus] LBJM:
I've turned off the power save due to the Linux kernel bug and dealing with the sleep of death bug. Helps wifi too you might want to try it out.
[Android Q&A, Help & Troubleshooting] corybucher:
Need help deciding what to do. Have the epic now but the radio on it isn't very good so was considering switching to the photon.
[Samsung Galaxy Nexus] Chirality:
For those interested, android-4.0.1_r1.2 was just pushed to the AOSP repo, containing the ITL41F kernel with the volume fix. Here's what they changed:

commit c45fce5d5ec098b3aaf6dbdde521e882037aff89
Author: Paul Eastham <eastham@google.com>
Date: Mon Nov 21 17:21:23 2011 -0800

New Prime prebuilt

a052f63 ARM: omap4: tuna: change key debounce time to 2ms
11e15a8 input: gpio_input: don't print debounce message unless flag is set

Change-Id: I2e01750eb70ab88c344d42ed840e7bf9ad3769c2

commit a00c7707709866a2ee4b87274734b8ec54eee936
Author: Paul Eastham <eastham@google.com>
Date: Mon Nov 21 13:33:16 2011 -0800

New kernel prebuilt

30b2a95 ARM: omap4: tuna: Add debounce time for power and volume keys

Change-Id: Ia484eb2f4808dc30b9b84afd6380cad3cd875daa
[Samsung Galaxy Nexus] cellzealot:
Looks like somebody goofed...that means it was never there to begin with if I am reading that right.
[Samsung Galaxy Nexus] Chirality:
What's even worse is that they knew about it a while ago. These commits have been in the experimental kernel branch for a while, but were only merged into the release branch on the 21st.

commit a052f63ff9095b93f66486c4dce951588b684f26
Author: tyoony <tyoony.yoon@samsung.com>
Date: Thu Nov 10 23:14:26 2011 -0800

ARM: omap4: tuna: change key debounce time to 2ms

Change-Id: Id22f726d7b74182663b0ca81bef1696f972bde2a
Signed-off-by: tyoony <tyoony.yoon@samsung.com>

commit 11e15a879dd5a176b469206a84193d6ecef8453d
Author: Dima Zavin <dima@android.com>
Date: Tue Nov 8 13:03:11 2011 -0800

input: gpio_input: don't print debounce message unless flag is set

Change-Id: I29ccb32e795c5c3e4c51c3d3a209f5b55dfd7d94
Signed-off-by: Dima Zavin <dima@android.com>

commit 30b2a956b35c24060466af687437af3b01997d15
Author: tyoony <tyoony.yoon@samsung.com>
Date: Fri Nov 4 03:05:05 2011 -0700

ARM: omap4: tuna: Add debounce time for power and volume keys

Change-Id: I8c7cd2e8c2f406e020e5c503c04ec21ff17befb1
Signed-off-by: tyoony <tyoony.yoon@samsung.com>
[Samsung Galaxy Nexus] Chirality:
Here's all the relevant code that was changed to fix the bug:

diff --git a/arch/arm/mach-omap2/board-tuna-input.c b/arch/arm/mach-omap2/board-tuna-input.c
index 1162207..febeb88 100644
--- a/arch/arm/mach-omap2/board-tuna-input.c
+++ b/arch/arm/mach-omap2/board-tuna-input.c
@@ -49,6 +49,7 @@ static struct gpio_event_input_info tuna_gpio_keypad_keys_info_high = {
.keymap = tuna_gpio_keypad_keys_map_high,
.keymap_size = ARRAY_SIZE(tuna_gpio_keypad_keys_map_high),
.flags = GPIOEDF_ACTIVE_HIGH,
+ .debounce_time.tv64 = 2 * NSEC_PER_MSEC,
};

static struct gpio_event_direct_entry tuna_gpio_keypad_keys_map_low[] = {
@@ -68,6 +69,7 @@ static struct gpio_event_input_info tuna_gpio_keypad_keys_info_low = {
.type = EV_KEY,
.keymap = tuna_gpio_keypad_keys_map_low,
.keymap_size = ARRAY_SIZE(tuna_gpio_keypad_keys_map_low),
+ .debounce_time.tv64 = 2 * NSEC_PER_MSEC,
};
[Samsung Galaxy Nexus] Luxferro:
How much can you really blame google though? Are they the ones testing the phone in all the different markets, or is it the manufacturer that should have caught it? I suppose if they had contract with carriers in those regions (like they do with verizon here), they would have found the problem too.

Just playing devils advocate :p
[Samsung Galaxy Nexus] Chirality:
Samsung did catch it, but it was a bit late. The two commits from Samsung that fixed it came on Nov 4th and 10th, but it was too late to make it into the release. I guess it's not really anybody's fault, and it was resolved not too terribly.
[Samsung Galaxy Nexus] Luxferro:
Yeah, I agree.
[Samsung Galaxy Nexus] kam187:
Wow thats interesting. De-bounce time is how long you wait to check if the key is really pressed. Eg if the IO is seen as closed, it waits 2ms and checks if its still closed, if yes, the button was really pressed, if not, then it was interference.

I guess with zero de-bounce any tiny level of interference could cause a false reading due to induction in the IO stage.

I'm pretty surprised someone 'forgot' to use debounce, maybe they thought they were scmitt triggers or some other threshold circuits and that was enough.

I think the fault clearly lies with whoever designed the hardware and the driver that monitors the IOs.
[Samsung Galaxy Nexus] Shodney:
I don't know about it being resolved 'not too terribly'.

When you look at the timeline of events, it took anybody (Google or Samsung) 4 or 5 days to even make a statement on the matter after it was noticed by users - and only after all the major blogs picked it up. It could also be argued that the statement they gave was somewhat lacking in details.

Samsung were allegedly deleting posts about the issue from their Facebook page.

The issue tracker page at Google still hasn't had an official response posted on it.

There was a lot of uncertainty from retailers, who stated that shipments had to be held because Samsung were fixing the handsets before sending them out. People waited a week or more, only to eventually receive the handset without the fix as promised.

There are people (me included - hence the small rant :D) who have had their handset from day one, having to put up with the problem every day, who still haven't had the OTA due to them rolling out the fix slowly. I can't understand such a slow roll-out for a critical bug fix?

And that's all before you get to the point that, judging by the dates, they knew all about this before the phone launched. As a result, it appears that they have knowingly released a product on sale that is faulty and not fit for purpose.

So my argument is that it hasn't been well handled at all. The majority of press we have seen about the Nexus so far has been negative, focusing on the launch delays and this bug.

Not a good launch, imo :)
[Samsung Galaxy Nexus] matt2053:
You know you can download the patch any time you want, right?
[Samsung Galaxy Nexus] Shodney:
You know I don't want to unlock the bootloader and wipe my phone, right?
[Samsung Galaxy Nexus] vADimko:
can anybody confirm rising of cpu load with this fix when it works? i mean when you put near another phone with 2g mode?
[Samsung Galaxy Nexus] flyerwire:
Why would you need to do that? Can't you just put the update.zip on your phone and apply like you used to be able to?
[Samsung Galaxy Nexus] bongadadu:
I'd like to know this as well. Does the CPU still get busy when trying to replicate the volume bug ?
[Samsung Galaxy Nexus] Shodney:
People in the other thread are reporting that this doesn't work unfortunately :(
[Samsung Galaxy Nexus] oscillik:
This does not work.
[Samsung Galaxy Nexus] omrij:
Google's images are signed, right?

Can be flashed without unlocking bootloader?
[Samsung Galaxy Nexus] oscillik:
No, the only way you can flash manually is by unlocking the bootloader.
[Samsung Galaxy Nexus] omrij:
are you sure?

i'm talking about this images

http://code.google.com/android/nexus/images.html
[Samsung Galaxy Nexus] cellzealot:
The issue is that the new recovery is setup to load signed files from the /cache directory only and not from /sdcard directory. The /cache directory is only available via root access, so unrooted users cannot manually put the file in the right place for the stock recovery to load it. The updates download to that directory by default for a normal OTA and then /cache is wiped after the installation, removing the update itself from the device.

Edt: Just checked that link. Those are new complete fastboot images so that still leaves unrooted users out in the cold because you need to be factory OEM unlocked to flash the images in fastboot.

Bottom line is, if you want to manage your device yourself you need to be rooted to have the level of control required for success.
[Samsung Galaxy Nexus] omrij:
i'm not talking about the OTA update (zip file)

i'm talking about the factory images
[Samsung Galaxy Nexus] oscillik:
Yes I'm sure. I actually own the phone. I have it in front of me. You need to have the bootloader unlocked to flash those images also.
[Samsung Galaxy Nexus] omrij:
I also have the phone in front of me

I just find it a bit odd that official images wouldn't be signed.
[Samsung Galaxy Nexus] cellzealot:
As I explained in my edited post...yes you still need to factory OEM unlock the phone at least long enough to fastboot these images, which will involve wiping the phone.

Personally, I see this as a trivial matter, but I understand why some may not see it that way. I wouldn't own a phone myself that I couldn't root and use a custom recovery to manage the device on my own.
[Samsung Galaxy Nexus] oscillik:
Yeah I agree. I'm just putting that guy straight when he keeps saying "are you sure?", after quite a few of us have tried and proven that it doesn't work.

---------- Post added at 05:22 PM ---------- Previous post was at 05:21 PM ----------

Yes. We all find it a bit odd that you cannot do this without unlocking the bootloader. But that doesn't change the fact that you cannot do it without unlocking the bootloader.
[Samsung Galaxy Nexus] omrij:
Well, you have a history of being wrong :)

(and to be an asshole)

I didn't see anyone on the forum who tried to flash this images on a locked bootloader

all the discussions were about the update zip
[Samsung Galaxy Nexus] oscillik:
Pot. Kettle. Black.
[Samsung Galaxy Nexus] Tjotte:
Maby google did not sign it yet to guinny-pig the root users and see what this update does before pushing it to the masses.
[Samsung Galaxy Nexus] cellzealot:
I think we would all fare better here getting the right information distributed if we cut the interpersonal crap and all try to behave a bit more cordially and avoid the bickering.

Thanks!
[Samsung Galaxy Nexus] oscillik:
I agree. Maybe the guy starting it off should bow out?
[Samsung Galaxy Nexus] cellzealot:
Moving on...my partner has suggested that there is a way to create a file that can be flashed with ODIN that bypasses the security check on the boot.img such that unrooted users could flash the full images.

We have all the required components to do this with the LTE version because we have a full ODIN to start from. Unfortunately, right now we do NOT have all the pieces for a Maguro compatible GSM version.

We will see what we can come up with regarding a possible solution.
[Samsung Galaxy Nexus] Chirality:
It shouldn't happen. This fix is very low level. The kernel now instructs the GPIO controller to debounce at a 2ms interval. This should prevent the spurious IO events from generating an interrupt, so the CPU won't even notice.

That said, it would still be nice if someone could verify this experimentally.
[Samsung Galaxy Nexus] oscillik:
That sounds awesome :beer:
[Samsung Galaxy Nexus] coolbho3000:
I told people in the other thread that all that was needed was a little debouncing, and I was right :p
[Samsung Galaxy Nexus] The Gingerbread Man:
I think Google are watching and saw your post knowing us here on xda would flash new updates straight away. Lucky for them you were right :D
[Samsung Galaxy Nexus] cellzealot:
I think Google and Samsung have been likely doing a lot of bitter squabbling over who is responsible for this "oversight" and who will take the PR hit for it.

When all of this first started to unfold, I spent several days trying to get verifiable information about it from my friend at Samsung, who knew nothing at all about it because he works with the CDMA/LTE models.

As I gave him more complete information about the nature of the problem, he said it all makes sense except for the fact that the type of testing that would have revealed this issue in the normal course of development is fundamental and he said this was a very bad and very stupid mistake on their part not to have included 900mhz EMI as a routine protocol for the UK/global model.

This entire affair has been very costly without question, despite the fact that a simple software fix is all that was required to fix the problem, and I firmly believe a good part of the delay in distributing the fix has been the result of the internal corporate wrangling over it.
[AT&T Samsung Galaxy S II SGH-I777] glad4pie:
Just a question, i am planning to order this SGP linear color or pure case . Would you guys recommend yellow linear color or the green linear pure one
[AT&T Samsung Galaxy S II SGH-I777] defnow:
You're asking what color somebody would want for YOUR phone? Lol....whatever makes YOU happy...pick that one.
[HTC Rezound] foister82:
Does anyone else's deep sleep not working? I think that might be why my battery only lasts 4-5hours with little use

http://touch.lockerz.com/s/161548382

Sent from a can on a string using XDA app.
[HTC Rezound] con247:
Possibly. Have you tried a factory reset with the RUU to see if it is software issue?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] scoot05redss:
So last night I noticed on the AT&T Premier site the Otter Box commuter case no longer said out of stock. So I went ahead added it to my cart and completed my order! Got the confirmation email and tracking number today! It's due to be here Monday! On the Otter Box site it's still not available. So if anyone has been waiting on an email notifying them that they are ready, just log onto AT&T's accessories site and it should be there. The only one available was the Blue/Black color but the Blue is dark and doesn't look half bad in the pictures. I'll update the post with pictures as soon as it gets here!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] LordGeek:
I already got mine .. ordered it from my local AT&T store, only difference is, you paid $40 for it .. I paid $34, I complained that the AT&T version was more than Otterbox sells for and also removes the included screen protector that comes with the official Otterbox version.

So .. $34 with free shipping, I got it 2 days later via FedEx .. excellent case, I got the Black Plastic / Night Blue Slip Cover version.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] scoot05redss:
Awesome that you got yours already, but WRONG on the price fella! I have a corporate account and only paid $24 bucks for mine! I can't wait til it comes in! How easily does it slide in and out of your pocket?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jayrod88:
Can you post pics of the case with the phone? I've been waiting for this case. Just not sure on the color.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] scoot05redss:
If he doesn't, I'll be posting pics as soon as I get it in on Monday!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] superfire71:
I actually have the commuter Otter box, picked it up last Thursday. Its also the blue/black one. Dunno what's up with this blue/black - why? Why not just offer black/black? Prolly returning it. I will say it provides robust protection for your skyrocket. If you happen to have slippery fingers, this should keep it safe and sound so long as the screen doesn't get struck directly. Here's a link to some pictures (they stink but i tried).

http://db.tt/0Ft9uXhy
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] dverse:
what am i missing here? STILL shows as 'coming soon'
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] alexninjam2:
Just got myself this otter case..

I like a lot....

View attachment 806734

View attachment 806735

View attachment 806736

View attachment 806737
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] scoot05redss:
That's the Defender, we are talking about the Commuter case, but it does look like it really protects the precious Skyrocket! Here's a few pics of the Commuter I got in today! The Flash makes the blue WAYYY brighter then it actually is! Very tight fit!! Kind of a pain to get it off if you need to remove the battery or SD card!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] scoot05redss:
This are from the AT&T site or a AT&T store, Otter Box"s site still says Coming Soon!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] offwiththeface:
Do you think this is way better than the sgp Neo hybrid
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] scoot05redss:
I've never used or saw that case in person . The case I was using before i'll post a picture of, was good. But this fits alot better. With the previous case I was getting creaking when holding the phone for phone calls. Hope someone with that case can chime in!

View attachment 807206

View attachment 807207

Sent from my Samsung Galaxy S II Skyrocket!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] androidpixar:
Is it flushed at the back? And can you take a pic with the case on its side, with the SR beside it? I would like to see the difference in thickness, when they are next to each other.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Mocaris:
Got the commuter today also. But having a issue with the silicone ending before the plastic on the back. Which is giving me camera flash issues. Besides that its a nice case.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jayrod88:
Can you post a picture of this fitment issue?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Mocaris:
This is it, maybe just got a bad case. Pretty sure the silicone should not end before the plastic.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jayrod88:
Have you tried to contact customer.service@otterbox.com? They have excellent customer service.

BTW, can someone in an LTE area go to www.otterbox.com and see if it actually shows their website? I get a weird website without photos on LTE and wifi. Not sure if its because of ad blocking or what. I'm in a rooted stock 2.3.6 rom.

-sent from my Samsung Galaxy S2 Skyrocket
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] 3inst3in:
I picked up a Defender case from AT&T two nights ago and the silicone wouldn't fit completely around the hard plastic inside case. AT&T had no more to exchange for, so I called Otterbox but they said they can't warranty it as they don't officially sell it yet, so I had to return it.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jslanger:
They JUST put them up on the Otterbox website. Too bad you returned it already...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] niezek:
Anyone else find that you have to press kinda hard for the volume and power keys to work?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] warlord420:
I got the defender series from amazon for 56 bucks for 2 day shipping.

this phone is tin, and i would HATE to break it. i figured what the hell add some weigtht to it and protect from top to bottom

:D

otto seems to make decent quality products
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] eshewski:
Yea I have noticed that you have press hard too. It's gotten just a little better the past few days but not enough to my liking.