I am very interested in porting Xperia L to OmniRom and had starting work on it. The kitkat sources is already available anyway(see here). Compiling it is easy, just follow the instructions. I now have a working kitkat rom which unfortunately seem to have a serious bug of unable to go into deep sleep(dropped >40% over a night).
I have started work on the kernel sources and wish to invite all developers who are interested to work together.
For those of you with wifi issue, make sure that you are on stock rom 15.3.A.x.x
Extracted from Sony opensource
Most of the AOSP for Xperia L device configurations are cloned from the official Xperia L software version 15.3.A.0.x, so please make sure that you upgrade the phone software to, for example 15.3.A.0.26, before flashing the AOSP for Xperia L images, or certain functions like WiFi may not work.
Known issues/workaround:
1. There are some missing KLOG information that prevent building of the kernel( fix by disabling CCI_KLOG)
2. Deep sleep issue seem to be caused by wait_for_irsc_completion timeout(workaround by disabling
MSM_IPC_ROUTER_SECURITY)
3. Enable reboot recovery
Sources
Kernel 3.4 from Sony
Github version by me
Modified from Holofied Red Holo Theme (http://forum.xda-developers.com/showthread.php?t=2405512)
Count me IN
Count me in PM me more info your status and are you planing to make CAF based kernel ?
Heres's my GitHUB Account : Navneet-Suresh
Best of luck mate! @ Ghostfreak NB see if you can help this guy in this project!!
Navneet Suresh said:
Count me in PM me more info your status and are you planing to make CAF based kernel ?
Heres's my GitHUB Account : Navneet-Suresh
Click to expand...
Click to collapse
Have not worked with CAF kernel before. Moreover, the most important thing now is to get a stable working kernel for kitkat before embarking on anything else.
I will update my progress here in this thread. Its good to keep the communication open here so that others can also contribute/help. Right now, I can successfully compiled the zImage. Going to test it out later on.
update: notice that you have the 15.3.A.1.14 sources. Where did you get it from? My phone was running on this build before I flashed the AOSP 4.4 rom. Dont you have the CCI_KLOG compilation error on 15.3.A.1.14?
I got playing with kit kat for few days and when the phone try to go in deep sleep there is QSEECOM errors that stopped the freezing...
Im not a pro dev,so I might be wrong.
Sent from my C2105 using xda app-developers app
siankatabg said:
I got playing with kit kat for few days and when the phone try to go in deep sleep there is QSEECOM errors that stopped the freezing...
Im not a pro dev,so I might be wrong.
Sent from my C2105 using xda app-developers app
Click to expand...
Click to collapse
Which ROM did you test from? I just flashed the one I compiled from source last night so did not get to test much. What I did noticed was that the battery dropped >40% overnight. I suspect that it might not have gone into deep sleep.
@KillerKink getting the zimage is easy you will have to make certain changes to kernel/ramdisk to make it compatible to KK
Sent from my C2104 using xda app-developers app
Count me in for starters... I'm very interested in getting this done as well..
Sent from my C2104 using XDA Premium 4 mobile app
Navneet Suresh said:
@KillerKink getting the zimage is easy you will have to make certain changes to kernel/ramdisk to make it compatible to KK
Sent from my C2104 using xda app-developers app
Click to expand...
Click to collapse
This is not an issue for me. What I would like to know is where did you get the A.1.14 sources from? Dont you have compilation errors from the sony sources
I guess. 14 sources aren't published by Sony yet right? At least I couldn't find it.. Where did you get that from?
Sent from my C2104 using XDA Premium 4 mobile app
Ghostfreak NB said:
Count me in for starters... I'm very interested in getting this done as well..
Sent from my C2104 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Wonderful. Did you manage to compile from sony sources with the sa77_defconfig without any change?
I had to disable CCI_KLOG.
Ghostfreak NB said:
I guess. 14 sources aren't published by Sony yet right? At least I couldn't find it.. Where did you get that from?
Sent from my C2104 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I dont have the .14 sources. Its .12 that I am working on.
KillerKink said:
Which ROM did you test from? I just flashed the one I compiled from source last night so did not get to test much. What I did noticed was that the battery dropped >40% overnight. I suspect that it might not have gone into deep sleep.
Click to expand...
Click to collapse
I use some version from General section, pure 4.4.2 AOSP and kernel compiled by me and patched to 3.4.79.
Sent from my C2105 using xda app-developers app
siankatabg said:
I use some version from General section, pure 4.4.2 AOSP and kernel compiled by me and patched to 3.4.79.
Sent from my C2105 using xda app-developers app
Click to expand...
Click to collapse
Cool! Did the kernel have deep sleep issue？ Do you have git for your work?
How did you resolved the CCI_KLOG compilation errors?
KillerKink said:
Cool! Did the kernel have deep sleep issue？ Do you have git for your work?
How did you resolved the CCI_KLOG compilation errors?
Click to expand...
Click to collapse
Ye it have that issue, I saw that QSEECOM error on it. And sorry,I don't know how to use git and don't have kernel uploaded there.I'm using this as kernel base and don't have compiling errors.
https://github.com/uberlaggydarwin/taoshan-tracking/tree/warningless-stock-kernel
See the commits and you will find how to solve that problem.And better use whole commit
P.s. Credits to uberlaggydarwin
Sent from my C2105 using xda app-developers app
siankatabg said:
Ye it have that issue, I saw that QSEECOM error on it. And sorry,I don't know how to use git and don't have kernel uploaded there.I'm using this as kernel base and don't have compiling errors.
https://github.com/uberlaggydarwin/taoshan-tracking/tree/warningless-stock-kernel
See the commits and you will find how to solve that problem.And better use whole commit
P.s. Credits to uberlaggydarwin
Sent from my C2105 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the site. Yup, he did the pretty much the same as me.
Update: Kernel compiled via source is bootable.
KillerKink said:
Update: Kernel compiled via source is bootable.
Click to expand...
Click to collapse
Count me in for help. BTW I just saw your screenshot in OP in which you've booted kernel successfully on AOSP, can you link me to that kernel source which you used? I would really like to investigate on it.
The Dark Knight said:
Count me in for help. BTW I just saw your screenshot in OP in which you've booted kernel successfully on AOSP, can you link me to that kernel source which you used? I would really like to investigate on it.
Click to expand...
Click to collapse
feel free to work on it. The sources is the same one that I posted in the first post. btw it seem that there are many working kernels around. Guess I will work on porting Philz Touch recovery first.
KillerKink said:
feel free to work on it. The sources is the same one that I posted in the first post. btw it seem that there are many working kernels around. Guess I will work on porting Philz Touch recovery first.
Click to expand...
Click to collapse
I really can't believe my eyes.
You booted stock kernel on AOSP.
Related
About
Based on Lupohirps kernel sources I present Icy.Kernel.
By request I made two branches, one with multitouch fix and one without.
Click to expand...
Click to collapse
Changelog
1.0 Recompile from Lupohirps sources with ext2/3/4 enabled
1.1 Added improved touchscreendriver from Der_Caveman
23 feb. Changed branches
Standard Icy.Kernel
1.0.1 Fixed WiFi
1.0.2 Based on cm-sources
Fixed ext4
Added tun.ko for vpn support
Improved Icy.Kernel (with multitouch fix)
1.1.1 Fixed WiFi
3.0 Alpha kernel
Click to expand...
Click to collapse
Installation
1 - Reboot into recovery
2 - Flash kernel version from this topic
3 - Reboot
4 - Done!
Click to expand...
Click to collapse
Downloads
Latest Standard version
Latest Improved version
Latest 3.0 kernel
Click to expand...
Click to collapse
Github for 3.0 kernel (still a WIP!!!)
Bugs:
No wifi in 1.0.2.
Thanks to have built it
Downloading...
I don't think includng the touch fix will be good.
It makes system choppy.
Thanks _Arjen_ , can u kindly tell us whats change-log ?
GonDr said:
Thanks _Arjen_ , can u kindly tell us whats change-log ?
Click to expand...
Click to collapse
Go back to the first post and actually READ IT this time....
I just pressed the 'Thanks' button. Sorry for that. We all know you make no contributions on development to our phone.[/sarcasm]
Seriously, it's just great. I'm looking forward to all the surprises you can come up with in this kernel.
MaKTaiL said:
I don't think includng the touch fix will be good.
It makes system choppy.
Click to expand...
Click to collapse
I agree. I would even suggest that he could include the stock touch screen driver. (if I'm not mistaken the stock ICS kernel has the driver made by franco which has this drawback of stuttery scrolling)
yuripg1 said:
I just pressed the 'Thanks' button. Sorry for that. We all know you make no contributions on development to our phone.[/sarcasm]
Seriously, it's just great. I'm looking forward to all the surprises you can come up with in this kernel.I agree. I would even suggest that you include the stock touch screen driver (if I'm not mistaken the stock ICS kernel has the driver made by franco which has those drawbacks of stuttery scrolling.
Click to expand...
Click to collapse
Stock driver would be great! I couldn't care less for performance on games.
I just want a phone smooth enough for all other tasks.
See CM7 Nightlies for instance, that kernel has stock touchscreen and it's smooth as hell.
Is it only a recompile of the sources from lupohirp? when not would be nice you could put your changes on github too.
MaKTaiL said:
Go back to the first post and actually READ IT this time....
Click to expand...
Click to collapse
I know what there in first post and no changlog !! there is one thing, Based on Lupohirps kernel sources
so if u seen any changelog plz tell me, thanks
Will consider it, guess I can make two branches, one with the multitouch-fix and one without
woglinde said:
Is it only a recompile of the sources from lupohirp? when not would be nice you could put your changes on github too.
Click to expand...
Click to collapse
When changes are added I will upload it to GitHub
As stated version 1 is a recompile with ext4 support.
_Arjen_ said:
When changes are added I will upload it to GitHub
As stated version 1 is a recompile with ext4 support.
Click to expand...
Click to collapse
Thanks _Arjen_, sorry for my question i'm a noob but is there a plan in future to bring kernel 3.x to p500 ?
GonDr said:
I know what there in first post and no changlog !! there is one thing, Based on Lupohirps kernel sources
so if u seen any changelog plz tell me, thanks
Click to expand...
Click to collapse
Ext4 support.
Sent from my LG-P500 using xda premium
MaKTaiL said:
Ext4 support.
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
Thanks but i know it also.
Two versions would be great. Can you consider including the touch driver from CM7 nightly?
Sent from my LG-P500 using xda premium
MaKTaiL said:
Two versions would be great. Can you consider including the touch driver from CM7 nightly?
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
Will take a look at it and compare with the driver from Franco's sources to see if there are any differences.
First post updated!
BUG: I do not recognize the WiFi signal.
Greetings !
_Arjen_ said:
About
Bugs
Wifi not working!!!
Click to expand...
Click to collapse
Wifi is not working because wifi module is broken.
I know it's broken , but you are wrong about the size
Rebuilding again to get new modules
When beta4 release I will test your kernel .....
wow cant believe they already released open source lol
seems like they need mental treatment
http://developer.sonymobile.com/dow...es/open-source-archive-for-build-15-3-a-1-12/
naitik2012 said:
wow cant believe they already released open source lol
seems like they need mental treatment
http://developer.sonymobile.com/dow...es/open-source-archive-for-build-15-3-a-1-12/
Click to expand...
Click to collapse
good news for our device buddy,
is it kitkat?
amazing ....
Sent from my C2104 using XDA Premium HD app
]Isn't it weird? Usually release comes first before the source?
Sony is just crazy, haven't release the update yet and givin to us source. Nice.
So what's the version of android?
Tapnięte z eL'ki
Commit #860560a at uberlaggydarwin/taoshan-tracking https://github.com/uberlaggydarwin/taoshan-tracking/commit/860560aa992d2511337ff517e659d22cf1becec1
I'm out at the shops now but I've made a quick diff for you guys..
See you in a few hours
Root should still work. Nothing too much seriously different except frame rate increase by 1 lol.
Sent from my C5303 using XDA Premium 4 mobile app
Excited for the update and CM too..
Perfect!
i hope this update is bugfree
Yeah, its strange!!!!
Sent from my C2104 using xda app-developers app
Apparently our CyanogenMod maintainer has had a look at the open source archive & says that numerous parts have been updated. I have no original source but am only going by what I read here. By what it says I am definitely looking forward to the update.
TheBil said:
good news for our device buddy,
is it kitkat?
Click to expand...
Click to collapse
i don`t think so,
if the number has 15.4.A.1.12 ,then only it's a new android version.
the 2nd digit after the 1st point change in every new android version
How they can fix all bugs in a single small update,interesting!
private
sohow it looks? android version?
mukulatri said:
How they can fix all bugs in a single small update,interesting!
private
Click to expand...
Click to collapse
They never can fix all the bugs
Sent from my C2105 using XDA Premium 4 mobile app
Yeah I also think that, if 15.3.A.0.27 was going to be released as a bug fix then why it was skipped you know I mean another bug fix has to be released only if 0.27 had bugs, so why a new build was certified before 0.27 was released. And if they wanted to add features like all the Xperia phones e.g. Xperia Themes etc. they have to update to Android 4.3 as all the Xperias with Android 4.3 are only eligible for them.
So why a big update?
I also agree with that second digit change thing for Android version increments.
But I can't understand the above done thing by Sony.
Sent from my C2104 using xda app-developers app
coolhz said:
Yeah I also think that, if 15.3.A.0.27 was going to be released as a bug fix then why it was skipped you know I mean another bug fix has to be released only if 0.27 had bugs, so why a new build was certified before 0.27 was released. And if they wanted to add features like all the Xperia phones e.g. Xperia Themes etc. they have to update to Android 4.3 as all the Xperias with Android 4.3 are only eligible for them.
So why a big update?
I also agree with that second digit change thing for Android version increments.
But I can't understand the above done thing by Sony.
Sent from my C2104 using xda app-developers app
Click to expand...
Click to collapse
I think you have not noticed, but 0.27 is already released. It was for a specific operator(T-Mobile i guess). :victory:
can i install this firmware?
guys there is link to a 156mb file for the latest firmware...so can i install it?...stock n rooted...has anyone installed it?any advantages or disadvantages by installing it thru this method rather than waiting for sony for ota update ?
nithin jain said:
guys there is link to a 156mb file for the latest firmware...so can i install it?...stock n rooted...has anyone installed it?any advantages or disadvantages by installing it thru this method rather than waiting for sony for ota update ?
Click to expand...
Click to collapse
No thats is not for installation purpuse.. Its source code
Sent from my C2104 using XDA Premium 4 mobile app
Can some one give me step to compile cm for xperia e i have successfully downloaded cm source using repo sync i am having problem in pulling device specific files
yto5 said:
Can some one give me step to compile cm for xperia e i have successfully downloaded cm source using repo sync i am having problem in pulling device specific files
Click to expand...
Click to collapse
what was the size of the source? !
which cm are you talking about?
do you have previous experience ?
How determined are you?
Grimlock007 said:
what was the size of the source? !
which cm are you talking about?
do you have previous experience ?
How determined are you?
Click to expand...
Click to collapse
Right to the point, aren't you? Just kidding.
Need to know what version of Android you're building. And extracting vendor files... are you trying to build everything from scratch?! (I mean, are you using this guide? http://wiki.cyanogenmod.org/w/Doc:_porting_intro)
I'm building on version cm10.1 and i am a complete noob i watched various guides
Sent from my Nexus 5 using XDA Premium 4 mobile app
I recently ported MultiROM to Xperia M and I have the sources up and I am willing not to waste them.
Disclaimer : I am not responsible for anything that happens to you or your device after flashing this mod. Though, nothing generally happens when you do it right. Make backup, always.
I have ported it xperia M
Here are some files for testing
You need CM-12.1 installed to test this.
Links removed
RECOVERY.IMG - To be flashed on fota partition
XL_CM-kexec-xx-xx-xxxx.zip - To be flashed in recovery
multirom-xxxxxxxx-v31x-UNOFFICIAL-taoshan.zip - To be flashed in recovery
Next boot should come up with multirom menu
If it does, post screens, if doesn't , post last_kmsg.
Due to lack of my knowledge, I have dismissed this project.
aweosomeabhijeet said:
I recently ported MultiROM to Xperia M and I have the sources up and I am willing not to waste them.
I have ported it xperia M
Here are some files for testing
You need CM-12.1 installed to test this.
TEST 1
RECOVERY.IMG - To be flashed on fota partition
XL_CM-kexec-xx-xx-xxxx.zip - To be flashed in recovery
multirom-xxxxxxxx-v31x-UNOFFICIAL-taoshan.zip - To be flashed in recovery
Next boot should come up with multirom menu
If it does, post screens, if doesn't , post last_kmsg.
Click to expand...
Click to collapse
May i have a look on sourcecode? Im mainly interested in where the rom+ kernel of second rom are saved
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
May i have a look on sourcecode? Im mainly interested in where the rom+ kernel of second rom are saved
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
Here you go
https://github.com/XperiaMultiROM/multirom/
https://github.com/XperiaMultiROM/android_bootable_recovery
aweosomeabhijeet said:
Here you go
https://github.com/XperiaMultiROM/multirom/
https://github.com/XperiaMultiROM/android_bootable_recovery
Click to expand...
Click to collapse
Ok seems like it goes from sd_ext .... What kernel you used? Varuns Caf? (The official one) and varuns device tree? If yes you may get wrong device errors while flashing
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
Ok seems like it goes from sd_ext .... What kernel you used? Varuns Caf? (The official one) and varuns device tree? If yes you may get wrong device errors while flashing
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
I used sources and device tree from CM's repo
Doesn't matter, because I had removed assert from updater-script and no ROM flashing is required in here.
So all files must be good and compatible.
Hey, great job in compiling this. I want to try this out but what are the risks? Can I get hardbricked?
The recovery included in the recovery.img is Cyanogen Recovery.
So cannot able to flash those zips.
I heard MultiROM uses modded TWRP.
Please check
corphish said:
The recovery included in the recovery.img is Cyanogen Recovery.
So cannot able to flash those zips.
I heard MultiROM uses modded TWRP.
Please check
Click to expand...
Click to collapse
Maybe the recovery is faulty and therefor cm recovery was loaded?
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
Maybe the recovery is faulty and therefor cm recovery was loaded?
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
Nope..I was on TWRP flashed on FOTA from your app.
Then flashed this img, voila, CM Recovery.
corphish said:
Nope..I was on TWRP flashed on FOTA from your app.
Then flashed this img, voila, CM Recovery.
Click to expand...
Click to collapse
Yes that what i.meaned ^^ you flashed this im in FOTAKernel dont you? Then my recovery will be overrided and if his recovery fails to load the kernelinbuild (cm) will be loaded....
The common cm device tree is not able to build a twrp properly... Im building with omnirom and a "changed" varun tree
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
Yes that what i.meaned ^^ you flashed this im in FOTAKernel dont you? Then my recovery will be overrided and if his recovery fails to load the kernelinbuild (cm) will be loaded....
The common cm device tree is not able to build a twrp properly... Im building with omnirom and a "changed" varun tree
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
Ohk I did not know about invalid recovery in fota partition would result in loading recovery from boot partition.
And its really a nice idea of you compiling modded TWRP, as soon as you are done, feel free to share as I am ready with other zips
corphish said:
Ohk I did not know about invalid recovery in fota partition would result in loading recovery from boot partition.
And its really a nice idea of you compiling modded TWRP, as soon as you are done, feel free to share as I am ready with other zips
Click to expand...
Click to collapse
i did have a look at this recovery.img ... its definitly a TWRP build... but its damn wrong.... wrong qcom.fstab and recovery.fstab ... NO twrp.fstab ... healthhd seems to have wrong size (ok im not 100% with that but experience says it must be bigger) ... the Size of theme images is wrong.... AND the ramdisk size is totally above the size the kernel will load... thats why it leads to a "broken" recovery-load .... that will lead to a emergency load of kernel-inbuild recovery....
@ OP didnt you got make errors? after seeing this im sure you have build with -i -k
---------- Post added at 08:36 AM ---------- Previous post was at 08:22 AM ----------
ok without any kind of warranty that this will work... i have manipulated this recovery.img (NOT BUILD FROM SOURCE! MANUALLY REPAIR! ) ... maybe this works maybe not....
like you know my device is gone atm.... so maybe if my device is back i will have a deeper look into this...
aweosomeabhijeet said:
I recently ported MultiROM to Xperia M and I have the sources up and I am willing not to waste them.
Click to expand...
Click to collapse
By making blind builds, you do "waste" the source code.
aweosomeabhijeet said:
I used sources and device tree from CM's repo
Click to expand...
Click to collapse
And you seriously expect a working build?
adil089 said:
Hey, great job in compiling this.
Click to expand...
Click to collapse
No, definitely not. He just used my sources (XperiaMultiROM) to compile it, which is a piece of cake. Honestly, if porting MultiROM was just a matter of compiling, monkeys could do it too.
OP: Blind builds are not encouraged on XDA. Especially when they're untested and broken.
And no, this shouldn't hardbrick your phone. You'll need to reflash your kernel and the system partition in the worst case.
Sent from my Xperia Z using XDA Free mobile app
Olivier said:
By making blind builds, you do "waste" the source code.
And you seriously expect a working build?
No, definitely not. He just used my sources (XperiaMultiROM) to compile it, which is a piece of cake. Honestly, if porting MultiROM was just a matter of compiling, monkeys could do it too.
OP: Blind builds are not encouraged on XDA. Especially when they're untested and broken.
And no, this shouldn't hardbrick your phone. You'll need to reflash your kernel and the system partition in the worst case.
Sent from my Xperia Z using XDA Free mobile app
Click to expand...
Click to collapse
Thank you for response thats exactly what i thought... He blind builded (see my comment above... Im not good in rom building but recoverys im good in... )
BTW maybe you let a word down on cm12.1 thread? Its a while ago now as varun said you will maintain our device... It would be nice to have a word from yourself about if its true or not
Sent from my Xperia T using XDA Free mobile app
Olivier said:
By making blind builds, you do "waste" the source code.
And you seriously expect a working build?
No, definitely not. He just used my sources (XperiaMultiROM) to compile it, which is a piece of cake. Honestly, if porting MultiROM was just a matter of compiling, monkeys could do it too.
OP: Blind builds are not encouraged on XDA. Especially when they're untested and broken.
And no, this shouldn't hardbrick your phone. You'll need to reflash your kernel and the system partition in the worst case.
Sent from my Xperia Z using XDA Free mobile app
Click to expand...
Click to collapse
Thank You.
Please apply for closure of the thread
Sent from my HTC One
To everyone:
I am sorry for doing it all wrong and blindly. I just had ported to a similar device and had it working perfectly.
Never knew CM sources wouldn't work for XL. Basically I trusted on CM people for device tree and kernel, which I shouldn't have definitely.
If anyone feels to, can apply for closing down the thread. I have other devices, I'll try getting it to work on them.
Thank you
Sent from my HTC One
Pls can someone else build MultiRom for Xperia L? Maybe you @SdtBarbarossa?
Sent from my C2105 using XDA Free mobile app
Xperia_L said:
Pls can someone else build MultiRom for Xperia L? Maybe you @SdtBarbarossa?
Sent from my C2105 using XDA Free mobile app
Click to expand...
Click to collapse
Sorry i am out of device... Maybe ask Olivier nice
Sent from my Xperia T using XDA Free mobile app
Thread closed upon request
Forum moderator,
matt4321
This is a development thread for Android 6.0.1 in mediatek devices, including mt6582 & mt6592, more MTK SoC may be supported in the future.
Source core:
CM-13.0:
https://github.com/ferhung-mtk
Omnirom:
https://github.com/omnirom-mtk
Any progress till now?
Did you get back your device in your hand?
thanks.
I have tried your code for my device - Xolo Q2500/Blu D650a. RIL is unstable and tried to make Wlan & BT work still Selinux is the issue. Made it permissive resulted in bootloop. Now trying to adapt CM13.0 repo using CM-12.1's patches. Let's see if it works!
Btw booting it was more than enough.
Yes ! Following the Thread , Would also like to work for my MTK device ?
Sent from my GIONEE M2 using Tapatalk
Rohan Taneja said:
I have tried your code for my device - Xolo Q2500/Blu D650a. RIL is unstable and tried to make Wlan & BT work still Selinux is the issue. Made it permissive resulted in bootloop. Now trying to adapt CM13.0 repo using CM-12.1's patches. Let's see if it works!
Btw booting it was more than enough.
Click to expand...
Click to collapse
Yes, but you still need some new patches in my github. Or you can't boot.
https://github.com/ferhung-mtk/android_device_Xiaomi_HM2014011/tree/cm-13.0/libmt6582
https://github.com/ferhung-mtk/android_system_core/commit/4741254f80be09c2d7a0b201a2146422166dba7d
https://github.com/ferhung-mtk/android_system_core/commit/8c3a8c5dd032685ef12426ed8fc65a367dc06458
If you have a crashing desktop, use this commit: https://github.com/ferhung-mtk/andr...mmit/7b451c57a7b6c0de6c068cef6cc0cad3e8e2c5ad
Sent from my m2 using XDA Free mobile app
waseemmayaa said:
Any progress till now?
Did you get back your device in your hand?
thanks.
Click to expand...
Click to collapse
Testing the new methods of sepolicy, which is from the MTK's MM.
Sent from my m2 using XDA Free mobile app
ferhung said:
Testing the new methods of sepolicy, which is from the MTK's MM.
Sent from my m2 using XDA Free mobile app
Click to expand...
Click to collapse
Good luck, hope it will work.
@hyperion70 Cm13.0 is working in my mt6592 device by getting the right vendor.
Sent from my m2 using XDA Free mobile app
ferhung said:
@hyperion70 Cm13.0 is working in my mt6592 device by getting the right vendor.
Sent from my m2 using XDA Free mobile app
Click to expand...
Click to collapse
Now I update revision r13 ==> r17 and made repo syncing.
However, I get a compile error:
Code:
Notice file: frameworks/base/packages/WAPPushManager/NOTICE -- /home/lex/cm-13_Fly/out/target/product/IQ4511/obj/NOTICE_FILES/src//system/app/WAPPushManager/WAPPushManager.apk.txt
/bin/bash: mvn: command not found
make: *** [/home/lex/cm-13_Fly/out/target/common/obj/JAVA_LIBRARIES/ambientsdk_intermediates/com.cyngn.ambient.ambientsdk-1.4.0.aar] Error 127
hyperion70 said:
Now I update revision r13 ==> r17 and made repo syncing.
However, I get a compile error:
Code:
Notice file: frameworks/base/packages/WAPPushManager/NOTICE -- /home/lex/cm-13_Fly/out/target/product/IQ4511/obj/NOTICE_FILES/src//system/app/WAPPushManager/WAPPushManager.apk.txt
/bin/bash: mvn: command not found
make: *** [/home/lex/cm-13_Fly/out/target/common/obj/JAVA_LIBRARIES/ambientsdk_intermediates/com.cyngn.ambient.ambientsdk-1.4.0.aar] Error 127
Click to expand...
Click to collapse
I update all source, now. You can sync again.
Sent from my m2 using XDA Free mobile app
ferhung said:
I update all source, now. You can sync again.
Click to expand...
Click to collapse
Unfortunately.
Last log https://gist.github.com/hyperion70/af952ca0e17c1cbf6e1a
Edit:
Package <maven> hasn't been installed. Many thanks @zander42.
hyperion70 said:
Unfortunately.
Last log https://gist.github.com/hyperion70/af952ca0e17c1cbf6e1a
Click to expand...
Click to collapse
did u repo init again? Don't repo sync directly. Repo init again, then repo sync.
If you still have problems, you can merge upstream by yourself.
Sent from my m2 using XDA Free mobile app
Hi OP.
I booted the CM-13 on my mt6592 device Fly Tornado One (Xolo x8-1000, Infinix Zero X506).
Thanks again for your work.
Source Code: https://github.com/hyperion70/android_device_fly_IQ4511
hyperion70 said:
Hi OP.
I booted the CM-13 on my mt6592 device Fly Tornado One (Xolo x8-1000, Infinix Zero X506).
Today, I will upload my device and vendor on github.
Thanks again for your work.
Click to expand...
Click to collapse
You are welcome.
Sent from my m2 using XDA Free mobile app
hyperion70 said:
Hi OP.
I booted the CM-13 on my mt6592 device Fly Tornado One (Xolo x8-1000, Infinix Zero X506).
Thanks again for your work.
Source Code: https://github.com/hyperion70/android_device_fly_IQ4511
Click to expand...
Click to collapse
Fix WIFI now.
https://github.com/ferhung-mtk/android_device_Xiaomi_HM2014011/commit/1a670ac5a2897ebfe8d80365d8991a5c35e878f6
Sent from my m2 using XDA Free mobile app
hyperion70 said:
Unfortunately.
Last log https://gist.github.com/hyperion70/af952ca0e17c1cbf6e1a
Edit:
Package hasn't been installed. Many thanks @zander42.
Click to expand...
Click to collapse
Yes. The lastest source should build with maven.
I forgot to tell u.
Now, we can open wlan. But I should have more time to get WIFI's data working.
Edit: If u test the wlan by this method and it's working, tell me more about the WIFI data connecting bug. In my country, the WIFI data is not working.
Sent from my m2 using XDA Free mobile app
ferhung said:
Edit: If u test the wlan by this method and it's working, tell me more about the WIFI data connecting bug. In my country, the WIFI data is not working.
Click to expand...
Click to collapse
Yes, I checked it.
WiFi data connection isn't work.
Last logcat: https://gist.github.com/hyperion70/d0282031e063fbbd3e5c
The problem is in the /data/misc/wifi. Now I don't have more ideas.
Pablito2020 said:
Can you share the rom?
Click to expand...
Click to collapse
cm-13.0-20160314-UNOFFICIAL-IQ4511
hyperion70 said:
Yes, I checked it.
WiFi data connection isn't work.
Last logcat: https://gist.github.com/hyperion70/d0282031e063fbbd3e5c
The problem is in the /data/misc/wifi. Now I don't have more ideas.
Click to expand...
Click to collapse
OK, I will fix it until i have enough time.
Sent from my m2 using XDA Free mobile app
ferhung said:
OK, I will fix it until i have enough time.
Sent from my m2 using XDA Free mobile app
Click to expand...
Click to collapse
If it's the same problem which I had I can provide a fix. I made a nearly fully working cm13 for mt6592 and the kk 3.4 kernel last year. I will check it when I'm at home...
fire855 said:
If it's the same problem which I had I can provide a fix. I made a nearly fully working cm13 for mt6592 and the kk 3.4 kernel last year. I will check it when I'm at home...
Click to expand...
Click to collapse
It's very kind of u to provide it.
Welcome back.
Sent from my m2 using XDA Free mobile app