Related
dell 0000000000000
dell 00000000000
reserve 2 ---
Shweet!!!!! If I knew how to code..I would surely help you!(If you have anything easy to work on..do tell )
I will die for it IceCream!!! the camera speed is so fast..
Using Gingerbread as a base presumably?
Given the amount of "non-standard" hardware in the SGS2, you'll need support libs from either an existing non-AOSP OEM firmware, or from CM7 won't you?
great.. i hope u will port in a bunch of days
it's so great.you can do it!
tongqihua said:
it's so great.you can do it!
Click to expand...
Click to collapse
Lol no he can't. There isn't a FULL system dump of the Galaxy Nexus yet. There is only the dump from the SDK. He will probably theme it like Ice Cream Sandwich. Anyways good luck to the dev
source is the power, says cyanogen. wont this be useless when the sources are released? wont this feel like wasting cuz when sources is released, other devs will easily make those ICS roms, instead of porting it.
well anyway good luck to the dev!
LuffyPSP said:
source is the power, says cyanogen. wont this be useless when the sources are released? wont this feel like wasting cuz when sources is released, other devs will easily make those ICS roms, instead of porting it.
well anyway good luck to the dev!
Click to expand...
Click to collapse
That's not the point. Of course, a dump would be a lot better. But being the first to port and get a working SDK rom... Now that's where the fun is
It is possible, we have the full SDK ROM.
Ask galnet how you import proprietary files with dependencies
Sent from my GT-I9100
I am working on it!
I am very newbie but we can do something
May the force be with you.. And make it fast cause i am getting itchy already hahaha... Goodluck.
Sent from my GT-I9100 using XDA Premium App
Face lockscreen already in SGS2 but not enabled
I can help you!!
hobbit19 said:
hello Friends
I started work porting IceCreamSandwich SDK port on the Samsung Galaxy S II
Details very soon!!
if there are developers willing to help me write a personal message
Click to expand...
Click to collapse
great!!!
10chars
I for one don't see this working as every device seems to be getting the same LibC error at the moment (except for some reason the G2).
The best hope seems to be getting a HC rom to work then using the boot.img from that to boot the ICS sdk port. (this is what we believe happened with the G2 to get it to boot)
I would be satisfied with the new gmail application including widget
Cheers!
Looking to try .Hope you have a great ICS.
Sent from my GT-I9100 using xda premium
Since the xperia x10 mini, galaxy mini and various other ARMV6 ldpi/mdpi devices are all getting MIUI v4 ports, whats the possibility of getting a port to the wildfire. This thread is just to raise awareness of it, and trying to get some developers involved. I may attempt to get a basic port from the galaxy fit or x10 mini working by using the basic tools in the rom kitchen. But thats the best I can do.
xperia x10 mini rom: http://forum.xda-developers.com/showthread.php?t=1511495
Oh god I hope this goes through and we get a working MIUI ROM.
I've been loving how MIUI looks ever since I first saw it
This sounds nice. Hopefully someone might look into it.
Sounds good to me, I was reading a thread about how they ported it for an mdpi device earlier today, it still sounds like a lot of work resizing but I think it can be done eventually.
I just read that the Armv6 version probably won't have themes.
I'm afraid it's unlikely themes will ever work because of the proprietary binary which MIUI uses to apply themes. It compiled for arm7 only.
Click to expand...
Click to collapse
http://miuiandroid.com/community/threads/miui-armv6.15487/
EDIT: MIUI is probably closer than we think!
http://forum.xda-developers.com/showthread.php?t=1499411
Actually, the guide is for hdpi only
Some guy got it working in mdpi, but with resizing.
nejc121 said:
I just read that the Armv6 version probably won't have themes.
http://miuiandroid.com/community/threads/miui-armv6.15487/
EDIT: MIUI is probably closer than we think!
http://forum.xda-developers.com/showthread.php?t=1499411
Click to expand...
Click to collapse
If you're going to use that tutorial, use the X10 Mini/Mini Pro version of MIUI most MIUI apps are resized to QVGA. We may have the possiblity of having themes in the future, since more apps are going to be opensourced. Anyway, thanks for providing the link to the tutorial. I'll try it out later.
UPDATE: Turns out its perfectly possible to port between two LDPI devices, I'll get a copy of Ubuntu setup tonight or tommorow, to start editing and compiling. I'll post any updates here.
What about getting help from the Galaxy Mini version?
It has a 3.14" 240x320 display (really close to ours)
http://forum.xda-developers.com/showthread.php?t=1516340
Please let someone take a look at it.
I guess it's a lot of resizing and the like, but I bet we can have it on our htc wildfire
nejc121 said:
What about getting help from the Galaxy Mini version?
It has a 3.14" 240x320 display (really close to ours)
http://forum.xda-developers.com/showthread.php?t=1516340
Click to expand...
Click to collapse
I'll PM the creators of both the X10 Mini and Galaxy Mini rom in a bit. If anyone can, try the tutorial that nejc121 posted. I've had trouble getting the final zip to flash. But maybe I'm doing something wrong..
UPDATE: Think I figured out the issues with my zip. Recompiling and testing in a minuite.
UPDATE II: Didn't work, can someone else try out the tutorial and see what kind of end results they get?
UPDATE III: Final update of tonight. Returned the update-script back to default ICS. leaving out the offending code from the MIUI tutorial.
Justice™ said:
I'll PM the creators of both the X10 Mini and Galaxy Mini rom in a bit. If anyone can, try the tutorial that nejc121 posted. I've had trouble getting the final zip to flash. But maybe I'm doing something wrong..
UPDATE: Think I figured out the issues with my zip. Recompiling and testing in a minuite.
UPDATE II: Didn't work, can someone else try out the tutorial and see what kind of end results they get?
UPDATE III: Final update of tonight. Returned the update-script back to default ICS. leaving out the offending code from the MIUI tutorial.
Click to expand...
Click to collapse
Yeah gave it a shot... guess you'll be happy to know that it boots, yeah?
Screenshots soon!
VigiDroid said:
Yeah gave it a shot... guess you'll be happy to know that it boots, yeah?
Screenshots soon!
Click to expand...
Click to collapse
Thats brilliant news Vigi! Its great to see a dev pick this up!
if we can get this ported well, what would the benifits be over the arco kang cm9?
heavy_metal_man said:
if we can get this ported well, what would the benifits be over the arco kang cm9?
Click to expand...
Click to collapse
Check out the thread in the development section, Its a completely new UI/UX!
MIUI v4 for wildfire: http://forum.xda-developers.com/showthread.php?t=1517856
What about porting from a wildfire s miui? i donno if our device and that one are similar, but porting from a fully functional Rom is pretty easier than a ics Rom. They still have big problems with calls and other things... so I'll today begin, if possible the porting.
Sent from my HTC Wildfire using XDA App
In contrast to what most people think, the Wildfire and the S version are similar only in looks and name.
The S has a better screen resolution, processor and a GPU.
Sent from my Ainol Novo7 Elf using xda premium
nejc121 said:
In contrast to what most people think, the Wildfire and the S version are similar only in looks and name.
The S has a better screen resolution, processor and a GPU.
Sent from my Ainol Novo7 Elf using xda premium
Click to expand...
Click to collapse
ok... but basically my idea is to port a fuly-working rom to the wildy, instead of a cm-dependant one. If a cm7 based miui exists and it's compatible with wildfire, that would be great, it won't be as cool as ICS but it would be a starting point even for other developers, who can still work with android 2.x if they want to;
that's something i'll try to do, i definetly want miui on wildfire, not necessarly ICS miui.
working
yupi
We have rom, where phone does not work/
togno said:
ok... but basically my idea is to port a fuly-working rom to the wildy, instead of a cm-dependant one. If a cm7 based miui exists and it's compatible with wildfire, that would be great, it won't be as cool as ICS but it would be a starting point even for other developers, who can still work with android 2.x if they want to;
that's something i'll try to do, i definetly want miui on wildfire, not necessarly ICS miui.
Click to expand...
Click to collapse
Gingerbread MIUI source is out there. I just haven't seen it compiled it for any armv6 phones. The WFS miui is just a theme and custom launcher and apps. Not true miui.
Sent from my HTC Wildfire using XDA App
Ok, so it's not like this that I have 23 hours of free time each day, and it's not that any and every suggestion that pops up on this thread will be looked into, but I just wanted to ask you guys...
What new do you want on the X10?
I'll update the list below as and when people keep submitting their requests/suggestions
Of course please refrain from posting things like
"I want Windows 8 to run on my X10"
I want some suggestions that are at least 'plausible' if not 'possible'
-------------------------------------
1. Get camera working on ICS/CM9/AOKP
2. Dual boot gb and ics
3. CM7 kernel based on latest FXP125 sources with more features
4. CM7 and CM9 kernels for locked bootloaders
5. Xperia S ics rom port
6. JellyBean for X10 (in distant future, so not thinking of it right now)
-------------------------------------
I wanna ask you if you can build a kernel based on fxp125 cm7 kernel with additional governors, oc etc. Just like your previous one but based on updated by fxp 125 one. Thanks
Sent from my X10i using xda app-developers app
Not asking for me but build cm7/cm9 based kernel for locked bootloader ( I am already unlocked lol). I dont know if its possible
I know that it will be an impossible work....but :
porting Jelly Bean for x10i..... Obviously the hardware features of the x10 are those....so you may try to bring the technical prescriptions of design or setting
thxxx
Focus on ICS ..
I think we have enough GB based roms..
It's jealy bean time beach!!!
Send from beneath my cloak of magic
I think your suggestions of a working camera and locked bootloader kernals would be great
1. Get camera working on ICS/CM9/AOKP
Dual booting ics along with gingerbread.. make gingerbread kernel default and we can boot ics by killing it.. something like that!!!
Sent from my SO-01C using xda app-developers app
For me its fantastic if anyone port Xperia s ics to our x10
varshil said:
Dual booting ics along with gingerbread.. make gingerbread kernel default and we can boot ics by killing it.. something like that!!!
Sent from my SO-01C using xda app-developers app
Click to expand...
Click to collapse
I believe making ICS kernel default would be better and getting the camera to work on ICS/CM9/AOKP.
Lord give us a team KTG 3.x kernel for ics. Whoops, wrong thread... jk. I would love it if you assisted tsuyou kou and the KTG team with their kernel development, as i believe the last commit to the 2.6.32.9 kernel was 1 month ago. Not bashing their work or asking for etas. Just hoping they can get more devs (assuming they want help of course...)
Cheers
Deveron3
Sent from my X10i using xda app-developers app
seeing that cyanogenmod has released their official CM 9 for around 40 devices, would it possible to make a port of that to the x10? I might sound like an idiot, but that seems easier than building an entire ROM from scratch...
inadequate said:
seeing that cyanogenmod has released their official CM 9 for around 40 devices, would it possible to make a port of that to the x10? I might sound like an idiot, but that seems easier than building an entire ROM from scratch...
Click to expand...
Click to collapse
it's a good idea
another suggestion:
.Starting from this ... to improve / redo it rom (http://forum.xda-developers.com/showthread.php?t=1731453)
xperia S ICS on x10
Xperia s ics
Vasishta Reddy said:
Hey Championswimmer if you want to bring the goodness of official ICS to x10 PM me, I will give you the partially working XPERIA ARC S ICS rom with XPERIA S ICS addons.
Click to expand...
Click to collapse
that will b awesome if all xperia S ICS goodies work on x10..
FPS unlock and camera on ICS would be awesome ! Just improve your AOKP and your kernels Champ, it's already really great ...
It's kinda off topic and useless, but I sent Sony Mobile an email about
camera sources (jni/wrapper).
You guys did a much better and well written topic, but maybe we can get something.
Just to ask, is buying/donating for Sony a possibility? In last case, would it be legally plausible, expensive?
Sent from my X10i using xda app-developers app
if u could get some jelly bean apps working on x10 would be nice. the new keyboard and galary maybe.. oh xperia keyboard if u cant get jelly bean working with CM 7.2
I recently heard that FXP will stop developing for the whole Xperia 2011 series, when just around the corner, Android 4.2 was standing with a bag of goodies, for which FXP has a valid reason, that these devices lack ram to support features of 4.2. I decided to build 4.2 from source for 2011 devices, for those who'd want to try out the latest version of android. I can handle compiling ROM. But need some help with kernel. if you can help out, or if you wanna be a part of the project. Leave a comment at this thread or PM me. After public release, Dev's can submit their patches / fixes for the ROM to that thread....
I do this because i don't want us to be stuck with stock based ROMs forever and because 4.2 looks awesome . All in all, Thankyou FXP for your work.
one thing that our xperia 2011 devices (especially neo/v ) lack is kernel developers ,we dont have linux 3.0 kernel which which would have made the user experience of JB 4.1 or 4.2 better , linux 3.0 supports many advanced features of JB ,but due to lack of these kernels our user experience will be incomplete , building & testing out these kernels will take hell of time and patience.
i hope this doesn't disappoint's any user or dev just a suggestion
linux 3.0 kernels would be awesome on our phones
i wish you all the best for taking such a great project
vimjam said:
one thing that our xperia 2011 devices (especially neo/v ) lack is kernel developers ,we dont have linux 3.0 kernel which which would have made the user experience of JB 4.1 or 4.2 better , linux 3.0 supports many advanced features of JB ,but due to lack of these kernels our user experience will be incomplete , building & testing out these kernels will take hell of time and patience.
i hope this doesn't disappoint's any user or dev just a suggestion
linux 3.0 kernels would be awesome on our phones
i wish you all the best for taking such a great project
Click to expand...
Click to collapse
look here https://github.com/ExPeacer/CAF_android-msm-3.0/commits/master
progres stoped for 1 Month dont know what is problem , can you resume it ?
---------- Post added at 01:52 PM ---------- Previous post was at 01:46 PM ----------
emwno said:
I recently heard that FXP will stop developing for the whole Xperia 2011 series, when just around the corner, Android 4.2 was standing with a bag of goodies. I decided to build 4.2 from source for 2011 devices. I can handle compiling ROM. But need some help with kernel. if you can help out, or if you wanna be a part of the project. Leave a comment at this thread or PM me. After public release, Dev's can submit their patches / fixes for the ROM to that thread....
I do this because i don't want us to be stuck with stock based ROMs forever.
Click to expand...
Click to collapse
officaly thay will stop at january 2013
Guys atleast try to make the linux kernel
I can be the tester of any Rom/kernel
If you want!
Sent from my LT18i using xda app-developers app
XtremeSilencer said:
Guys atleast try to make the linux kernel
I can be the tester of any Rom/kernel
If you want!
Sent from my LT18i using xda app-developers app
Click to expand...
Click to collapse
all andoid kernel are linux (andoid is based on linux )
I want to participate in, I am not a dev but I can test all ROM fast and give ideas
n1kolaa said:
all andoid kernel are linux (andoid is based on linux )
Click to expand...
Click to collapse
I meant linux 3.0
Sent from my LT18i using xda app-developers app
I don't really need any testers if that's what your saying. I need people who can work, who can help me out.
emwno said:
I don't really need any testers if that's what your saying. I need people who can work, who can help me out.
Click to expand...
Click to collapse
then pm peaple like jader maxio fxp zackconsole pandemic ... i hope you accomplish this project!!
XtremeSilencer said:
then pm peaple like jader maxio fxp zackconsole pandemic ... i hope you accomplish this project!!
Click to expand...
Click to collapse
1. I'm not forcing any one to work on this
2. Jader, Maxio, pandemic are all greats devs but they build themes / stock, and I need help with kernel building
3. I was planning to ask FXP for some sources
4. Zack already has his hands full, look at his work.
+1
+1
emwno said:
1. I'm not forcing any one to work on this
2. Jader, Maxio, pandemic are all greats devs but they build themes / stock, and I need help with kernel building
3. I was planning to ask FXP for some sources
4. Zack already has his hands full, look at his work.
Click to expand...
Click to collapse
Hey. Why cant u ask nobodyatall. Aka naa. He has brought minicm10 to 2010 xperia Minis. Which is more stable than our cm10. I can help you with patches once you start compiling Rom. Cheers.
Sent from my MK16i using xda app-developers app
+1
+1
Sent from my Xperia Arc S using xda app-developers app
yeah the +1 counter thread
I would like to help, though I'm not of that much use YET.
Right now I'm mainly into developing apps, currently learning myself the basics of Kernel Development, I'm also capable of compiling Android.
Going to mess around a bit today, haven't compiled Android for my Xperia Pro yet.
Dympy.
Ok so.. Half way through compiling it failed, because of low storage or something. I read up online and found out that I need atleast 30gigs for compiling, where as I only have around 15-20 free on my laptop, lol unlucky I guess.. So project delayed - until I get more storage for my pc or if someone compiles for me if I give them the sources (if want 4.2 faster). And as for the kernel, instead of building a kernel (which may take long). I'll be modifying the current JB kernel for 4.2
~emwno
emwno said:
Ok so.. Half way through compiling it failed, because of low storage or something. I read up online and found out that I need atleast 30gigs for compiling, where as I only have around 15-20 free on my laptop, lol unlucky I guess.. So project delayed - until I get more storage for my pc or if someone compiles for me if I give them the sources (if want 4.2 faster). And as for the kernel, instead of building a kernel (which may take long). I'll be modifying the current JB kernel for 4.2
~emwno
Click to expand...
Click to collapse
I'm almost done with re-setting up my Linux Install, it got wiped when I installed Windows 8 on my laptop..
Anyway, I have about 800GB of storage left, if you sent me a PM with some directions and such, I'll try to compile when the install is done.
Dympy.
emwno first dev to go for 4.2
you rock
+1 pleease
Guys,
Naturally, as the title states, its a general discussion thread for huashan LBL users. I want to discuss some things with like-minded people and hopefully once the momentum builds, we can try to achieve something.
Android L official release is just around the corner and our official fate is sealed by Sony @ 4.3.
But i plan on trying to port L using existing 4.3 kernel and make it at least boot so we know later on its a possibility for Locked Bootloader to have Android L.
Unlocked Bootloader guys are advised to stay away, as sooner or later, they will get proper AOSP 5.0.
Some points i want to make important.
1. This is NOT a cheer thread. Dont just post to show your excitement. It blocks the purpose of healthy discussion.
2. This is not for people who want new android. Have some sense, it isnt going to come anytime soon.
3. This is strictly for Locked Bootloader guys. So any other person coming and commenting might just be wasting his time.
Although, if you really have some positive thing to contribute, than whatever you have, LBL or UBL, please do share with all.
This is a good starting place to study.
https://github.com/Android-L-Porting-Team/Android-L-Mako/commits/master?page=3
Lets begin !
Im not sure how much id be able to contribute but ill be willing to help any way I can do. Do we even have a vague idea of what kernel modules would be needed for L? Im assuming thats what we'd need as I remember Bagyusz saying thats what he had to do for KK.
Has any of the freexperia team looked at L yet to your knowledge? Perhaps they may be able to give some small insight into drivers etc for LBL/UBL.
Will PA still be updated while this is being looked at? I'm assuming PAC wont need anything now unless problems occur as its all automated. Until L is working PA is a good thing for those wanting L due to them implementing features from L in KK such as recents and tinted bars (if they ever release them to legacy!!).
Oblox said:
Im not sure how much id be able to contribute but ill be willing to help any way I can do. Do we even have a vague idea of what kernel modules would be needed for L? Im assuming thats what we'd need as I remember Bagyusz saying thats what he had to do for KK.
Has any of the freexperia team looked at L yet to your knowledge? Perhaps they may be able to give some small insight into drivers etc for LBL/UBL.
Will PA still be updated while this is being looked at? I'm assuming PAC wont need anything now unless problems occur as its all automated. Until L is working PA is a good thing for those wanting L due to them implementing features from L in KK such as recents and tinted bars (if they ever release them to legacy!!).
Click to expand...
Click to collapse
Dont worry so much. PA is at a stage that if u have linux, u can just compile it right away and all is on Auto.
I will release milestone builds... No point pushing weekly updates if there arent any major changes.
For PAC, i have even taken that burden off and compiling and uploading is not my headache now.
And apart from above, i dont use PA personally. PAC suits me best.
As you stated the main concern is how well "the sealed by Sony @ 4.3. bootloader" will be able to cope with android L?
I really appreciate your enthusiasm. And yes there is only one way to find out. And that is to actually try porting it.
mmfh said:
As you stated the main concern is how well "the sealed by Sony @ 4.3. bootloader" will be able to cope with android L?
I really appreciate your enthusiasm. And yes there is only one way to find out. And that is to actually try porting it.
Click to expand...
Click to collapse
Porting is not an issue. We need a team. Not a band, but maybe 3 people. One compiler, One to tinker with trees and files, One tester. Just my suggestion.
One person cannot do it alone, unless he is an expert dev.
And about coping with L, all current devices having L port are using 4.4 kernel. And our 4.3 copes with 4.4. Technically there are not much issues compatibility wise. Just ramdisk and correct blobs.
I may be wrong, but thats why this discussion is goign on, if someone wants to correct me, please do.
I think this is an interesting project, XDA needs ppl like U
you think is easy port L with 4.3 kernel? I mean I'm just talking w/o reference, but Sony is just (until now) ignoring ART which is the biggest change for L (since 4.4 but well, now is not optional), and I think that could be a barrier to port new android for older phones (like SP)... what do you think about?
I hope this thread came with great news in the near future, :good:
This can be either hard or easy, hell or heaven, depending on the changes in L official release. Up until now, the changes are lying in ramdisk, but some features aren't available in the beta release.
But here are a few things that I noticed right now, before the official release:
1. UBL and LBL are stuck with 4.3 blobs. We are already using patched libraries, I guess it will get worse later, even on UBL.
2. I think we should wait until the CM12(?) will be working on UBL, while helping with bringing it up. If it works on UBL, then we should tinker with the LBL version. Actually, we have the hijack part, and we have the patches needed. I think it will be easy to get it to boot.
3. I think when @delewer finishes his kexec modules, some people that are experienced with kernel development could port it to SP, and then we could use it on forever locked phones. It will take some time, but will be the best for our phones.
So overall, if we have some luck, we would only have to kang CM trees, add the patches for hwcomposer, etc., add hijack and maybe some kernel modules. But we can be extremely unlucky and... I don't even want to imagine the worst case scenario.
Dont worry, the ground work is there. bagyusz gave us a great gift. I am sure Final release wont have boot-related changes. Maybe framework and libs, but not more.
The best thing is, 4.3 SONY rom DID NOT support ART. Bagyusz made it work even on LBL. and as Android L only supports ART, so thats the most important point i think.
Hmm, is ART even kernel-dependent?
I think that's not the case, and it's just great for us. So, bagyusz did a great work(it's just amazing), but I don't think he made any change to support ART.
And yeah, maybe there are just changes in frameworks and libs, but I'm still paranoid about this.
Anyway, I think that we are going to make it. That's what I feel, and I hope it comes true
neXus PRIME said:
Porting is not an issue. We need a team. Not a band, but maybe 3 people. One compiler, One to tinker with trees and files, One tester. Just my suggestion.
One person cannot do it alone, unless he is an expert dev.
And about coping with L, all current devices having L port are using 4.4 kernel. And our 4.3 copes with 4.4. Technically there are not much issues compatibility wise. Just ramdisk and correct blobs.
I may be wrong, but thats why this discussion is goign on, if someone wants to correct me, please do.
Click to expand...
Click to collapse
As I'm far from developer, I'm afraid cannot be of big help to you.
But I'm willing to contribute by testing builds and discovering bugs.
MrSteve555 said:
Hmm, is ART even kernel-dependent?
I think that's not the case, and it's just great for us. So, bagyusz did a great work(it's just amazing), but I don't think he made any change to support ART.
And yeah, maybe there are just changes in frameworks and libs, but I'm still paranoid about this.
Anyway, I think that we are going to make it. That's what I feel, and I hope it comes true
Click to expand...
Click to collapse
Not kernel dependant, i know, but you know what, booting a new android version using old kernel with just hijack n scripts is one HELL of a job.
And ART even didnt work for a long time on AOSP CM for huashan on UBL.
My point was, what we have here is a 4.3 kernel and blobs which might or might not be enough for android L. But before official release, we can try to port L from mako, by replacing blobs and ramdisk and boot, so that we have at least a proof of concept that LBL CAN boot L. Just boot. Nothing else.
neXus PRIME said:
Not kernel dependant, i know, but you know what, booting a new android version using old kernel with just hijack n scripts is one HELL of a job.
And ART even didnt work for a long time on AOSP CM for huashan on UBL.
My point was, what we have here is a 4.3 kernel and blobs which might or might not be enough for android L. But before official release, we can try to port L from mako, by replacing blobs and ramdisk and boot, so that we have at least a proof of concept that LBL CAN boot L. Just boot. Nothing else.
Click to expand...
Click to collapse
"Just" hijack? Bagyusz gave us an excellent base(hijack), and I bet we can boot FFOS or Ubuntu on that.
I didn't even know that ART didn't work on huashan before. Wasn't it a Gapps problem?
And yeah, these maybe aren't enough, as we are already patching some libs.
Ans one thing - I don't think we could port that from mako. It uses a little different base, and it isn't a CAF base. I think we should just wait
MrSteve555 said:
"Just" hijack? Bagyusz gave us an excellent base(hijack), and I bet we can boot FFOS or Ubuntu on that.
I didn't even know that ART didn't work on huashan before. Wasn't it a Gapps problem?
And yeah, these maybe aren't enough, as we are already patching some libs.
Ans one thing - I don't think we could port that from mako. It uses a little different base, and it isn't a CAF base. I think we should just wait
Click to expand...
Click to collapse
Just hijack meant different in a positive sense. But maybe it came out wrong.
And I'm talking about porting. Framework. Not building from source. They are actually doing same thing. I'll have to give it some time though.
neXus PRIME said:
Just hijack meant different in a positive sense. But maybe it came out wrong.
And I'm talking about porting. Framework. Not building from source. They are actually doing same thing. I'll have to give it some time though.
Click to expand...
Click to collapse
Yes, I know what you are trying to say with porting L. Actually, there would be a few things that would break:
1. The YUV color palette support (fixable with our hwcomposer, gralloc etc)
2. GPU drivers - this is the "best" part. L is precompiled, and I think it uses the libRS override, which doesn't work on our huashan because of a kernel difference (if we could build from source, we could just not enable it). There are a few other things that aren't compatible. So even if we got it to boot, it would just show black screen, and I assume by "just booting" you mean actually seeing the effort
3. The whole "thing" is built off AOSP repos, not CAF ones. Idk if SP's stock kernel would play nicely with the whole different stuff.
These are just my assumptions, in the end everything could work just fine. If you have the sufficient time, it's nice to try. Just deleting the mako proprietary stuff, and adding the needed huashan blobs + adding correct ramdisk would get it to the bootable/half working state (or there is a chance that the "build" wouldn't even boot.). I guess it's not done yet for a reason.
Anyway, I have to squash one last bug in my CM builds. If it will work, I could also try porting the magical "L".