I would like to know if anybody is working on porting the dev preview. I have it running on my Nexus 4 and its is perfectly stable and honestly I would go as far as to say good enough for a daily driver.
Still has some problems like app compatibility and a few quirky bugs like MMS failing while connected to WiFi but overall I've heard it was pretty fast and battery efficient.
At this point I haven't heard or seen anything released outside of themes.
There really isn't much point porting the Dev preview as there are still quite a few quirks that would probably just become worse with a port. I can't see a developer wanting to spend time porting a rom that really isn't meant as a daily driver even on the devices it's designed for. It would be tough to figure out if a bug is caused by code in the preview build itself, or the ported code.
Unfortunately, you'll probably have to wait until the final release of L for developers to port it (and even then it may take time to iron out the bugs)
Related
I am very happy to see that the android OS is finally taking place on the HTC Blackstone.
The operativesystem is running so smooth already that i am using it on a daily basis.
However we still have some issues left to fix, the two most important i would say is camera and the battery draining issue.
Will we have android ROM's anytime soon, developers?
The OS is already "good-to-go" except for a few issues, but i do think this will be sorted out over time.
Some guys are working on flashing a rhodium and if they're successful, that can be ported over to our devices.
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>
I don't think I fully understand how ROM's device drivers work. Stock is supposed to be more stable because most manufacturers use closed source drivers, which have to be reverse engineered for any non stock ROM (is that correct?).
But on my Nexus 4, I've had the same problems with stability as any other device, despite the open source drivers. Apps still frequently cause my phone to reboot, which from what I understand can only be caused by driver bugs, otherwise the app would simply crash.
Am I just expecting stability AND features and wondering why I can't have my cake and eat it too? I'm running the stable version of SlimKat atm and usually go for stable versions of ROMs that go for speed and stability, no experimental bleeding edge features or anything.
Could anyone explain what I seem to be missing. I'm an amateur programmer so technical details appreciated.
v1nsai said:
I don't think I fully understand how ROM's device drivers work. Stock is supposed to be more stable because most manufacturers use closed source drivers, which have to be reverse engineered for any non stock ROM (is that correct?).
But on my Nexus 4, I've had the same problems with stability as any other device, despite the open source drivers. Apps still frequently cause my phone to reboot, which from what I understand can only be caused by driver bugs, otherwise the app would simply crash.
Am I just expecting stability AND features and wondering why I can't have my cake and eat it too? I'm running the stable version of SlimKat atm and usually go for stable versions of ROMs that go for speed and stability, no experimental bleeding edge features or anything.
Could anyone explain what I seem to be missing. I'm an amateur programmer so technical details appreciated.
Click to expand...
Click to collapse
I wish someone could answer this because I'm considering one of the new Nexus devices because I thought I could have this best of both worlds that he speaks of. Is this not the case, do open source driver devices like Nexus phones suffer with the same issues as other unlocked phones that have closed source drivers?
I hate to be a moaner, and don't get me wrong what you devs do is awesome, but I really can't seem to grasp why everyone puts so much focus towards making sure their s4 has the latest version of android on their phone, even though, it's not really anywhere near stable enough for convenient every day use yet...
You'd think people would be more on the lookout for roms that are fully stable and fully harness their phone's potential instead of constantly flashing builds that could ruin their afternoon suddenly because something broke unexpectedly that they're used to having work perfectly?
I get that there needs to be development and testing, and it's all great work that's being done, but seriously, is there only this little number of stable S4 builds?
I don't care what anybody says, I haven't tried an LP rom yet that's been 100% stable, something always breaks and leaves me rolling back to KK just to have more peace of mind
rynoism said:
I hate to be a moaner, and don't get me wrong what you devs do is awesome, but I really can't seem to grasp why everyone puts so much focus towards making sure their s4 has the latest version of android on their phone, even though, it's not really anywhere near stable enough for convenient every day use yet...
You'd think people would be more on the lookout for roms that are fully stable and fully harness their phone's potential instead of constantly flashing builds that could ruin their afternoon suddenly because something broke unexpectedly that they're used to having work perfectly?
I get that there needs to be development and testing, and it's all great work that's being done, but seriously, is there only this little number of stable S4 builds?
I don't care what anybody says, I haven't tried an LP rom yet that's been 100% stable, something always breaks and leaves me rolling back to KK just to have more peace of mind
Click to expand...
Click to collapse
This things differ from user to user and phone to phone.
A rom might work 100% stable for me and might be very unstable for you. Happens all the time. I see users, running the same rom as me, who have issues that I don't have. Or vice-versa.
And I don't think "Stable" means necessarily bug free. I think it means more in the direction that it won't crash and won't give you random reboots, and that most of the stuff works (only minor problems).
People upgrade due to the performance improvements, battery life improvement potential and, possibly, because of new features and additions the rom and/or kernel has. And some people simply like to have the latest software.
If you have problems, you just go back to the previous version using the backup you (hopefully) made before flashing and wait for a fix.
So far I have run these roms: 5.0.1 GPE, CM12 Optimzed builds, SaberMod CM12 Builds, SaberMod CM12.1 builds and now Resurrection Remix, and haven't had any serious issues or issues that couldn't be fixed.
The only serious problem I ever had was with an early build of SaberMod CM12.1 where the sms app I was using (hello sms) kept crashing when receiving a message. This caused the notification to not show, meaning I could only see that I received a text message when I opened the app.
The most stable and bug free (for me at least) was Danvdh's 5.0.1 GPE rom.
rynoism said:
I hate to be a moaner, and don't get me wrong what you devs do is awesome, but I really can't seem to grasp why everyone puts so much focus towards making sure their s4 has the latest version of android on their phone, even though, it's not really anywhere near stable enough for convenient every day use yet...
You'd think people would be more on the lookout for roms that are fully stable and fully harness their phone's potential instead of constantly flashing builds that could ruin their afternoon suddenly because something broke unexpectedly that they're used to having work perfectly?
I get that there needs to be development and testing, and it's all great work that's being done, but seriously, is there only this little number of stable S4 builds?
I don't care what anybody says, I haven't tried an LP rom yet that's been 100% stable, something always breaks and leaves me rolling back to KK just to have more peace of mind
Click to expand...
Click to collapse
It's because you assume everyone wants a bugfree rom. Some people just want cutting edge technology. Also if something is a bug for you, it doesn't mean that someone else is annoyed by it.
And I have to disagree with you. There are plenty of roms that are stable running Lollipop. Look for example at the CM 12.1. It's ready for daily use and rock solid. Sure there are some minor bugs, but nothing that annoys me.
Bottom line: It comes down to personal preference.
I have searched for literally months now, switching back and forth from stock to CM and this problem is absolutely maddening.
The bluetooth is garbage on CM. Constant stuttering. Anytime I unlock the phone, go to bluetooth settings, or even just leave the phone alone it skips horribly.
Is there any fix or resolution for this? I want the speed and features of CM, but this is ridiculous.
No, it is a CM problem and CM needs to be the one to fix it. Judging from the history of the problem, I doubt that will happen anytime soon.
For me it only stutters if I unlock the phone or if a notification comes in and when it does stutter it only stutters for 3 seconds. I'm on latest resserection remix.
That's the reason I stopped using CM13 on my Nexus 6P and probably never going back to it. At first I thought it was just a bug that cropped up in early builds and it would be quickly addressed, but when the second snapshot didn't fix it I just moved on.
I still can't believe that a serious bug that prevents the use of one of the basic functions of the phone is still ignored by the CM team. Unacceptable, if you ask me. I know CM is free, but it shows the lack of support CM has become notorious for.
That's the underlying problem with CM. There is never a "stable" build, it's a forever work in progress and by the time it reaches a point where is "good enough" as a daily driver, the next version of Android is available, so there is really no point to use it on Nexus devices anymore.
Sorry for the rant, but I was a supporter of CM in the early days and seeing it going down this road is very disappointing.
MaxNXS said:
That's the reason I stopped using CM13 on my Nexus 6P and probably never going back to it. At first I thought it was just a bug that cropped up in early builds and it would be quickly addressed, but when the second snapshot didn't fix it I just moved on.
I still can't believe that a serious bug that prevents the use of one of the basic functions of the phone is still ignored by the CM team. Unacceptable, if you ask me. I know CM is free, but it shows the lack of support CM has become notorious for.
That's the underlying problem with CM. There is never a "stable" build, it's a forever work in progress and by the time it reaches a point where is "good enough" as a daily driver, the next version of Android is available, so there is really no point to use it on Nexus devices anymore.
Sorry for the rant, but I was a supporter of CM in the early days and seeing it going down this road is very disappointing.
Click to expand...
Click to collapse
As was I. I've always loved CM. But when they're releasing "stable" builds that still have this major flaw....on a very popular device, makes me wonder what the hell they're doing.
What a shame.
CM is GARBAGE. As is almost anything based of it other then maybe RR. This is why everyone is re baseing off AOSP.
Sent from a Shaftamle Nexus 6P
"Thanks Button" is always appreciated!
149ThemedGoogleKeyboards!!!!!!
Double R - 6.0.1
To add onto what @Shaftamle said, ultimately the reason there are even CM based ROMs around is because CM has done the work to bring up support for almost every Android device imaginable (kernels, device trees, vendor blobs, etc). So it is easy for someone to fork CM and add their own mods and make it their own (like AICP, RR, and Temasek) while keeping support for all of those devices and making a name for themselves. CM is technically AOSP mixed with CAF for all of those other devices but it is not needed on Nexus devices and ends up screwing some stuff up. What would be ideal is for ROMs to have a pure AOSP variant for the Nexus devices and an AOSP + CAF (CM) variant for all other devices. Dirty Unicorns is a prime example of this. It is more effort for the developers but it makes for a better user experience. Just my two cents.
Cvansetten said:
I have searched for literally months now, switching back and forth from stock to CM and this problem is absolutely maddening.
The bluetooth is garbage on CM. Constant stuttering. Anytime I unlock the phone, go to bluetooth settings, or even just leave the phone alone it skips horribly.
Is there any fix or resolution for this? I want the speed and features of CM, but this is ridiculous.
Click to expand...
Click to collapse
Hasn't anyone got this solution yet im using unofficial cm13 and doesn't turn on Bluetooth