Hi, i just recently rooted using win team recovery tool. I installed Purity rom and faux kernal on my android 4.3 nexus. This was my first rom ever and when i use my android now, every time i swipe from side to side, or open my app list, it gets all choppy. What i mean is, the app's straight lines become broken as if it was lagging.
Does anyone know the solution?
Yeah use stock kernel unless Faux has the GPU fixes in for 4.3 which it does not sound like
i had the same problem after trying faux kernel think the one you downloaded was for JSS15J and not JWR66V ....go back to stock kernel and all will be fine
Related
Can I install 4.1.2 on top of Paranoid Android's custom ROM? (Trinity kernel) The one thing I have noticed so far on PA is that the home screen still has no rotation which I know 4.1.2 fixed. Not a huge deal, but I am assuming that means PA is still based on the earlier JB version. Will it break anything if I manually update to the latest? I am new to tablets/rooting so I wanted to check before I tried it. (Almost bricked my tablet earlier today cause I had the wrong .zip for PA. Made me hesitant...)
Lazarus416 said:
Can I install 4.1.2 on top of Paranoid Android's custom ROM? (Trinity kernel) The one thing I have noticed so far on PA is that the home screen still has no rotation which I know 4.1.2 fixed. Not a huge deal, but I am assuming that means PA is still based on the earlier JB version. Will it break anything if I manually update to the latest? I am new to tablets/rooting so I wanted to check before I tried it. (Almost bricked my tablet earlier today cause I had the wrong .zip for PA. Made me hesitant...)
Click to expand...
Click to collapse
Lastest release PA 2.2 is based on 4.1.2.
Lazarus416 said:
Can I install 4.1.2 on top of Paranoid Android's custom ROM?
Click to expand...
Click to collapse
No, you cannot.
after 4.2.1, i cant find a kernel that will work with stock rom that allows overclocking?
Motley
I really like Metallice's motley kernel, located in nexus 7 android developemnet.
Edit: Click my Sig pic for a link
trinity kernel works fine too
I'm loving the trinity kernel myself! It is blazing fast at 1.7Ghz. (gets a little warm but other than that it is just awesome) No issues so far using stock 4.2.1 ROM
Stock ROM, as in not rooted? If you are running a custom 'stock' ROM, as in you flashed it to your device than any number of good kernels will do what you want.
But at a minimum you need to be rooted and have a custom recovery installed.
Sent from my Nexus 7 using xda premium
Just got my Nexus yesterday, came stock with 4.2.2 and with those little nipples on the back of the phone that came in the newest revisions. I immediately rooted, flashed the newest PA and Morfic's kernel, and I've been told that I sound like crap on the phone.
I came from the Galaxy S2 running JB, which had a call echo problem, does this phone, or some of these ROM's have this issue, or is it Kernel related?
I am on CM 10.1 M3 with Franco Kernel nightly 122 and my in-call sound is quite OK. No buzz or echo problem. Has Nexus few months already and first day procedure was the same as yours - root, custom recovery, CM + franco kernel.
My Nex is w/o nipples and rev. 11.
Thanks
Sent from my Nexus 4 using xda app-developers app
Hey guys.
I flashed the ktoonz kernel about a week ago and it works just fine except one thing: after a reboot my phone has forgotten my wifi password and i have to connect it again.
every time i restart the phone it's the same. it worked on stock kernel.
does anyone know this problem? it's quite annoying..
--edit--
i forgot to mention that i'm on stock samsung rom android 4.3 with touchwiz
and it's the international s4 (i9505).
TweeXta said:
Hey guys.
I flashed the ktoonz kernel about a week ago and it works just fine except one thing: after a reboot my phone has forgotten my wifi password and i have to connect it again.
every time i restart the phone it's the same. it worked on stock kernel.
does anyone know this problem? it's quite annoying..
--edit--
i forgot to mention that i'm on stock samsung rom android 4.3 with touchwiz
and it's the international s4 (i9505).
Click to expand...
Click to collapse
I make the same mistake
Originally Posted by monkteo View Post
Hi,I just install the (I9505 XXUEMKE JB 4.3 Pre-Rooted STOCK ROM's) great rom and I thanks you for bring it here.
Question; after installed I try to flash a custom kernel (AOSP/TW/GE - 4.2/4.3 KT-SGS4 - MFD - KTweaker) and everything started to work wrong (no wifi,net fc,and many others)please tel my what kernel it's perfect for your rom and also if it's realy ned to flash a custom kernel ?
10X
A custom kernel is not required for these ROMs as they include the stock Samsung TouchWiz kernel which I'd say is probably the best kernel for the stock ROMs.
Isn't there a way to get WiFi working without flashing a new rom? I don't want to wipe the phone actually and the kernel is pretty nice I think.
It's pretty konservative with the battery and gives me extra power when I need it.
Isn't there a WiFi-fix or something like that?
TweeXta said:
Isn't there a way to get WiFi working without flashing a new rom? I don't want to wipe the phone actually and the kernel is pretty nice I think.
It's pretty konservative with the battery and gives me extra power when I need it.
Isn't there a WiFi-fix or something like that?
Click to expand...
Click to collapse
WiFi-fix
Regards
Got the same issue with 4.4.2 and newest kernel version...
Tried changing build.prop line but with no success.
Is there any kind of help or a adequate wifi fix for kitkat?
Solved: wiped cache and dalvik and fixed permissions couple of times. Now it works
Sent from my GT-I9505 using xda app-developers app
I'm using GT-I9505 "international" with Paranoid Android 4.45 and successfully installed Ktoonsez kernel (3.4.94) with flashify app using Philztouch cwm recovery.
No problems at all, everything works, not tweaking by KTweaker, just raised 2.2GHz from PA's processor settings, ondemand as processor governor and Noop on i/o scheduler.
Tried few KTweaker profiles first but didn't find any good what understands to drop processor on deep sleep mode, almost all keeps it running all the time, PA's own handling with freshly installed KT-SGS4 kernel did best job for me.
Testing with profiles was frustrating thing, there wasn't way back to same situation what I got on fresh install.. few PA flashes later stand on "default".
Props to KToonsez (kernel), Christian Göllner (Flashify) and Paranoid Android.
Hi all,
Today has been a disastrous day for me. My Nexus 4 decided to update itself and got stuck at "Android is updating.... Starting apps.." screen. It is rooted and the bootloader is unlocked. Fastboot recognized my phone but not adb and I couldn't figure my way out of that so I basically reset my phone, flashing the stock version of Android 4.4.2.
It worked fine for a few minutes, so I tried flashing the latest snapshot version of CM-11, but that failed. I believe it was after I restarted my phone that everything became discoloured and the screen was zoomed in and repeated.
I tried flashing the stock ROM again in hopes of fixing the discolouration and zooming, but it didn't help. I've attached a picture of what my phone's display looks like. The colours of the bootloader are normal and unaffected.
Can anybody help me with this? I've been using Android Toolkit 1.2.8 and Nexus Root Toolkit on my Windows 8.1 x64 laptop. My Nexus 4 currently has the stock version of Android 4.4.2.
I'm inexperienced at this, so please let me know if more information is required.
you are using a kernel that support AOSP rom with a CM11, you should use a compatible kernel
Svarion said:
you are using a kernel that support AOSP rom with a CM11, you should use a compatible kernel
Click to expand...
Click to collapse
Thanks for the fast response,
Sorry, could you be more specific? I not QUITE sure what that means, but could it not be an issue if I've flashed the stock 4.4.2 onto my phone?
Thank YOU!
I guess I kind of remember flashing the stock 4.4.2 failed (I think it said too many connections), but I retried it just now after restarting my computer and the display is back to normal.
In terms of kernels, how will I know which kernel(s) is/are compatible?
n4helpneeded said:
I guess I kind of remember flashing the stock 4.4.2 failed (I think it said too many connections), but I retried it just now after restarting my computer and the display is back to normal.
In terms of kernels, how will I know which kernel(s) is/are compatible?
Click to expand...
Click to collapse
if you are using cm11 or any rom based on cm11 you should use a compatible kernel, if you are using stock/aosp rom you can use almost all kernels like franco.kernel, ak, hellscore