Related
Hi,
I thought this was not yet possible to port Cyanogenmod on Dual Sim devices, at least not properly, but then I saw this post:
http://forum.xda-developers.com/showthread.php?t=2246874
It gave me a real hope for the generic MT6589 device I am currently using.
I am new to all of this, so I hope I don't bother everyone.
Also, my device uses obviously different hardware, but uses the same processor, so I managed to install the above ROM and got it working but without any screen display.
In other words, it was working, and I could see everything as far as the installation wizzard was concerned, so I thought I was fine, but then when I was done and it rebooted, I could not see anything on the display anymore, but the phone was still working working.
So I am assuming some obvious hardware drivers differences, and that the old drivers were still working till I restarted?
Is there a way to modify the rom to make it work?
What files would I need to pull from my device to add/replace in the posted ROM to make it worlk, if that is possible?
Or does cynanogenmod have to compile with the files of my device to work, even though the processor bit had already been done?
If so, I have no problem in trying to compile cyanogenmod from scratch, but I will still get the dual SIM problem, and I thought this has been fixed in this ROM.
So what modifications would need to be done to incorporate the DUAL SIM issue, and make it work, or has this already been resolved upstream?
Is there a github or such of the modifications and alterations that were done to Cyanogenmod for this posted ROM in order to get it working?
I am willing to use those files and port it to my device, but without these modifications, I will not be able to do anything, even though the kernel sources for MT6589 are openly available now.
Sorry for asking this question here, but I tried to reply to the original post and it did not let me.
Is it okay to ask this here?
If not, please excuse me, and if you can forward me to the right place.
Thanks and regards
noobworld said:
Hi,
I thought this was not yet possible to port Cyanogenmod on Dual Sim devices, at least not properly, but then I saw this post:
http://forum.xda-developers.com/show....php?t=2246874
It gave me a real hope for the generic MT6589 device I am currently using.
I am new to all of this, so I hope I don't bother everyone.
Also, my device uses obviously different hardware, but uses the same processor, so I managed to install the above ROM and got it working but without any screen display.
In other words, it was working, and I could see everything as far as the installation wizzard was concerned, so I thought I was fine, but then when I was done and it rebooted, I could not see anything on the display anymore, but the phone was still working working.
So I am assuming some obvious hardware drivers differences, and that the old drivers were still working till I restarted?
Is there a way to modify the rom to make it work?
What files would I need to pull from my device to add/replace in the posted ROM to make it worlk, if that is possible?
Or does cynanogenmod have to compile with the files of my device to work, even though the processor bit had already been done?
If so, I have no problem in trying to compile cyanogenmod from scratch, but I will still get the dual SIM problem, and I thought this has been fixed in this ROM.
So what modifications would need to be done to incorporate the DUAL SIM issue, and make it work, or has this already been resolved upstream?
Is there a github or such of the modifications and alterations that were done to Cyanogenmod for this posted ROM in order to get it working?
I am willing to use those files and port it to my device, but without these modifications, I will not be able to do anything, even though the kernel sources for MT6589 are openly available now.
Sorry for asking this question here, but I tried to reply to the original post and it did not let me.
Is it okay to ask this here?
If not, please excuse me, and if you can forward me to the right place.
Thanks and regards
Click to expand...
Click to collapse
link is dead.
who is the dev.
prantoroy said:
link is dead.
who is the dev.
Click to expand...
Click to collapse
Thanks for the headsup.
I placed in an incomplete link, here is the complete link:
http://forum.xda-developers.com/showthread.php?t=2246874
I also updated the post.
The developper seems to be:
bgcngm
Thanks
noobworld said:
Thanks for the headup.
I placed in an incomplete link, here is the complete link:
http://forum.xda-developers.com/showthread.php?t=2246874
I also updated the post.
The developper seems to be:
bgcngm
Thanks
Click to expand...
Click to collapse
give sme time.will try
---------- Post added at 10:44 AM ---------- Previous post was at 10:42 AM ----------
prantoroy said:
give sme time.will try
Click to expand...
Click to collapse
just as I thought.the kernel.
its not fr u. ask dev to create a kernel fr u!
Thank you for your fast reply.
Where do I ask?
Also, I was hoping to learn how to do it, and have the sources if possible, or at least how to modify the sources, because I have about three of these chinese devices, all using the same processor, but with different hardware.
Thanks
prantoroy said:
give sme time.will try
---------- Post added at 10:44 AM ---------- Previous post was at 10:42 AM ----------
just as I thought.the kernel.
its not fr u. ask dev to create a kernel fr u!
Click to expand...
Click to collapse
noobworld said:
Thank you for your fast reply.
Where do I ask?
Also, I was hoping to learn how to do it, and have the sources if possible, or at least how to modify the sources, because I have about three of these chinese devices, all using the same processor, but with different hardware.
Thanks
Click to expand...
Click to collapse
Ask The dev
And Its not that easy
prantoroy said:
Ask The dev
And Its not that easy
Click to expand...
Click to collapse
Well, I tried posting on the original thread, but couldn't.
Then tried to send a private message, but couldn't.
So I started this thread.
You said:
And Its not that easy
Click to expand...
Click to collapse
Did you mean it is not easy to contact the dev, or not easy to compile the sources for my devices?
Just wanted to be sure.
Thanks again
noobworld said:
Well, I tried posting on the original thread, but couldn't.
Then tried to send a private message, but couldn't.
So I started this thread.
You said:
Did you mean it is not easy to contact the dev, or not easy to compile the sources for my devices?
Just wanted to be sure.
Thanks again
Click to expand...
Click to collapse
no you cant post until u have 10 posts
and its not easy to develop rom
prantoroy said:
no you cant post until u have 10 posts
and its not easy to develop rom
Click to expand...
Click to collapse
I can see that, but I think with some patience I can do it.
Also, I have been using Linux for years now, and it seems I just need to figure out how things are laid out in Android.
And once I get used to that, then things become easier.
I am assuming that the linux kernel needs to be compiled with the specific drivers related to my hardware, right?
However, that would still not take into account:
- The changes made in Android/Cyanogenmod that take into account Dual SIM functionality
- How Cyanogenmod is actually laid-out, such as are changes done directly to stock android, or applied as patches?
I was thinking of the following:
1) Checking for the difference between stock Android and Cyanogenmod, and save aside the diff changes to make a patch file.
2) Then hope to find the sources of the stock android that has already been modified to work with MT6589, since these devices obviously use Android on them with some modifications
3) Then apply the patch made in (1) on these sources
Thus, I also need one important question answered:
If I were to download the sources for Cyanogenmod (which I already did), are the patches to the stock Android already applied, or are they placed in a separate folder, and applied on compilation?
I have this feeling that the above patches will probably not work out, because there will probably be extra functions, code that the patch will not be able to take into account, and will have some type of non-working or broken system, until I figure out what is missing.
I might get it to boot to a certain point (most probably shell like), and it would stop there.
Well, in either case, after writing all this down, I started to visualize more the hard part you are talking about, and this would require good knowledge of Android Code and structure.
Thus, if anyone can give me the required Cyanogenmod sources that have already been modified to work on an MT6589, or the diff patches between the normal and modified Cynogenmod, then that would be amazing.
Then I will have to only figure out at that point the propriety files I need to pull from the device, and specific vendor modifications.
Of course, I am just speculating, as this depends on how Android/Cyanogenmod is structured, and I could be completely off the mark, and have no idea what I am talking about.
Thanks
noobworld said:
I can see that, but I think with some patience I can do it.
Also, I have been using Linux for years now, and it seems I just need to figure out how things are laid out in Android.
And once I get used to that, then things become easier.
I am assuming that the linux kernel needs to be compiled with the specific drivers related to my hardware, right?
However, that would still not take into account:
- The changes made in Android/Cyanogenmod that take into account Dual SIM functionality
- How Cyanogenmod is actually laid-out, such as are changes done directly to stock android, or applied as patches?
I was thinking of the following:
1) Checking for the difference between stock Android and Cyanogenmod, and save aside the diff changes to make a patch file.
2) Then hope to find the sources of the stock android that has already been modified to work with MT6589, since these devices obviously use Android on them with some modifications
3) Then apply the patch made in (1) on these sources
Thus, I also need one important question answered:
If I were to download the sources for Cyanogenmod (which I already did), are the patches to the stock Android already applied, or are they placed in a separate folder, and applied on compilation?
I have this feeling that the above patches will probably not work out, because there will probably be extra functions, code that the patch will not be able to take into account, and will have some type of non-working or broken system, until I figure out what is missing.
I might get it to boot to a certain point (most probably shell like), and it would stop there.
Well, in either case, after writing all this down, I started to visualize more the hard part you are talking about, and this would require good knowledge of Android Code and structure.
Thus, if anyone can give me the required Cyanogenmod sources that have already been modified to work on an MT6589, or the diff patches between the normal and modified Cynogenmod, then that would be amazing.
Then I will have to only figure out at that point the propriety files I need to pull from the device, and specific vendor modifications.
Of course, I am just speculating, as this depends on how Android/Cyanogenmod is structured, and I could be completely off the mark, and have no idea what I am talking about.
Thanks
Click to expand...
Click to collapse
ok I will help u.
go here
http://forum.xda-developers.com/forumdisplay.php?f=613
prantoroy said:
ok I will help u.
go here
http://forum.xda-developers.com/forumdisplay.php?f=613
Click to expand...
Click to collapse
Wow... Even though I searched for so long, I did not find this.
I guess I did not know what to search for.
I thank you a lot.
I will probably take a while to learn how to use this, so I will disappear until I figure it out.
If I managed to do anything, then will come back and post my status.
Thanks again
noobworld said:
Wow... Even though I searched for so long, I did not find this.
I guess I did not know what to search for.
I thank you a lot.
I will probably take a while to learn how to use this, so I will disappear until I figure it out.
If I managed to do anything, then will come back and post my status.
Thanks again
Click to expand...
Click to collapse
glad I could help.
and don't bother .its my job to help new.
and pm me if u need smthing.
and please close thread.
Q&A for [KERNEL][n80xx][Samsung JB] Boeffla-Kernel 2.5 stable (03-09-2014)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [KERNEL][n80xx][Samsung JB] Boeffla-Kernel 2.5 stable (03-09-2014). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Lord Boeffla said:
Hi all,
3.0-beta3 is now ready for you (both n8000 and n801x variants).
Change log is the same for both kernels.
Version 3.0-beta3
22.10.2014
Update zzmoove to version 1.0-beta1 (credits to ZaneZam)
Update exFat driver to 1.2.9
Update the flash binary in the boeffla-kernel-reset recovery script, bump to version 3.1
Enjoy
Andi
Click to expand...
Click to collapse
It sjust awesome
help to find kernel n8013
Someone.. anyone.. where can i find this kernel ? a download link would great.. thanks in advance..
3.0-beta3 is now ready for you (both n8000 and n801x variants).
Change log is the same for both kernels.
Version 3.0-beta3
22.10.2014
As always... Read the op.
Then you will see everything is here:
www.boeffla-kernel.de
Andi
hello I'm New On Android, I want to ask regarding flashing the kernel ...
Do I need to run Kernel cleaning Script Afterflashing the kernel? Thanks
Sent from my GT-N8000 using Tapatalk
Araragi said:
hello I'm New On Android, I want to ask regarding flashing the kernel ...
Do I need to run Kernel cleaning Script Afterflashing the kernel? Thanks
Sent from my GT-N8000 using Tapatalk
Click to expand...
Click to collapse
Hm... are you talking about leaving Boeffla-Kernel or moving to Boeffla-Kernel?
If you leave Boeffla-Kernel, you do not need to use any cleaner script. Boeffla stores everything under /data/.boeffla, and this cannot be used by any other kernels.
If you move to Boeffla, also usually no cleaning before required.
Only exception: If you were on a kernel before that stored all his configuration into init.d scripts, then you should cleanup your /system/etc/init.d folder before flashing Boeffla.
That's all however.
Andi
Where can I find ur beta version of the kernal and how can I flash it...im using gnabo rom..could u plz guide me through
w_ayon said:
Where can I find ur beta version of the kernal and how can I flash it...im using gnabo rom..could u plz guide me through
Click to expand...
Click to collapse
All you need is on the homepage, as stated in the OP of all kernel threads.
www.boeffla-kernel.de
Andi
ALL: Google is again playing games and locked down the first of my 3 donation apps in Playstore. Of course no compelling reason provided.
But as I already prepared for that half a year ago, I would like to remind you to use your personal unlock key to gain donation functionalities.
If you have not yet generated (this can be done in the donation app itself) and entered it into Boeffla-Config, it is now urgent to do that!!!
I cannot ensure Google will not lock down the other two donation apps as well soon, so you should be prepared now.
From my side, next Boeffla-Config app version will not support these donation apps anymore but only personal unlock codes.
Also, I will replace remaining donation apps in Playstore very soon (today or tomorrow) with a dummy app that tell users to get in touch with me manually.
Thanks for understanding... and alohas Google, all done wrong, guys there.
Cheers
Andi
Hi all. I have a gnabo rom v7 on my n8000. Can I install this kernel to my device? Android version is 4. 4. 2. Thanks beforehand.
sarvar97 said:
Hi all. I have a gnabo rom v7 on my n8000. Can I install this kernel to my device? Android version is 4. 4. 2. Thanks beforehand.
Click to expand...
Click to collapse
Absolutely, take latest 3.0-beta version for your device (n8000, not the n801x version).
Andi
Lord Boeffla said:
Absolutely, take latest 3.0-beta version for your device (n8000, not the n801x version).
Andi
Click to expand...
Click to collapse
Thanks a lot, the kernel is fantastic.
Hi from Russia. Excellent operation! I tried to pay, but my payment system of it doesn't allow to make. Sorry. The kernel for N8000beta5 isn't set through TWRP2.8.3.0 "error bynary". I set through Odin. Everything is great. Good luck!
And you can also use Boeffla-Config app to flash kernel updates now.
Surprised twrp throwing an error, s3 and opo kernels flash fine with twrp. But I only report what others say, I never use twrp. I am a philz touch guy...
Andi
Lord Boeffla said:
And you can also use Boeffla-Config app to flash kernel updates now.
Surprised twrp throwing an error, s3 and opo kernels flash fine with twrp. But I only report what others say, I never use twrp. I am a philz touch guy...
Andi
Click to expand...
Click to collapse
OK! I set Philz v6.48.4. The kernel of beta5 was normally stitched. Last versions of kernels were normally sewed on TWRP. Thanks! Good luck!
Guroff1974 said:
OK! I set Philz v6.48.4. The kernel of beta5 was normally stitched. Last versions of kernels were normally sewed on TWRP. Thanks! Good luck!
Click to expand...
Click to collapse
But this is unexplainable then... the flash binary has not changed for more than half a year.
However I got to know in the OnePlus One thread, TWRP seems to have introduced some issues lately. But never used TWRP myself, so it is just second hand information I have seen.
Andi
Guroff1974 said:
OK! I set Philz v6.48.4. The kernel of beta5 was normally stitched. Last versions of kernels were normally sewed on TWRP. Thanks! Good luck!
Click to expand...
Click to collapse
Ah, but can be something else.
In order to avoid people are flashing wrong kernels, I put asserts in.
Could you please just boot your tablet and look in /system/build.prop file what the entries are there for:
ro.build.product
ro.build.model
ro.build.device
Many thanks
Andi
Ok, for the time being I uploaded the kernels again without the assert checks.
So be careful to not flash the kernel on a different device than the Tab10.2
Please redownload the zip again, it should work now also in TWRP.
Thanks
Andi
Lord Boeffla said:
Ok, for the time being I uploaded the kernels again without the assert checks.
So be careful to not flash the kernel on a different device than the Tab10.2
Please redownload the zip again, it should work now also in TWRP.
Thanks
Andi
Click to expand...
Click to collapse
I redownload N8000beta5 of 31.01.2015. Now everything is good. The kernel is set through TWRP and Philz. Gnabo v8 firmware. Thanks! Good luck!
problem with boeffla kernel v3 beta 6 for samsung note 10.1 (n801x)
Hi ! I am using the samsung kitkat stock rom 4.4.2 rooted in a samsung galaxy note 10.1 (n8010). First time trying a kernel. I have tried to install the boeffla kernel mentioned in the title, both via odin and trwp, but i have the same problem once installed... when rebooting the tablet it just stays in a black display after the "samsung galaxy note 10.1" title. It just does not start, i have to boot in download mode and reinstall the stock rom via odin. Help please! I would like to try this kernel in my tablet ! Thanks!
Hi,
I have the note 10.1 (n8010) I am currently using Lirokoas CM13 build
The kernel that comes with this ROM is this https://github.com/littlelerroyy/android_kernel_samsung_n80xx
However I want to use this kernel instead (is newer, has f2fs support, want it for the basis for new modifications, etc) https://github.com/littlelerroyy/android_kernel_samsung_smdk4412
I have cloned the cm13 branch and compiled using the cyanogenmod_n8013 deconfig.
When i flash using the ramdisk supplied by the stock kernel. The system doesnt bootloop, it simply shows a black screen and never boots.
I need to know what I could be missing or what i need to start to do to fix this issue. Please ask any relevant questions, All suggestions welcome.
Cheers.
little_lerroyy said:
Hi,
I have the note 10.1 (n8010) I am currently using Lirokoas CM13 build
The kernel that comes with this ROM is this https://github.com/littlelerroyy/android_kernel_samsung_n80xx
However I want to use this kernel instead (is newer, has f2fs support, want it for the basis for new modifications, etc) https://github.com/littlelerroyy/android_kernel_samsung_smdk4412
I have cloned the cm13 branch and compiled using the cyanogenmod_n8013 deconfig.
When i flash using the ramdisk supplied by the stock kernel. The system doesnt bootloop, it simply shows a black screen and never boots.
I need to know what I could be missing or what i need to start to do to fix this issue. Please ask any relevant questions, All suggestions welcome.
Cheers.
Click to expand...
Click to collapse
You are a senior member , xda assist is for new members to be guided to the correct forum to ask their question. Please post you question in the Note 10 forum not in assist
Regards
Moderation Team
SM-G389F Marshmallow Port for SM-G388F
Hello Everyone,
So we all know that the SM-G389F has Marshmallow as it's OS,
But when we look on the side of the SM-G388F, we still have Lollipop as it's OS, So I decided to port the OS version of the SM-G389F to the SM-G388F while configuring it to be compatible with it's hardware! :laugh:
I might need some help....
But we can start by Converting the Firmware Download to a Zip for the Custom Recovery to flash it
(Link to Download)
Thanks for Tuning in,
I will keep you all Updated soon! :fingers-crossed:
Hello Everyone,
I've wasted plenty of time trying to extract the SM-G389F Marshmallow Firmware but it was all for nothing. So now I am asking you all who own this device to flash the ROM link above using odin (https://www.sammobile.com/firmwares/galaxy-xcover3/SM-G389F/BTU/download/G389FXXS1APK1/114774/) and then creating a backup via TWRP including the system.img and the boot.img and sending it to me via Dropbox, Google Drive...
Anyway I would like to forgive myself for failing to do this operation without owning the phone because of the md5 protection, but now I will be leaving this part in your hands
Thanks in Advice,
Diamond26
For all intents and purposes consider the two devices as completely separate/different. First of all the got completely different SoC's (not revisions but completely different brands of SoC's). I started try to compile LineageOS (my sources are up on github), but I was facing completely obscure or unheard of errors that where difficult to fix and the amount of free time I have has changed so I more or less have stopped doing that for the time being.
I will be writing up all the info I know off the device but that task has gotten away from me at the moment due to computer problems.
Matt07211 said:
For all intents and purposes consider the two devices as completely separate/different. First of all the got completely different SoC's (not revisions but completely different brands of SoC's). I started try to compile LineageOS (my sources are up on github), but I was facing completely obscure or unheard of errors that where difficult to fix and the amount of free time I have has changed so I more or less have stopped doing that for the time being.
I will be writing up all the info I know off the device but that task has gotten away from me at the moment due to computer problems.
Click to expand...
Click to collapse
Thanks for including yourself in this thread!
But may I ask which device do you own please?
Diamond26 said:
Thanks for including yourself in this thread!
But may I ask which device do you own please?
Click to expand...
Click to collapse
Well in currently typing it from my Samsung xCover3, with the Marvell SoC, so it's the SM-G388F
Matt07211 said:
Well in currently typing it from my Samsung xCover3, with the Marvell SoC, so it's the SM-G388F
Click to expand...
Click to collapse
Oh ok!
I was just eager to see if someone with a SM-G389F has come, maybe he could back up his 6.0 Stock ROM and maybe I could modify it.
That's why!
Diamond26 said:
Oh ok!
I was just eager to see if someone with a SM-G389F has come, maybe he could back up his 6.0 Stock ROM and maybe I could modify it.
That's why!
Click to expand...
Click to collapse
Please re-read my initial post in this thread, it's not possible. Your dealing with two different types of SoC's, so what your proposing is not possible, compiling from stock Android sources is (if you can fix every compile error)
Matt07211 said:
Please re-read my initial post in this thread, it's not possible. Your dealing with two different types of SoC's, so what your proposing is not possible, compiling from stock Android sources is (if you can fix every compile error)
Click to expand...
Click to collapse
I just want to mess around with the ROM, maybe I could modify something!
PixelBoot said:
I just want to mess around with the ROM, maybe I could modify something!
Click to expand...
Click to collapse
Do what ever you want, you can still mess around a lot, you just can't transplant files from the value edition to the Normal edition.
There is some cool mods you can do if you modify system apks.
https://forum.xda-developers.com/showthread.php?t=2799050
Is this thread still up?
Rrrrrrx404 said:
Is this thread still up?
Click to expand...
Click to collapse
Thinking about it...
I was thinking the same thing… I have an old Xcover, so i just wanted to try…
Did you succeed?
Guys, I can't find any Oreo roms for my Z5.
Is it possible to build one with Xperia Open Devices Project?
yes it is but will take you a long time
XperiaDev has not updated the sources to support Oreo.
This means that you will not be able to compile AOSP.
GreyLeshy said:
XperiaDev has not updated the sources to support Oreo.
This means that you will not be able to compile AOSP.
Click to expand...
Click to collapse
yep, any support official (Sony) or "unofficial" (SonyXperiaDev) got abandoned,
so community needs to step in ...
There could be a way to get the phone part, etc. working from what I read (sonyxperiadev)
HOWEVER that would leave out the camera from the equation (something similar is currently happening for the M4 Aqua where burtcubbins is porting the device to 4.4 kernel)
So the thing is:
if anyone ported the device to the 4.4 kernel (which includes "legacy" gpu driver support) we would have all functionality, except camera
and probably a blazing fast phone + much extended AOSP & update support (including Android 8.0 and 8.1 and perhaps beyond)
Anyone has interest to work on it ?
zacharias.maladroit said:
So the thing is:
if anyone ported the device to the 4.4 kernel (which includes "legacy" gpu driver support) we would have all functionality, except camera
and probably a blazing fast phone + much extended AOSP & update support (including Android 8.0 and 8.1 and perhaps beyond)
Anyone has interest to work on it ?
Click to expand...
Click to collapse
Maybe @Myself5 could help!
shehabskull said:
Maybe @Myself5 could help!
Click to expand...
Click to collapse
How about No?
I was part of the stock based bringup for a reason. That reason was to never ever touch the SODP Kernel along with the Z5 ever again.
So the answer is No.
Absolutely Not.
No.
@Myself5 I understand you dont want to help because you have done a lot but ocasiaonly peaks and tests or edits would not hurt would it and to any developer reading this please just try
Quantumkk123 said:
@Myself5 I understand you dont want to help because you have done a lot but ocasiaonly peaks and tests or edits would not hurt would it and to any developer reading this please just try
Click to expand...
Click to collapse
Mate, he already said "NONONONONONONO", lol
EugenStanis said:
Mate, he already said "NONONONONONONO", lol
Click to expand...
Click to collapse
I know but I am trying my luck here
zacharias.maladroit said:
So the thing is:
if anyone ported the device to the 4.4 kernel (which includes "legacy" gpu driver support) we would have all functionality, except camera
and probably a blazing fast phone + much extended AOSP & update support (including Android 8.0 and 8.1 and perhaps beyond)
Anyone has interest to work on it ?
Click to expand...
Click to collapse
Do you have Telegram? Contact me @EnesSastim
EnesSastim said:
Do you have Telegram? Contact me @EnesSastim
Click to expand...
Click to collapse
Thanks, unfortunately I don't have telegram and I won't sign up in the near future
zacharias.maladroit said:
Thanks, unfortunately I don't have telegram and I won't sign up in the near future
Click to expand...
Click to collapse
I'll try to make oreo device tree, if you can make the kernel we can build Oreo.
EnesSastim said:
I'll try to make oreo device tree, if you can make the kernel we can build Oreo.
Click to expand...
Click to collapse
even the other devs (seemingly ?) aren't really sure what commits are needed to get the full/enhanced functionality - the basics might be there but perhaps something's missing
in any case the repo is at: https://github.com/sony-msm8994
I'm right now not interested in working on Oreo or any other matter,
I've flashed to Marshmallow again on the Z5 and do some investigation related to battery consumption and others there.
Currently not much time for flash-testing and ROM development.
I remember having seen kernels with commit changes from Nougat to Oreo but not sure which exact kernels those were,
bullhead, angler , oneplus2 - some of those must have been
We really want you guys to do it. Oreo port would be a beast of ROM <3
Not having the updated kernel sources (probably) shouldn't be a problem
since we can (attempt to) port the Oreo ROM from Xperia X and add the missing kernel changes from the Xperia X device (kernel diff)
https://forum.xda-developers.com/xperia-x/development/ub-xgen-rom-1-0-5-xperia-x-t3778738
HOWEVER
after reading the following:
https://forum.xda-developers.com/xperia-x/help/upgrade-via-ota-to-oreo-terrible-t3754928
it's rather pointless to try anything related to porting or updating to a higher Android version:
best battery for now (at least in my experience) use a modded Nougat or Marshmallow ROM with Stock kernel + Stock kernel modules,
that'll get you the best battery runtime when e.g. listening to Music, browsing, etc.
Also: I've done countless passes of different kernel releases and each time as soon as security updates, enhanced performance, etc. is added to the picture at some point (couldn't pinpoint exactly how or why, I suspect it's somehow perhaps looping inside the kernel) it miraculously starts to drain like it had a 4000 mAh battery
- this is ridiculous !
There simply isn't much potential to be gained in this device ( /me peers at the Note 3 and its improvements over time ... /sigh )
hi @zacharias.maladroit so is there still development for the z5 oreo rom or is there no point? I will try port that rom for xperia z5 just like i did for z3+ because believe it or not it actually works and i wll see how it goes
---------- Post added at 05:21 PM ---------- Previous post was at 05:11 PM ----------
also are you developers already trying to copy to the z5 cos if so it would be appreciated as i am a noob and just discovered the files are a lot different so now i need to actually learn
Quantumkk123 said:
hi @zacharias.maladroit so is there still development for the z5 oreo rom or is there no point? I will try port that rom for xperia z5 just like i did for z3+ because believe it or not it actually works and i wll see how it goes
---------- Post added at 05:21 PM ---------- Previous post was at 05:11 PM ----------
also are you developers already trying to copy to the z5 cos if so it would be appreciated as i am a noob and just discovered the files are a lot different so now i need to actually learn
Click to expand...
Click to collapse
Not that I'm aware of, just noticed the similarities in hardware between the X and Z5, Z5 series and did a superficial quick comparison
So not sure if others are currently working on it ...
@Quantumkk123
https://forum.xda-developers.com/android/help/tut-how-to-convert-dat-br-to-dat-t3723926
https://forum.xda-developers.com/an.../how-to-conver-lollipop-dat-files-to-t2978952
https://source.android.com/devices/architecture/vintf/comp-matrices
https://source.android.com/devices/architecture/vintf/resources
Well, a lot of files would need adaptation, and then there's the question if the GPU could be driven ... at all
the file and folder structure looks quite different ...
vendor/ueventd.rc
vendor/manifest.xml
vendor/qcril.db -> vendor/radio/qcril_database/qcril.db (?)
msm8994 specific hardware bits / drivers, thermal (very important !, or we're relying on third-party thermal driver solutions to try avoiding any potential issues)
touchscreen (also synaptics clearpad?)
and that's only looking at the vendor folder