Hi,
I have a Nexus 4 with faux Kernel mako-jb-kernel-005m.zip installed.
Android version is JOP40D stock.
Since I use the stable version of faux kernel 004m I have some problems with my display.
If the screen was looked and I unlook the screen the colors are changed.The contrast is bad and all looks a little bit blue. If I restart my phone all colors are fine. Today morning I started my Phone and the screen won't start fast, first some stripes lighting and after 10 sec the boot screen was shown.
The core clock was min/max 384/918 MHz, GPU max clock was 400 MHz and the core was undervoltet -25mV. All works fine with kernel 003 stable version before.
Now I have reset my kernel to the stock kernel and test if the error came back.
Has anyone the same problem?
I don't know if it is a known bug thus I must send my phone abck to google or is this a software bug?
Sry for writing here, but I cant write inside the defeloper post to the faux kernel before I have written 10 posts.
thx
When you restart your phone, the color is stock settings, after awhile the settings you set in the faux app are accessed and set. You should try the Nexus display spreadsheet for colors you can use if you don't know what you're doing. You might have changed some settings in the app by mistake, but I'm not familiar with your issue but if kernel 003 was working better then just use that one or try the latest kernel 005
You can also try franco kernel, its better IMO and its flash and forget, if you want to get color control you'd have to buy the franco.Kernel updater though
Thanks for the post.
I have never changed my Color settings because I think the stock settings are OK. At the momment I running the stock kernel and all i fine. I will test to switch back to faux_005.
Thanks you are right, one of the last fauxClock updates has changed all shift controlls in the color setting to max (in both presets). I don't know why. I have set alle to factory settings with the table from your link.
thx for help
---- solved ---
Related
I have been using nearly all the build out there before settling on Hyperdroid 1.7
On all of them I have been having the problem with the screen not waking up when you push the power button - the lights come on but the screen never wakes.
Now I know that some people have been saying this is due to the light sensor and holding the device close to a birght source does seem to wake the device up properly.
But I have been using 1.7 now for two days and found an almost instant on every time without any black screen of death or requirement of holding the device up to a light source.
I had/have always been using both Juice Defender and SetCPU - and tried on both the CPU scaling functionality - but both caused lockups.
Until - I change the LOW value of any profile to 422 and max 998.
Changing the low value from 245 up to 422 seems to have cured things for me. With the new 1.7 Michy kernel I still get 4-7ma in standby as reported bu currentwidget - and overnight my battery went down just 8% in 10 hours!
The only other piece of software I have installed is Taskiller which I have set to kill on screen off - and have put all the usual suspects on the "ignore" list.
Device has been working perfectly over two days now completely stable and not a single reboot - except for one very strange issue where the wifi (which is turned on and off with the screen via Juice) said it was turning on and then failed - leaving it greyed out and "turning on" but never did.
This only happened once and other than that wifi has been turning on and off perfectly.
My only reason for raising the lowest CPU setting was something I remember from the TD2 I had before - that too hated going to some of the very low frequencies and caused lock ups etc but if you scaled up a bit everything was fine.
Hope this helps.
I have same issue, I am using nexus built 2.2, I had guess Set CPU might responsible for this issue, can please specify your set CPU profile settings
I have changed builds many times since posting this as there were odd errors on almost every build - I have it down to the usual two now. Screen freezes vs data drops.
I am using tytung NexusHD2-FRG83 V1.6 PPP + RMNET - Release Date: 8.Nov.2010
Default settings which uses the hastarin 8.1 kernel.
No setCPU.
I no task killer but have system panel installed to help with the odd runaway app.
Link: http://forum.xda-developers.com/showthread.php?t=793924
But am keeping my eyes on the PPP development for the data freezes as once this is sorted PPP will be a fully working build - unfortunately it doesn't appear that as much work is being done on the RMNET route - so it's just a wait and see game.
Hope this helps.
rparmar said:
I have same issue, I am using nexus built 2.2, I had guess Set CPU might responsible for this issue, can please specify your set CPU profile settings
Click to expand...
Click to collapse
the OP did mention to NOT set your minimum to 245 mhz but about 400 mhz. whatever your profile is, try to avoid setting the minimum to 245
Hi,
I have this annoying problem regarding waking up my device when its locked. Normally i should press the power button, or the trackpad as im running virtuous rom, and the screen should give me the lock screen. But this does not happen, intead screen stays black, the keys on the bottom do light up, and it registers my touches on the screen as i can put the music player on again.
This is happening for quite some time, but lately its more often and its really frustrating me because i have to hit the power button for like 10 times in a row before it finally goes on again.
When it stays black and i put it off again, touching the power button, moste of the times the screen will flash the lockscreen and go black again.
Ive tried to find a sort of system in it, like a period of time or somthing like that, but it seems as if its completely arbirtrary when it happens and when it doesnt.. Only thing i remarked was that when it's off for a longer time, it will have more chance of getting on the first time then when its off for a shorter period...
Any suggestions to fix this evil thing?
cheers
This is a very comman problem.
what you need to do is setting up a screen off profile on setCPU
min 245
max 368
scalling : powersave
I agree check your screen off profiles. Also try not to oc too high. You might also want to install the pershoot kernel if you haven't already. I had this issue when I fist installed the virtuous rom & switching kernels and tweaking my cpu profiles resolved this issue.
Sent from my HTC Vision using XDA App
Screen off profile doesnt help, What does work is less oc'ing it... stupid thing is i can only oc to 902 mhz for the screen to turn on all the time... Thats like not oc'ing it at all ><... I'm on the virtuous kernel now, will try the pershoots in a min, i'll keep you updated
Oh sorry, screen off profile does help, didnt enable profiles in a whole ... pershoot kernel helps a lot, with that one and the screen off profiles, i can oc to 1517 and even then its just not going on very rarely... thanks for the help... Only thing thats regrettable is that the pershoot kernel does not have the smartass governor ...
EDIT: I realised i didnt enable the profiles while using the virtuous kernel either, so i installed that one again and guess what, it works!! Every single time i hit that power switch it goes on like it should... what a relieve thx guys
grtz
Just as the title says, but here's some more details.
I have my cpu set to 1.1Ghz during the normal day 245Mhz min.
I have my widget on my homescreen and a custom profile set for when the screen is off for 368max and 245min.
When I turn my screen on and unlock it, it lags on my screen and says 368 max, then it jumps to the 1.1 and everything is fine.
It seems to lag there longer than it used to, has anyone else noticed this problem.
I used to have Pershoots Kernel on 6.1, do you think if I put Pershoots Kernel back on it will eliminate the lag and switch to 1.1 faster than it does now?
Just some thoughts and advise would be great, thanks guys.
Sent from my HTC Vision using XDA App
I would ditch setCPU and use CM's built in overclocking settings. set your clock speed to whatever you like and use the ondemand governor.
your screen wake lag will almost certainly disappear and I bet your battery life doesn't change a bit. you can play around with it, of course, and find what's best, but I have found that since CM introduced built-in overclocking, it is more functional to use it instead of setCPU. my battery life hasn't changed a bit, partly because when the phone is in an idle state it is underclocked by default, and also because I don't have setCPU constantly having to think to make changes to my clock speeds and governors based on what profiles I've set up.
Hi all! Yesterday I installed GingerDX and alfs kernel (both the latest version), with full wipe and everything seems ok. But today, some strange display glitches appeared on display. Picture looks like cut. It's difficult for me to explain it, watch the video and see.
View video here!
Doomguy said:
Hi all! Yesterday I installed GingerDX and alfs kernel (both the latest version), with full wipe and everything seems ok. But today, some strange display glitches appeared on display. Picture looks like cut. It's difficult for me to explain it, watch the video and see.
View video here!
Click to expand...
Click to collapse
Try Re-flashing your ROM... Initiate full wipe before reflashing
Happens. Often made worse by overclocking. Don't fret. Start over again as advised
If you overclock on Alfs kernel, you have to set the governor to smartassV2 before you raise the cpu clock to prevent screen cuts. I use my phone with 691mhz always, but with smartassv2 governor, there wasn't any cuts, but as soon as I set to ondemand, there is garbage on screen. Hope it helps.
Sent from my X8 using XDA
Thank you all
Hi everyone,
Thanks for reading this . As specified above, my phone has a rather serious problem of overheating. To try and reslove the issue I tried modifying the CPU frequency, to set it low enough. And a very bizarre thing just happend.
Opening Kernel Adiutor, I saw that 4 out of my 8 cores (the 2.5 ones) were running normally. No overclock, stock settings, stock governor and so on. The issue seems to be in the other 4 (the 2.3 ones). Both the minimum and highest frequency allowed is set up to the same parameter (1556 mHz), forcing it to stay at maximum clock all the time. I tried modyfing via Kernel Adiutor the settings, lowering the minimum frequency allowed to stock one (which should be around 300 or something), but it had no effects: it immediatly comes back to 1556 and just won't come down.
All of this started happening after i removed Franco Kernel from my system, flashing another ROM (Chroma) with a different kernel altogether. I'm currently on Cataclysm ROM and after doing a clean install, formatting internal storage as well as every other partition, i couldn't resolve the issue. Moreover, Kernel Adiutor sometimes won't even show my CPU settings, stuck on an infinite loading. If anyone could help me, it would be much appreciated. It's really important. I'm by no means Android expert but i do have a rather basic understanding of ADB and so on.
Thanks a lot for your time.
-LVBNR5
I used to own a n7 and that allowed me to set min and max freq. with apps fine but i am also seeing this on my 6p, i don't notice any "overheating" although it may be due to me being used to it always running hot since i run a lot of heavier programs and also you know... SD810 but i guess it does the frequency thing as a way that frequency is actually controlled on this platform or something, because it sticks fine to the limits you set while flashing a kernel but no app can get it to stick. Then again this is just me sharing my experience with it as it is my first phone with this platform, so maybe someone who knows more about this could offer some help.
ml11ML said:
I used to own a n7 and that allowed me to set min and max freq. with apps fine but i am also seeing this on my 6p, i don't notice any "overheating" although it may be due to me being used to it always running hot since i run a lot of heavier programs and also you know... SD810 but i guess it does the frequency thing as a way that frequency is actually controlled on this platform or something, because it sticks fine to the limits you set while flashing a kernel but no app can get it to stick. Then again this is just me sharing my experience with it as it is my first phone with this platform, so maybe someone who knows more about this could offer some help.
Click to expand...
Click to collapse
Thanks anyway, i really appreciate it!