Just curious
I'm using xylon.
Thread locked in 3....2.....1....
Sent from my Grouper
Sveke said:
I'm using xylon.
Thread locked in 3....2.....1....
Sent from my Grouper
Click to expand...
Click to collapse
....1......2.......3 opened
Waste of energy and time.
I am usually an AOKP guy, so when the unofficial AOKP builds started poping up, i jumped on them. they were OK with some issues here and there. but the browser locked up on my every time i tried using it.
i am on CM10.1 (again, unofficial nightly build) with no issues.
CM has always been smoother than AOKP, i just liked AOKP's options more.
Stock
Nothing wrong with your choice and reasons.
I use Paranoid because it has tablet mode. It also updates pretty constantly but not everyday where it becomes tedious to stay current.
Sent from my Nexus 7 using XDA Premium HD app
Way too many of these threads have been and gone.
R.I.P POINTLESS THREAD!
Sent from my Nexus 7 using xda premium
I'm using my own build of AOSP right now, tried stock and CM nightlies. Actually tried to build CM too, kind of fixed a build problem, but wouldn't get past the boot loader. Would love to post in the forum about it, but I don't have ten posts yet. Well, here's one, I guess.
JUST SEE THIS ROM AND YOU TELL ME WICH ROM IS.....OK
http://www.youtube.com/watch?v=QLLNR...ature=youtu.be
Related
Recently i installed CM10.1 stable(clean install).
After i applyed franco kernel it rebooted then 2 weeks after i uninstalled Tasker after it was done it gone for reboot.
I extracted last_kmsg.txt and it just said at the end Reason:Reboot.
No UVs or OCs all default settings from kernel.
http://db.tt/QWqFEqqm
Not only reboots but my phone turns off just without a reason when i am playing music. Think i am going to flash paranoid again
(Using cm kernel btw)
Sent from my Nexus 4 using xda app-developers app
sonikk4ever said:
Not only reboots but my phone turns off just without a reason when i am playing music. Think i am going to flash paranoid again
(Using cm kernel btw)
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I think im gonna wait for Android 4.3 update then go back to stock just whit root,im not doing flash 4.3 sysdump thing.
how about try the 10.1.2?
http://get.cm/get/jenkins/34261/cm-10.1.2-mako.zip
it runs pretty stable for my daily driver, never slows down or even reboots itself. im using matr1x kernel on default setting.
did you undevolt?
Sent from my Nexus 4 using Tapatalk 2
The nightlys have been rock solid for me
Guyz im on lastest CM10.1 whit FK kernel but still i have issues whit screen flickering and more.I think its device hardware itself.
Karlo666 said:
Guyz im on lastest CM10.1 whit FK kernel but still i have issues whit screen flickering and more.I think its device hardware itself.
Click to expand...
Click to collapse
have u tried going back to stock first? i believe it's a hardware issue because in my experiences using so many custom roms based on aosp, cm and aokp, i never even seen the screen flickering issue at all.
Sent from my Nexus 4 using Tapatalk 2
Just asking who has flashed 4.3 then found its full of bugs and then reflashed 4.2.2 !!
Sent from my Nexus 4 using xda app-developers app
nickslg said:
Just asking who has flashed 4.3 then found its full of bugs and then reflashed 4.2.2 !!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Me, just now.
Was unhappy with the scrolling (stuttery & laggy - to me it seemed like the touch sensor was being polled less because while your finger was touching & moving, the screen scroll stuttered, when released, it continued its scrolling smoothly)
Also, WiFi was sometimes not reconnecting - had to either reboot or forget / re-join.
also had an issue with the camera flash failing to operate after 3 or 4 photos.
I was beginning to think I was imagining my N4 was nice an smooth - but I got so annoyed with 4.3 I unlocked & flashed 4.2.2 factory image. IT Is DEFINITELY smoother.
Screen stutter/lag can be rendered by checking "hardware overlays" in dev options
Sent from my Nexus 4 using xda app-developers app
I'm missing aokp ROMs from 4.2.2 going back when I get to my computer later today
Sent from my Nexus 4 using xda app-developers app
nickslg said:
I'm missing aokp ROMs from 4.2.2 going back when I get to my computer later today
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I've flashed a couple of 4.3 ROMs starting with stock but keep going back to LiquidSmooth v 2.9. I don't see any degradation in performance with 4.3, I have been getting better battery life from LiquidSmooth.
There were a couple of apps that I use that were not performing well with 4.3. I decided to flash back to cm because of this. It was mainly Swype that was driving me crazy. I'm unsure if it was the fault of Swype not being updated for 4.3 or if it was the screen polling of 4.3 everyone is talking about.
Sent from my Nexus 4 using xda app-developers app
Still on 4.2.2 lol Never upgraded...:victory:
nickslg said:
Screen stutter/lag can be rendered by checking "hardware overlays" in dev options
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I don't see hardware overlays. Do you mean "disable HW overlay " or "force GPU rendering" ?
These were default (I.e not disabled and not forced)
Im not sure these would help?!?!
I tried 4.3 two times, but after a few hours I reverted back to CM10.1 :silly:
I'll wait for good and stable custom kernels, and for good custom ROM's.
It's me. I expect 4.3 very much. I update to stock 4.3, Titanium can't remove system app. So I tried to use PA rom, version 3.91, while I'm download PA rom, I detect a new version of PA, version 3.92. I'm very suprise with PA group speed, they're provide rom patchs continuous. And I had to download from beginning. After that, I install new rom with a big expectation but titanium still can't remove system app. Finally I had to restore to PA 3.69 by TWRP and wait a new rom version :crying:
Tried a custom CyanogenMod 4.3 Build, but I prefer to stay with the "current" nightlies right now.
Theres a reason why they didnt start rolling out nightlies already.
A question, where did you get the CM build? Is it from the team itself or was it made by someone else?
4.3, same on the outside, fubar on the inside.
My fears about the head honcho of android chrome being made head of the whole OS have come to bare.
If it wasn't for the fact that 4.3 fixed the double dial issue for us Solavei users id go back to CM 10.1.2 (4.2.2)
Sent from my Nexus 4 using Tapatalk 4 Beta
Am I the only one whose 4.3 is working just fine?
From a Nexus 4 bathing in Jelly Beans
Logomotph said:
Am I the only one whose 4.3 is working just fine?
From a Nexus 4 bathing in Jelly Beans
Click to expand...
Click to collapse
No, mine's working great also on 4.3. Missing the added functionality of custom Roms atm. Just waiting on cm 10.2 to become official:thumbup:
Sent from my Nexus 4 using Tapatalk 4 Beta
Logomotph said:
Am I the only one whose 4.3 is working just fine?
From a Nexus 4 bathing in Jelly Beans
Click to expand...
Click to collapse
I find it hard to believe its working as it should be
Sent from my Nexus 4 using xda app-developers app
I might revert back. I get several hours less battery time with 4.3 because Android OS "keep awake" is draining my battery. I never had such issues with 4.2.2. :/
lowrider262 said:
No, mine's working great also on 4.3. Missing the added functionality of custom Roms atm. Just waiting on cm 10.2 to become official:thumbup:
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I quite like the stock rom....kinda sad Matr1x only supports the JSS build....might flash a JSS rom...or maybe build it myself.
But yeah, I'm happy with 4.3. Never had any issues with OTAs
nickslg said:
I find it hard to believe its working as it should be
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Everything seems to be working well. I couldn't test BLE, because I don't have a BLE device, but otherwise everything seems to be fine.
Yea I went back to 4.2.2... I'll wait for liquid smooth too upgrade to 4.3 before I flash another ROM.
Sent from my Nexus 4 using xda premium
Hey guys I just rooted and installed a few custom ROMs on my n4. When I install a custom 4.3 kernel on any 4.3 ROM I get ridiculous flickering issues. It never happened on stock and only happens on custom ROMs when flashing another kernel. Am I missing something obvious? I have searched for an answer but have come up empty. Any help would be appreciated cuz I really would like to run Franco or faux ( my two favs from my Gnex days). Thanks a lot guys
Edit: sorry I meant to put this in q and a mods feel free to move
Sent from my Nexus 4 using xda app-developers app
Flash the proper kernel for you ROM hint there are two different builds for 4.3
Sent from my Nexus 4 using xda premium
I did flash the correct kernel. At least I think I'm running cm 4.3 (jss15j) and I tried flashing faux's latest 4.3 kernel. If that is for some reason incorrect which faux or Franco would u recommend?
Edit. Ahh I see what u mean by two different builds. Thanks I thought there was only one build on 4.3
Sent from my Nexus 4 using xda app-developers app
Hello,
I am running CM 10.2 (latest nightly). I flashed the franco kernel r191 for the first time and it bricked the phone. The boot animation won't come up. It gets stuck after the Google logo. I would appreciate if you could help me out. Fortunately, I had a full nandroid backup and was able to recover my phone.
I use the TWRP recovery.
Thanks.
You need to learn what the definition of bricked means.
a bricked phone is worthless and unrecoverable, it makes a great paperweight/door stop. flashing a kernel that wont boot is not bricking a phone, and not close, and there are many ways to recover from a non booting kernel, nandroid restore being one way. you can also just flash a good kernel or your rom to recover.
Thank you for clarifying the definition of brick. I did not know that. Please feel free to chime in regarding my original question. Thank you.
devadam1 said:
Thank you for clarifying the definition of brick. I did not know that. Please feel free to chime in regarding my original question. Thank you.
Click to expand...
Click to collapse
What IS your question? From what I've read, you were able to restore your nandroid, right? Just don't flash that kernel if it messes things up.
Sent from my LG-LS970 using xda app-developers app
try a different franco kernel. are you sure that you pucjed the right kernel? 4.2.2 kernels dont boot on 4.3, and 4.3 kernels dont boot on 4.2.2.
simms22 said:
try a different franco kernel. are you sure that you pucjed the right kernel? 4.2.2 kernels dont boot on 4.3, and 4.3 kernels dont boot on 4.2.2.
Click to expand...
Click to collapse
According to the author, I am supposed to flash the one that has a JSS tag in the file name. http://franciscofranco.minooch.com/Nexus4/4.3/zips/
I am sure I downloaded the correct file and flashed the right version. Since I am new here, I am not allowed to post in the original thread, which is here:
http://forum.xda-developers.com/showthread.php?t=2002782
iamterence said:
What IS your question? From what I've read, you were able to restore your nandroid, right? Just don't flash that kernel if it messes things up.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
I would like to know whether there is a way to flash the franco kernel on CM 10.2. It seems to be buggy. I wanted to post my question here: http://forum.xda-developers.com/showthread.php?t=2002782
But I need at least 10 posts to ask my question there.
devadam1 said:
I would like to know whether there is a way to flash the franco kernel on CM 10.2. It seems to be buggy. I wanted to post my question here: http://forum.xda-developers.com/showthread.php?t=2002782
But I need at least 10 posts to ask my question there.
Click to expand...
Click to collapse
no. custom kernels no longer work on cm properly, if at all.thats probably is the reason why franco kernel wont boot. cm changed their base code from aosp to qualcomm a few weeks ago, and that broke the ability to use custom kernels on cm. custom kernels are based on aosp, and qualcomms code breaks stuff because of it.
Thank you so much! Now I understand why.
Sent from my Nexus 4 using xda app-developers app
when did this start? currently running cm10.2 and Franco190, now I'm scared to update cm as I need Franco for the battery life
Sent from my Nexus 4 using xda app-developers app
Started a couple of days ago. Not sure if the r191 is the cause or the cm 10.2 nightly.
Sent from my Nexus 4 using xda app-developers app
As said previously CM is the cause, Franco still remains AOSP based, you can try hellscore kernel, Google it, it as a nice reputation for amazing battery life and has a CM version of it.
Sent from my Nexus 4 using Tapatalk
devadam1 said:
Started a couple of days ago. Not sure if the r191 is the cause or the cm 10.2 nightly.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
it started with a nightly about 2 weeks ago
Thank you! I'll definitely give it a try.
Sent from my Nexus 4 using xda app-developers app
simms22 said:
it started with a nightly about 2 weeks ago
Click to expand...
Click to collapse
You're right. I just installed the nightly later on.
mine is Sept build good thing I didn't update
Sent from my Nexus 4 using xda app-developers app
albundy2010 said:
You need to learn what the definition of bricked means.
Click to expand...
Click to collapse
simms22 said:
a bricked phone is worthless and unrecoverable, it makes a great paperweight/door stop. flashing a kernel that wont boot is not bricking a phone, and not close, and there are many ways to recover from a non booting kernel, nandroid restore being one way. you can also just flash a good kernel or your rom to recover.
Click to expand...
Click to collapse
Aka: soft brick.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Endoroid said:
Aka: soft brick.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't even like the way that term is used to be honest. To me a soft brick is more or less something that requires a JTAG.
A bootloop or a failed boot just isn't any type of brick at all really as far as I'm concerned.
You really should change the title of the thread. Franco does great work and really does not need to be slandered. After all cm is preventing your device from booting not Franco's kernel. If you want to rant maybe you could change the title to cm bricked my phone
Sent from my Nexus 4 using XDA Premium 4 mobile app
There are some cm11 daily builds for our devices. Which one do you recommend to use? Thanks.
İ think you dont use cm11.. İ suggest psx rom.. Fast, smooth ve stable.. You should try it..you will like it
Sent from my Nexus 4 using xda app-developers app
I second this question. I've seen around 5 unofficial CM11 builds. Of those, which one is good?
Side question, so far, which 4.4 ROM works the best?
Sent from my Nexus 4 using xda app-developers app
İ am using psx kitkat rom.. While i using 4.3 i was using. My favourite is psx rom.. Exactly you should install and live speed
Sent from my Nexus 4 using xda app-developers app
the "what is best" topics aren't really allowed on this forum.
OP is asking about CyanogenMod, not PSX.
You should use Euroskank, it's the next closest to official ÇyanogenMod.
http://fitsnugly.euroskank.com/
sent from tapatalk
Most of them are going to be nearly identical unless the builder has added their own changes. I personally use these, just make sure you choose the ones tagged 4.4, as the poster also does 4.3 and 4.2 builds on a nightly basis.
I'd recommend building your own, if you're capable.
I normally flash whichever one is the most recently compiled. Got to have the latest version right? On the odexed version by Bruce and i think it's the best performer bit i always like euroskank. Always had features before they are merged
Sent from my Nexus 4 using Tapatalk