Hi friends. Can you check this kernel source's is real or useless?
https://github.com/nofearnohappy/android_vendor_xiaomi_hermes
https://github.com/lbule/android_device_xiaomi_hermes
This isn't a kernel source, it's a device tree for build CyanogenMod
~ Xiaomi Redmi Note 2 Prime ~
SkiFire13 said:
This isn't a kernel source, it's a device tree for build CyanogenMod
~ Xiaomi Redmi Note 2 Prime ~
Click to expand...
Click to collapse
ho great so cyanogenmod is comming?
tailslol said:
ho great so cyanogenmod is comming?
Click to expand...
Click to collapse
We will see, it is very hard to port when kernel is not given. There are people working on it and doing a very good job!
Sadly, the complete kernel (custom kernel with drivers) was leaked for a short period and a few devs have it.. but they are afraid to use or publish it because they don't want to be sued.
tailslol said:
ho great so cyanogenmod is comming?
Click to expand...
Click to collapse
For now someone built it but it's very unstable
~ Xiaomi Redmi Note 2 Prime ~
Sad news about this device's kernel source.
is this usefull?
http://forum.xda-developers.com/cro...al/marshmallow-source-codes-mediatek-t3218602
chris5932 said:
We will see, it is very hard to port when kernel is not given. There are people working on it and doing a very good job!
Sadly, the complete kernel (custom kernel with drivers) was leaked for a short period and a few devs have it.. but they are afraid to use or publish it because they don't want to be sued.
Click to expand...
Click to collapse
Wow didnt know that, really the full source kernel was leaked??? And some devs have it D:?. If its true i hope they decide one day to make a nice ROM build, i guess everyone of us would wait for that
chris5932 said:
We will see, it is very hard to port when kernel is not given. There are people working on it and doing a very good job!
Sadly, the complete kernel (custom kernel with drivers) was leaked for a short period and a few devs have it.. but they are afraid to use or publish it because they don't want to be sued.
Click to expand...
Click to collapse
Sued? The ones to be sued are mediatek and/or xiaomi for not complying gpl license
adaltavo said:
Wow didnt know that, really the full source kernel was leaked??? And some devs have it D:?. If its true i hope they decide one day to make a nice ROM build, i guess everyone of us would wait for that
Click to expand...
Click to collapse
At least someone has it.. I am not so sure on how many have it. Don't be too excited yet, we might not get it (soon). The source can not just be published to the public, the one who does will face some problems.. (see what happened to incomplete source).
chris5932 said:
At least someone has it.. I am not so sure on how many have it. Don't be too excited yet, we might not get it (soon). The source can not just be published to the public, the one who does will face some problems.. (see what happened to incomplete source).
Click to expand...
Click to collapse
May i ask what happened?. And i know is not that easy, what i meant is that he (or they) could make a nice ROM build with that source, maybe as an anonymus guy or something like that, is not necesary to publish full source code. Our another hope is wait for MTK to release it , but it wont be soon, even could never happen
adaltavo said:
May i ask what happened?. And i know is not that easy, what i meant is that he (or they) could make a nice ROM build with that source, maybe as an anonymus guy or something like that, is not necesary to publish full source code. Our another hope is wait for MTK to release it , but it wont be soon, even could never happen
Click to expand...
Click to collapse
We can build roms ourselfs, just need proper kernel. Just let me say that much: I have a reliable source that told me someone has it. I don't think (anymore) it was leaked to the public ever, all kernel leaked on git were incomplete.
All kernel sources I've seen for X10 are not for our device. Another thing is the AOSP sources are very buggy and unfinished.
I finally made progress on my AOSP 5.1 and fixed the slow app launch (maybe you've seen one youtube video posted here - this is my build).
Unfortunately I don't have kernel source for Redmi Note 2 and it is impossible to build a custom kernel, so I'm trying to finish the ROM and will use prebuilt kernel.
If you think it is easy as porting, then you're wrong. Compiling something from source and fixing all bugs is completely different animal.
CM 12.1 also booted, but a lot of work needs to be done there too.
https://github.com/omlet05/MediaTek-HelioX10-Kernel
yay?
tailslol said:
https://github.com/omlet05/MediaTek-HelioX10-Kernel
yay?
Click to expand...
Click to collapse
Check the date and please stop posting same thing again and again. This is the original broken half source that was leaked over 2 months ago now.
I.nfraR.ed said:
All kernel sources I've seen for X10 are not for our device. Another thing is the AOSP sources are very buggy and unfinished.
I finally made progress on my AOSP 5.1 and fixed the slow app launch (maybe you've seen one youtube video posted here - this is my build).
Unfortunately I don't have kernel source for Redmi Note 2 and it is impossible to build a custom kernel, so I'm trying to finish the ROM and will use prebuilt kernel.
If you think it is easy as porting, then you're wrong. Compiling something from source and fixing all bugs is completely different animal.
CM 12.1 also booted, but a lot of work needs to be done there too.
Click to expand...
Click to collapse
What is time to wake? On miui time is long :/ On our last phone (A820) time to wake is much better.
How aboute "tap to wake"? What is result on antutu? When you publish rom?
AOSP boots up and works faster than MIUI and also has much much better ram management, although it would be good if we could make a custom kernel.
Tap to wake normally needs to be supported in kernel, so the answer is "no".
Antutu score is irrelevant, but normally I get about 48K with the basic model. I've seen higher, seen lower.
It also depends on kernel.
Don't forget that for A820 I have a custom optimized kernel.
Hello
When you share rom? How to progress?
Known XDA rule, don't ask for ETA He'll tell us when ready
bumcykcyk said:
Hello
When you share rom? How to progress?
Click to expand...
Click to collapse
It will be shared when it is done.. Ussd/BT working but camera still doesnt
Related
http://developer.htc.com/
With the code to the kernel and drivers developers and tinkerers can start building custom ROMs which can make the smartphones go faster, batteries last longer, and who knows what other sorts of cool stuff!
Click to expand...
Click to collapse
via Pocketnow.com
Maybe it`s useful for the devs.
Yeah I saw that earlier, don't think it would be of much help now, the custom ROMs seem to be faster and more stable than the HTC ones now...
Maybe that reading the code someone will find a bug to gain root access... I hope...
Those are the kernel sources the custom kernels are based on, so nothing new.
arco68 said:
Those are the kernel sources the custom kernels are based on, so nothing new.
Click to expand...
Click to collapse
Oh well, I just thought it would be nice to share the news.
Hey guys was just wondering if there any developers who are working on some new ROMS for our MXP as it seems very quiet in the development sections of the forums, couple of variations of stock rom and that's pretty much it.
Was expecting for development to pick up after the MM but its been VERY quiet.
Not a complaint just wondering if there are things going on behind the curtains like development being done or some CM13 or anything along those lines.
djsynth said:
Hey guys was just wondering if there any developers who are working on some new ROMS for our MXP as it seems very quiet in the development sections of the forums, couple of variations of stock rom and that's pretty much it.
Was expecting for development to pick up after the MM but its been VERY quiet.
Not a complaint just wondering if there are things going on behind the curtains like development being done or some CM13 or anything along those lines.
Click to expand...
Click to collapse
Having MM OTA out is not enough.
Not much can be done until Motorola will release the kernel source
nimrodsv said:
Having MM OTA out is not enough.
Not much can be done until Motorola will release the kernel source
Click to expand...
Click to collapse
Any idea if its going to get released and if yes then when ?
and out of self interest what does the kernel source enable developers to do ?
djsynth said:
Any idea if its going to get released and if yes then when ?
and out of self interest what does the kernel source enable developers to do ?
Click to expand...
Click to collapse
It's totally depended on Motorola.
The source enable developers to release AOSP roms and custom kernels.
nimrodsv said:
It's totally depended on Motorola.
The source enable developers to release AOSP roms and custom kernels.
Click to expand...
Click to collapse
Has Motorola been known to release kernel sources before for previous flagships ?
Would love for them to release the binaries and device tree for AOSP builds...
djsynth said:
Has Motorola been known to release kernel sources before for previous flagships ?
Click to expand...
Click to collapse
They are required to release any changes to the kernel they have made due to the GPL license that the linux kernel is protected by. so its not a matter of if but when.
MM and now kernel source released, and still, slow as hell. Sucks. I thought this phone would be one of the most active in development, was i wrong.
Sent from my XT1575 using Tapatalk
I'm on retail Asia variant which leaves me with 1 rom. And I can't even get mm for my variant let alone custom roms.
What happened to this phone?
Please go to http://forum.xda-developers.com/moto-x-style/help/happened-to-phone-t3283551
to continue this topic if possible, thank you
Hello from Moscow, Russia. I can't write in Firmware section, so I write here.
I'm and my teammate(Dblm) ported 3.10.33 kernel from Nvidia Shield. TWRP works fine with this kernel. But android don't work cuz our graphical blobs are very very old. So may be somebody can find necessary blobs and run android.
zImage: https://drive.google.com/open?id=0B2...nhPdlJkWkdYQjg
TWRP recovery with this kernel: https://drive.google.com/open?id=0B2...FhQTHJIa2xVems
reserved
Artemka2008 said:
Hello from Moscow, Russia. I can't write in Firmware section, so I write here.
I'm and my teammate(Dblm) ported 3.10.33 kernel from Nvidia Shield. TWRP works fine with this kernel. But android don't work cuz our graphical blobs are very very old. So may be somebody can find necessary blobs and run android.
zImage: https://drive.google.com/open?id=0B2ALf4H-2aBrZnhPdlJkWkdYQjg
TWRP recovery with this kernel: https://drive.google.com/open?id=0B2ALf4H-2aBrZFhQTHJIa2xVems
Click to expand...
Click to collapse
Thanks a lot for posting this. It would be more helpful if you could post your source code for the port and the source (the original shield kernel).
drakonizer said:
Thanks a lot for posting this. It would be more helpful if you could post your source code for the port and the source (the original shield kernel).
Click to expand...
Click to collapse
At the moment my teammate does not want to publish the source code.
CPU fixed in this build(all 4 cores work)
Artemka2008 said:
At the moment my teammate does not want to publish the source code.
CPU fixed in this build(all 4 cores work)
Click to expand...
Click to collapse
I really appreciate your work. Don't get me wrong. But Linux is licensed under GPL. The law requires you to open source your work, and so does XDA. This is why we didn't have a Mi Pad forum till now. To avoid problems and to prevent XDA from banning you or closing this thread, I suggest you either publish your source or remove the link.
None of the devs can help you if you don't release the source code. Please co operate with the open source community.
Thanks for understanding.
drakonizer said:
I really appreciate your work. Don't get me wrong. But Linux is licensed under GPL. The law requires you to open source your work, and so does XDA. This is why we didn't have a Mi Pad forum till now. To avoid problems and to prevent XDA from banning you or closing this thread, I suggest you either publish your source or remove the link.
None of the devs can help you if you don't release the source code. Please co operate with the open source community.
Thanks for understanding.
Click to expand...
Click to collapse
ok, I will delete this thread.
Artemka2008 said:
ok, I will delete this thread.
Click to expand...
Click to collapse
You don't have to delete the thread. It can be used for discussions. You can upload your kernel whenever you feel its appropriate to release your source code.
On a more helpful note: I can't say much without seeing the source code, but if you have ported the kernel drivers as well from shield, you can try using the blobs from Shield itself. You'll probably need to use blobs that match the version of the kernel you are trying to port.
so does that mean that there is a chance for cm12+?
Jahhhhhhh said:
so does that mean that there is a chance for cm12+?
Click to expand...
Click to collapse
Without camera and sound now. I tried to run Android 5.1.1 with our kernel. But I can't find working graphical blobs. I need help with it.
This is my last logcat https://drive.google.com/open?id=0B2ALf4H-2aBrX3dCRkthR21wM1U
This is going nowhere until you share the source code with the community as per GPL. How long does your teammate want to drag the process? Release the source code today and start getting feedback from other devs - what's the hold up?
Palm Trees said:
This is going nowhere until you share the source code with the community as per GPL. How long does your teammate want to drag the process? Release the source code today and start getting feedback from other devs - what's the hold up?
Click to expand...
Click to collapse
God, the source code will not help here. You just need to pick up the blobs to run android. With the kernel of today there are no problems.
Artemka2008 said:
God, the source code will not help here. You just need to pick up the blobs to run android. With the kernel of today there are no problems.
Click to expand...
Click to collapse
Blobs are heavily linked to the kernel drivers. Without even knowing what kernel you have used as a source for the port (the one for Shield), how can we randomly test blobs and somehow magically fix this? I really don't want to piss you guys off, but the reason why you can do the work you do is because the Linux kernel is open source. And it's stayed that way because people have followed the GPL (with only a few exceptions like Xiaomi). I do not understand why you don't want to release the source code. Nobody is trying or will try to steal your work and claim credits. In the end we all want the same thing - stable Android 5/6/7 on the Mi Pad. Let other people help too.
drakonizer said:
Blobs are heavily linked to the kernel drivers. Without even knowing what kernel you have used as a source for the port (the one for Shield), how can we randomly test blobs and somehow magically fix this? I really don't want to piss you guys off, but the reason why you can do the work you do is because the Linux kernel is open source. And it's stayed that way because people have followed the GPL (with only a few exceptions like Xiaomi). I do not understand why you don't want to release the source code. Nobody is trying or will try to steal your work and claim credits. In the end we all want the same thing - stable Android 5/6/7 on the Mi Pad. Let other people help too.
Click to expand...
Click to collapse
That's my point exactly. Have you tried asking in the Nvidia Shield xda thread: http://forum.xda-developers.com/shield-tablet/development. There's plenty of development going on, you might be able to get some tips and tricks.
Palm Trees said:
That's my point exactly. Have you tried asking in the Nvidia Shield xda thread: http://forum.xda-developers.com/shield-tablet/development. There's plenty of development going on, you might be able to get some tips and tricks.
Click to expand...
Click to collapse
Not the point. The shield developers will not be able to help us. Things will become very easy if this shield kernel port works. We will probably be able to use the newer blobs meant for the Shield, which makes development very easy, if this becomes bootable/stable. I really hope the OP manages to get it working. We either need newer blobs from Xiaomi or we need to write wrappers to use the current kitkat blobs (not easy, since Nvidia documentation is nowhere near as detailed as say, Qualcomm) or we need to get this port working well, which would enable us to use most of the blobs from the Shield (provided Xiaomi hasn't gone out of their way to screw with their blobs). The first two ways are practically impossible, which leads me to rest all my hope on this port. Unfortunately without the source code, we will just have to be silent spectators, waiting for some news.
Here's my effort for asking sheild developer- http://forum.xda-developers.com/shield-tablet/help/help-support-xiaomi-mipad-custom-rom-t3512695
I also posted a xiaomi forum link where Sheild Lollipop kernel is accessible for developers. It's available in Xiaomi forum.
Here's the link - http://en.miui.com/thread-439620-1-1.html
I have just shared the information available. Not taking any credit away from developer from 4pda.ru.
Thanks
rocky869 said:
Here's my effort for asking sheild developer- http://forum.xda-developers.com/shield-tablet/help/help-support-xiaomi-mipad-custom-rom-t3512695
I also posted a xiaomi forum link where Sheild Lollipop kernel is accessible for developers. It's available in Xiaomi forum.
Here's the link - http://en.miui.com/thread-439620-1-1.html
I have just shared the information available. Not taking any credit away from developer from 4pda.ru.
Thanks
Click to expand...
Click to collapse
I asked LuckyMeAgain to publish on the official website, so it's the same thing. I am ArtemkaVZM on 4pda and arttt on en.miui.com MiuiSmokeRom dev team.
Presumably the easiest way is to go through TheMuppets repo and testing them at different points in time by checking commit history.
https://github.com/TheMuppets/proprietary_vendor_nvidia
Harrynowl said:
Presumably the easiest way is to go through TheMuppets repo and testing them at different points in time by checking commit history.
https://github.com/TheMuppets/proprietary_vendor_nvidia
Click to expand...
Click to collapse
I think that we have to make a new build. Current builds are useless for us now. I mean available android 5 roms.
This is my last logcat with 5.1.1 Vartom's SlimRom: https://drive.google.com/open?id=0B2ALf4H-2aBrX3dCRkthR21wM1U
Artemka2008 said:
I think that we have to make a new build. Current builds are useless for us now. I mean available android 5 roms.
This is my last logcat with 5.1.1 Vartom's SlimRom: https://drive.google.com/open?id=0B2ALf4H-2aBrX3dCRkthR21wM1U
Click to expand...
Click to collapse
looks like hwcomposer is the broken blob. Have you tried using the hwcomposer.tegra.so from a Sheild ROM to boot it?
drakonizer said:
looks like hwcomposer is the broken blob. Have you tried using the hwcomposer.tegra.so from a Sheild ROM to boot it?
Click to expand...
Click to collapse
All the necessary blobs were taken from Shield. More no such files, which could be replaced.
Hello all,
Can any dev actually make official TWRP for Redmi 3s. I know cofface and the other guy made TWRPs but they aren't official.
So if anyone who knows Chinese can either contact those devs and ask for them to develop twrp officially.
Or if any one can actually develop an official version for our device.
Kind regards all
Official means if TWRP devs work on it
I don't think they've that much time to work on such devices
Instead they make it for premium phone.
And it's not hard to port TWRP if you've the original one
Please read the official twrp site, they only need sources, once the twrp is built for a device.
Redmi 3, redmi 1s, redmi note 2 all have official twrp
Oh come on people, this is the first step to official custom ROMs
can anyone tell me what is stopping them to make official TWRP for so long? every single device has it even redmi 1s redmi 3 and redmi note
Well I'm guessing that the devs are contemt with the cofface and flou twrps, but it would still be nice if we got the attention of somebody, who knows how to build a recovery and make it official.
I would do it, but I would need to learn from scratch and it would probably take to long
Devs pls help
I never really understood why people are unsatisfied with unofficial builds, as long as they work without any issues
What's bugging you?
Kizoky said:
I never really understood why people are unsatisfied with unofficial builds, as long as they work without any issues
What's bugging you?
Click to expand...
Click to collapse
there is the reason they are unofficial,it all depends on one person ro maintain regular updates,no regular fixes less room to work with and btw not a single build so far is bugless or stable on our device so maybe that is why. No one fixed dark video in camera recording so far for almost 3 months with kernel source out.
So no one with a bit of knowledge is willing to to do this. I'll try to make a build, but cannot guarantee I'll successed
bekcicandrej said:
So no one with a bit of knowledge is willing to to do this. I'll try to make a build, but cannot guarantee I'll successed
Click to expand...
Click to collapse
That would be still unofficial.
Kizoky said:
That would be still unofficial.
Click to expand...
Click to collapse
https://twrp.me/faq/OfficialMaintainer.html
What is the difference between official and unofficial as they are working the same.
harnamgour said:
What is the difference between official and unofficial as they are working the same.
Click to expand...
Click to collapse
Official is when TWRP acknowledged it as trusty
i.e.: an Official build is updated every week, month, and is always upgraded to the next level of android, or not. (Redmi 3 still has 5.1 TWRP official, but no 6.0)
Unofficial is when it wasn't acknowledged, so a developer/user built it from scratch, and it gets only updated once, or twice, It depends on the user/developer itself.
Once I get my 3S finally (possibly after 2 weeks), I'll try to make a bugless TWRP
The TWRP we are using is basically a port (I couldn't find anywhere else the sources for Redmi 3S TWRP)
Given by how Kenzo is similar to Land, I have made a semi-working TWRP tree
https://github.com/Kizoky/android_device_xiaomi_land
It needs a pre-built kernel, which is obviously based on Stock or CM (Stock would be the best)
https://github.com/Kizoky/android_device_xiaomi_land/blob/android-6.0/BoardConfig.mk
It is lined out here.
Also, If some of you found some bugs within this tree just let me know
I won't make it as a seperate thread unless It is fully functional
Yey, thank you @Kizoky
bekcicandrej said:
Yey, thank you @Kizoky
Click to expand...
Click to collapse
No problem, but since I don't have the phone yet, I can't test it, that's why I need guinea pigs
Kizoky said:
No problem, but since I don't have the phone yet, I can't test it, that's why I need guinea pigs
Click to expand...
Click to collapse
I'm volunteering
bekcicandrej said:
I'm volunteering
Click to expand...
Click to collapse
Are you able to build?
Kizoky said:
Are you able to build?
Click to expand...
Click to collapse
Well I have a intel 4770k ocd to 4.4 and 16gb ram.
But no knowledge of actually building something :/
bekcicandrej said:
Well I have a intel 4770k ocd to 4.4 and 16gb ram.
But no knowledge of actually building something :/
Click to expand...
Click to collapse
Well, we need someone who is capable of building kernels/recoveries
Even though I have a strong PC, I don't have a large unneeded space for building Android (613GB is not enough when it is 90% full)
Hi there people,
I've been hearing good things about ElementalX kernel, but from what I see there isn't this kernel for our phone, what do you think?
evronetwork said:
Hi there people,
I've been hearing good things about ElementalX kernel, but from what I see there isn't this kernel for our phone, what do you think?
Click to expand...
Click to collapse
Why don't just choose from available kernels instead? The dev of elementalX kernel is not supporting bacon because he does not have this device.
Mr.Ak said:
Why don't just choose from available kernels instead? The dev of elementalX kernel is not supporting bacon because he does not have this device.
Click to expand...
Click to collapse
Already using Franco kernel but why not try this one if it was possible(or if someone ported this to our device)? ...thread was created about this kernel and not talk about alternatives
P.S. I heared quite good stuff about this kernel that is all
evronetwork said:
Already using Franco kernel but why not try this one if it was possible(or if someone ported this to our device)? ...thread was created about this kernel and not talk about alternatives
P.S. I heared quite good stuff about this kernel that is all
Click to expand...
Click to collapse
But you need permission from the kernel developer first.
Mr.Ak said:
But you need permission from the kernel developer first.
Click to expand...
Click to collapse
If he says you need then ok if he doesn't and gives his source like that then no ...just port it and say it's his - problems solved. You get into technical problems while I comment on what you think about the kernel and/or if someone is willing to do a port(asking dev if needed OC)
evronetwork said:
If he says you need then ok if he doesn't and gives his source like that then no ...just port it and say it's his - problems solved. You get into technical problems while I comment on what you think about the kernel and/or if someone is willing to do a port(asking dev if needed OC)
Click to expand...
Click to collapse
Tbh I don't think anyone will.
Mr.Ak said:
Tbh I don't think anyone will.
Click to expand...
Click to collapse
tbh I'd rather watch devs working on 3.10 kernel(there's one for our phone) or newer e.g. 3.18 but that's a different matter
evronetwork said:
tbh I'd rather watch devs working on 3.10 kernel(there's one for our phone) or newer e.g. 3.18 but that's a different matter
Click to expand...
Click to collapse
Since erorcun's OPO's screen is broken he probably won't work on 3.18.xx.
Mr.Ak said:
Since erorcun's OPO's screen is broken he probably won't work on 3.18.xx.
Click to expand...
Click to collapse
Gather 10 skilled devs to work around 3.18.xx for a few months and you'll have a pretty decent stable core with quite a few benefits ...but kernel isn't like roms, needs fine tuning and when we're talking about upped versions there are some restrictions, you need to create workarounds for some stuff and some devs don't like to do that and since we've got no actual open source drivers workarounds are inevitable
evronetwork said:
Gather 10 skilled devs to work around 3.18.xx for a few months and you'll have a pretty decent stable core with quite a few benefits ...but kernel isn't like roms, needs fine tuning and when we're talking about upped versions there are some restrictions, you need to create workarounds for some stuff and some devs don't like to do that and since we've got no actual open source drivers workarounds are inevitable
Click to expand...
Click to collapse
Most of the devs think upstreaming kernel is just a waste of time and efforts.
Mr.Ak said:
Most of the devs think upstreaming kernel is just a waste of time and efforts.
Click to expand...
Click to collapse
Yeap true still it's the future and there won't be one if we stuck in 3.4.x (3.4.x already reached EOL - https://www.kernel.org/category/releases.html - linux kernels EOL )
P.S. Sultan tried to make a kernel but saw it would require too much time and effort and stopped, if he has time and passion about the kernel this would have a much better future. It's obvious that a proper optimized kernel does have benefits(of course to match the maturity of 3.4.x is not an easy thing ...still this would make our phone last 5+ years ....if a proper stable 3.18.x kernel was around) - not sure if the electronics of my 1+1 would live by then but just saying
evronetwork said:
Yeap true still it's the future and there won't be one if we stuck in 3.4.x (3.4.x already reached EOL - https://www.kernel.org/category/releases.html - linux kernels EOL )
P.S. Sultan tried to make a kernel but saw it would require too much time and effort and stopped, if he has time and passion about the kernel this would have a much better future. It's obvious that a proper optimized kernel does have benefits(of course to match the maturity of 3.4.x is not an easy thing ...still this would make our phone last 5+ years ....if a proper stable 3.18.x kernel was around) - not sure if the electronics of my 1+1 would live by then but just saying
Click to expand...
Click to collapse
I think 3.10.xx will reach EOL soon.
Mr.Ak said:
I think 3.10.xx will reach EOL soon.
Click to expand...
Click to collapse
Oct 2017
Mr.Ak said:
I think 3.10.xx will reach EOL soon.
Click to expand...
Click to collapse
arjun said:
Oct 2017
Click to expand...
Click to collapse
Yeap, wish we had some devs working on:
3.18.x for our device
bring treble for our device(not sure if this can be done) - not just have android O(without treble)
This would ensure that the phone would live until all the electronics die from natural cause(age)
I think @erorcun was working on 3.10 and then 3.18 before his screen broke.
I don't know how common it is for devices to have merged or official kernel jumps, but I remember the S3 starting with 3.0 and ending at 3.4. CM builds got it first and then miraculously followed suit in the final OTA, which nobody who cared about their bootloader ever took.
LLStarks said:
I think @erorcun was working on 3.10 and then 3.18 before his screen broke.
I don't know how common it is for devices to have merged or official kernel jumps, but I remember the S3 starting with 3.0 and ending at 3.4. CM builds got it first and then miraculously followed suit in the final OTA, which nobody who cared about their bootloader ever took.
Click to expand...
Click to collapse
Well oneplus won't give you anything ..that's a sure thing. Usually they don't up the kernel version. You get a phone with 3.10 it will die with 3.10.
The real problem comes with the drivers of the device. In order to get a real fully functional kernel without workarounds we need the help of qualcomm, would they provide drivers so we can have a real 3.18 kernel with proper support from android o? ...of course not, why do that when they can sell you a new phone with better SoC(they have a company to run and to do that they want to sell SoC ...so you should buy a new phone )
evronetwork said:
Well oneplus won't give you anything ..that's a sure thing. Usually they don't up the kernel version. You get a phone with 3.10 it will die with 3.10.
The real problem comes with the drivers of the device. In order to get a real fully functional kernel without workarounds we need the help of qualcomm, would they provide drivers so we can have a real 3.18 kernel with proper support from android o? ...of course not, why do that when they can sell you a new phone with better SoC(they have a company to run and to do that they want to sell SoC ...so you should buy a new phone )
Click to expand...
Click to collapse
If my OPO dies,my next device will be Redmi Note 4 which has 3.18.xx
Mr.Ak said:
If my OPO dies,my next device will be Redmi Note 4 which has 3.18.xx
Click to expand...
Click to collapse
Mediatek SoC ...good luck with that
Mediatek is worse than Qualcomm when it comes to open source roms
..but at least you'll have 3.18 which isn't bad at all heh
evronetwork said:
Mediatek SoC ...good luck with that
Mediatek is worse than Qualcomm when it comes to open source roms
..but at least you'll have 3.18 which isn't bad at all heh
Click to expand...
Click to collapse
Just get the version with the snapdragon 625
evronetwork said:
Mediatek SoC ...good luck with that
Mediatek is worse than Qualcomm when it comes to open source roms
..but at least you'll have 3.18 which isn't bad at all heh
Click to expand...
Click to collapse
Sur,I iz puar but not that puar that I'll buy mediatek(It wasn't bad when Qualcomm didn't produce budget chips,but it is way worse now in front of Qualcomm budget chips).
Btw,afaik,mediatek variant only available in China which is exactly why I don't live there.