Related
k i read about an app called spare parts on here so i figured hey i'll try it out. i did saw what extra setting were there and decided i wasn't gonna use it didn't even change any settings.
after opening the app and then pressing home something wierd happened i saw a white screen with HTC in green in the center for about 3-5 seconds my backround with a loading pop-up and nothing else for about another 3-5 seconds. this is happening every time i press the home button or exit out of an app. it's getting infuriating, i'm also getting wicked bad lagg in sense and lot's of hang up's and force closes. also wicked bad battery life. i don't know what to do to fix it.
i have the OTA and rooted last night with unrevoked method, this morning is when i tried the app around 10 or 11 not sure last couple days is a blur.
can anyone help, how can i restore what i had previously, do i have to do a full wipe.
nobody...... anyone plz, it is cripling my evo
thorpe24 said:
k i read about an app called spare parts on here so i figured hey i'll try it out. i did saw what extra setting were there and decided i wasn't gonna use it didn't even change any settings.
after opening the app and then pressing home something wierd happened i saw a white screen with HTC in green in the center for about 3-5 seconds my backround with a loading pop-up and nothing else for about another 3-5 seconds. this is happening every time i press the home button or exit out of an app. it's getting infuriating, i'm also getting wicked bad lagg in sense and lot's of hang up's and force closes. also wicked bad battery life. i don't know what to do to fix it.
i have the OTA and rooted last night with unrevoked method, this morning is when i tried the app around 10 or 11 not sure last couple days is a blur.
can anyone help, how can i restore what i had previously, do i have to do a full wipe.
Click to expand...
Click to collapse
get used to it if you intend to use sense, the screen you speak of is sort of like the htc sense/rosie intro. If you dont like it you can go vanilla and use another launcher, like adw froyo,launcherpro, or even the extra launcher thats included....
Sounds like you enabled aggressive handling of apps. Can you get in there to turn it off?
jmxp69 said:
Sounds like you enabled aggressive handling of apps. Can you get in there to turn it off?
Click to expand...
Click to collapse
Or just do a factory reset.
also, you are experiencing some isolated problems which leads me to beleive the issue is software related rather than hardware.I have experienced NOT ONE of the issues you speak of. Make sure you update prl. I can vouch for that one. My data was 90% broken till i did. Also try and wipe data, that would prolly fix everything as well.....FYI, i cannot gurantee the problem lies with your hardware OR software. Thats just my diagnosis. Good luck
Thats what it was the agressive handling of processes thanks alot guys feel like a fool.....
Sent from my PC36100 using Tapatalk
thorpe24 said:
Thats what it was the agressive handling of processes thanks alot guys feel like a fool.....
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Heh...I did that once on my hero. I know the feeling.
some versions of spare parts come with a launcher. the problem is that when you press the home button now, it's trying to goof with /system, which is forcing the reboot. even though you may be rooted, you don't have rw privileges in /system while messing with android.
you may be able to get away with accessing /system and erasing your goofy installed spare parts app. you'll have to do that through adb shell, and the custom recovery. do a search for 'remove apps', you should find it easily enough. i think the thread was moved from dev to general, or q and a.
anything that will call a write to /system (i.e. a rooted app that needs access to it to work right) has the potential to cause the phone to reboot. when i installed adfree, it had the same effect. trying to install hosts (which write to /system/etc) caused a reboot. i had to install hosts through recovery with a push after remount.
hope that helps
Hmm I installed autokiller and it appears to work doesn't mess with anything that is
I really dunno a way of testing that its actually working though if you where looking for a way to manage memory
I was using a task killer but read up on stuff and turned it off just keeping it in case I need it for something that wont close and the phone is running great and battery life keeps getting better and better.
Sent from my PC36100 using Tapatalk
autokiller
People you need to be careful with autokillers!
Make sure that you are not closing down sense items.
Put anything that says htc or sense on ignore.
If not you are shutting down parts of sense. Then sense has to reboot. Witch is why you see the white screen with the htc logo in the middle.
does anyone know of a way to disable the vibrate that takes place during startup,x power off or reboot? Its probally right in my face and im just overlooking how to disable it.
also just noticed even when mine is on silent i still get the vibrate on said functions.
either im getting no replies cause of my ignorance or others sit and scratch heads as well.
I think that's the one vibration you can't get rid of...this might be able to happen with a custom recovery, so post this q in the development section and see what you get.
thanks for answering. As for posting this in the dev section, lol...no way, itll get moved back here to Q&A so fast it wont get 1 reply because its not a rom or mod. Unfortunatly ill have to wait till someone does know and happens to stumble upon my thread before it gets pushed to page 2 cause then its a lost cause. thanks for atleast replying though...l8ter, veritas
Sent from my HTC Vision using XDA Premium App
Not sure this is something you can change, and if you can it won't be easy. A custom Boot animation won't effect it because the vibrate comes before the animation anyways. Not sure man, sorry.
Yea I don't think it's possible to change the vib setting. Maybe it's the phones way of letting you know it's turned on as a fail safe, I mean incase the screen breaks etc.
I found this app https://market.android.com/details?id=eu.chainfire.nomoarpowah
Actually works only for some samsung devices, but the idea is good
Infact the app is able to switch on the phone when the alarms is going to be activated, even if the phone is completely turned off, in order to make it ring..The unique requirements is that the phone is under charging and is rooted of course
I think the same can be applied to our desire as well, because when the charger is connected, the kernel should be loaded, correct me if im wrong
So this mean that we (but not me ) can modify the kernel in order to do a simple thing: it have to check the current time in order to reboot the phone when the time is going to be near to the time set by the stock alarm app (the alarm time is of course written somewhere on the /data partition)
Anyone can say if this can be done through some changes to the kernel?
I know that the solution is to leave the phone on or in airplane mode, but this could be a nice feature for our "old" desire, at least when its charging; but i think that everyone charge it on night and have the alarm set for the morning
Thanks in advance and sorry for my english
Bump! No one have an idea if this can be done?? And no one like this idea?
I thought this already worked.
I was sure my alarm went off on a plane before when the phone was off...
Lothaen said:
I thought this already worked.
I was sure my alarm went off on a plane before when the phone was off...
Click to expand...
Click to collapse
lol, impossible
Lothaen said:
I thought this already worked.
I was sure my alarm went off on a plane before when the phone was off...
Click to expand...
Click to collapse
Absolutely not...If ur phone is completely turned off, the phone will remain off forever (even if the alarm is set) untill u turn it on obviuosly
I think I remember my old Samsung dumb phone done that anyway.. if the phone was off the alarm would still sound... maybe it is a Samsung feature? Does the desire have a charging screen when the phone is off?
Edit: desire screen doesn't stay on, Samsung one does (my friends sgs does anyway). Only led on when charging desire...
Sent from my HTC Desire using XDA App
My SE-P1i (Symbian UIQ 3.0) was working in that way. This is an OS issue as well.
Sent from my HTC Desire using XDA App
mattmanwrx said:
Edit: desire screen doesn't stay on, Samsung one does (my friends sgs does anyway). Only led on when charging desire...
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
That's correct, but the led color is controlled by the kernel..When chargin is amber, when full charge is green, this mean we can implemnt some logics on the kernel as well..For example we can implement in the kernel something like reboot (turn on) the phone when the alarm is going to ring (reading the setting from the phone file system)
andQlimax said:
That's correct, but the led color is controlled by the kernel..When chargin is amber, when full charge is green, this mean we can implemnt some logics on the kernel as well..For example we can implement in the kernel something like reboot (turn on) the phone when the alarm is going to ring (reading the setting from the phone file system)
Click to expand...
Click to collapse
Seems logical and and theoretically would work... however, I know my phone takes a long time to boot... others more, others less, so how long would you be starting the phone before alarm? 15 minutes?
Sent from my HTC Desire using XDA App
mattmanwrx said:
Seems logical and and theoretically would work... however, I know my phone takes a long time to boot... others more, others less, so how long would you be starting the phone before alarm? 15 minutes?
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Well, my phone is about standard for the boot time, is about 1 minute (even on stock sense, custom sense roms, aosp roms)..5 minutes before the alarm is enough..But I don't think this is a big problem, even 15 minutes before, just to be sure, it's ok..We just need someone that is able to do the necessary kernel changes (if this is possible; seems strange that no one never implemented this kind of logics when the phone is off under charging)
andQlimax said:
I don't like hibernation mode as is the same as put the phone in airplane mode, the phone remain still on
my idea is to make the phone ring with the phone completely turned off, and seems possible if the phone is on charging (even if off)
Click to expand...
Click to collapse
Quoted from manu kernel thread...
So the actual idea is to make the phone ring.so you don't miss a call? Would the phone not need to be "on" constantly... and if so, why not just leave it on charge overnight? That's what I do?
Sent from my HTC Desire using XDA App
I mean make the alarm clock ring...
andQlimax said:
I mean make the alarm clock ring...
Click to expand...
Click to collapse
I was gonna say just leave it on... but yea, boot the phone 5-10 mins (maybe users choice?) before the alarm sounds... I do like it...
Sent from my HTC Desire using XDA App
It´s interesting to think about this and see if it´s technically possible.
But I don´t get the motivation behind it
Why turn the phone completely off if it´s supposed to hang on the cable anyway? To save the 5-20 mA it uses when in airplane-mode?
germanhoss said:
It´s interesting to think about this and see if it´s technically possible.
But I don´t get the motivation behind it
Click to expand...
Click to collapse
The motivation is exactly that, see if it is technically possible..I agree that is not a great advantage having that feature..
Would be nice I think, even nicer if it worked without having it charging.
Nionor said:
Would be nice I think, even nicer if it worked without having it charging.
Click to expand...
Click to collapse
But the charging is what is keeping the kernel awake... otherwise you nay as have the phone on..
Sent from my HTC Desire using XDA App
Nionor said:
Would be nice I think, even nicer if it worked without having it charging.
Click to expand...
Click to collapse
That actually could work only if the hardware will support a sort of "wake up from power off" functionality (our desire hardware support it???)..Like pc and some nokia have..
Alarm and Calendar event reminders goes off after reboot or restart!
I have captivate that runs on Firefly froyo ROM. I have an alarm set in my phone that is supposed to sound every morning. But when I reboot my phone everytime for replacing the spare battery, the alarm is not re activated. In simple works, alarm scheduled to sound everyday does not reactivate itself after reboot. Have to open the alarm, disable it and again enable to reactivate it.
Any solution for this. Also any app that solves the problem? Same thing happens with calendar reminder events. After reboot, the calendar reminder events do not work. HAve to go to the calendar app for it to activate. Any alternate apps for the problem?
I think it must be possible what did my previous phone Nokia 6220 classic had that my newer fella doesn't have it, and that phone could do it. Actually, it turned on a little sooner to ring exactly at the time you've wanted it.
But trust me it isn't that much good you know especially when you don't know there's such a feature. You've turned off your phone and you're sleeping you would kill anyone who dared to wake you up and suddenly a death metal music starts ringing 5:30 in the morning, you got the point :banghead:
Sent from my HTC Desire using Tapatalk
Not sure if anyone found a fix, but someone on the Google Code forum has found a solution. I am NOT taking credit for his fix, simply getting it out there as it is a huge issue.
1) Open up the .zip for your custom or stock Rom and look in the /system folder for a file called "build.prob". Copy this to your Desktop as you will be editing the file and then replacing the original on the Rom.
2) Open Notepad++ or any text editor of your choice and open the file. You are going to want to search for a line that says:
# try to disable proximity sensor in call by default
gsm.proximity.enable=false
Uncomment that line and make it equal to false.
3) Next, copy it back onto the /system directory of the Rom and then flash it. If it doesn't work for you, I am sorry. This is what worked for me so I just wanted to get another solution out there.
Again, I did not make this solution! I found it on Google Code forums.
Enjoy!
What problem does this fix ?
After making a phone call, there should be a process called Dialer. It gradually increases over time to 99% and kills the battery
Sent from my HTC Wildfire S A510e using XDA App
Small correction
Hey, small correction to your above post, hopefully this helps somebody out there
The file is actually build.prop
And the original commented line looks like the below WITH the hash in front
# try to disable proximity sensor in call by default
#gsm.proximity.enable=false
Instead of reflashing the ROM I booted the phone into recovery, then did
adb shell
adb mount /system
exited the adb shell, then
adb pull /system/build.prop c:\temp
edit c:\temp\build.prop, removed the comment hash
adb push c:\temp\build.prop /system/build.prop
rebooted, made a call, watching the battery usage, and dialer isn't at 98% after 30 minutes, in fact, it hasn't even shown its ugly face!
Awesome, thanks for that find!
Ah. Been reading posts all over and they all say to remove the hash tag. I'll give this a try later. You can for sure tell its not showing up after a reboot, power off, etc.? This really is an frustrating bug we have on our hands and I for one hate having a phone that lasts ~5 on a ful charge.
Sent from my HTC Wildfire S A510e using XDA App
Quick question. Dialer is already in my processes running. Will it still work or do I need to clear it first, cause I have no idea how to do that lol.
Sent from my HTC Wildfire S A510e using XDA App
Need your help. I'm trying to run these commands, but they aren't working for me. When I go to type adb shell mount /system, it keeps saying adb: not found. Any help with this? I used to be able to do this, but it's not letting me do it
Please clarify one thing for me...
I don't know for sure but this seems to disable the phone's proximity sensor during calls, so the screen will be always on while calls are being made (until the screen timeout activates).
Am I right? If so this fixes one bug and creates another problem.
I would be glad if someone that already tried this can confirm what I'm thinking.
Thanks a lot in advance.
Confirmed,i used this long time ago and the display stayed on for whole time during call and also proximity was disabled for screen auto brightnes(probably more apps)
aigaming said:
Confirmed,i used this long time ago and the display stayed on for whole time during call and also proximity was disabled for screen auto brightnes(probably more apps)
Click to expand...
Click to collapse
But it seemed to work for me. I did it and rebooted my phone and the Dialer process was gone. I then made a test call and while the call was on, the Dialer process was not there. Then, I kept checking and it still did not appear. I also applied the best battey tip you'll ever need.
aigaming said:
Confirmed,i used this long time ago and the display stayed on for whole time during call and also proximity was disabled for screen auto brightnes(probably more apps)
Click to expand...
Click to collapse
aigaming, thanks a lot for confirming what I already suspected.
This is a "fix" that creates an even bigger problem.
Last week I had a phone call with an Engineer that lasted more than 80 minutes.
If the screen was on during this period then instead of the Dialer draining the battery I would have the LCD draining the battery.
I don't need the proximity sensor for auto-brightness for example (like to set it on my own) but it shouldn't be turned off because it's probably necessary for the camera application (for example).
This Dialer battery drain is just a cosmetic bug IMO.
If we want to know what really eats our batteries then we should use *#*#4636#*#*, usage statistics instead.
There is info in miliseconds of usage by each app.
And what about fix for S-ON phones?
shaarky said:
And what about fix for S-ON phones?
Click to expand...
Click to collapse
If you edit the file, replace it on the ROM and flash it, then this method works on s-on phones. Be warned that the screen will remain on during calls.
miguelca said:
I guess that's off-topic here. This thread is about another problem.
Click to expand...
Click to collapse
Well, I mean if there is some way to apply this on S-ON phone.I think it's not, so better to update name of the thread...
I also interested in fix for battery drain on s-on phones. Mine adb says permission denied.=(
shaarky said:
Well, I mean if there is some way to apply this on S-ON phone.I think it's not, so better to update name of the thread...
Click to expand...
Click to collapse
The method drzerog uses is for s-off phones. The method on the first post works with all, s-on included.
Sent from my HTC Wildfire S A510e using XDA App
shaarky said:
Well, I mean if there is some way to apply this on S-ON phone.I think it's not, so better to update name of the thread...
Click to expand...
Click to collapse
I updated my posts. Sorry for the mistakes but now info is correct. Please read again. Thanks.
Sent from my HTC Wildfire S A510e using XDA App
I can also confirm that, for me, during a call it does NOT leave the screen on. It turns it off on my device. Maybe it's different for each phone? But that can't be. Weird. Again, confirming it works on my device and my battery is now showing proper statistics, as well as Dialer process not appearing
Also wanted to make note that I have changed the topic title and noticed this thread is now in the rom/recovery/guides/kernal/root stickie!! VERY COOL!
Not work for my WS rom 2.3.5 stock/ S-OFF, the dialer process still keep 92%
Alright, so my girlfriend's Samsung Galaxy S II started to go through these weird partial reboots several weeks ago (maybe even months). The phone would randomly go black, play the stupid shutdown/startup (dont remember which) jingle...then just simply be at the lock screen with a crossed out circle where the signal bars would be (for just a couple of seconds). When this happened, I used to just tell her to shutdown the phone, take out the battery, and let it sit for about 30 seconds, then put everything back together and start it back up. This seemed to work, which made me think it might have just been a software or at worst a memory issue of some kind.
This issue was always intermittent, but now, no matter what I do, it just keeps looping this "restarting" problem. I can't access any internal memory space from my computer because in the time it takes to connect, it just "reboots" again. I made a logcat of the phone up until the "reboot", and in doing so noticed that when I would browse the phone via adb shell, I saw no mount for the sd card...which then lead me to believe maybe it was an issue with that. I checked the sd card for corruption (and prior to even using it, checked that all blocks were read/writable (legit)), but that led nowhere.
Anyways, not having any idea where to go next, nor where to begin or what to look for in the 5000+ lined logcat, I turn to xda with hopes of getting some sort of help. Thanks in advance for any I get!
EDIT: Oops, some other important notes I didn't mention (other than in title); this is running stock firmware, only OTA. I tried once to upgrade her to ICS via Kies, but the upgrade would never complete. She also refused to let me root her phone...so unless there is a stock recovery mode, her phone has none...
bump, as its been a week and no responses. If anyone has any ideas or can figure out whats wrong from the logcat, please help.
Almost 3 weeks...no answer...isn't there at least 1 person who has an idea or can deduce one from the logcat? Pretty soon I'm gonna have to tell her to give up and get it "fixed" (ie, swapped for a refurb with most likely all her data lost)...
EarthBoundX5 said:
Almost 3 weeks...no answer...isn't there at least 1 person who has an idea or can deduce one from the logcat? Pretty soon I'm gonna have to tell her to give up and get it "fixed" (ie, swapped for a refurb with most likely all her data lost)...
Click to expand...
Click to collapse
Looking at the logcat if it is accurate the problem is overheating and it is shutting itself down. That's why it keeps rebooting from I read but I could be wrong. Also looks like it has wakelock issues. Lot of wakelock errors in logcat. Some app or apps are causing the wakelock issue find them and remove them that might solve the problem.
Sent from my SGH-T989 using Tapatalk
EarthBoundX5 said:
Almost 3 weeks...no answer...isn't there at least 1 person who has an idea or can deduce one from the logcat? Pretty soon I'm gonna have to tell her to give up and get it "fixed" (ie, swapped for a refurb with most likely all her data lost)...
Click to expand...
Click to collapse
i say try to odin back her phone to stock on here there a good post for it to get her back and if she had Gmail sync there shouldnt be a problem unless she really dont want to download everything again i say give odin a shot and then from there upgrade through kies its tricky you have to make sure you have 50% battery life or more and kies errrors out sometimes but it does work i update my friends phone as he does not like all the root stuff lol so i always your kies after a couple errors it will work and thats your best option if she doesnt want to loose anything kies will back it all up for her and are you sure that power button aint sticking sounds like you have a looping issue are you able to go into download mode or are you familiar with this ?
Idk how to read logcats but another idea could be you have the sticky power button issue. I think if it was overheating u would feel it and mention it in the op.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
I used to have this problem when my phone was on ICS. I found that putting it back to GB, and using custom JB roms fixed it. I'd try those.
For starters, thanks everyone for the responses! After this long, its really great to see so many in one day!
richardlibeau said:
Looking at the logcat if it is accurate the problem is overheating and it is shutting itself down. That's why it keeps rebooting from I read but I could be wrong. Also looks like it has wakelock issues. Lot of wakelock errors in logcat. Some app or apps are causing the wakelock issue find them and remove them that might solve the problem.
Click to expand...
Click to collapse
Thats what I thought, because it seemed to get exceptionally hot before "rebooting"...at first...then I was noticing it "rebooting" when clearly cold. If it is indeed overheating like I had thought in the very beginning, is there anything I can do about it? What does it use for heat conductivity and displacement? And for that matter, I would think if it was overheating though, it would actually reboot, not the half-ass semi-reboot its been doing...
And what is wakelock exactly that it would cause an issue? Only apps I see using it are WootWatcher, KeyguardViewMediator and PowerManagerService.
krazierokz said:
i say try to odin back her phone to stock on here there a good post for it to get her back and if she had Gmail sync there shouldnt be a problem unless she really dont want to download everything again i say give odin a shot and then from there upgrade through kies its tricky you have to make sure you have 50% battery life or more and kies errrors out sometimes but it does work i update my friends phone as he does not like all the root stuff lol so i always your kies after a couple errors it will work and thats your best option if she doesnt want to loose anything kies will back it all up for her and are you sure that power button aint sticking sounds like you have a looping issue are you able to go into download mode or are you familiar with this ?
Click to expand...
Click to collapse
I would use odin...but the phone doesn't stay on long enough to do much of anything before "rebooting". Also, she is already using stock firmware + OTA updates. And her contacts are not what I am worried about, its her photos and such. This is the very reason why I hate internal memory for phones...
And I'm pretty sure its not a sticky power button, I had seen that being a common issue when researching before posting. And again, if I have not been clear, its not exactly "rebooting", just semi-rebooting; phone starts up, crap starts running, a min or 2 later, phone acts like its restarting (plays sound and all), then just comes back to the lock screen immediately...I can't really describe it much more than that.
And no, I'm not familiar with "download mode"
bzlik88 said:
Idk how to read logcats but another idea could be you have the sticky power button issue. I think if it was overheating u would feel it and mention it in the op.
Click to expand...
Click to collapse
Ya, like I said in the reply above this, I don't think its the sticky power button problem...but I could always be wrong. I only didn't mention over heating because I felt I did a good job of ruling it out.
DeliciousLimeJuice said:
I used to have this problem when my phone was on ICS. I found that putting it back to GB, and using custom JB roms fixed it. I'd try those.
Click to expand...
Click to collapse
Its running GB atm, never updated to ICS via Kies...
I wish I could help you further but i can say one thing, the rebooting that your describing is called a "hot reboot". I know what ur talking about and others will too if u use that term. Good luck.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app