yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] eddyykamal:
same here, my aws radio is gone. My phone is rooted and I tried so many roms. Still am only connecting to rogers 2g network. Which is pointless because I can't make any calls. My only option is project sarah but I hate the on screen keyboard. There's just got to be a way to fix the radio on this thing...
[Android Q&A, Help & Troubleshooting] eddyykamal:
I just installed project sarah and the aws radio still doesn't work??? what gives? where can I find some roms for my aws? Also I experienced this right around the time I was experimenting with roms and I came across that kenya firmware.
[Android Q&A, Help & Troubleshooting] hallucinogenics:
you may freeze the android keyboard in titanium backup.
[LG Thrill 4G] DracoAzule:
I did this on my LG Thrill 4G. But it may work on other phones as well. I'm not saying I discovered this. Because I didn't. I'm just posting some simple instructions on how to do it, for those of you who may not know about it.

Basically we are going to modify your LCD density to give it a high resolution look and feel (notice how I said LOOK and FEEL...you can't transform a non HD screen into an HD screen). This will not only make everything look sharper, but also smaller. Meaning you can fit more material on your screen at once.

Requirements:

1. Rooted phone

2. Root explorer

3. The ability to mount your system folder as R/W

Reccomendations:

1. Backup

2. BACKUP

3. BACKUP!

Depending on what ROM you're using and what theme this may brick your phone. So BACKUP.

Make sure you can mount system as R/W and open up root explorer. Navigate to your system folder and then copy build.prop to either your internal or external SD card. Now connect your phone to your PC with USB and open build.prop in notepad. Find lcd_density, and change the number to the right of it. On the LG Thrill the number is 240, and I would recommend setting it to 200. I'm not sure what it's set as on other devices. But the lower the number, the smaller and sharper everything looks. The higher, the larger everything looks.

Now save it, go back to root explorer, set your system folder as R/W and then copy it back, overwriting the original.

Now reset your phone. If it worked, awesome. If not, then simply reflash the backup you made.

I've included some screenshots of what your phone will look like if it works.
[LG Thrill 4G] a2r3f:
Although it looks nice it inhibits the phone from certain apps and games from the market.
[LG Thrill 4G] bzlmnop:
Has anyone found away around the market problems caused by changing the LCD density?

I used to just change it back and forth but got tired going through the hassle of changing it back and forth and having to reinstall the market sometimes...

I tried digging through the market and market updater apk, but couldn't find anything...
[myTouch 4G Q&A, Help & Troubleshooting] rickeyswenson:
Can someone help me downgrade my device? Its a mt4g. Ive looked at the guides and I dont understand them... Maybe downgrading for dummies?
[myTouch 4G Q&A, Help & Troubleshooting] Skipjacks:
The downgrade guides out there are already as simple as they could possibly be.

Using them involves a lot of cutting and pasting and not much more.

If that's over your head (and no offense if it is....most people would be intimidated by something that has the potential to kill their expensive phone) you should probably step away from the modding process and enjoy your phone as stock.
[myTouch 4G Q&A, Help & Troubleshooting] 3r0k:
What exactly do you need help with, Like the post above states, this is not easy stuff, so you may want to leave your phone stock.
[HTC Inspire 4G] toxicpaulution:
Any ideas about a nice pipboy theme or something for absolution rom to do with pipboy would be awesome :)
[HTC Inspire 4G] dj sampson:
I have seen a pipboy skin in the Droid marketplace. It had a bunch of icons from fallout.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] seeking:
I'm having a hell of a time finding one that uses the LED flashlight but also has a decent interface

any suggestions?

I'm coming from the Nexus 1 and there were handful of flashlights specifically designed for that phone alone. Not so much the case with the Note it seems.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] jimbob456:
I'm using tiny flashlight, has quite a few features
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] seepage:
why does tiny flashlight need to read phone status and ID and have full internet access?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] brotbuexe:
I use tesla led
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] vviz:
Tesla LED works great, I use it as a widget. Also widgetsoid's toggle switch in mode 2 for flash light works too
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] DarkShot666:
Yet another Tesla LED user.

The widget is a godsend for immediate use.

I just gotta find out if I can theme it.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] seeking:
I'll try out Tesla LED. all I want is an LED flashlight, I dont care about anything else like strobe or colored screens
[General Topics] DAMIEN123_666:
Hi all i just got my self the xda app but i cant upload images to the forum.. Why?
[General Topics] Bobguy21:
I cant either and it makes me mad
[General Topics] ltdanno360:
i use tapatalk app from android market

works to upload anything ! to xda
[General Topics] Bobguy21:
True but I don't like the layout. Its a bit different from xda app.
[General Topics] Techvir:
I have both but only use tapatalk as it works better.
[Kindle Fire General] zonbal33:
I tried following this thread: http://xdaforums.com/showthread.php?t=1349652

When I open a CMD window and type this is what happens:

c:\>cd adb

c:\adb>adb shell

$ su

su

# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system

mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system

# rm /system/app/Superuser.apk

rm /system/app/Superuser.apk

# rm /system/bin/su

rm /system/bin/su

rm failed for /system/bin/su, No such file or directory

# rm /system/xbin/su

rm /system/xbin/su

# rm /system/bin/su

rm /system/bin/su

rm failed for /system/bin/su, No such file or directory

#

I can't seem to remove '/system/bin/su". I restarted my KF and typed "adb shel" "su" and it says "permission denied". Does that mean my KF is good to ship back and not rooted now?
[Kindle Fire General] jlocohustler:
Try to install an app that requires root like OpenVPN for example. If it doesn't install or work properly, you're unrooted. Or try to su in with a terminal emulator.
[Android Software/Hacking General [Developers Only]] flavioaugustosbc:
Hello, I'm with ATRIX 2 and failed fastboot appears when you start, the screen is black, the Gingerbread 2.3.5 AT & T U.S., someone has the file that I run the RSD?

if yes, send to my e-mail flavioaugustosbc@hotmail.com

Bom dia, estou com o ATRIX 2 e quando inicia aparece failed fastboot, fica na tela preta, Gingerbread 2.3.5 da At&t americano, alguém tem o arquivo para que eu rode no RSD?

se sim, encaminhe para meu e-mail flavioaugustosbc@hotmail.com
[Nook Color Q&A, Help & Troubleshooting] ididitforthenookie:
I apologize if this has been asked before, but dalingrin's size agnostic installer thread is a little vague for newbies like me.

I'm trying to boot CyanogenMod 7.1.0 (File: update-cm-7.1.0-encore-signed) from an SD card. I'm a little confused as to which version of the installer image I should use -- version 1.2 or version 1.3. I believe he says that nightly versions 87 and later should use 1.3, but I don't know if CM 7.1.0 stable is prior to that nightly or not.

Question in short: Do I burn generic-sdcard-v1.2.img or generic-sdcard-v1.3.img to my SD card to boot cm 7.1.0?

Also, what exactly is the difference between the two installer image versions?

Thanks
[Nook Color Q&A, Help & Troubleshooting] koopakid08:
You should use 1.3. Nightly 87 was a LONG time ago. I think we were up to 234 before the build bot broke.

Also, for a more noob friendly(step by step) check out the install to an SD card section of the guide in my sig.

Sent from space
[Nook Color Q&A, Help & Troubleshooting] votinh:
Firstly, it's verygreen's one, not dalingrin's

Secondly, you should use the v1.3 one.
[Galaxy Note GT-N7000 General] DAMIEN123_666:
Hi all how do i make the app work for me

It says Jpeg wrong file type
[Galaxy Note GT-N7000 General] DAMIEN123_666:
Arrr got it workin now sorry about random image its my phones wallpaper i used it to test this app with
[Galaxy Note GT-N7000 General] rossygnol:
How do you upload pictures by the way. Can't see how thx
[Galaxy Note GT-N7000 General] martcerv:
When you post in the app click more, select the image you want to upload from gallery out other options. I found that if i tried to keep original image it wouldnt work but the small size option works fine. Next click inline and your pic should appear like this one.

View attachment 825762
[Galaxy Note GT-N7000 General] martcerv:
Sorry for the double post, but looks like the board doesn't except .png images which the note saves in. The small version is converted to .jpg
[Galaxy Note GT-N7000 General] Prozac69:
I get the same error and it will only let me post smaller size images. Do we know why this is?
[Samsung Galaxy Nexus] flowtime:
Android centreal wrote and article about a battery bug for the galaxy nexus. http://www.androidcentral.com/ice-c...ss-something?utm_source=ac&utm_medium=twitter

up until this point i hadn't heard of it but I just got me a second Gnexus and figured i'd try it out.

Just over an hour into to test and you can see the same issue that had.

Testing conditions:

-both phones are rooted with the stock kernel and rom on Verizon

-I went to the settings and turned of every service possible the only that kept coming back was youmail which was on both phones

-I left the phone off (press the power button to put it to sleep) the whole time except between every call of duty match to check on the times and take screen shots

-screen brightness is exactly the same

-both phones started at 100%

I messed up the screen shots and that's why the volume pops up over the thing

Pretty crazy, I'm going in tomorrow to exchange mine ( the one that is draining ) tomorrow

My wife came home and plugged her phone up and mess my test up. I will try again, but this morning when I woke up the VZW network was down so i figured i do one more thing. I had my screen on for 90 seconds put it to sleep and then got in the shower. Here is what i saw when i got out.

The slight time difference is from the time it took me to get into android OS and take a screen shot

Here's another point of data.

I have a 2 batteries and I switched my second battery into the phone and got very different results. It may have been the restart that did something or it may be a battery issue. who knows
[Samsung Galaxy Nexus] eakrish:
Both VZW phones? Does the one on the right apper to have a better signal also, or is it just me? My phone with much less screen time has AOS with about the same usage as yours on the right.
[Samsung Galaxy Nexus] Chirality:
Looks like it's caused by the Media service which is running on the left phone but not the right phone...
[Samsung Galaxy Nexus] Resun:
I noticed my OS is using between 30 - 33%. I'm averaging between 6-8 hours between charges since I got it Friday.
[Samsung Galaxy Nexus] eakrish:
What's your usage like?
[Samsung Galaxy Nexus] flowtime:
Yes they are both verizon phones, and no it's not just you the phone right beside each other and the one on the right alaywas had better signal

I don't know what that is. It ran for like 2 minutes. I went in to the applications and turned it off

for the test none. I kept both phones "asleep" the whole time except when I woke them both up to take screenshots and check stats
[Samsung Galaxy Nexus] flowtime:
My wife came home and plugged her phone up and mess my test up. I will try again, but this morning when I woke up the VZW network was down so i figured i do one more thing. I had my screen on for 90 seconds put it to sleep and then got in the shower. Here is what i saw when i got out.

The slight time difference is from the time it took me to get into android OS and take a screen shot
[Samsung Galaxy Nexus] gsxr1kmatt:
I saw a rom that had a fix for the battery bug..

are your feelings that it is a software or hardware bug?
[Samsung Galaxy Nexus] madpoet:
My battery drain is insane. I'm losing roughly 10% every 30 minutes, with 70% of that being the screen. My brigthness is dialed down to 40%. And I have the extended battery!
[Samsung Galaxy Nexus] flowtime:
I'm not sure. It seems like it would be software because I can't see any hardware keeping the phone from going to sleep
[Samsung Galaxy Nexus] pharpe:
Is your screen on the whole time? You might need to adjust you time out setting. I always manually turn mine off as soon as I'm done looking at it.
[Samsung Galaxy Nexus] madpoet:
It's set to 30 seconds. I guess I need to use it less ;)
[Samsung Galaxy Nexus] flowtime:
Give us this info.

Total time on battery -

Screen: Time on -

Android OS: Keep awake -
[Samsung Galaxy Nexus] madpoet:
I rebooted about an hour ago trying to get data back (before I read about the outage).

1h 1m on battery

Screen 69%

Android OS 16%

Cell Standby 5%

Dolphin Browser 3%

Android System 3%

Phone Idle 3%

Phone 2%

Time on 29m 51s

Keep awake 56m 37s
[Samsung Galaxy Nexus] flowtime:
Yeah that's keep awake is the problem

Your phone was on for 61 minutes and it was awake for 56 of those minutes.
[Samsung Galaxy Nexus] madpoet:
That would be a problem. Hope it gets fixed, I like the phone but it's killing me to have to plug it in.
[Samsung Galaxy Nexus] flowtime:
I hope it gets fixed quickly
[Samsung Galaxy Nexus] gsxr1kmatt:
Just checked my phone, unplugged for 34 minutes, only 2 minutes awake time. looks like I don't have the issue. I will post screen shots in a bit.

I have data turned off in my phone right now since data network is down. Could someone who is sure they have the issue test with data off? see if that changes anything to help validate my testing.

I should also note, I'm running Android Revolutions 2.1.1... will update to 2.1.2 later today.
[Samsung Galaxy Nexus] gsxr1kmatt:
Update,

After 2 hours. 91% remaining.

first hour, data was off, dropped 4% to 96%.. turned data on for 45'ish minutes, dropped another 5%... not unacceptable.

here are my screenshots for the 1st hour.
[Samsung Galaxy Nexus] gsxr1kmatt:
and after almost 2 hours.
[Samsung Galaxy Nexus] KWKSLVR:
If this so called "battery bug" is going to be properly tested between two identical phones side by side, it needs to be done with a FRESH wipe and identical setup, down to the apps that are on the phone and the ROM and sync settings.

NO restoring of Apps/Data (even just apps) from the Titanium Backups taken from your old phone. The device needs to be COMPLETELY clean.

NO restoring of Apps/Data from Google

Then, it needs to be tested again with the batteries swapped to determine if the battery is to blame.

No offense to the people experiencing this, but the hysteria associated with this is completely over the top. I'm not denying the very GOOD chance that there is an issue on the kernel level, but people are complaining and freaking out and not sharing any form of useful information about how their phones are setup.

If someone restored their apps/data from their old android, has every CPU sucking widget on their home screens, 15 apps running on sync constantly and are on LTE with a weak signal, then not only is their phone going to suck, but their battery is going to last about 5 hours. ;)

I have 4 factory batteries for my Vibrant. They all give me different average battery lifespans. I don't think that's the culprit, but swapping batteries between a device with "bad" battery life and one with "good" battery life when all other variables are equal is a good way to test this out.

As far as concerns about what your battery does @ 100%, then yanked off the charger, the first 10% doesn't count. Your battery is going to trickle charge and discharge while still plugged in and still read 100%. What matters, in my opinion, is what the device is doing from 90% on down.

Test with a factory fresh install, with your Google Account rocking, no widgets, GPS, WiFi, Bluetooth, etc AND DO NOT RESTORE APPS FROM TB FROM YOUR OLD DEVICE IF YOU DID :p

Just friendly suggestions. :D

---------- Post added at 01:14 PM ---------- Previous post was at 01:09 PM ----------

Your last photo is very telling to me. Unless you have an app that is properly displaying actual charged milliamps, you easily could have taken the phone off the charger @95% or 96%, with it displaying 100% and it's using roughly 2%-3%/hr on LTE. Considering the Thunderbolt was initially chewing 10%/hr on LTE while sleeping, this is OUTSTANDING battery life. My Vibrant on an official ROM eats more than that while on 3G.

You need a longer test sample, and you need to verify that your batteries are properly calibrated (and they probably are).

But really, the first 10% if your displayed battery life is completely irrelevant. This needs to be tested over full charges with the phones completely drained, fully charged, taken off the charger at the same time and used in the EXACT same manner as close as reasonable possible and in the same place. In other words, take a Saturday and hold your calls. ;) Once a baseline is established, apps/processes/etc can be added in one by one until the issue reoccurs.
[Samsung Galaxy Nexus] player911:
Well I'm running RootzBoat 4.0.3 stock AOSP rom, stock kernel, latest 4.0.3 Radio/Baseband.

5 hours from charge and I'm at 79%. This is with normal day to day usage plus setting up FaceUnlock. My Android OS standby time is like 3min.

At this rate I'll be getting 25 hours out of this puppy.

I do have my screen off time from 30s to 15s. Max screen brightness though.
[Samsung Galaxy Nexus] paOol:
interesting, I'm also on rootzboat 4.0.3 and I've had the same Android OS keep awake problem in stock, 4.0.1, in HD revolution, and I still experience it in rootzboat 4.0.3.

However, I'm using fobolous' kernel and not the stock kernel, also on the latest radio/baseband.

I was at 96% before I went to sleep, woke up to about 83% or so. Much better than I used to get (20~% drain overnight), but today was the whole VZW data outage, so that might have messed up the results.

I'll try the stock kernel tonight and see if that fixes it.
[Samsung Galaxy Nexus] player911:
Yea I'm pretty happy with the setup. Got the SmartDialer, 1% Battery, WiFi Tether, Wallet.
[Samsung Galaxy Nexus] keatre:
It's not LTE - its mobile data. Throw it on WiFi (or airplane mode) and you'll see AndroidOS decrease. Currently testing a personal kernel for fixes. Reference other thread:

http://xdaforums.com/showthread.php?p=20548184
[Samsung Galaxy Nexus] flowtime:
I thought LTE was mobile data?

I don't have wifi for 80% of the day so a kernel with a fix would be awesome
[Samsung Galaxy Nexus] aohus:
they really need to fix this issue ASAP. I have about 12 days left. If its not fixed by then, I'm returning this device.

hate to say it, but this is a perfect example of why Google is Google and Apple is Apple.

Apple tends to work out the big bugs before release. Google lets the bugs stay and cause frustrations on the end user. This should be fixed imo.

I've had this device on for 45 minutes and its already at 84% lol.
[Samsung Galaxy Nexus] cam30era:
That's why owners were delighted with battery life on the new iPhone 4s, right?
[Samsung Galaxy Nexus] aohus:
Apple resolved it in a timely manner. Lets see if Google can do the same.
[Samsung Galaxy Nexus] flowtime:
What about the iphone that didn't work when you held it a certain way

and this phone has only been out for less than a week how do you know it hasnt been a timely manner
[Samsung Galaxy Nexus] KWKSLVR:
I've also seen some people complaining over CPU cycles @ idle. I actually went to Verizon this afternoon and picked up a GN. After looking at it with System Panel, I think people are misinterpreting what is really going on when it shows that it's chugging along at 384mhz - 430mhz and then jerking their knees over it.

This is a dual core phone. System Panel is reading the sum of both core's activities. Each core is working in between the high side of 100mhz and the low side of 200mhz. This is no different than single core activity on the Vibrant I'm typing this on right now. System Panel shows both core's being 98%-99% free at idle, screen on. People are freaking out over nothing.

While letting my partially full battery drain completely, I unlocked the bootloader, rooted, then stepped away to run some errands for a couple hours. The phone was at 19% when I left it. When I came back a little over 2 hours later, it was @ 12%. So it's chewing around 3-4% an hour on LTE. I saw no sleep issues and there is zero wrong with a device that burns juice at that rate on LTE.

I haven't updated yet or installed any additional apps other than System Panel, and don't plan to until I've played with the device more, but on first impression, I don't see what the big damn deal is?

Any notion that you're gonna have 30 minutes of screen on time an hour and rock 10 hours+ of battery life every day is completely silly.
[Samsung Galaxy Nexus] paOol:
I think the problem isn't LTE, as evidenced by this anandtech article

http://www.anandtech.com/show/5254/investigating-the-galaxy-nexus-lte-signal-issue

I think the problem currently is the Android OS bug. It's always the second or the first most draining process and it is what's killing our batteries. I'm sure developers will eventually solve this issue and we'll be looking at much much better battery life. the performance is already great.
[Samsung Galaxy Nexus] Valkyrie743:
**note that im using the stock battery but plan on buying the extended battery**

so is this good or no?

4.0.2 with ARHD 2.1.2, (stock kernel) with nova launcher just flashed the rom last night and did a battery calibration. waiting for this to die. so far its pretty good but i have not used the phone allot. i have gmail syncing and facebook is syncing but only messages and didnt get many during this day. the thing the bugs me though is you see the sudden drops in battery life on the graph. theres 3 sudden drops. the first and second ones are the worse. they happened when my phone was at idle for a while and right when i turn the phone on and started to surf the web or do whatever it dropped that much in the matter of 10 minutes if not that.

my screen brightness is almost all the way to the left. (auto brightness is off) well what you think. is this good or no
[Samsung Galaxy Nexus] det1034:
Id have to say that its not that great and that your keep awake time seems a little high. Im stock rooted with extended battery and my phone went about 22 hours with a keep awake time of only about 1 hour. However I did let my battery completely die the first time and wiped battery stats then charged it for about 10 straight hours. But I still think the keep awake time is high. I just pulled my phone off of the charger about 30 min ago and my keep awake time is only at 1 min. So Id still say a little high.
[Samsung Galaxy Nexus] TiltedAz:
I never experienced the bug until last night. The OS consumed 40% or so overnight. The only thing I did different yesterday was attempt to connect to a wifi at my physical therapist's office. I never did succeed with that connection. Wonder if my GN went into the weeds after that.

In any event. I restarted my phone later this morning and battery discharge while asleep is normal again.
[Samsung Galaxy Nexus] det1034:
I was only referring to the keep awake time... no need to get over excited