Database Users

100% awake time fix for DamagedTrev 2.0.1?

I have tried the Airplane Mode trick, and it did not work...anyone find a solution? This build runs great other than this battery life issue...

Did you try this method: http://forum.xda-developers.com/showthread.php?t=651848

Thanks for the suggestion. I tried that previously, and while it reduced the "time without signal", the awake time is remains at 100%.

Does anyone know if this 100% awake is an issue with Fresh Rom 2.0c?

ronnienyc said:
Does anyone know if this 100% awake is an issue with Fresh Rom 2.0c?
Click to expand...
Click to collapse
That issue isn't guaranteed to happen, or *not* happen, on any particular 2.1 rom, but seems to happen to people on occasion on different roms, and perhaps for different reasons. I did not have that issue on Fresh 2.0c, for what it's worth.
No matter which rom you want to end up on, it might be a good idea to restore back to something that previously worked, confirm that it still does, then re-wipe (Data/Dalvik/Ext) and re-flash the rom of your choice. If all goes well you won't have the issue, and will have only a slight lingering frustration over what unknown factors were causing it.
...and good luck!

This sounds fine, except for having to set up all my apps., etc, etc all over again :-(
Is there a way to avoid that?

ronnienyc said:
This sounds fine, except for having to set up all my apps., etc, etc all over again :-(
Is there a way to avoid that?
Click to expand...
Click to collapse
Depends on what you mean by 'set up' -- saved .apks for easy re-installation, yes. Saved .apks with all relevant configuration intact -- well, that's what nandroid is for, so in that case no, not really.
Best case, if you happen to be using apps2sd, when you do a nandroid backup (+ext) it puts all your .apk in a neat and tidy .tar file for you labeled ext. You could certainly unzip that and push them back after you get the basics set up again.
If you are not using apps2sd, you can still backup most of your .apk files using AppMonster or Astro, both free from the market. They might not be able to backup some paid apps, or certain protected free ones, but it will get most of them. If you are comfortable reading up on, and learning adb a bit, you can 'adb pull [source] [destination]' to get the files that the apps won't copy on to your PC.
Regardless, don't rush to dump everything back before you check to see that your awake time drops when the phone is off for a while (and not plugged in to pc, for good measure).

I am assuming hat wiping and using a nandroid backup will not fix this issue...correct?

ronnienyc said:
I am assuming hat wiping and using a nandroid backup will not fix this issue...correct?
Click to expand...
Click to collapse
Oh it might, but if the rom you restore isn't the rom you want to end up on you will clearly still have a few more steps to take. Since the issue isn't really that well understood the only way to find out for sure is to try it.
If I had to wager, I would say that yes, if you restore a backup of a rom that didn't give you 100% awake time trouble before, it should be fine once again when restored over a setup that was giving you trouble.
The real point is that if you then went *back* to the one that was giving you trouble, there is just as good a chance that it would work fine this time as there is that you would have the same issue again. Only one way to find out...

Thanks for all of your help askwhy. Too bad no one understands this issue - it seems that it *should* be a very simple fix ;-)

Wow, I just flashed Fresh 2.0b and the awake time issue is resolved. Also, the Cell Standby issue is also solved - it's at 29%, rather than the 69% I had with the Damaged One...now tlet's see what is broken in the Fresh version...

I had 100% awake on DamageControl v2.0r2. Just flashed Damaged-Regaw 2.0b1.3 and the issue is solved as well as all the other issues I was having.

Troy, what other issues did it solve, and where did you get it?
I am now thinking of staying with Fresh, as it seems to be more responsive...thanks.

i am on darkledgend 4.2.2 and to fix the problem on that rom here are the steps, give it a try.
from dialer
*#*#4636#*#* (give it a second and you will go into a menu)
press menu hard key
press select radio band (you will get a force close, acknowledge and ignore it)
select "cdma auto prl" from the drop down menu
press home hard key
you have to do this every time you reboot

ronnienyc said:
Troy, what other issues did it solve, and where did you get it?
I am not thinking of staying with Fresh, as it seems to be more responsive...thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=654300 there is a list of fixes here as well

Thanks Smitty. I tried that some time ago, and while it seems to fix an issue, but it does nothing to help the 100% awake issue. Thanks though.

for what its worth i have never had the issue using the full rom -
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I updated my first post with some info, try run spare parts, go to battery history & check partial wake usage

Are the people with 100% awake time already patched with this file?
http://www.4shared.com/file/252386050/cb94052d/Facebook_DamagedTrev.html
(From the first page of http://forum.xda-developers.com/showthread.php?t=653622 )
I noticed I had the 100% awake time before trying to fix the Facebook syncing problems; patched with this file and now I'm down to about 50% awake time (sounds accurate as I haven't had the screen off for a lot of the time).
Its only been a bit over an hour but though I would mention it.

good point about fb urinsane last thing i did before i started session in above screenshots was test out that update.

TrevE said:
good point about fb urinsane last thing i did before i started session in above screenshots was test out that update.
Click to expand...
Click to collapse
Oh wow, didnt realize there was a patch. when i posted above about Regnaw's rom, I hadnt set up facebook yet.....so it wasnt syncing. Once I did, it was back to 100% up time so I tried the facebook fix zip and wouldnt you know it....up time is once again going back down.

Galaxy S - screen problem

Guys,
my "galaxy s" has problem on the screen, I noticed that it becomes more evident only in a few programs / screens.
When I take a screenshot of the screen and send it to a computer or other phone the picture is normal.
I think the image is being "generated" correctly, but not being "displayed" correctly on the screen.
As an example I posted a screenshot taken of "sound recorder app", and
immediately below is a picture that I took with a camera to show how I am
seeing the image on the screen.
If you have any idea whats happening because I dont want to have to leave at service center and whait for days without the phone.
any ideas?
photo below is a screenshot taken by telephone and sent to the
computer
Updating post!!!
The screen or the display died less than a month after the problem started, left at samsung service repair office to change the display or the handset
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this photo was taken with a camera showing how it is being shown

Mine does the same...

Let´s digg the web and find out what´s happening.
If you find something please remember to contact me.

That's new and I doubt its software related - reflash with stock rom and if it doesn't help - send to service for replacement (or fix).
HTH

Something like this happened to my old phone (not galaxy) as it overheated

never happens to me, i think its a software issue.

I flashed it whith different roms, voodoo kernel and the result is always the same.
I dont want to believe that it's a hardware issue, but at this point I'm losing my hope.

Looks like voodoo kernel
Either that or the superamoled screen has deteriorated.
My screen has burn in of the battery clock and wifi icons. Sucks.
Sent from my GT-I9000 using XDA App

rodrigoresende said:
Guys,
my "galaxy s" has problem on the screen, I noticed that it becomes more evident only in a few programs / screens.
When I take a screenshot of the screen and send it to a computer or other phone the picture is normal.
I think the image is being "generated" correctly, but not being "displayed" correctly on the screen.
As an example I posted a screenshot taken of "sound recorder app", and
immediately below is a picture that I took with a camera to show how I am
seeing the image on the screen.
If you have any idea whats happening because I dont want to have to leave at service center and whait for days without the phone.
any ideas?
photo below is a screenshot taken by telephone and sent to the
computer
this photo was taken with a camera showing how it is being shown
Click to expand...
Click to collapse
Is it running on the original firmware?

In some kernels (example SpeedMod K13B), there are options for color tweaking in the Recovery Menu.Try disabling those if you are using such kernels.

Faulty screen. Flash original firmware and take it in to get fixed.

Reflash or Speedmod Recovery for Neutral Color settings

Maddmatt said:
Faulty screen. Flash original firmware and take it in to get fixed.
Click to expand...
Click to collapse
Ι have the official 2.2.1 and it does the same to me. Should i send it to service?

Same here.
Darky v9.2 & SpeedMod K13B
I don't think it's a hardware issue.
Sent from my GT-I9000 using XDA App

If you have this kernel (SpeedMod) could you try to use the settings to adjust color and post if it helped.
"In some kernels (example SpeedMod K13B), there are options for color tweaking in the Recovery Menu.Try disabling those if you are using such kernels."

Here it goes
rodrigoresende said:
If you have this kernel (SpeedMod) could you try to use the settings to adjust color and post if it helped.
"In some kernels (example SpeedMod K13B), there are options for color tweaking in the Recovery Menu.Try disabling those if you are using such kernels."
Click to expand...
Click to collapse
Try this. I hope you flashed SpeedMod kernel.
If you haven't done so please disable the lagfix and tweaks in the kernel you are using now.Flash the SpeedMod kernel available here http://forum.xda-developers.com/showthread.php?t=822756&highlight=yaok
1. Go to the recovery mode
2. advanced SpeedMod ULK features
3. COLOR & BRIGHTNESS options
4. NEUTRAL Color (default)
Please reply if it helped.

I already have neutral color. Switched to cold, same thing.
Can anybody else show us his screen @ voice recorder app ?
Sent from my GT-I9000 using XDA App

theos0o said:
I already have neutral color. Switched to cold, same thing.
Can anybody else show us his screen @ voice recorder app ?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I think that I can't apply this kernel (SpeedMod K13B) to the brazilian model I9000B, but as "theos0o" said it didn't solved the problem.

I don't really think it's faulty screens.
It's just a weakness of (current?) AMOLED technology.
Check this out:
http://arstechnica.com/gadgets/news...xus-ones-screen-science-color-and-hacks.ars/3

I was looking at its screen when the colors changed and since then, it looks like the images I posted. It suddenly flicked and from that moment looks weird as you could see.

My camera is'nt working very well..

i've installed GingerDX rom [2.3.5] and it says in the thread that the camera is working.
when i turn on the camera, i see some weird colors on the screen[like green and pinkish colors] and when i take a picture it shows me a black screen and does nothing.
any idea why ?

It works on v005 and v006 just some camera-related apps are not workin well.
Sent from my X8 using Tapatalk

i'm not using any apps for the camera im using the built-in app.

Here's a pic . [took the picture from samsung magic touch =\]
sorry about the quallity
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

i don't have problems with taking pictures, works fine at 3MP but i do have problems recording video. It still has lag even if it says that the lag was a froyo problem in general.......and it lags a lot, like trying to play Tomb Raider 2 in a MMX with a 4mb pci diamond video card.....
E15a if it matters....

i've just checked the camera in the original rom [2.1 Eclair] and it seems to have the same problem. does it means that my camera is brokem ? or i can fix it somehow

You seem to have a broken camera, because it exists even in Eclair.
@damian824: you should remove overclock module if you're using it

doixanh said:
You seem to have a broken camera, because it exists even in Eclair.
@damian824: you should remove overclock module if you're using it
Click to expand...
Click to collapse
Agreed, cuz mine is working flawlessly, no lags at all.

=o is there any way to fix it ?

sultanovski said:
=o is there any way to fix it ?
Click to expand...
Click to collapse
Yeah.. send phone to the repair

i managed to film a video
what do u guys think?

Nice land phone you got there.
It's hardware related...(I'm 100% sure) you dropped your phone or something.
Your camera is broken.
Repair

i did dropped the phone a couple of times =\
and are u sure there is no way i can fix it ? except sending it to repair

doixanh said:
@damian824: you should remove overclock module if you're using it
Click to expand...
Click to collapse
i dont have it, it was deleted when i installed the .zip file. the only thing left whas setcpu. but even tryed doing a full wipe and still happened.
i checked the files anyway and the only one i saw was x8uv.so but that's something else.
just in case, i always record in vga/high, and i use a 16gb class 6 sdhc (20/12 r/w with a card reader)

sultanovski said:
i did dropped the phone a couple of times =\
and are u sure there is no way i can fix it ? except sending it to repair
Click to expand...
Click to collapse
I dropped mine dozens of times and it's fine.. mather of luck..
By installing roms no.
here is what you do..
reflash with seus... and send to repair ...
P.S: I'm little drunk hope u understand me

Try full wipe in the xRecovery options.
Sent from my W8 using XDA Premium App

GAME ON said:
Try full wipe in the xRecovery options.
Sent from my W8 using XDA Premium App
Click to expand...
Click to collapse
i said i already tried with that, but the lag persisted.
i thought it could be something to do with froyo so went back to SE's default and instaled the zip then wiped and the same.
this doesn't happen in SE's default, so it isn't broken.
one more thing, i still don't know much about how android works, i know it's based on linux, etc..... but what is it that lags the camera hardware or is it cpu related?

Dare-Devil Inside said:
I dropped mine dozens of times and it's fine.. mather of luck..
By installing roms no.
here is what you do..
reflash with seus... and send to repair ...
P.S: I'm little drunk hope u understand me
Click to expand...
Click to collapse
whats seus =o

sultanovski said:
whats seus =o
Click to expand...
Click to collapse
SEUS = SonyEricsson Update Service
You can download it from SonyEricsson page

damian824 said:
i said i already tried with that, but the lag persisted.
i thought it could be something to do with froyo so went back to SE's default and instaled the zip then wiped and the same.
this doesn't happen in SE's default, so it isn't broken.
one more thing, i still don't know much about how android works, i know it's based on linux, etc..... but what is it that lags the camera hardware or is it cpu related?
Click to expand...
Click to collapse
try to delete x8uv.ko, it's undervolting, it saves battery but it makes my phone lag a log, maybe this causes you problem

Nexus 7 Auto Rotation stopped responding

Not sure what's happened, but the Auto Rotate functionality on my Nexus 7 doesn't seem to be responding anymore?
I have Nova Launcher Prime installed, auto rotate enabled everywhere I can find. It had been working perfectly, and I'm not really sure why nothing is rotating.
It seems to be getting stuck in whatever view it's currently in. I started up Transformers to see if the screen would rotate, it did because it was forced to, but then I quit the movie and my Nexus was stuck in landscape mode.
The only way I can seem to get it back to portrait mode it by making it go to sleep and then unlocking it. I've already powered it off and on to see if that would make a difference, but no luck yet.
I've owned Android devices for 2+ years now, and I've never seen this happen before... Ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Sorry for the smudged screen, but here's another picture doing an accelerometer test, and the little ball was stuck at the top

Did you try default launcher? If not try that.
Another suggestion is uninstalling Nova Launcher Prime, and reinstalling.

His problem is happening everywhere, not just the homescreen, so messing with the launcher won't fix it.
Nick: This thread might help (seems like it might or might not work).
http://androidforums.com/nexus-7/594159-new-n7-wonky-accelerometer.html
Btw, you probably don't need to turn on the flash when taking pictures of your screen. Turning it off would probably result in clearer pictures.

Mine had the problem from the start and various things I try sort it out temporarily but don't fix it.
You're problem could be reversed if it was ok to start with, something might have knocked the gyro off somehow?
Might be worth backing up and doing a factory reset?

Thanks for the suggestions everyone, but it doesn't seem to have solved the issue...
I tried uninstalling and re-installing Nova Launcher - No change
I tried to calibrate using that Compass app - No change
I then tried to do a factory reset - No change
My baseline app for testing ATM is Hyper Jump, and the little dude just goes flying off constantly to the right, and I have absolutely no control of him

Did you accidentally lock your orientation in the notification bar? It's the icon to the left of the settings button.
Sent from my Nexus 7 using Tapatalk 2

RoidPusher said:
Did you accidentally lock your orientation in the notification bar? It's the icon to the left of the settings button.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Double and triple checked all of my settings - photos posted above showing settings. Everything appears to be right.
Here's a clip of the game Hyper Jump on my Nexus

AZImmortal said:
His problem is happening everywhere, not just the homescreen, so messing with the launcher won't fix it.
Nick: This thread might help (seems like it might or might not work).
Btw, you probably don't need to turn on the flash when taking pictures of your screen. Turning it off would probably result in clearer pictures.
Click to expand...
Click to collapse
I see see, that makes more sense.
Seems like a hardware issue then, best to give Google or Asus a call?

O29C said:
I see see, that makes more sense.
Seems like a hardware issue then, best to give Google or Asus a call?
Click to expand...
Click to collapse
I'm gonna be heading to Futureshop after work today and see about an exchange / refund. This'll be the 2nd one I've returned
Hopefully Futureshop got some in stock

NickDblU said:
I'm gonna be heading to Futureshop after work today and see about an exchange / refund. This'll be the 2nd one I've returned
Hopefully Futureshop got some in stock
Click to expand...
Click to collapse
http://www.droid-life.com/2012/07/17/yes-the-nexus-7-has-auto-rotate-just-not-from-the-home-screen/

Try reimaging with stock 4.1?

Hi,
I was having the same problem. I first tried the compass app and went through the calibration and it was the same. I then did a complete erase. Still the same. I was resigned to sending it back, but was reluctant too as I'd bought it in an airport in the UK and I'm sure it would've taken some time and there would be some hoops to jump through. I then went into Youtube and started to rotate the device around quite aggressively and found if it was upsound down and I shook it, it changed to landscape / portrait. I then tried the compass app again, went through the calibration and hey presto - it worked!!!!!! :laugh::laugh: Don't know if the compass app fixed it or if shaking it agressively did the trick.
It now changes seemlessly from portrait to landscape and vice versa. If you're used to an iPad or iPhone you might have to wait a fraction of a second longer for it to work.

mclarenpaul said:
Hi,
I was having the same problem. I first tried the compass app and went through the calibration and it was the same. I then did a complete erase. Still the same. I was resigned to sending it back, but was reluctant too as I'd bought it in an airport in the UK and I'm sure it would've taken some time and there would be some hoops to jump through. I then went into Youtube and started to rotate the device around quite aggressively and found if it was upsound down and I shook it, it changed to landscape / portrait. I then tried the compass app again, went through the calibration and hey presto - it worked!!!!!! :laugh::laugh: Don't know if the compass app fixed it or if shaking it agressively did the trick.
It now changes seemlessly from portrait to landscape and vice versa. If you're used to an iPad or iPhone you might have to wait a fraction of a second longer for it to work.
Click to expand...
Click to collapse
Hi..
Or problem is here? code.google.com/p/android/issues/detail?id=58349

Can't touch bottom of screen

Well, I'm running the latest CM10.1 Nightly, and no other mods. For some reason, in some apps I can't touch things at the bottom of the screen. For instance, in Snapseed, I can't apply an edit, because it doesn't let me touch it. Also, in the messages app it takes forever to get the keyboard to come up. Does anyone else have this problem? Is it a CM10 thing? TIA!

So, I flashed the Google Official ROM, and still the problem persists. Going to fully unroot and see if it fixes itself.

Nex.us 4 said:
So, I flashed the Google Official ROM, and still the problem persists. Going to fully unroot and see if it fixes itself.
Click to expand...
Click to collapse
ouch

Could I please get some opinions? This is getting very annoying. It only seems to happen in apps, because I can access the app drawer and docked apps fine. I flashed the stock ROM, and un-rooted but the problem is still here. Any help?

Go into developer options. There should be an option for Pointer Location. Turn that on, and scribble all over the area you're having touch problems with. See if it is even registering your touches.

btse said:
Go into developer options. There should be an option for Pointer Location. Turn that on, and scribble all over the area you're having touch problems with. See if it is even registering your touches.
Click to expand...
Click to collapse
while in that same area.. another option is z-device test. go to screen and menu key to perform sensitivity tests and such. if you dont have a menu key in the navbar... it will not work.

Okay, thanks for the tips guys. This is really weird. There's like, a barrier where I can't touch at the bottom of the screen. I took some screenshots to show you guys.
http: //i.imgur. com/RajcK.png
http: //i.imgur. com/F2GRs.png
Any help would be appreciated, I'm really hoping this isn't a hardware problem.
For the record, I've flashed back to the stock image, unrooted, and locked my bootloader. The problem persists. Thanks!

Are you using any kind of screen protector? Just that I had some weird touch problems in the past which disappeared when I switched screen protector.
Sent from my HTC Vision using xda premium

steviewevie said:
Are you using any kind of screen protector? Just that I had some weird touch problems in the past which disappeared when I switched screen protector.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I'm actually not, but thanks for the suggestion! This is really bumming me out.

Nex.us 4 said:
I'm actually not, but thanks for the suggestion! This is really bumming me out.
Click to expand...
Click to collapse
Are you using screen filter app?
Sent from my Nexus 4 using Tapatalk 2

I found someone on another forum who had the same problem. He went with it being a hardware problem, and I recently sold my phone. Shoot.
http: //forums.macrumors. com/showthread.php?p=16534236#post16534236

Flashing the touch responsiveness zip helped me
Sent from my Nexus 4 using xda app-developers app

Looks like a hardware problem :/

I figured this out and it's pretty weird. The height of the deadzone is exactly the same as the height of the nav. bar. Anyone got any ideas? Or has LG f***ed me over?
http: //i.imgur. com/TLs8Y.jpg

Nex.us 4 said:
I figured this out and it's pretty weird. The height of the deadzone is exactly the same as the height of the nav. bar. Anyone got any ideas? Or has LG f***ed me over?
http: //i.imgur. com/TLs8Y.jpg
Click to expand...
Click to collapse
It would seem to be a software issue, where the launcher believes you are touching the nav bar so ignores input, that'd be my guess.
Try a different launcher maybe?

Another weird discovery. It seems that if I swipe over the dead-zone fast enough, it registers. That leads me to believe that it's a software problem, but after flashing stock ROM, un-rooting, and relocking I don't see how it could be. This is weird.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Its definitely a hardware problem you should RMA it