Hi team,
hope you can help me...I just rooted my phone, did everything what was needed before flashing a custom rom.
I tried the Android Revolution HD 2.1 custom rom, and it worked fine, but once I made my first phone call, the process com.android.phone started to consume 100% of my CPU, the phone started to be hot, battery rapidly down etc. The only thing helped was the restart and not to make phone call. I searched in the different forums, I tried the USB debugging and also to clear calendar cache, but nothing...I flashed a different kernel as well (Leddroid) but no luck...still the same issue, 100% cpu usage after a phone call.
I decided to flash another custom rom, which was Leedroid 2.2.0...was hoping that it will fix the problem, but again...phone call and cpu on 100%...the strange thing is, that this time it did not do right after the first phone call, but 2 days later. Tried to disable all the synchs, usb debugging, calendar cache etc. but still got this problem
Anybody can help please? I would appreciate
Weird..
I've noticed my phone burning my leg while its in my pocket randomly when im not using it? Maybe a bug on HTC's behalf.Download fast reboot off the market and try using that to kill all the apps, its the best one ive used and normally stops it being so hot
Thank you, but it did not help...it actually kills everything, but as soon as I make the next phone call, the CPU gets back to 100% :-(
Anybody can help please...I installed a different kernel as well, but no luck...tried stock, Leedroid kernel and still got the 100% cpu issue.
Perhaps a full wipe can help. Make a Backup before.
Thanks MysthMob...I tried that one as well...used the SuperWipe from mike and from Leedroid as well...reinstalled the custom rom, everything worked fine till the first phone call...than it went up again to 100%
I was thinking of that it is caused by any 3rd party app...I have these installed:
Advanced task killer pro
Battery widget pro
Automatic bluetooth dongle pro
You dont need a task killer! Sense has one built in called Low Memory Killer
Good to know thank you...just removed, but the problem still persist...I am tired to reboot the phone all the time I make a phone call.
If you still have problems i would send it back for repair, Maybe it has a hardware fault
Do not think so...it was working fine with stock Rom...its just in custom Roms..but with all? I flashed back stock Rom and its working fine, but I want a custom one, I think I do not need to explain why
I will probably go back to the stock rom :-(
Mike is planing to release his 3.0.1 version, maybe he will include a fix...will wait till he posts it
Related
I installed serendipity 6.4 w/ hardcore speedmod about 3days ago and everything works very well,but when I get a incoming call the phone rings once and I drop signal "no service" a second or two goes by signal comes back everythings fine no missed call shown, like I never got a call...But I can make outgoing calls...plz help
Same exact problem for me, I even tried restarting fresh and doing the whole flashing process over again and still have the same issue.... I'm about to switch roms if this keeps up but I really liked Serendipity
Same problem here, same ROM, same version.
What have you guys tried?
I've flashed back to stock using ODIN and then flashed back to Serendipity again. Problem appeared to be resolved at first, but then 2 days later the symptoms started to repeat.
That made me suspect the problem was with particular apps or widgets I'd stuck on my home screen, so I tried removing my newer apps & widgets such as Facebook and NYT to no avail.
Anyone else with ideas?
I do rather like Serendipity, but will probably end up flashing back to Cognition or something to get around this. Guess I'll wait for Mikey's 2.3 to stabilize!
Update:
Flashed back to a clean Serendipity 6.4 and did not use Titanium Backup to restore my apps. It's working fine right now. In the next few days I'll restore individual apps as I need them, and see if the problem recurs.
Best theory so far is that the problem is either
a) Caused entirely by a particular app or widget
b) Caused by some sort of strange incompatibility between Serendipity 6.4 and a particular app or widget
Hi All,
Having a strange issue with my Sensation wheras the WiFi is switching itself on at night.
Normally I will switch it off using the 'power bar' when I go to bed and then switch it back on when I wake up but since the Twitter update (on Orange which seems to have updated my market as well) it comes on by itself. If I turn it off again it stays off.
I know that both nights the phone has been about 7% battery and is in power save mode but this doesn't switch the WiFi off, just the sync. I then press the WiFi off and plug it into the mains.
Any ideas on why this is happeneing and if it is a known bug? Also if there is a way to fix it?
Thanks
Darren
Details??
Is your phone S-OFF?? rooted? If so, which ROM are you using? Please post all the details.
I had this bug twice with ICS, ma battery starts screaming at 21% while it was 80% just 2 hours before,it was wifi that was ON by itself
retardedrockstar said:
Is your phone S-OFF?? rooted? If so, which ROM are you using? Please post all the details.
Click to expand...
Click to collapse
Sorry, standard Orange ROM, not rooted or anything
Android 2.3.4
Sense 3.0
Software 1.50.61.1
Kernel 2.6.35.13-gle13373
Baseband 10.58.9035.00U_10.15.9035.02_2
Seems to only have done it since the twitter update on saturday which also updated my marketplace.
Darren
Hi,
I have the same problem. In my case, I am using ICS4.0.3 on my Telstra HTC Velocity (rooted but stock ROM ).
I think it might be Juice Defender , but I'll confirm that in couple of days time.
I have used it once, and uninstalled it, but I think it might have left behind the settings (network scheduled to be turned on at night to sync).
I installed it again, and by default that option was turned on. I have now turned it off and uninstalled it again.
I shall let you know the outcome soon
i have this issue on my previous ARHD 6.6.0
i tried to flash with different kernel,it wont fix
all i do is flashed to New leedroid 7.3.0 the issue gone.
So i assume is ROM problem.not quite sure about this.
I think it was a problem with a specific base that was used (either in the stock or making the rom),
I had it on IC5.2 I think, but then updated my rom and it went away, it presented itself on all the roms that used that base (I believe) it should be gone now with the updated base that was released. Not sure of the specifics and version numbers, maybe a dev can provide if needed, but the updates shouldn't have that issue anymore
My adventures with the HTC One S just dont seem to end. Here is a short history:
First thing I did when I got the phone was flash over CM9 as I dont like Sense
All was good until the home button issue popped up, this was at that time my only issue and sync worked just fine
I flashed over CM10 when it was stable enough, this didnt fix the home button issue though
I then flashed over the new RUU with radio 2.21 and directly after that CM10 again (I still dont like Sense)
After the first flash I had a lot of grey signal bars (either bad signal or no connection with Google servers) so I flashed CM10 again.
The signal bars where blue after that and the new radio (2.21) has improved the signal a lot and therefor minimizing the home button issue
But since the new radio I'm experiencing a new problem, just as much annoying. My phone wont sync when the screen is off or wont sync at all unless I do it manually.
This is what I have tried so far:
First cleaned cache from Gmail, Google Services Framework and Market -> no fix
Rebooted the phone with airplane mode on and enabling data connection afterwards -> no fix
Factory reset from recovery, flash CM10 again and restore apps with TB -> no fix
Factory reset from recovery, flash CM10 again and no restore of apps but just vanilla CM10 -> no fix
I have ran out of options so I could use some help here. Why are emails not pushed to my phone when the screen is off?
I had all kinds of sync issues with that radio until I flashed Trickdroid 7.1 which is built off the base which included that radio. Can't figure out how, but it's like they work best together though my best guess is that TD just maintains more free memory, so whatever process syncs the phone doesn't get killed. You can even desense TD as part of the tweak pack if you want to try it
Sent from my HTC One S using xda app-developers app
el_smurfo said:
I had all kinds of sync issues with that radio until I flashed Trickdroid 7.1 which is built off the base which included that radio. Can't figure out how, but it's like they work best together though my best guess is that TD just maintains more free memory, so whatever process syncs the phone doesn't get killed. You can even desense TD as part of the tweak pack if you want to try it
Click to expand...
Click to collapse
Hmmm ... thanx for this info. I hoped the problem was not related to the radio and I missed something stupid. When I have some time I'll make a nandroid backup of CM10 and will give Trickdroid 7.1 a go, see if it fixes things.
Another solution I was thinking of was buying Tasker and schedule a sync job. When set up right it might even save me some battery juice.
el_smurfo said:
I had all kinds of sync issues with that radio until I flashed Trickdroid 7.1 which is built off the base which included that radio. Can't figure out how, but it's like they work best together though my best guess is that TD just maintains more free memory, so whatever process syncs the phone doesn't get killed. You can even desense TD as part of the tweak pack if you want to try it
Click to expand...
Click to collapse
I tried Trickdroid 7.1 today but spent no longer then 5 minutes on this ROM. Although I selected all options of going back to stock and removing anything related to Sense in the Trickdroid Tweaks it was no where near the AOSP feeling I like best. So I didnt like Trickdroid at all.
Didnt properly test the syncing but in the one test I did I received my email instantly. So I guess there is indeed a problem with the new radio and CM10. I'll report this in the CM10 support thread.
Hi folks
I have a Nexus S (i9020a). It has stock 4.1.2 Jelly bean from Google (downloaded the stock image and flashed it). It worked fine for over a month.
Suddenly few days back this device got a problem. When I dial any number I can't hear any dialing sounds and even after the call has connected I can't hear the opposite person and the opposite person also can't hear me (The phone still shows as 'Dialing' though it's already connected). The same is true when I answer any call. Both parties can't hear anything.
This is solved by rebooting the phone for the first phone call only. After I reboot, the 1st phone call works fine, then this problem persists for any calls I make/receive until I reboot the phone again.
I tried flashing a different radio but this problem is still there. I tried my sim card on a different phone and it works fine, so the problem is not that too. My 3G data works just fine.
I need this phone for the next few days/weeks (hopefully not months) before my Nexus 4 gets delivered :laugh:
Thanks..
Edit: Modified the title; Probably gave the wrong meaning that the problem is solved.
<bump> Modified the title. Earlier title gave an impression that the problem is solved whereas I still have a problem.
Have you installed any apps which could somehow affect the dialler?
Unless someone else can give you a different advice, I can't think of any other option than do a full wipe and reflash.
I haven't installed any such apps.
Also, I already did a full wipe and flashed the stock image again. The problem is still there.
Don't know what else you could try, sorry mate - hope someone else can help you sort it out!
Thanks for trying. I think I will go to some hardware shop and see if they can figure out..
Try using a headset for making phone calls so that we can identify if it's really the hardware's problem.
ej8989 said:
Try using a headset for making phone calls so that we can identify if it's really the hardware's problem.
Click to expand...
Click to collapse
That's the first thing that I tried... doesnt work.
mailrachit said:
That's the first thing that I tried... doesnt work.
Click to expand...
Click to collapse
I had similar problem when RAM running out. Usually a reboot fix the problem for a bit.
What I did:
1. With Titanium Backup Pro, froze unused RAM hogging system apps, like Google+, Google play magazine,etc
2. Froze or uninstall Facebook, Word with Friends, etc which are resident and hog RAMs .
3. Install marmite kernel, free up more usable RAMs.
Hope it helps you too.
_android_ said:
I had similar problem when RAM running out. Usually a reboot fix the problem for a bit.
What I did:
1. With Titanium Backup Pro, froze unused RAM hogging system apps, like Google+, Google play magazine,etc
2. Froze or uninstall Facebook, Word with Friends, etc which are resident and hog RAMs .
3. Install marmite kernel, free up more usable RAMs.
Hope it helps you too.
Click to expand...
Click to collapse
Thanks for the suggestion!
I tried this too but doesn't work...
Try any custom ROM instead of stock ROM and a different kernel too. There could be chances that you've flashed the wrong ROM / radio too.
Sent from my Nexus S
Problem solved.
I went to a hardware store today. The guy said that it's a problem with the 3G service of my carrier (Vodafone India). The moment I enabled the '2G only' option in the Mobile networks settings area, this problem was gone. The technician said that this issue is affecting some people randomly. He said that since 3G service was launched just last year, the networks are not yet capable of handling all kinds of devices (he claims that the bug is so erratic that another Nexus S i9020a may work just fine with the very same bootloader/radio/rom which doesn't make any sense). When I said that 3G service was working fine before, he said that most probably my carrier changed some settings on their side which is causing this issue for me.
I have tried this for 6-8 hours now, making a lot of phone calls and it seems that the issue is gone. It saddens me that I am off 3G for now but at least my phone calls and basic EDGE internet works fine. I will have to work with Vodafone to solve this or simply wait for my new phone (Nexus 4) and hope it won't have the same problem..
I'm relatively new here...and to rooting... I do a heckuva lot more reading than posting here...and searching this problem brings a wide variety of other people's similar experiences and the solutions they've tried...but most of them are not exactly what I'm experiencing. The one case that matches exactly, never found a solution...
So here's my case... Every time I reboot my phone, it boots normally...and 3-7 minutes later, system_server begins hogging up CPU%...freezes...then reboots the phone. This cycle goes on forever. I have successfully used several different solutions, but the fix is not repeatable...it works once, but if I need to use the fix again, it won't work...
My current setup: Inspire 4g, Viper 1.2.3, BeastMode v0.5, oc 1497 interactive gov. (set on boot NOT checked)(no additional CPU or voltage tweaks)...I also had this problem with TrickDroid, before I ever tried overclocking...although my gut tells me the problem is related to oc, it occurs whether or not max speed is the stock 1024 or faster...
Here's what I've tried that has worked at least once, but failed to work ever since:
Turn off data and wifi connections
Turn off data, wifi, autosync, gps
Wipe cache and dalvic
Wipe cache, dalvic, fix permissions
Wipe cache, dalvic, dirty flash rom
Turn off data, wifi, autosync, gps, autorotate
Wipe data, cache, dalvic
Wipe data from setCPU and uninstall it
Install kernel BeastMode v. 0.5
And the only solution that works every time is....full wipe, reflash rom...once I do this and system is stable, I can build everything back up....flash BeastMode kernel, restore apps and home screens, even overclock...everything stays stable and works perfectly...
...but, you know... It's impossible to resist the urge to tweak something, flash something...or do SOMETHING that requires a reboot...and that's when the problem occurs...
Every. Single. Time.
Is there anyone here that can share some knowledge, or point me to some buried thread I haven't found after weeks of searching??
One more bit of info that may or may not be related...I dunno... I've tried overclocking with both setCPU and Juice Defender Ultimate...set on boot is always left UNCHECKED...however, the settings seem to stick anyway...randomly...sometimes it does, sometimes not...
Please...if you can help me, or educate me, or point me in the right direction, or have any thoughts or some personal experience with this bug...post here... I'm very interested in your ideas...
Sent from my Inspire 4G using xda-developer's app
This sucks...
Here's a possible solution...but it sounds complicated... I guess setCPU changes something...
http://forum.xda-developers.com/showthread.php?t=983524&page=2
I'm probably just going to screw up the phone if I go trying to edit files...if I can even find this file.
*frustrated*
I've reset permissions to 700 for /sys/devices/system/0cpu/cpu/cpufreq/stats/time_in_state... My phone stayed stable for about the same amount of time...4 days...then it rebooted and went into the boot loop again.
Nothing fixes anymore except fullwipe/reflash...but I can restore my tweaks settings, overclock, restore apps and homescreens, etc pretty quick now, and it stays stable for a few days...so once every four or five days isn't THAT bad I guess...
Sent from my Inspire 4G using xda-developer's app
RuggedHunter said:
I've reset permissions to 700 for /sys/devices/system/0cpu/cpu/cpufreq/stats/time_in_state... My phone stayed stable for about the same amount of time...4 days...then it rebooted and went into the boot loop again.
Nothing fixes anymore except fullwipe/reflash...but I can restore my tweaks settings, overclock, restore apps and homescreens, etc pretty quick now, and it stays stable for a few days...so once every four or five days isn't THAT bad I guess...
Sent from my Inspire 4G using xda-developer's app
Click to expand...
Click to collapse
Just for ****z and grinz, have you tried wiping and just installing a plane Jane ROM and not tweaking anything other than installing most used apps? My suspicion is that the kernel you are using or one of your power/super teaks are messing with your hardware and causing the issue. Try just using a base ROM for a week and resist tweaking it during that time. Then add addition tweaks on a weekly bases till it becomes unstable again. The you know what is causing it. I suspect the kernel since it is according to you used on all your ROM installs. Might try a different kernel if you must tweak from the get go.
Thanks man, that's great advice! I've had this problem with TrickDroid (and whatever kernel that came with), Viper 1.2.3 (and whatever kernel that came with), and same Viper with BeastMode v0.5 kernel. I haven't tried any other roms, but I don't think I can blame this on the rom...
I've tried a lot of things that I haven't posted yet, and I think I have it pretty much 100% narrowed down to overclocking...this problem never started until I started using JuiceDefender to overclock...then SetCPU...
Through process of elimination I've been able to rule out just about everything else...after a fullwipe, I can reflash the rom and let it settle...then reboot, and it does not loop...then flash new kernel, no bootloop...retweak some personalization stuff, still no loop...then restore all apps, still no loop...open SetCPU and set max speed to ANY speed...if I reboot it'll loop...if I just leave it alone, it'll stay stable for days...when it reboots, while watching Diagnosis I see system_server running at 65-95% CPU for about 90 seconds and the phone severely lags or freezes, then hot reboots...
Also, in the past, before I had this bootloop problem but after I started overclocking...I could still reboot my phone and everything would be fine, but the maxspeed was still set to oc, even though 'Set On Boot' was not checked and no profiles were used. This was true with all 3 kernels and both roms, and the app I used to overclock made no difference...SetCPU or JuiceDefender...even setting everything back to original settings before uninstalling both apps...oc settings always stick...
Last week, I read about someone thinking this issue was related to something about the relationship between mbuffer and time_in_state...one is 256 bytes, and the other 280 which recreates the problem...someone found a solution by changing the permissions of time_in_state back from 777 to 700...my phone rebooted and looped on Thursday, so that didn't work...
I've downloaded another rom to try, so when my phone goes on the fritz again in a couple days and I have to wipe anyways, I'll try a couple out and see if a different rom/kernels work...Thanks!
Sent from my Inspire 4G using xda-developer's app
Well, I got another random reboot then loop last Sunday, so I switched things up and flashed Pipeliner's cm10 on jellybean. So far, so good... I've overclocked with the rom's internal settings instead of setcpu, and I can reboot normally every time...
Thanks again for the help...
*edit* for... not get...
Sent from my Inspire 4G using xda-developer's app