Related
So, I finally bought an HDMI cable for My EVO, but when I did some research Most Kernels Do not support HDMI Output..!!!!
FML RIght!!!
so, I was wondering.....................
Which Kernels support HDMI Output while not sacrificing most of the Benefits of having a Custom Kernel..
I am currently running Netarchy Toastmod 4.1.9.1
I would greatly Appreciate it if someone can point me in the right direction!
ins0dus said:
So, I finally bought an HDMI cable for My EVO, but when I did some research Most Kernels Do not support HDMI Output..!!!!
FML RIght!!!
so, I was wondering.....................
Which Kernels support HDMI Output while not sacrificing most of the Benefits of having a Custom Kernel..
I am currently running Netarchy Toastmod 4.1.9.1
I would greatly Appreciate it if someone can point me in the right direction!
Click to expand...
Click to collapse
If you are using one of my kernel builds you already have hdmi output support.
I am Using your Kernel !! Love it by the way!!
Just that whenever I hook up my cable to my Phone nothing happens?????
Is it the Rom thats causing this then??? im using Virus Rom Sense RC3
if So, how can I fix this?
HDMI output doesn't work for every function on the phone, only certain ones. So you won't get your home screen on your HDMI TV, for instance.
Slideshow, YouTube and gallery video will play over hdmi. Nets roms all support hdmi except the fresh compatible cfs 4.1.9.1 does not do Slideshow. If you flash that first and then flash anything else other than the stock kernel Slideshow still won't work.
I was Using Netarchy 4.1.9.1 but when I connected the HDMI cable. Nothing popped up in the homescrean showing that I had connected an HDMI Cable to the Phone.. its like if nothing happened!
Just curious. I have about decided that Paranoid Android is going to be my rom of choice for my Nexus 7. Looking to see what kernel everyone is running and which one they think is best.
I've been using trinity for a few days with that paranoid and it has been working brilliantly, the battery life is excellent, very quick, and any instability I can definitely credit towards my inexperienced tinkering
Sent from my Nexus 7 using xda app-developers app
You can use the Franco Kernel, or otherwise (my favourite) Faux ES Kernel!
Careful with faux123 014b1/014b1es kernels
chris.wueste said:
Just curious. I have about decided that Paranoid Android is going to be my rom of choice for my Nexus 7. Looking to see what kernel everyone is running and which one they think is best.
Click to expand...
Click to collapse
I also love faux123 kernels, especially 013m (or 013es if battery life is an issue). USB OTG charging works if enabled in FauxClock, very stable.However, 014b1/b1es freezes if Bluetooth is enabled and BT device connects.
Hope it helps.
Running M-Kernel - a29 here. Been trying out a few for the past couple days. Best advice I can give you: play with each one for a while and makes some notes of how your device feels with each kernel.
Also, check out this thread if you haven't already: http://forum.xda-developers.com/showthread.php?t=1889571
ever process is different and hence react differently to kernels, try and test for urself thats the only way ull know for sure.
and for average scoring for battery and benchmarks i suggest visiting this thread
http://forum.xda-developers.com/showthread.php?t=1889571
Which kernel would increase speed and numbers in quadrant standard?
xateeq said:
ever process is different and hence react differently to kernels, try and test for urself thats the only way ull know for sure.
and for average scoring for battery and benchmarks i suggest visiting this thread
http://forum.xda-developers.com/showthread.php?t=1889571
Click to expand...
Click to collapse
This. There is no such animal as an across the board best kernel.
Sent from my Galaxy Nexus using Tapatalk 2
I see a lot of lag and complete lockups on my Nexus 7. The only kernel I haven't seen this on is m-kernel. Just my 2 cents.
Sent from my Galaxy Nexus using xda premium
Hey I just ordered my nexus 4. Just a quick question, which custom rom most resembles the stock one that the n4 comes with but with better tweaks and battery life?
Coming from an s3 and I've always used a touchwiz based custom rom.
So I would like to stay with the rom that most is similar to the one the n4 comes with. Ty
Sent from my SGH-T999 using xda app-developers app
Probably Primerunner under Nexus 4 Android Development. Seems pretty stock but with some enhancements.
Sent from my Nexus 4 using Tapatalk 2
MiNCO v6 ROM resembles the stock ROM. No customizations.
Sent from my Nexus 4 using Tapatalk 2
All of them resemble stock. They're all themed the same, it's just a matter of added features while maintaining the same look as stock.
I don't get what you're trying to get at op. It's not like s3 roms where everybody is trying to theme their rom. A lot of roms on n4 aren't themed, some are but most are left it's holo look.
Sent from my Nexus 4 using xda premium
zephiK said:
All of them resemble stock. They're all themed the same, it's just a matter of added features while maintaining the same look as stock.
I don't get what you're trying to get at op. It's not like s3 roms where everybody is trying to theme their rom. A lot of roms on n4 aren't themed, some are but most are left it's holo look.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I guess... From a stability point of view... To be as stable as the stock.
I've ran cm10.1 and cm10...Along with some other aokp roms on my s3 before and of course it's not as stable as the stock tw rom.
Sent from my SGH-T999 using xda app-developers app
Minco
Sent from my Nexus 4 using xda premium
All the ROMs should be very stable since they are all based on the same AOSP code. This is very different from a non-Nexus phone where custom ROMs might be less stable.
Sent from my Nexus 4 using xda premium
Don't want to create new thread so will ask here as I'm also coming from S3...
Are the any major bugs with CM rom? With the S3, Picassa sync and Bluetooth didn't work...I'm assuming with the N4 everything should be more or less 100%?
steviewevie said:
All the ROMs should be very stable since they are all based on the same AOSP code. This is very different from a non-Nexus phone where custom ROMs might be less stable.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Yeah that makes sense... Thanks.
Sent from my SGH-T999 using xda app-developers app
Crisisx1 said:
I guess... From a stability point of view... To be as stable as the stock.
I've ran cm10.1 and cm10...Along with some other aokp roms on my s3 before and of course it's not as stable as the stock tw rom.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Well the difference is that this is NEXUS device and is AOSP supported. So 99.9% of the ROMs that come out for this phone are stable. They're not stable on the S3 for AOKP/CM right away because they have to actually do work to make it work; whereas, N4 is AOSP supported and its like.. BAM! it works out of the box. As for S3, the phone ships out with TouchWiz. Going from TouchWiz to AOSP requires work to make everything work.
I'd say CM/AOKP are pretty stable overall. All ROMs are stable. This is one of the many benefits of having a Nexus device and I don't believe in when people are wanting to upgrade and people say "oh just get a S3.. it doesnt have latest but just flash a custom rom and you'll be on latest android) no it doesn't work that way just because of like what you said... instablity. When Android 5.0 (Key Lime Pie) comes out, N4 will be one of the first devices to launch with it and we'll have the most stable ROM day one without having to rework code to make all the functionalities like calling, 3G/4G, WiFi, Bluetooth, Screen Rotation, Data, etc to work (I know on other phones, people release dirty ROMs and things like what I listed don't work as of yet until its fixed)
Shopping for a ROM/Kernel is like shopping for a car. Some tips to take,
1) Browse the original and android dev forums. Search around and look for whats interesting.
2) Find it interesting? Read OP post and the past 6-7 posts (dont even read it.. skim through it for feedback)
3) Like what you see? Check for screenshots or even a YouTube video
4) Still like it? Flash it and try it
and most of all, ENJOY.
zephiK said:
Well the difference is that this is NEXUS device and is AOSP supported. So 99.9% of the ROMs that come out for this phone are stable. They're not stable on the S3 for AOKP/CM right away because they have to actually do work to make it work; whereas, N4 is AOSP supported and its like.. BAM! it works out of the box. As for S3, the phone ships out with TouchWiz. Going from TouchWiz to AOSP requires work to make everything work.
I'd say CM/AOKP are pretty stable overall. All ROMs are stable. This is one of the many benefits of having a Nexus device and I don't believe in when people are wanting to upgrade and people say "oh just get a S3.. it doesnt have latest but just flash a custom rom and you'll be on latest android) no it doesn't work that way just because of like what you said... instablity. When Android 5.0 (Key Lime Pie) comes out, N4 will be one of the first devices to launch with it and we'll have the most stable ROM day one without having to rework code to make all the functionalities like calling, 3G/4G, WiFi, Bluetooth, Screen Rotation, Data, etc to work (I know on other phones, people release dirty ROMs and things like what I listed don't work as of yet until its fixed)
Shopping for a ROM/Kernel is like shopping for a car. Some tips to take,
1) Browse the original and android dev forums. Search around and look for whats interesting.
2) Find it interesting? Read OP post and the past 6-7 posts (dont even read it.. skim through it for feedback)
3) Like what you see? Check for screenshots or even a YouTube video
4) Still like it? Flash it and try it
and most of all, ENJOY.
Click to expand...
Click to collapse
Great reply... awesome, makes a lot more sense now. Thank you. I can't wait til my N4 arrives : )))
I've been reading at other threads about people complaining about quick battery drain and the screen not looking too good... I hope that isn't the case with me.. but I'm pretty sure a custom rom and kernel can fix all of that.
Crisisx1 said:
Great reply... awesome, makes a lot more sense now. Thank you. I can't wait til my N4 arrives : )))
I've been reading at other threads about people complaining about quick battery drain and the screen not looking too good... I hope that isn't the case with me.. but I'm pretty sure a custom rom and kernel can fix all of that.
Click to expand...
Click to collapse
Quick battery drain. Hmmmm, you will probably notice that battery won't be good until at least 2-3 charge cycles. Why?
1. You just got the phone, obviously you're going to be playing with the phone. Downloading apps, changing settings, setting up your home screen etc.
2. It takes time for the phone to get its charging cycle.
3. Stock kernel has the msm wakelock. Fixed in a future OTA.
Screen looks great. I don't have any problems. But yes you are right, custom kernel does fix #3 and you can alter your colors until it satisfy your eyes. Stock values are good enough for me. It looks A LOT better than Samsung's Super AMOLED, I came from a Galaxy Nexus.
Hey guys,
I`am thinking of ordering a Oppo Find 5 32GB, i have a Nexus 4 atm and i`am looking for something new.
Is it a definate upgrade? The specs on paper seem great but how does the phone do in real life.
Would appreciate some user feedback
Same here. I am thinking of doing the same. I am particularly hoping for a stable PA/CM10.1 ROM soon, and more kernel development if possible.
gee2012 said:
Hey guys,
I`am thinking of ordering a Oppo Find 5 32GB, i have a Nexus 4 atm and i`am looking for something new.
Is it a definate upgrade? The specs on paper seem great but how does the phone do in real life.
Would appreciate some user feedback
Click to expand...
Click to collapse
it's not a goodupgrade..
same CPU, RAM, GPU, same problems with: OTG, no microSD expansion, no removable battery
you get a better/larger display, slightly better(in specs) or worse(in terms of software capabilities so far) camera....
and worse battery life / smoothless/performance in ROMs.....and more expensive
no matter how good the CM10.1 port for the find 5 is, nexus 4 ports will be snappier as they have the backing of google
If ports are based on aosp how can they be snappier .....only a bit of kernel tweaks and some camera enhancements will make this phone awesome
Sent from my Find 5 using Tapatalk 2
munchy_cool said:
If ports are based on aosp how can they be snappier .....only a bit of kernel tweaks and some camera enhancements will make this phone awesome
Sent from my Find 5 using Tapatalk 2
Click to expand...
Click to collapse
i'm talking specifically about the device/kernel tree....
for nexus 4, it comes from google (who has access to all the proprietary documents, binaries)
for oppo find 5, it comes from people like XpLoDWilD, Entropy512, ... . They may have to interpret that info based on how the Oppo Stock Rom works, previous experience, hacks needed to make stuff work...
this portion will contain bugs / inefficiencies in the codebase
and when you move from different android versions, the proprietary binaries differ and may not be compatible. For Nexus devices, google gives you those updated binaries... for other devices (like Oppo), you may have to beg Oppo to get the latest binaries, steal it from a similar device that has the update, or hack your way (which creates inefficiencies / bugs)
see: https://developers.google.com/android/nexus/drivers
this is why you have: stable cm10.1 ports on some devices, but still buggy/slow compared to the nexus line
paperWastage said:
i'm talking specifically about the device/kernel tree....
for nexus 4, it comes from google (who has access to all the proprietary documents, binaries)
for oppo find 5, it comes from people like XpLoDWilD, Entropy512, ... . They may have to interpret that info based on how the Oppo Stock Rom works, previous experience, hacks needed to make stuff work...
this portion will contain bugs / inefficiencies in the codebase
and when you move from different android versions, the proprietary binaries differ and may not be compatible. For Nexus devices, google gives you those updated binaries... for other devices (like Oppo), you may have to beg Oppo to get the latest binaries, steal it from a similar device that has the update, or hack your way (which creates inefficiencies / bugs)
see: https://developers.google.com/android/nexus/drivers
this is why you have: stable cm10.1 ports on some devices, but still buggy/slow compared to the nexus line
Click to expand...
Click to collapse
I agree with you but that's the case with all non-Google devices.
if you want latest android version you gotta stick with Google devices.
munchy_cool said:
I agree with you but that's the case with all non-Google devices.
if you want latest android version you gotta stick with Google devices.
Click to expand...
Click to collapse
i'm talking about the device tree on the current android version.... device tree port by CM developers vs device tree from google
since hardware is mostly the same from nexus 4, but you're moving software-wise from a "optimized" port (with device tree from google) to a Cm10.1 port (with device tree that is still buggy and not optimized by google)..
don't see the reason to switch from nexus 4.
Find 5: aosp -> cm10.1 + device tree from CM developers = ROM
Nexus 4: aosp -> cm10.1 + google's device tree = better ROM
replace cm10.1 with anything else (AOKP, PAC, PA)...
paperWastage said:
i'm talking about the device tree on the current android version.... device tree port by CM developers vs device tree from google
since hardware is mostly the same from nexus 4, but you're moving software-wise from a "optimized" port (with device tree from google) to a Cm10.1 port (with device tree that is still buggy and not optimized by google)..
don't see the reason to switch from nexus 4.
Find 5: aosp -> cm10.1 + device tree from CM developers = ROM
Nexus 4: aosp -> cm10.1 + google's device tree = better ROM
Click to expand...
Click to collapse
the reason to switch from n4 would be better & bigger screen, but in that case I would recommend the DNA
I'm making the switch. Mainly for the screen and I didn't feel like paying $650 for the dev HTC One. It'll be interesting to see how Oppo's firmware is as well.
I switched from a Nexus 4 that I've had since November. I was just getting tired of the device and was looking for something with a slightly larger/higher resolution display, but I wasn't looking for a full on phablet (Note II). I have been incredibly satisfied with the unit's build quality and am only slightly thrown off by it's less than stellar stock rom. No worries though, as PA has been rock solid for me. :good::good: Two thumbs up on making the switch!
I'm also thinking of making the switch and also coming from a nexus 4. What I want to see get more development though is on the android ROMs as there are none. On the original android development I do see cm 10.1,pa,ect.. Which is pretty much the stuff I'm running on the nexus 4 already. I wanna see oppo find 5 u.i based roms.if I'm gonna make the switch and use the same base ROMs as the nexus 4 I might as well stick with the nexus 4 instead.
marcviado said:
I'm also thinking of making the switch and also coming from a nexus 4. What I want to see get more development though is on the android ROMs as there are none. On the original android development I do see cm 10.1,pa,ect.. Which is pretty much the stuff I'm running on the nexus 4 already. I wanna see oppo find 5 u.i based roms.if I'm gonna make the switch and use the same base ROMs as the nexus 4 I might as well stick with the nexus 4 instead.
Click to expand...
Click to collapse
I think it is pretty unlikely that you'll see a lot of custom ROM's for Find 5, considering much lower number of users compared to other phones.
I think i`am gonna stick with the N4 for now and mainly for its optimized firmware. The firmware of the Oppo is clearly not as good (or finished) as the N4`s. Pitty, would have liked to try it out. Aah well, maybe at a later point or its successor. Thanks for the reply`s guys :good:
marcviado said:
I'm also thinking of making the switch and also coming from a nexus 4. What I want to see get more development though is on the android ROMs as there are none. On the original android development I do see cm 10.1,pa,ect.. Which is pretty much the stuff I'm running on the nexus 4 already. I wanna see oppo find 5 u.i based roms.if I'm gonna make the switch and use the same base ROMs as the nexus 4 I might as well stick with the nexus 4 instead.
Click to expand...
Click to collapse
MIUI is the closest "alternative" to Find 5's stock UI rom... find one (probably won't be on XDA) that works on a phone you would want, then buy that phone
next alternative would be the iPhone
N4 owner as well. While I have a hard time putting down my Find 5, if I'm to be totally honest, the N4 is hard to beat. Mostly software I guess, its hard to find a flaw. The Find 5 is still being optimized and tweaked on a regular basis... which is great but not needed in the Nexus. Still though, the Find 5 is one nice device with a lot of potential!
sent from my <Nexus 7>
We can basicly use this thread for discussion, general talk, Q/A as long as its about CM.
Bugs:
Deadlocks (JSS15J bug)
Miracast & PTV3000
You tell me
F.A.Q
Enable root: Developer settings->Root Access->Apps and ADB. Also turn on USB-debugging.
Gapps: Photosphere is not included in standard gapps, use an alternative gapps package.
Links:
Download: http://get.cm/?device=flo (Wi-Fi)
GApps: http://goo.im/gapps
BBQLog: http://changelog.bbqdroid.org/#/flo/next
Whats a deadlock? Its obviously different from a wakelock? I have been on CM10.2 for a week now, surprising no noticable issues day to day. Good performance and battery life.
Just tested out Miracast last night using the Rocketfish receiver (RF-WFD301) from BB. Miracast worked for me although there were some pixelations and momentary screen freezes here and there. Of course, there's also the lag that you'd expect with Miracast at this stage.
Am on the latest CM10.2 nightly which was cm-10.2-20130819-NIGHTLY-flo.zip when I tested.
Planning to return the Miracast receiver though. Don't think the technology is quite ready for prime time yet and personally, was more of a urge to check it out but don't really have a need for it.
I mentioned this elsewhere, but I might as well bring it up here too since this will probably turn into a more official thread...
I've noticed here that my tablet isn't automounting USB drives (via OTG) on its own; I need an external app to do that, unlike my phone (d2att; both devices running 8/21 right now).
Is this intentional, a hiccup, or something else?
Deadlock is when it freezes, caused by a keyboard bug
Sent from my Nexus 7 using Tapatalk 4
I've only had one deadlock and I flash about 2 nightlies a week
CM Kanged rom is working great here. No more reboots and lots of options. Closest thing to the official AOKP rom there is until they start making AOKP 4.3 roms.
I did have one deadlock that recovered but I was updating some apps, which is expected from time to time.
I'm using a release from 8/8. Can't find a reason to update. I think there might be some issues with 8/20 because I tried many CM based nightly ROMs and all FC the AOSP keyboard on my Galaxy Nexus. Flashed a 8/18 nightly and it appears fine.
I'm happy with the CM Kanged rom until they mature enough to upgrade. Fast, smooth, no quirks, no random reboots like stock ROMs experience. Quite happy. It has the new HALO notification and SideBar built in. Probably has that weird navigation PA feature too that I don't use. HALO is weird but growing on me. Works good on a tab. Not sure about using it on my phone yet. I had to watch a video on how to use it before it really made sense.
Sent from my Nexus 7 using XDA Premium 4 mobile app
cowabunga said:
Just tested out Miracast last night using the Rocketfish receiver (RF-WFD301) from BB. Miracast worked for me although there were some pixelations and momentary screen freezes here and there. Of course, there's also the lag that you'd expect with Miracast at this stage.
Am on the latest CM10.2 nightly which was cm-10.2-20130819-NIGHTLY-flo.zip when I tested.
Planning to return the Miracast receiver though. Don't think the technology is quite ready for prime time yet and personally, was more of a urge to check it out but don't really have a need for it.
Click to expand...
Click to collapse
Might be ptv3000 issue then, removing it from bugs list.
smelenchuk said:
I mentioned this elsewhere, but I might as well bring it up here too since this will probably turn into a more official thread...
I've noticed here that my tablet isn't automounting USB drives (via OTG) on its own; I need an external app to do that, unlike my phone (d2att; both devices running 8/21 right now).
Is this intentional, a hiccup, or something else?
Click to expand...
Click to collapse
This is normal on nexus devices as far as I know.
Sent from my Nexus 7 using Tapatalk 4
Hey utacka ..lived your work on PA for the note !!
Planning to dev for the flo as well ??
Sent from my HTC One using Tapatalk 2
aamitabh28 said:
Hey utacka ..lived your work on PA for the note !!
Planning to dev for the flo as well ??
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Not planning going back to PA, maybe some gerrit patches to CM (mako, flo or whatever).
Sent from my Nexus 7 using Tapatalk 4
This is the first time I've ever run a CM rom. How long will it take them to incorporate JSS15Q now that its out?
Utacka said:
This is normal on nexus devices as far as I know.
Click to expand...
Click to collapse
Is this a hardware issue, then? That sounds implausible at best.
SalTNutz said:
This is the first time I've ever run a CM rom. How long will it take them to incorporate JSS15Q now that its out?
Click to expand...
Click to collapse
Yeah. How long will it take CM10.2 to pick the latest update changes up?
Should we expect overclocking options in the official CM in the future? I'm curious to see what my device can handle, but I prefer to stick with official CM builds where I can trust that code is the same as what's public.
Sent from my Nexus 7 using xda app-developers app
ragesoss said:
Should we expect overclocking options in the official CM in the future? I'm curious to see what my device can handle, but I prefer to stick with official CM builds where I can trust that code is the same as what's public.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
You usually have to install one of the other developer kernels to get fancy with the kernel (ie. OC, UV, fancy governors, fancy schedulers, etc...).
cowabunga said:
Yeah. How long will it take CM10.2 to pick the latest update changes up?
Click to expand...
Click to collapse
I'm not seeing them yet. Give it some time.
8/13 just came out for a bunch of devices including flo. Not sure if the latest stock update fixes (ie. multi touch, gps, etc...) are in this build.
cowabunga said:
8/13 just came out for a bunch of devices including flo. Not sure if the latest stock update fixes (ie. multi touch, gps, etc...) are in this build.
Click to expand...
Click to collapse
I trust you mean 8/23
And no, the stock update fixes aren't in it.
I don't know if it's just me but, every time i launch the focal app the image that I get is always darker than with the stock camera app?
Sent from my Nexus 7 using xda app-developers app
cowabunga said:
8/13 just came out for a bunch of devices including flo. Not sure if the latest stock update fixes (ie. multi touch, gps, etc...) are in this build.
Click to expand...
Click to collapse
They will be in the next build
Anyone successfully changed the CPU governor to Interactive? Mine reboots a few seconds after setting it to that