Related
Hi, I have seen news about Oppo releasing the Kernel Source and supporting the AOSP community (the same Sony and HTC right now).
My question is, when Android 5.0 and a CM11 is released, does this source or information already released today about the device works for future releases of AOSP based ROMs without the support of the company?
Trying to be clear, Oppo (Sony and HTC too...) release some source today, but the next year they don't support this model, can the AOSP ROMs implement a new stable version using that last year released source from a prior Android version?
Thanks
pedroren said:
Hi, I have seen news about Oppo releasing the Kernel Source and supporting the AOSP community (the same Sony and HTC right now).
My question is, when Android 5.0 and a CM11 is released, does this source or information already released today about the device works for future releases of AOSP based ROMs without the support of the company?
Trying to be clear, Oppo (Sony and HTC too...) release some source today, but the next year they don't support this model, can the AOSP ROMs implement a new stable version using that last year released source from a prior Android version?
Thanks
Click to expand...
Click to collapse
No one knows. We would hope so, but no one would really know. Maybe.
Sent from my Oppo Find 5
kernel-wise - the cyanogenmod team has been able to merge it with the Qualcom sources, so if Qualcom keeps it up to date (most likely yes), then that's no problem (also, nexus 4 shares a lot of the same underlying hardware: CPU/SoC, GPU... that device will get updates, which could be ported over)
http://forum.xda-developers.com/showpost.php?p=40671515&postcount=5
proprietary library-wise - maybe? sometimes, they're compatible cross-android version, sometimes not, and you have to do workarounds to make it work on the new version.... could also steal libraries from other devices (see nexus 4 again)
Hey guys,
I use version 4.4.4-2015-02-18-jflte-NIGHTLY on my S4. Till this version updating works fine but now no updates are shown at the integrated updater. When I try to update by downloading the rom manually and flashing it with TWRP (2.8.4.0), I loose my IMEI and Baseband and have no connection to mobile network anymore. Restoring the backup let me use my phone again but updating my phone doesn't work.
I searched on the internet and found, it may be a problem with the modem and installing the modem after updating would fix it, but this solution didn't work for me.
Is there anyone with an idea what I can try?
Thank you!
The same problem
Hi,
I'm with the same problem that fukuk: I haven't had connection since February updates
I hope you can help us! Thank you very much for all your work
Since I don't believe @jakew02 no longer has his jflte, we probably should have killed nightlies for this device ages ago.
It's not going to get fixed unless someone who actually owns the device troubleshoots it. There's nothing in the commit history for anything on the 4.4 branch that would explain breakage on February 18 - everyone was working on Lollipop by then.
Entropy512 said:
Since I don't believe @jakew02 no longer has his jflte, we probably should have killed nightlies for this device ages ago.
It's not going to get fixed unless someone who actually owns the device troubleshoots it. There's nothing in the commit history for anything on the 4.4 branch that would explain breakage on February 18 - everyone was working on Lollipop by then.
Click to expand...
Click to collapse
I still have it, it's just been collecting a fine layer of dust for the past few months, I've been overwhelmed with classes (starting to get into doing clinical psych work and writing papers every single week) and a new job..
I do have the android-5.0 branch booting on it right now, I just have to work out some bugs before I push anything to gerrit
jakew02 said:
I still have it, it's just been collecting a fine layer of dust for the past few months, I've been overwhelmed with classes (starting to get into doing clinical psych work and writing papers every single week) and a new job..
I do have the android-5.0 branch booting on it right now, I just have to work out some bugs before I push anything to gerrit
Click to expand...
Click to collapse
No problem. Can you reproduce this issue that supposedly started on Feb 18? I've been seeing various people complaining about it but can't figure out what might have caused it - since no one merged anything to the 4.4 branches around then...
Entropy512 said:
No problem. Can you reproduce this issue that supposedly started on Feb 18? I've been seeing various people complaining about it but can't figure out what might have caused it - since no one merged anything to the 4.4 branches around then...
Click to expand...
Click to collapse
Same here I have this issue..
Still we wait for fix or explain how to fix it.
System and radio logcats from both a working and broken build would be useful, along with a dmesg
Also which exact jflte variant you have WHEN you post the logs.
The problem is, if you look through Gerrit's merge history, nothing was merged between February 13 and February 27.
The only thing that might have caused radio issues is https://gerrit.omnirom.org/#/c/11694/ - but that would've broken things on the February 14 build, and all builds from the 14th onward would be broken - but builds from the 14th to 18th are apparently OK?
Guys, is there any way to download the offical jflte 18-2-2015 version?
your help is much appreciated.
alfayez0z said:
Guys, is there any way to download the offical jflte 18-2-2015 version?
your help is much appreciated.
Click to expand...
Click to collapse
I just flashed the 2015-04-16 build and indeed the ril is broken.
I flashed my android-5.1 build from about an hour ago and rather than having the "no service" icon (outline of signal bars), it just says "No SIM", so I'm pretty sure RIL is working in this android-5.1 build. I just don't have Sprint service (but a Sprint variant, since it was the cheapest on Swappa when I bought this replacement last year) to actually test the calling, BUT a guy at work has Sprint so I can probably bug him this weekend for his SIM card, unless I can get a Sprint tester here?
jakew02 said:
I just flashed the 2015-04-16 build and indeed the ril is broken.
I flashed my android-5.1 build from about an hour ago and rather than having the "no service" icon (outline of signal bars), it just says "No SIM", so I'm pretty sure RIL is working in this android-5.1 build. I just don't have Sprint service (but a Sprint variant, since it was the cheapest on Swappa when I bought this replacement last year) to actually test the calling, BUT a guy at work has Sprint so I can probably bug him this weekend for his SIM card, unless I can get a Sprint tester here?
Click to expand...
Click to collapse
I have the GT-I9505 jfltexx, i will be glad to help if i can. I'm ready
jakew02 said:
I just flashed the 2015-04-16 build and indeed the ril is broken.
I flashed my android-5.1 build from about an hour ago and rather than having the "no service" icon (outline of signal bars), it just says "No SIM", so I'm pretty sure RIL is working in this android-5.1 build. I just don't have Sprint service (but a Sprint variant, since it was the cheapest on Swappa when I bought this replacement last year) to actually test the calling, BUT a guy at work has Sprint so I can probably bug him this weekend for his SIM card, unless I can get a Sprint tester here?
Click to expand...
Click to collapse
Out of curiosity, does a self-build from the 4.4 trees have broken RIL?
If so that says there's something that needs to be cleaned out/up in the build server.
I didn't try out a self build I used the jenkins build from the server to replicate the scenario of a user downloading and flashing normally. I'll fire up a self build now with the 4.4 branches and check.
jakew02 said:
I didn't try out a self build I used the jenkins build from the server to replicate the scenario of a user downloading and flashing normally. I'll fire up a self build now with the 4.4 branches and check.
Click to expand...
Click to collapse
Is there any update?
Entropy512 said:
No problem. Can you reproduce this issue that supposedly started on Feb 18? I've been seeing various people complaining about it but can't figure out what might have caused it - since no one merged anything to the 4.4 branches around then...
Click to expand...
Click to collapse
Entropy512 said:
Out of curiosity, does a self-build from the 4.4 trees have broken RIL?
If so that says there's something that needs to be cleaned out/up in the build server.
Click to expand...
Click to collapse
I'm testing something right now to fix RIL for the 4.4 builds. I had moved the property out of the common device tree and forgot to add it to the jflte specific tree while I was working on another device.
Tonight's nightly should be fine, I'm compiling now to verify before submitting.
jakew02 said:
I'm testing something right now to fix RIL for the 4.4 builds. I had moved the property out of the common device tree and forgot to add it to the jflte specific tree while I was working on another device.
Tonight's nightly should be fine, I'm compiling now to verify before submitting.
Click to expand...
Click to collapse
That's strange - how did it break on Feb 18 as opposed to some other time then?
I don't see any changes to qcom-common or msm8960-common for quite some time?
I fixed it. I pushed a commit to samsung qcom common to move Ril to the device trees while I was bringing up lt03 and npushforgot to push to jf.
It's been fixed so the next nightly build will be working, confirmed on my device. Without Sim it still has signal bars
jakew02 said:
I fixed it. I pushed a commit to samsung qcom common to move Ril to the device trees while I was bringing up lt03 and npushforgot to push to jf.
It's been fixed so the next nightly build will be working, confirmed on my device. Without Sim it still has signal bars
Click to expand...
Click to collapse
Yeah. Thanks for figuring out why it broke.
I still wish I knew how it was working from October through until the build server housecleaning in February, since it should not have been working.
Great, thank you!
When will it be possible to download it? Last available version is 2015-04-17.
Thanks you all, Confirm now it's working fine.
When Moto X Play is getting official CyanogenMod 13? Any updates?
Nitish247 said:
When Moto X Play is getting official CyanogenMod 13? Any updates?
Click to expand...
Click to collapse
Probably never. Does it matter? No, not at all. What is better about an official version compared to the unofficial? Nothing at all.
But why? Any specific reason? All Moto phones till date have official CM.
It's my understanding cm13 will turn official some day.
Nitish247 said:
But why? Any specific reason? All Moto phones till date have official CM.
Click to expand...
Click to collapse
If you are following the cm13 thread then you would know that squid has told that he would push for the cm13 build to become official but there is no estimated time.
Sent from my XT1562 using Tapatalk
It's a matter of fixing bugs. My intention has always been to make CM13 official once it is ready. There are three bugs blocking this:
Use of WiFi assisted location causes soft reboots if you don't add additional bounds checking. I am not sure if this bounds checking should really be there or if it is a symptom of some other problem.
A mysterious issue with the new camera drivers is causing memory corruption in the audio HAL. I'm not sure of the cause (other than the crash only happening when liboemcamera is updated to the Marshmallow version). I have a crude hack to work around this, but it is not suitable for merging into official CM. This will be tricky to debug and fix properly.
The RIL needs fixing on XT1562. I don't have an XT1562, so that makes it more difficult for me to troubleshoot, but @scritch007 will be looking into this in the coming days.
squid2 said:
It's a matter of fixing bugs. My intention has always been to make CM13 official once it is ready. There are three bugs blocking this:
Use of WiFi assisted location causes soft reboots if you don't add additional bounds checking. I am not sure if this bounds checking should really be there or if it is a symptom of some other problem.
A mysterious issue with the new camera drivers is causing memory corruption in the audio HAL. I'm not sure of the cause (other than the crash only happening when liboemcamera is updated to the Marshmallow version). I have a crude hack to work around this, but it is not suitable for merging into official CM. This will be tricky to debug and fix properly.
The RIL needs fixing on XT1562. I don't have an XT1562, so that makes it more difficult for me to troubleshoot, but @scritch007 will be looking into this in the coming days.
Click to expand...
Click to collapse
Great news. Laud your hard work have a great year ahead squid2
Sent from my XT1563 using Tapatalk
squid2 said:
It's a matter of fixing bugs. My intention has always been to make CM13 official once it is ready. There are three bugs blocking this:
Use of WiFi assisted location causes soft reboots if you don't add additional bounds checking. I am not sure if this bounds checking should really be there or if it is a symptom of some other problem.
A mysterious issue with the new camera drivers is causing memory corruption in the audio HAL. I'm not sure of the cause (other than the crash only happening when liboemcamera is updated to the Marshmallow version). I have a crude hack to work around this, but it is not suitable for merging into official CM. This will be tricky to debug and fix properly.
The RIL needs fixing on XT1562. I don't have an XT1562, so that makes it more difficult for me to troubleshoot, but @scritch007 will be looking into this in the coming days.
Click to expand...
Click to collapse
Thanks! Thats' awesome! :good:
We expect lux on official CyanogenMod list soon
squid2 said:
It's a matter of fixing bugs. My intention has always been to make CM13 official once it is ready. There are three bugs blocking this:
Use of WiFi assisted location causes soft reboots if you don't add additional bounds checking. I am not sure if this bounds checking should really be there or if it is a symptom of some other problem.
A mysterious issue with the new camera drivers is causing memory corruption in the audio HAL. I'm not sure of the cause (other than the crash only happening when liboemcamera is updated to the Marshmallow version). I have a crude hack to work around this, but it is not suitable for merging into official CM. This will be tricky to debug and fix properly.
The RIL needs fixing on XT1562. I don't have an XT1562, so that makes it more difficult for me to troubleshoot, but @scritch007 will be looking into this in the coming days.
Click to expand...
Click to collapse
I tried the version from the 25th of December, and I don't have any issue with it (I own a dual sim xt1562) and only have one sim inserted, but just after the boot I was prompted for the pin code. So I won't be of any help...
I'm running the 24.11.18.lux_retasia_ds.retasiaall.en.03 retfr version as my main version, so all my partitions were updated to 6.0
I think mi note 2 has been out for a long time but it seems that developers without much attention to this phone. I'm curiously Why ?
Because of old story - MIUI never release kernel source code ? or ...
Whatever it is, I would like to see there is lineageOS 14.1 in this phone.
Kris Chen said:
I think mi note 2 has been out for a long time but it seems that developers without much attention to this phone. I'm curiously Why ?
Because of old story - MIUI never release kernel source code ? or ...
Whatever it is, I would like to see there is lineageOS 14.1 in this phone.
Click to expand...
Click to collapse
It's the old story of lack of kernel source. Historically kernel sources have been released about 3/4 months after global rom availability, which happened a few days ago.
It doesn't help that availability all round has been limited for these. With so many people wanting the global edition and there being shortages of that model there's just not that many of these around at the moment in the hands of people that want to mod it. MIUI is very popular in China.
I'm hoping another 3-6 months we'll start to see some serious progress.
Luckily it's in the same device tree as a few other recent releases so there's some level of cross compatibility, lithium (Mi Mix) for example would require only minor modification to work and there seems to be more dev interest in that,
I did consider making a cooked MIUI rom for the Mi Note 2 (inc. xposed, root, a few tweaks here and there) but there didn't seem to be much demand and realistically if you want those features you already get them yourself without any real struggle.
I'm an old dev for CyanogenMod on Xperia.
I will try to put Lineage OS when the source of the kernel will be available.
A port can be possible with the source of the One Plus 3t (i supposed) but is better to wait official release of the kernel.
troufiniou said:
I'm an old dev for CyanogenMod on Xperia.
I will try to put Lineage OS when the source of the kernel will be available.
A port can be possible with the source of the One Plus 3t (i supposed) but is better to wait official release of the kernel.
Click to expand...
Click to collapse
Any news concerning kernel from Xiaomi or even Lineage?
//SkylarFlux// said:
Any news concerning kernel from Xiaomi or even Lineage?
Click to expand...
Click to collapse
Nope and nope :/
See here.
Thanks !
StoneTrapper said:
See here.
Click to expand...
Click to collapse
Has someone tried this? https://www.androidfilehost.com/?w=files&flid=168440&sort_by=date&sort_dir=DESC
AngelHxH said:
Has someone tried this? https://www.androidfilehost.com/?w=files&flid=168440&sort_by=date&sort_dir=DESC
Click to expand...
Click to collapse
Me and HondaJohn88 are working on new builds. It works and there are a few improvements and a few steps back, it still needs polishing before release.
LineageOS 14.1(Android 7.1.2), update to date - 20170512. Everything going well. (Thanks to hondajohn88)
https://www.androidfilehost.com/?fid=889764386195898578
Camera is not official one, it's snap camera - photo&video are working(Video recording, Front-1080p/Back-4K)
Auto brightness is working
Fingerprint Touch is working
... Others ... you try it and you will know...
Kris Chen said:
LineageOS 14.1(Android 7.1.2), update to date - 20170512. Everything going well. (Thanks to hondajohn88)
https://www.androidfilehost.com/?fid=889764386195898578
Camera is not official one, it's snap camera - photo&video are working(Video recording, Front-1080p/Back-4K)
Auto brightness is working
Fingerprint Touch is working
... Others ... you try it and you will know...
Click to expand...
Click to collapse
Tanks​ you ?
New Update:
https://www.androidfilehost.com/?fid=817550096634771139
New Update 0526:
https://www.androidfilehost.com/?fid=745425885120734790
Again thanks for your work!
Do you think it's possible that this becomes official?
meuhmeuh51 said:
Again thanks for your work!
Do you think it's possible that this becomes official?
Click to expand...
Click to collapse
These Lineage builds are by HondaJohn88 who I'm working with.
I've been bugging him to post them himself (when he does I'll get the old thread locked) but he hasn't yet.
Be aware that not every build he uploads is one that he's planning on sharing (or even an improvement over the last) - occasionally things break and some are more for archiving than actual use.
He shares his work in the Mi Note 2 Telegram group so I'd recommend joining so you can find out which build would be the most worthwhile.
StoneTrapper said:
These Lineage builds are by HondaJohn88 who I'm working with.
I've been bugging him to post them himself (when he does I'll get the old thread locked) but he hasn't yet.
Be aware that not every build he uploads is one that he's planning on sharing (or even an improvement over the last) - occasionally things break and some are more for archiving than actual use.
He shares his work in the Mi Note 2 Telegram group so I'd recommend joining so you can find out which build would be the most worthwhile.
Click to expand...
Click to collapse
Tank you
Thanks for this, gave new life to an old phone.
The latest build is from July 2017, right?
casacristo said:
Thanks for this, gave new life to an old phone.
The latest build is from July 2017, right?
Click to expand...
Click to collapse
There are newer builds of Lineage OS 14.1. Latest is from 12 January, if i'm not wrong
alexmanu1 said:
There are newer builds of Lineage OS 14.1. Latest is from 12 January, if i'm not wrong
Click to expand...
Click to collapse
Is that for Hermes or Scorpio? and where is the URL ?
Also I lost the IMEI (still have the number on a sticker) and so far failing miserably to restore it.
casacristo said:
Is that for Hermes or Scorpio? and where is the URL ?
Also I lost the IMEI (still have the number on a sticker) and so far failing miserably to restore it.
Click to expand...
Click to collapse
For scorpio. https://forum.xda-developers.com/mi-note-2/development/rom-lineageos-14-1-t3724739
About the imei issue , i don't know how to restore it , honestly.
Hi,
Only a question : is there any ROM for i9000, which
- will be supported for a while
- has the latest security patches (KRACK attack, BT bug discovered in the summer)
I saw only those which are 4.4.4 based., and 14.1 Lineageos, but the latest update for these is 2017.04... I know that i9000 is old, but i hope there will be an up-to date ROM.
Thanks for all tips
The only one that seems up to date is:
https://forum.xda-developers.com/galaxy-s-i9000/i9000-development/rom-lineageos-14-1-t3703447
Data doesn't work apparently but that's not an issue for my usage of it.
exadeci said:
The only one that seems up to date is:
https://forum.xda-developers.com/galaxy-s-i9000/i9000-development/rom-lineageos-14-1-t3703447
Data doesn't work apparently but that's not an issue for my usage of it.
Click to expand...
Click to collapse
Wow! Thanks, it seems great. What do you mean in "data"? The networking?
I hope that the latest security patches are involved in the last build.