Related
Ok, so I have searched this forum until my eyes have bled and the closest I have come is a key which changes the HKLM/comm something or another from 1 to 0 (I'd have to look at the thread again to be specific).
Here is my issue...
I installed an app--WMWifi Router. It became shareware, and my key went bad. I un-installed it. Since then when my Wiz goes into standby mode it goes into a sort of BSOD (black screen of death) and wouldn't recover without a reset. After much frustration I discovered that my backlight would actually set itself to the lowest setting which simulated a BSOD (because it went totally black). I made a shortcut into programs for backlight, and soft-keyed it to make it easier...but frankly, it is a right royal pain in the ass to reset the backlight EVERY time my Wiz goes into sleep mode. Oh, and I had removed all the checks telling it to sleep mode, but it ate my battery worse than pacman going for a ghost! So I ended up checking them off but setting the time to the longest settings.
So...
I am seeking your help. I need a reg entry that will keep backlight set to a higher lighting, and will keep it at this setting even into sleep mode, so that all I have to do is hit a button and my Wiz awakens nice and bright (like it used to).
I am running NTS's Jag rom and it has been uber-stable until uninstalling the above mentioned application. It has been doing this backlight BSOD issue ONLY since installing/uninstalling WMWifi Router. I have hard reset, but my backup is a post un-installation backup...so if I cant find a reg key to work this issue out, I fear I will have to hard set and lose all data, and manually re-stage my Wiz (which is an absolute last ditch effort in my mind).
So please...help.
Your speedy response, assistance is much appreciated! Thank you in advance.
Jenn
??
Sorry to hear about a useless program like that jacking your rig.
Sad to say chief, but in all the time you spent bleeding your eyes reading, You could have already reflashed the rom and your programs.
5 mins to flash and MAYBE 15 mins installing the program you actually use, should be pretty easy if you're used to flashing new roms. You seem to know what you're doing, so that's a bonus!
The fix to the problem you're having is not even worth your time in my opinion, when you can redo the whole thing in less than 20 mins.
So unless you're just really not wanting to reflash, I doubt anyone will make a regkey for this (I don't know how, maybe someone will cause I wrote this
Goodluck
Thanks for responding to my thread.
The only reason I am hesitant to reflash is because I let my kids play on my laptop (I shoulda known better) and ended up having to reformat the damned thing...and lost a bunch of apps. So, you're right, normally it would take a whole 15-20 minutes out of my life, but since I use my laptop exclusively and it was just formatted...it will take a bit longer. BUT...good news, I have managed to recover most of my drive, so now it is a matter of weeding out things to find the progs I need to flash my Wiz...so it may still end up being easier--just time consuming.
Moral of the story...don't try to wifi your connection with soft that will take out your reg files when you un-install it...AND...no matter how much your kids fight and get on your last damned nerve, don't let them play on your laptop!!
I have a strange problem with my Hero that is hard to describe. Even before I rooted my phone I had this problem which leads me to believe it could possibly be a hardware malfunction. Anyways..
The problem is that over time after a complete wipe and flash of a custom rom (I've tried several) that my phones slowly deteriorates. It will be running fast and great for a week or two and then its starts to slow down to the point where it is completely unusable and I am forced to wipe and flash again. While its acting this way I have tried killings tasks, emptying cache, hard resets... every simple solution I can think of....
The other odd thing is that I use my phone very lightly. I only install 4-6 apps and those are the basics like pandora and such...
And I'd like to add that maybe I'm wrong about my phone acted this way when I had 1.6 official on it. It's been awhile.... so maybe I corrupted something when I rooted my phone for the first time?
Really I wish you could see the way my phone acts... its ridiculous . I would take a youtube video of it if I wasnt too lazy too. Crazy stuff like it taking a whole 30 seconds to a minute for a unlock pattern to finally go through, Or how when I try and type a phone number its like 3 or 4 presses "behind" as I type ( and im not typing quickly) or when I try to scroll through my contact list it just gets stuck and then finally it "catches up" and stutters all the way down to the bottom because of how many swipes I attempted.....
...help
have you tried.....?
Have you tried to run an RUU of eith 1.6 or 2.1? if you runn an RUU it will clear out any lerking "software" issues and then just re-root and try that out then try a custom rom after that.
Try Autokiller from the market. Once you install it, run it. Set the autokiller settings to something like Optimum or Strict (if that doesn't work for you, try Aggressive).
This will adjust the low memory killer settings to a more aggressive number. This, hopefully, will help.
smash58 said:
I have a strange problem with my Hero that is hard to describe. Even before I rooted my phone I had this problem which leads me to believe it could possibly be a hardware malfunction. Anyways..
The problem is that over time after a complete wipe and flash of a custom rom (I've tried several) that my phones slowly deteriorates. It will be running fast and great for a week or two and then its starts to slow down to the point where it is completely unusable and I am forced to wipe and flash again. While its acting this way I have tried killings tasks, emptying cache, hard resets... every simple solution I can think of....
The other odd thing is that I use my phone very lightly. I only install 4-6 apps and those are the basics like pandora and such...
And I'd like to add that maybe I'm wrong about my phone acted this way when I had 1.6 official on it. It's been awhile.... so maybe I corrupted something when I rooted my phone for the first time?
Really I wish you could see the way my phone acts... its ridiculous . I would take a youtube video of it if I wasnt too lazy too. Crazy stuff like it taking a whole 30 seconds to a minute for a unlock pattern to finally go through, Or how when I try and type a phone number its like 3 or 4 presses "behind" as I type ( and im not typing quickly) or when I try to scroll through my contact list it just gets stuck and then finally it "catches up" and stutters all the way down to the bottom because of how many swipes I attempted.....
...help
Click to expand...
Click to collapse
tkirton said:
Try Autokiller from the market. Once you install it, run it. Set the autokiller settings to something like Optimum or Strict (if that doesn't work for you, try Aggressive).
This will adjust the low memory killer settings to a more aggressive number. This, hopefully, will help.
Click to expand...
Click to collapse
I agree. I use auto killer on aggressive with CM6 and it runs great forever
My phone does the exact same thing!
I first really noticed it when I flashed the official sprint 2.1 update. I think it has something to do with the buildup of cache on the phone.
I have been running CM6 for a little over a month and have recently noticed it getting slightly hung up at times, but nothing compared to how it was with the official 2.1 update. Also, remember that CM6 does not have Sense, which can really slow down the phone.
I also I agree with you that it seemed like my phone did not do this on 1.6, but it has been quite sometime since I flashed 2.1.
Does anyone know what really causes this exponential slow down; to the point where the phone is barely useable?
hm... I will try autokiller.....thanks for the advice
as for CM6..... I've tried not using sense UI but to me its my favorite part of my phone... for example the facebook/twitter/flickr integration with my contact list is invaluable.... is there a replacement for this?
is anyone else able to add anything else?
smash58 said:
hm... I will try autokiller.....thanks for the advice
as for CM6..... I've tried not using sense UI but to me its my favorite part of my phone... for example the facebook/twitter/flickr integration with my contact list is invaluable.... is there a replacement for this?
is anyone else able to add anything else?
Click to expand...
Click to collapse
Try Zen-Rom. It has all that you are looking for and is very fast and stable.
Sent from my Zen-Rom Hero!
Auto killer is the way to go. I found Aggressive setting too much for my tastes; if I was on a webpage, then went to the home screen for something else and opened back up the browser, it would have to reload it because it was killed. I set it on optimum, and get no slow down, and can still truly multi task.
chefthomas99 said:
Try Zen-Rom. It has all that you are looking for and is very fast and stable.
Sent from my Zen-Rom Hero!
Click to expand...
Click to collapse
Or NFX-Hero. I'm not a Sense guy, but I've experimented with that ROM, and it was the fastest Sense 2.1 IMO.
Just curious but does pandora have a cache file on your sdcard? I had an app that was reading and writting to a cache on my sdcard and it would slow my phone down a lot. When your phone slows try ditching some of your apps and see if maybe one could be responsible for it, if it is there are tons of options different apps that do the same thing.
Hi everyone,
I searched before I posted, but couldn't find a similar issue.
I'm running Cognition 3.04, and touch input seems to freeze up. If I let the screen go to 'sleep' and unlock the phone it will work for a few seconds, then start freezing again. Sometimes I can just wait a couple seconds and it will accept input. Even after a reboot, it will start this behavior after a few minutes.
The issue goes away when I go back to stock 2.1, though.
I realize the obvious solution is to stay with stock, but I was just curious if anyone else had experienced this and knew of a better solution (who wants to be on stock).
Thanks in advance.
That has happened to me before. Went away with a fresh flash and wipe of cache.
canadaboy37 said:
Hi everyone,
I searched before I posted, but couldn't find a similar issue.
I'm running Cognition 3.04, and touch input seems to freeze up. If I let the screen go to 'sleep' and unlock the phone it will work for a few seconds, then start freezing again. Sometimes I can just wait a couple seconds and it will accept input. Even after a reboot, it will start this behavior after a few minutes.
The issue goes away when I go back to stock 2.1, though.
I realize the obvious solution is to stay with stock, but I was just curious if anyone else had experienced this and knew of a better solution (who wants to be on stock).
Thanks in advance.
Click to expand...
Click to collapse
You didn't restore system data when you flashed this, did you?
canadaboy37 said:
Hi everyone,
I searched before I posted, but couldn't find a similar issue.
I'm running Cognition 3.04, and touch input seems to freeze up. If I let the screen go to 'sleep' and unlock the phone it will work for a few seconds, then start freezing again. Sometimes I can just wait a couple seconds and it will accept input. Even after a reboot, it will start this behavior after a few minutes.
The issue goes away when I go back to stock 2.1, though.
Thanks in advance.
Click to expand...
Click to collapse
Do you have any over/underclock settings applied? Are there are any voltage settings that you find?
cappysw10 said:
You didn't restore system data when you flashed this, did you?
Click to expand...
Click to collapse
The first time I flashed, I did that which I later realized to be a huge mistake. When this issue started, I flashed back to stock did a master clear and reflashed Cog, but the issue remains. Is there some step I missed in clearing out the old stuff?
This happens to me in swype occasionally. Super annoying bc it thinks I am taking my finger off the screen when I am not causing swype to be worthless. after a reboot it goes away
Sent from my SAMSUNG-SGH-I897 using XDA App
trekie86 said:
Do you have any over/underclock settings applied? Are there are any voltage settings that you find?
Click to expand...
Click to collapse
I haven't played with anything other than flashing Cognition onto the phone.
I'm going to try going through the whole thing again, but this time not reinstalling any old apps/data through Titanium Backup. I'll set everything from scratch and see if that makes a difference.
Hello...
I'm a newbie to modding phones (obvious from the question/problem I've about to ask). I have an HTC Inspire and I followed the one click rooting guide and installed Coredroid7 with the 3rd set of radio/RIL listed in that thread. With a bit of a struggle I got it working - worked great and I loved it. Unfortunately I found on the market place an app (Overclock Widget by Billy Cui ) - clicked on "load on boot" and a few bad settings and the entire phone froze. Since then whenever I boot my phone is stuck on the white screen with green HTC logo. The config on my phone is:
s-off
hboot 0.85.0019
micop-0438
radio 26.09.04.11_m2
emmc boot
I've googled all of the internet and followed advice such as reflashing the radio/RIL. went into recover and typed the "adb shell, etc... to remove files indicated (but they were not there)". tried to do recover but the recovery files werent there. At this state, there is only so many combinations you can do and I feel I have done it all.
there are a lot of advice on set cpu problem with other HTC devices but none of them work/can be applied to the Inspire.
Can someone please help me? In your answer please answer me in a dumb down way - keeping in mind I am new and have a hard time understanding acroynms and how to perform complex operations with the hint of a word phrase (ie - please be explicit for me on how to flash radio, instead of saying flash radio XYZ)
Thanks in advance
PS: I am already nervous/scared of what has happened, I am hoping I don't have to do a eng s-off as part of the solution please
based on my description (white screen with HTC logo) have i bricked my phone or is it in a boot loop?
i tried the following
http://forum.xda-developers.com/showthread.php?t=1033353
and when i say install PD98IMG.zip it just says installation aborted. This is the image I got from Coredroid7 that was working before the problem started.
also tried this:
http://forum.androidcentral.com/lg-...cks/50301-setcpu-forgot-uncheck-set-boot.html
but my phone does not have the file they wanted me to delete
If you see the white HTC logo your always okay. The problem comes when there is nothing showing, you must have changed some settings that won't let the phone complete some core processes.
This can easily be fixed by pulling battery hold volume down button and power and booting into Hboot. Then go into recovery factory reset and wipe dalvik_cache(under advanced) and flash the desired ROM or do a restore from a point your phone worked perfectly.
Sent from my Inspire 4G using XDA Premium App
ThEiiNoCeNT said:
If you see the white HTC logo your always okay. The problem comes when there is nothing showing, you must have changed some settings that won't let the phone complete some core processes.
This can easily be fixed by pulling battery hold volume down button and power and booting into Hboot. Then go into recovery factory reset and wipe dalvik_cache(under advanced) and flash the desired ROM or do a restore from a point your phone worked perfectly.
Sent from my Inspire 4G using XDA Premium App
Click to expand...
Click to collapse
First... THANK YOU very very much for telling me it is not as bad as it seems.
I have done the following:
go into hboot
recovery option
wipe dalvik
flash coredroid7 again by having it be embedded in PD98IMG.zip however like mentioned above this fails.
Right now I am redoing the process again by formatting my sdcard, creating /download to put the PD98IMG.zip in follow the procedures again above. In case this fails, what are my options?
thanks for the guidance. i flashed it again with:
CoreDroid_Desire_HD_GB_2.3.3_V7.0_RV
and I am out of the white screen mode.
Just remember if your phone boots up but not all the way its still ok you can save it. The easiest although most annoying solution is reflash the rom. Also i know you hear about people bricking there phone. I truly think its harder than anyone thinks. Good luck with the inspire. Also if you want overclocking/underclocking stick with setcpu(you can get it free for being an xda member just search xda). Let it auto detect speeds. Give it root permission (itll pop up asking make sure you check remember above the allow button). If your overclocking I recommend staying undler 1.6 ghz (1600 on setcpu) and go to profile select enable. Then set up a profile for screen off and set it for around 300 mhz to help with battery life.
Carlrobling said:
Just remember if your phone boots up but not all the way its still ok you can save it. The easiest although most annoying solution is reflash the rom. Also i know you hear about people bricking there phone. I truly think its harder than anyone thinks. Good luck with the inspire. Also if you want overclocking/underclocking stick with setcpu(you can get it free for being an xda member just search xda). Let it auto detect speeds. Give it root permission (itll pop up asking make sure you check remember above the allow button). If your overclocking I recommend staying undler 1.6 ghz (1600 on setcpu) and go to profile select enable. Then set up a profile for screen off and set it for around 300 mhz to help with battery life.
Click to expand...
Click to collapse
I think I've had about every kind of soft boot thre is on the sticky guide, and one that isn't, and I have always been able to recover (knock on wood). Even black screens...
I was stuck in a similar situation once:I forgot to take off "load on boot" and increased the max speed all the way to like 1.9. And phone froze.
SetCPU gets permissions in the process of phone boot up, after the whole OS is loaded. There is a tiny time gap between home screen coming up, and SetCPU being granted SU permissions. So this is what I did:
I did a reboot. And after the phone starts, without giving any time opened the app drawer for "SuperUser" app, and took off SetCPU permissions from there. This denied SetCPU of it permissions and it was loaded at default speeds. Then I went into Settings-->Applications, and erased all SetCPU data.
Well, it took me like 3-4 reboots before I could master the timing to get to SuperUser and take off SetCPU from there. But it atleast saved me the hazzle of reflashing everything again. And yes sir, I forgot to take a nandroid backup
thanks
Thanks All
Problem fixed
same issue only worse
I have the same situation. I flashed absolution 2.0 last night. Everything went good. Turned it on this morning seemed to work fine also then I turned it off for work and tried turning it back on at the end of the day and it just runs a loop. I can get to the HBOOT menu but I only have 5 options; fastboot, recovery, factory reset, sim lock, and image crc. There is no advance settings and when I choose any of the available options nothing happens except the phone reboots (crc does run a check but then nothing). Hooked to my pc and it says found android 1.0 but I can't do anything with it. I have also pulled the battery and sims card.
freedompc said:
I have the same situation. I flashed absolution 2.0 last night. Everything went good. Turned it on this morning seemed to work fine also then I turned it off for work and tried turning it back on at the end of the day and it just runs a loop. I can get to the HBOOT menu but I only have 5 options; fastboot, recovery, factory reset, sim lock, and image crc. There is no advance settings and when I choose any of the available options nothing happens except the phone reboots (crc does run a check but then nothing). Hooked to my pc and it says found android 1.0 but I can't do anything with it. I have also pulled the battery and sims card.
Click to expand...
Click to collapse
What happens when you select recovery and press power?
It just turns off and starts back up and runs its loop. Same for fastboot and factory reboot.
Go here, I've already informed attn1 and his group that you'd be coming.
Going to the link.
They'll get ya fixed up.
Thanks TX. Those guys on that site were awesome. Attn1 worked with me for over an hour. Unfortunately, my phone itself has a hardware failure. Never the less, GREAT support. I wish there was a thank you button for them. This was my first android phone (lasted 3 months) and b/c of the DEV's and other members it won't be my last. Just hope the next one lasts longer.
freedompc said:
Thanks TX. Those guys on that site were awesome. Attn1 worked with me for over an hour. Unfortunately, my phone itself has a hardware failure. Never the less, GREAT support. I wish there was a thank you button for them. This was my first android phone (lasted 3 months) and b/c of the DEV's and other members it won't be my last. Just hope the next one lasts longer.
Click to expand...
Click to collapse
Dang man, that sucks. I can honestly say I've never had a device fail like that.
Good luck on your next device, whatever it may be.
Tx
Disregard... posted in error
sent from my secret agent phone in my shoe
So I have the i9020T (from Wind in Canada). I enjoyed running CM9 nightlies on it, but then Jellybean came along and I went nutso over it (like so many others). I flashed back to stock ICS, and then ran the OTA update on it to JB.
My experience has been disappointing. It was unfathomably slow. It was running-Windows-7-on-a-Pentium-III slow. The new UI and features are glorious, but I need a lot of patience if I expected to use them. I'm talking about delays of around 5 seconds to start an app, switch apps, or even open the app drawer, 2-3 seconds lag when bringing up the keyboard, and 5-10 seconds to bring up Google Now.
I automatically decided to nuke everything and start from a clean slate. I grabbed the 4.1.1 stock image from Google, then formatted /system and threw it on. After the initial setup, and before I even got to rooting the thing (never mind restoring from Titanium), it was still muscle-atrophyingly slow.
I ended up just restoring all of my apps and data, and using it as-is, figuring this is what I should expect from an older device. Yet everyone online raves about how much faster JB is than ICS on the Nexus S. Either you're all trolling me really hard, or I'm doing something very wrong.
Here's some more gory details:
Like I said, I wiped /system before loading the new image. I did it on the phone using Clockworkmod recovery, then used fastboot from my computer to load the image. I did not wipe data or cache, because I figured the whole image-writing thing would be obliterating all my stuff anyway, but perhaps I was wrong?
I've been playing with the CPU usage overlay, available in the Developer Options. First off, I have no clue what the different colours mean or what scale those bars represent, but I can tell you my load is typically 2.0 (even just sitting there idle with the screen on), all the way up to 15 or so if I'm trying to do something like use Chrome while listening to Google Play Music. system_server is always the top process, and its bar is always 3-4 times bigger than the next, with the sole exception of loading up Google Play Music, in which case the mediaserver process holds the top spot with a fairly long bar. ksmd, com.android.systemui, surfaceflinger, and com.android.phone are always running, but only ksmd even has a bar long enough to be visible. Other processes pop in and out, and of course they start going willy-nilly when I actually start using apps and switching between them.
There have been a handful of times where an app will die while I'm in the middle of using it, and 2-3 times the phone has outright rebooted itself.
So there's my story. Can someone tell me if I'm just plain doing it wrong? Perhaps there's a guide on how to completely sterilize the phone before loading the stock image? Or perhaps my hardware is broken? :-/
I was with you there, trying to figure out why everyone thought it was so fast and I was being left in the dust. Google Now in particular was painful to interact with. I downloaded and installed Air Kernel, which seemed to help a little bit but then I switched the CPU governor from "ON DEMAND" to "SMARTASSV2" and it was like night and day. It's flying and I'm satisfied.
Cool... I'm looking into it, and can't find any directions whatsoever on what I should download or how to install it. I'll keep digging, though. Thanks!
While I am not sure what is causing your issue I can confirm that stock jb should not be performing like you are describing. Except for loading up Google now. That does take some time but even that once its loaded runs OK.
Did you clear your SD card? If not back that up to a computer and wipe it. That's all that I can think of and it may actually fix it.
At first I noticed painfully slow speeds as well. Changing my min setting to 200 helped so much! I've heard the the Interactive governor is amazing with JB in terms of speed. You could try that out.
Nexus S. (GSM i9020a)
Paranoid (1.97 - 4.1.1)
Matrix (CFS - 22.5)
Ondemmand (1000/200)
Deep Idle (On - Deadline)
I've just flashed Air Kernel (I just picked one of four options, I don't know what the heck "blue color" means), then set the governor to smartassv2, and so far it feels snappier. I'll have to keep using it to see if it's the solution I need. Thanks to all who've made suggestions so far!
Sent from my Nexus S using xda app-developers app
If your phone is going crazy slow it could be a number of things like apps could be slowing down the phone in the background or the phone might be trying to sync. You could backup all of your apps and then wipe your phone fully it should speed it up quite a bit and then you can restore each app 1 by 1 to determine if its a rogue app causing it. But if you can't be arsed to do that and wipe then just try and flash Thalamus kernel and see what its like if you set the governor to interactive on that it should go crazy fast.
Sent from my Crespo using xda premium
Please provide clear advice Nexus S so slow on Jelly Bean
ronnygunz said:
I was with you there, trying to figure out why everyone thought it was so fast and I was being left in the dust. Google Now in particular was painful to interact with. I downloaded and installed Air Kernel, which seemed to help a little bit but then I switched the CPU governor from "ON DEMAND" to "SMARTASSV2" and it was like night and day. It's flying and I'm satisfied.
Click to expand...
Click to collapse
I can see there are many 'fixes' for slow running devices on Jelly Bean. However, I have no idea:
1. how install Air Kernel or where to get it from
2. How to change the CPU governor from "on-Demand" to "SMARTASSV2" or where to download this from
Please can someone give me the complete idiots guide to getting my Nexus S running properly again??
THANK YOU
There are a million guides on this forum for all of this. If you don't know how to flash a kernel or adjust CPU speeds, you need to familiarize yourself with these things and understand the risks. First off, try cleaning your phone up. Take all your important stuff off your external storage, and do a factory reset. My Nexus S never ever ran slow, even on stock.
Have you tried a more simple but fast kernel like marmite 4.2 from bedalus? Give it a try.