Has anybody else had the Dialer show up in Spare Parts under "Partial wake usage"? It seems to be keeping the Nexus awake. This has only happened since flashing the latest nightly of CM7 and Matr1x 5.5 kernel.
I might just wipe and reflash, but I was wondering if anybody else has experienced this.
Its normal. Aosp thing I'm thinking...
Sent from my Nexus S 4G using XDA App
It only started showing up with the latest flashes, though. For the past month of using CM7 and various kernels, I would never have the problem with the dialer.
I'm on the same settings with no dialer issue...
Its the proximity sensor in call and it's normal, I'm telling ya. There's a whole thread in the evolution section about it
*can you post a screen shot?
Sent from my Nexus S 4G using XDA App
So far, after wiping cache and Dalvik and reflashing the Matr1x 5.5 CFS, it seems to be behaving.
Perhaps something just went bad in the original flash.
Make a few phone calls and see if it changes
imekul said:
So far, after wiping cache and Dalvik and reflashing the Matr1x 5.5 CFS, it seems to be behaving.
Perhaps something just went bad in the original flash.
Click to expand...
Click to collapse
Sent from my Nexus S 4G using XDA App
No questions in development. Thread moved and closed.
Related
Im having issues that the lockscreen is freezing up so i have to pull out the battery to make it work again
You can't make such a bold statement, and not include info like what ROM you're running and other relevant info. There's also no need to start a new thread...there's already a thread on the Gingerbread kernel in the development section.
So, because you're having problems, you want to warn everyone on problems that no one else is having??..
Faux's kernels are working just fine for me.
Faux's Kernels are fine. Update and don't listen to this Guy.
Sent from my HTC Glacier using XDA App and a perfectly working Faux Kernel.
WOW. Really, Really ???
Running without a kernel...That's amazing...
Faux's kernels are rock solid...Running 2.5.1 since release and NO issues...
then why has my mytouch freezing alot when i get it out of sleep
Plus i am on RoyalGinger V1.6
OP is an idiot. Faux kernel works fantastic. If you have problem with the rom, ask in the rom thread. Don't try and talk about something you don't understand.
Sent from my HTC Glacier using XDA Premium App
Had problems with it the other day. Running stock rom. Kept losing signal and data. Wifi stopped after about 10 minutes and had to restart the phone just to get it working again. Went back to what I was using before and problem went away.
Not sure what the real deal was as I have NEVER had a problem with his kernal.
Sent from my HTC Glacier using XDA App
mustk1ll20 said:
Had problems with it the other day. Running stock rom. Kept losing signal and data. Wifi stopped after about 10 minutes and had to restart the phone just to get it working again. Went back to what I was using before and problem went away.
Not sure what the real deal was as I have NEVER had a problem with his kernal.
Click to expand...
Click to collapse
The kernel being discussed here is faux's Gingerbread version.
Wouldn't it be great if there was a Mytouch 4G forum that was specifically for roms, kernals, and any other type of hacking? Oh wait there is one and this thread is in the wrong forum.
baller1 said:
then why has my mytouch freezing alot when i get it out of sleep
Click to expand...
Click to collapse
you're a retard.. the reason why your phone is freezing on lockscreen, is cause you either have setcpu installed & have your screen off settings too low! don't have Max set below 368, which 245 freezes your phone! set min& Max to 368 and you will not get any freeze ups and save a lot of battery also! try it!
just don't make a thread about smashing someone's kernal who works so hard to make it for us! faux has great kernals, & you should give him the credit.
Lol sorry. Was on latest cm when tried it. Long day forgot what all I went through with this. Went back to stock rom after it was screwing up. Prolly try again with cm and this kernal. Think maybe it was a bad download causing the problem for me. Although would think I would get some kind of error when installing it.
TeeJay3800 said:
The kernel being discussed here is faux's Gingerbread version.
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA App
This thread is full of nubness.
+1000 for not reading. Not searching. Posting in the wrong section.... and thinking faux would ever fail us lowly 4g users.
Sent from my HTC Glacier using XDA App
First check whatever Rom is fully downloaded. Then check to make sure you fully downloaded the kernel. Make sure you have the proper kernel for your rom. Make sure you wipe cache and wipe dalvik cache. Then install the proper kernel when it boots up let everything load for 4-5 minutes then reboot. If your using a low voltage version try stock version. Also use the cfs kernel and not bfs since your phone is lagging.
Sent from my HTC Glacier using XDA Premium App
I switched to MIUI a few days days ago, and I've been loving it so far. But I have been having a couple of issues.
Every so often my phone restarts for no reason. Sometimes when I'm in the settings application. Other times when I'm playing music. Regardless which music app I'm using, it'll restart my phone after 15-20 minutes.
My other issue is that my phone thinks its a Desire HD. is there a way to change
that? I can't access certain apps in the market because of that.
Thanks in advance.
I would try reflashing the rom. What kernal are you using with the rom and which version of MIUI? There is a discussion somewhere in the MIUI thread about changing the description in the build.prop file to make it show as an Inspire
I'm running miui 1.7.23. Not sure which kernel, probably the stock one. I haven't really read anything about the differences or why one is better than another.
Sent from my Inspire 4G using XDA App
theox88 said:
I'm running miui 1.7.23. Not sure which kernel, probably the stock one. I haven't really read anything about the differences or why one is better than another.
Sent from my Inspire 4G using XDA App
Click to expand...
Click to collapse
It sounds like a bad rom flash. I would wipe data, cache, and dalvik cache. Then I would reload the rom. The stock kernal that comes with the latest rom needs to be updated with the latest Lordmod kern but it should not cause the problems you are having.
I thought these battery usage statistics are only meant to get "Reset" when you full charge battery or when you wipe battery stats. But mine are resetting back to 0 minutes every time I reboot the phone. Is there a fix for this?
Did you do a proper wipe before you installed the ROM?
Yes I did a proper wipe. :/ I guess you don't have this issue?
I went back to nightly 116 and it started to work again. So looks like its broken in recent nightlies.
Nope just broke on yours. latest nightly doesn't reset for me.
Sent from my LG-P999 using xda premium
Looks like it is just me :'(. I have done FULL wipes and everything, even formatted SD cards and flashed back to stock. Seems to be a problem with Nightly 124 and all of the recent KANG builds. But nightly 116 and stock GB has no problems. It can't be hardware then right?
Ok, I have narrowed it down. This happened in Nightly 118. Worked in Nightly 116. There was a kernel update from CM_arcee in between these which might be the cause.
The guys that can't reproduce it, are you running Stock kernel?
I am running nightly 124 and it happens to my phone as well. Any reboot (hard or soft) resets the battery counter ...
Does it on mine also.
Using 124 and fauxs kernel
Sent from my LG-P999 using xda premium
Does it on mine also running trigger 8/22 2.3.5GB with faux123's oc/uv kernel. Not a big deal just hard ta screen shot the great battery life. .
Sent from my LG-P999 using xda premium
It does it on mine also. NIghtly #147 stock cm7 kernel.
I flashed faux uv kernel (ds) and it didn't reset in the first charge. But once I chearged it again, the battery use reset in every reboot.
Is anyone able to contact the CM7 maintainers for our phone?
syl0n said:
Is anyone able to contact the CM7 maintainers for our phone?
Click to expand...
Click to collapse
Sadly, only via postcard
I'm having this problem too. It was fine on the CM7.1 RC I believe. Pretty sure it only started happening to me after moving on to the stable release. Same results on stock CM, as well as when using Morfic's and Faux's kernels...
Just updated to the latest CM7 Nightly, and so far twice today, when I went to hit the sleep button. The screen remains black. I can see a blacklight go on though or something, as the screen changes from when its in sleep. But it remains black.. Is this a known bug? Any suggestions? I would really hate to have to go back to Weapon as I spent all day setting up CM7.
edit: upon further investigation, this appears to be called sleep of death? Are there any known fixes for it?
I had the same problem, happened with every cm7 based rom....i tried posting my problem on this forum for help but no 1 really had any idea what was the issue or how to fix it...as far as I know we're stuck using 2.3.3 roms
Btw do you have a wind optimus 2x or a tmobile g2x? Mine is from wind
Sent from my LG-P999 using XDA App
Faux123's 0.4.4 kernel has a patch for it. It will work with CM7 nightlies.
jamadio said:
Faux123's 0.4.4 kernel has a patch for it. It will work with CM7 nightlies.
Click to expand...
Click to collapse
Will it only work with the nightlies? I would've preferred to use the stable release or the cm7 eagleblood
Sent from my LG-P999 using XDA App
i installed his latest CM version along with the CM rom and it happened still. Is there a seperate patch? or is the kernal on its own supposed to fix it?
Thanks for posting that, I was about to test it myself
Sent from my LG-P999 using XDA App
I think there are 2 different sleeps of death, one of them only happens sometimes, whereas the one we get happens every single time the screen turns off
Sent from my LG-P999 using XDA App
hopefully we can fix this problem together.. It seems Cm7 has better battery life then the other roms so I would hate to go back.
well weapon has been pretty good for me...can't complain really...which CM rom did u try with faux's kernel?
The very latest nightly. Cant remember off hand which one it is.
Also, If I flashed weapon right now (being on CM7 + faux kernel), will I retain the faux kernel? Or will I need to reflash faux's kernel. And even though this kernel says CM7, will it still work with weapon?
I believe the kernel would be flashed over by the stock kernel in weapon, if it doesn't get flashed over then i doubt your phone would be able to boot up, because the kernel shouldn't be compatible with stock 2.3.3
give a shot and try it out, also if you want to over clock on weapon there should be another kernel by faux that u can use, look for it in the development forum
I am going to stay a little longer on CM7, maybe someone can help me with these SOD's.. Then I guess I wil go back to weapon or try out that eagle one. Not sure which is better..
i think the stock eagleblood is very plain and clean....i like weapon because its a little more customized, plus its the only stock rom that has the notification power menu...and from the looks of it, our problem seems very rare so i don't think anyone has or will develop a fix for it
---------- Post added at 02:07 AM ---------- Previous post was at 01:16 AM ----------
hesher said:
i installed his latest CM version along with the CM rom and it happened still. Is there a seperate patch? or is the kernal on its own supposed to fix it?
Click to expand...
Click to collapse
i ended up trying it for myself even though it didn't work for u, and it actually ended up working for me
i'll give u detailed steps for what i did and maybe it'll work for u too
(this is all on CWM recovery)
after backing up i factory reset (wiped data), wiped cache, wiped dalvik, and formatted /system
then i flashed the latest CM7 nightly (195), then i flashed gapps
i wiped cache and dalvik again then i flashed faux's 0.4.4 CM SV kernel
i then pessimistically rebooted and voila for the first time i had a functional CM7 rom....i've put the screen to sleep about 10 times so far and it awoke every time so i think it should be fixed
I hope it works for you. I probally didnt see my first SOD until maybe 50 or 60 sleeps.
well I used to get the SOD on the first sleep so its definitely an improvement for me...i'll let you know if it lasts i guess
I was just wondering whether there are any 4.4 roms available? The only one I found was CM but I feel like there must be more. I might be just going blind, however I could not see any other roms. Any links or suggestions are appreciated. Thank you.
mefistofel666 said:
I was just wondering whether there are any 4.4 roms available? The only one I found was CM but I feel like there must be more. I might be just going blind, however I could not see any other roms. Any links or suggestions are appreciated. Thank you.
Click to expand...
Click to collapse
nope those 3 build threads are it
I suggest using kitkang http://forum.xda-developers.com/showthread.php?t=2525831
as its the latest rom with Nightlys going on every night
and seems to be the only one making progress so far (FCC,SD,Overall UI smoothness,Video GPU performance)
SSPENCER10 is working very well for me. Everything he is putting out is stable and appears to be having fewer issues than KitKang. It is even working just as well with ART as it was with Dalvik. The 11-23 build also has the new CM11 boot animation.
markdapimp said:
I suggest using kitkang http://forum.xda-developers.com/showthread.php?t=2525831
as its the latest rom with Nightlys going on every night
and seems to be the only one making progress so far (FCC,SD,Overall UI smoothness,Video GPU performance)
Click to expand...
Click to collapse
You realize they are all based on exactly the same code right?
And you realize that if one makes 'progress' they all make 'progress' because they use the same code right?
[ROM][4.3.1][Official][OSE Rom][d2vzw]
I'm using this one and so far so good.
It has nightlies that have 4.4
I'd recommend KitKang. It's been extremely stable and has really good battery life. ART works very well.
Sent from my SCH-I535 using Tapatalk
KitKang!!
Second that!!
Sent from my SCH-I535 using xda app-developers app
markdapimp said:
I suggest using kitkang http://forum.xda-developers.com/showthread.php?t=2525831
as its the latest rom with Nightlys going on every night
and seems to be the only one making progress so far (FCC,SD,Overall UI smoothness,Video GPU performance)
Click to expand...
Click to collapse
Summary: I don't think KitKang is recognizing my SIM card, and is causing "Phone" to crash every second or two.
Hey guys, I tried flashing the latest KitKang ROM last night, but ran into a big issue. I wiped system, cache, dalvik cache, etc. I then reflashed the MF1 firmware (it was already flashed, but for some reason I always feel better re-flashing it every time.) Then I flashed the latest KitKang D2VZW nightly linked above, and flashed the GApps mentioned in that thread too. However, upon rebooting, every second or so it would say "phone has forced closed" (or something along those lines. Also, there was no signal. I got through the setup process after a VERY long time of pressing "okay" to that error and setting up my CM and Google accounts with one key in between each error. I thought I would be able to go into Mobile Networks and change the settings, which fixed certain early issues with CM10.1 or 10.2, but to no avail. I then tried reflashing (after wiping clean) CM10.2 again to get certain files for the phone to work, then flashing CM11 over that, and it seemed to work up until it freezes after getting to the home screen. Any thoughts on what the issue may be and/or how to fix it?
Thanks!
Sent from my SCH-I535 using xda app-developers app