Related
Hey Guys,
I've noticed many other phones have guides explaining how to download and compile Android for their phones including proprietary drivers and misc files. I know CM6/CM7 and MIUI all are very clearly doing this but I was wondering if we could get any kind of documentation like that for the Epic? It doesn't have to include any super detailed coding information other then how to download AOSP, Samsungs required drivers, and build them into a "working" rom of some kind..
The drivers and kernels you guys have been using so far must be available via some kind of git command..
I'd love to be able to compile a ROM just to learn about it lol.
Think a quick and dirty write up for compiling a rom could happen? I think it would really help incoming developers and newbies alike.
+1 on this.
+1 as I would like a good starting point...
Samsung Epic using Team Viper's latest ROM and kernel
I'm glad to see some support for this. I sincerely hope a developer takes this seriously enough to help us out!
I'm answering my own question here
Check it out... it's how to build CM for the epic. Anyone interested in learning the process could probably follow this guide and accomplish it. Took it from the CM post in General.
http://cmsgs.com/mediawiki/index.php?title=Build_CyanogenMod_for_Samsung_Epic
Thank you! That is very interesting. I must try it!
Sent from my Shoe.... I mean my Samsung Epic
mxcoldhit said:
Thank you! That is very interesting. I must try it!
Sent from my Shoe.... I mean my Samsung Epic
Click to expand...
Click to collapse
I'm trying it now for fun... still downloading the source... the first repo sync takes a while, I believe it's a few GB's in size..
I don't believe this includes the kernel though... I'm sure it's posted somewhere for those interested in looking at it.. just gotta dig around.
TheDub said:
I'm trying it now for fun... still downloading the source... the first repo sync takes a while, I believe it's a few GB's in size..
I don't believe this includes the kernel though... I'm sure it's posted somewhere for those interested in looking at it.. just gotta dig around.
Click to expand...
Click to collapse
way to go, man. keep us posted...
yogi2010 said:
way to go, man. keep us posted...
Click to expand...
Click to collapse
Steps seem to be broken.. the ./get-rommanager and ./getgooglefiles -v HDPI or whatever both don't work because of broken web links.
Seems this hasn't been updated in a while..
I tried to go on without them following the directions but it doesn't work, says something about the vibrant? idk.. I think the directions would need updating to work properly.. at least the code was fun to look at.
Still hoping a developer can teach us how to compile lets say just 100% AOSP for our phones using our progress so far with the drivers.. i think the drivers need to be their own branch of code so all devs can use them for their own roms.. maybe it's already like this? Idk pretty new to rom compiling.
This is now obsolete, Erasmux has ported the hardware (some of it) which i am havign trouble doing.I dont intend to steal his work so please use his!
http://forum.xda-developers.com/showthread.php?t=1026699
To revert MTD and flash back please see HERE
Issues and Changelog
Changelog..
First version..
Issues..
WIFI
MICROPHONE
CAMERA
NETWORK DATA - A little fishy
ROTATE - Think ive fixed in next version
MARKET - Loops Crashing?
BROWSER - Loops Crashing?
Well no bug or something, but I've added the rom on my mirror . here
Good luck with this. It's great to see that there are still some people who believe in a 2.2 sense rom for the hero
when the rom is tested a bit i will add it to my rom database
dude, you built a rom! congrats on being so bleeding edge bonesy!
I'm impressed with your guts
um, don't take this the wrong way, but I'm not about to try it just yet... ;-) It's just because I need my phone and it's camera etc for daily use. I have faith in you - you've been messing with this stuff longer than I have probably dude and your flashing instructions are VERY clear which is comforting.
I'm really impressed that you persevered like this though man!
cheers
Don
Like I said gonna give it a try when at work. Great work man. And ill report back in here all my findings.
Like don said. Great to see this still happening to the hero.
Sent from my HTC Hero using Tapatalk
What is working? What not?
krygo said:
What is working? What not?
Click to expand...
Click to collapse
see 2nd post,Lots working but lots not,was up untill 4am trying to fix some,as soon as i get mic and / or wifi going ill release 0.2
hi there!
I'm a bit puzzled how to revert to pre-MTD changes state.
I am willing to test this rom, but I would like to have an option to nandroid back without much of a problem. I read through the topic bonesy linked, but haven't found a simple answer/solution.
I hope I could help some more, at least confirm bugs or something.
Cheers!
brat.haneq
EDIT:
Is it as simple, as flashing "remove" zip?
Nearly, you will need to re-flash recovery too, Through fastboot..
Im struggling at the moment as i have 2 different builds on 2 different computers.As soon as i can get to my work computer i can carry on with it all
Call me stupid but is CustomMTD really necessary ? This rom can't work as all roms do? I've flashed it without MTD method and I am stuck on first splash-screen (mine says HERO on black background).
BTW ty for working on a Froyo Sense port for Hero GSM
omg Ninpo is involved, <3 him (nogay)
I will try when it's a little bit better ^^ and can be used for 1 day at school
good work man!
Wupper said:
Well no bug or something, but I've added the rom on my mirror . here
Click to expand...
Click to collapse
offtopic:
omg you again XD hahahaha
I will not flash this yet but still I want to say thanks to all devs for working on froyo sense
@bonesy. how are you hoping the development of this ROM will be community driven? Would you like us to simply try it and report bugs (no different to most other ROMS I think) or would you like us to get down and dirty with code wherever possible?
Im just a regular user but i'd like to help with the development of this rom. if i was pointed in the right direction I would even be willing to learn about how to develop this rom!
anyway good effort for starting on this (I expect, long) journey
f_padia said:
@bonesy. how are you hoping the development of this ROM will be community driven? Would you like us to simply try it and report bugs (no different to most other ROMS I think) or would you like us to get down and dirty with code wherever possible?
Im just a regular user but i'd like to help with the development of this rom. if i was pointed in the right direction I would even be willing to learn about how to develop this rom!
anyway good effort for starting on this (I expect, long) journey
Click to expand...
Click to collapse
Im hoping all devs will see that there are still people wanting Sense on their hero's,FroYo sense stopped as soon as GB was booting up on the hero and now it seems to be forgotten.Ideally id like to learn how to do ll the porting but theres not much in the way of advice out there..
Is custom MTD really necessary?
Click to expand...
Click to collapse
In a word..Yes (its over 200mb in size just on /system partition) hopeing eventually it wont need it
bonesy said:
Im hoping all devs will see that there are still people wanting Sense on their hero's,FroYo sense stopped as soon as GB was booting up on the hero and now it seems to be forgotten.Ideally id like to learn how to do ll the porting but theres not much in the way of advice out there..
Click to expand...
Click to collapse
I couldnt agree more! well if you do find anything useful I will help anyway I can
bonesy said:
Im hoping all devs will see that there are still people wanting Sense on their hero's,FroYo sense stopped as soon as GB was booting up on the hero and now it seems to be forgotten.Ideally id like to learn how to do ll the porting but theres not much in the way of advice out there..
In a word..Yes (its over 200mb in size just on /system partition) hopeing eventually it wont need it
Click to expand...
Click to collapse
Well took a quick look at this. Will try to devout some more time over the next few days and see if it'll get me anywhere.
What I got for now is:
a) There is quite a lot of "junk" on the system partition here, after a short cleanup it fits very nicely without the MTD patch .
b) libwebcore.so fixes the browser crashes and most likely the markets too.
If I have time tomorrow I'll try to give the microphone a shot, cause this is the most critical problem at this point - whats the point of having a telephone you even talk to...
Hopefully I'll also release something for testing tomorrow...
Thanks Erasmux, i would have gtalked you today but been at work and the boss was in...so no devvin on the work pc lol.Got market and browser fixed as you say and also rotate and i think light sensor.I removed nabservice.apk as it only FC'd.Would be great if we can arrange a time over the W/end to talk
Opened a new thread for "my" version of this port:
http://forum.xda-developers.com/showthread.php?t=1026699
Please note, that the amount of effort I will be able on such a (closed source) ROM is limited. I mainly what to see how far I can get this, especially in terms of hardware support, with my past experience.
So its up to you if you want to continue to keep your version going in parallel. If you do (or anyone else), please feel free to reuse anything from "my" ROM....
HELLO EVERY BODY I was just wondering if it is possible to do a port of benjamingwynn's super awsome .sense rom to the mytouch 3g slide?
It's just a really great rom that might just bring the mt3gs back for one last time.
Just don't want to give up on this phone, I love it to much.
well, i might, but, im more focused on getting WiFi to work in ANY sense 3.5 rom
Well that is important and I thank you for working on it! I
I just wanted to know so I can give porting a rom a try. Want to contribute something instead of just using.
Oh by the love your roms
Sent from my SGH-I897
can anyone give me any suggestions to get me in the right direction so I can learn how to port roms
mon5trum said:
can anyone give me any suggestions to get me in the right direction so I can learn how to port roms
Click to expand...
Click to collapse
well, start by setting up either a linux partition, or install cygwin (you need the custom one in the dsixda kitchen thread) and setting up your kitchen, but for the most par, just make sure you are trying to port a non-sense rom with a sense base, or vise-versa
Also, always replace /system/usr and /system/bin/akmd
but you will figure out what else on your own
Whoareyou said:
well, start by setting up either a linux partition, or install cygwin (you need the custom one in the dsixda kitchen thread) and setting up your kitchen, but for the most par, just make sure you are trying to port a non-sense rom with a sense base, or vise-versa
Also, always replace /system/usr and /system/bin/akmd
but you will figure out what else on your own
Click to expand...
Click to collapse
Thank you very much for taking some time to help out a total NOOB!
Whoareyou you are great!
Sent from my Wildfire S
Dont know if this will help or not. You may or may not be aware of it. I checked out the thread a little, http://forum.xda-developers.com/showthread.php?t=1445517 and development has been suspended. Apparently there were some problems with wifi and cell service on the latest version 3.0 from the little bit I read there. I did notice a few people saying that v2.0.1 was working pretty good for them though.
It also appears that they had it working for the Legend in v2.0.1 so that could be the easiest port if you do decide to tackle it. (The Legend is nearly identical to our Espresso if I am remembering correctly)
v3.0 was available for the Wildfire and the Salsa, and since we have a working port of Salsa, that may help as well (for either the 3.0 or 2.0.1).
Sorry I can't be much more help than this right now. Hopefully this can help give you some ideas.
Note: the download links do not work at all, but i did find them all here.
http://goo.im/devs/benjamingwynn/dotsense/
Good Luck to you!
DocHoliday77 said:
Dont know if this will help or not. You may or may not be aware of it. I checked out the thread a little, http://forum.xda-developers.com/showthread.php?t=1445517 and development has been suspended. Apparently there were some problems with wifi and cell service on the latest version 3.0 from the little bit I read there. I did notice a few people saying that v2.0.1 was working pretty good for them though.
It also appears that they had it working for the Legend in v2.0.1 so that could be the easiest port if you do decide to tackle it. (The Legend is nearly identical to our Espresso if I am remembering correctly)
v3.0 was available for the Wildfire and the Salsa, and since we have a working port of Salsa, that may help as well (for either the 3.0 or 2.0.1).
Sorry I can't be much more help than this right now. Hopefully this can help give you some ideas.
Note: the download links do not work at all, but i did find them all here.
http://goo.im/devs/benjamingwynn/dotsense/
Good Luck to you!
Click to expand...
Click to collapse
Thank you for your support and advice.
That is a very good starting point. Once the weekend gets here I will try to get started.
One more question what are the minimum requirements for a PC, I have 4 gigs of ram two hard drives one with 250 gb the other with 1 tb and a pentium core duo processor I think. (Not sure on the processor, been a while since I looked)
Sent from my Wildfire S
I would say that should be plenty. I have not yet attempted compiling or porting myself but i use a much weaker machine for a lot of my android stuff and it has been pretty good for the mods and such ive been working on. Search google or xda for android development min requirements and you should find some info on recommended specs for what u want to do.
Sent from my Little Engine That Could using XDA App
one more thing I tried to plug my mt3gs to my pc but neither my wife's laptop or my desktop wont recognize my phone neither htc sync or as a mass storage device, as I am going to start my little project on saturday. So just want to know if there is a solution for this? Can someone please help me your help is very very appreciated.
Have u tried a different cable? Does the phone start charging when u plug it into the PC? if u just want to transfer files u can try an app like SwiFTP from the market. I believe there are also ways to run adb over wifi, but ive never looked into it so not totally sure bout that. Did u check to make sure in settings that its not set to Charge Only?
Sent from my Little Engine That Could using XDA App
DocHoliday77 said:
Have u tried a different cable? Does the phone start charging when u plug it into the PC? if u just want to transfer files u can try an app like SwiFTP from the market. I believe there are also ways to run adb over wifi, but ive never looked into it so not totally sure bout that. Did u check to make sure in settings that its not set to Charge Only?
Sent from my Little Engine That Could using XDA App
Click to expand...
Click to collapse
This all started to happen with the original cord that came with the phone but I will try different cords just too see if I can get it to work. And if not I will look in to that adb through wifi thing, but most likely if a different cord works I will still research that whole process. I thank you for your help and advice. :thumbup:
Sent from my all powerful ANDROID phone!!
Hello again everyone, Sorry that I haven't posted any news or anything but my life just got a little crazy and it cut down my free time considerably. I was just wondering if I was to late to start this project and someone else started with it, or am I still good with it...
Thanks for any responses!!!
Sincerely
The mon5trum under your bed
I have, for the most part, returned from my leave of absence and hopefully this time around I will be able to provide you folks with something a bit more useful.
Admittedly, this was a fairly halfhearted attempt but, hey, it's something to start with. I branched the CM7 for Nook Color source. Part of the compilation process involves running a script (system/device/bn/encore/extract-files.sh) that extracts proprietary libraries (or something?) from stock Nook Color, so I plugged in a rooted N2E instead for this step and ripped the files off of it. Some files were missing from the N2E, so I copied those over from a Nook Color. Here's a list of those files:
Code:
/system/lib/libOMX.TI.720P.Decoder.so
/system/lib/libomap_mm_library_jni.so
/system/etc/powervr.ini
/system/lib/libpvrPVR2D_FLIPWSEGL.so
/system/lib/libusc.so
/system/lib/libpvrPVR2D_FRONTWSEGL.so
/system/lib/libOpenVG.so
/system/lib/libOpenVGU.so
/system/lib/liba2dp.so
/system/lib/hw/alsa.omap3.so
/system/usr/share/alsa/init/hda
/system/usr/share/alsa/init/00main
/system/usr/share/alsa/init/help
/system/usr/share/alsa/init/default
/system/usr/share/alsa/init/info
/system/usr/share/alsa/init/test
Compilation of the franken-nook-color source went without problems.
Unfortunately although unsurprisingly, the produced userland doesn't boot. I'll keep y'all updated with my progress; this is only the very tip of the iceberk.
I have two NST so I can use one for testing your rom if you promise no to brick it very often ;-)
I have a NST that, while the 3/4's of the screen is broken, it still functions fine and I can see anything in the top right quadrant of the screen. It doesn't do anything else for me, so you're welcome to brick it in the name of experimentation.
Thanks for the offering! I am not really in need of anything just yet but should anything come up I will PM y'all.
Anyhow, I tried again but this time excluded all the missing prop files from the build by editing them out of device-vendor-blobs.mk. It still didn't work so that means we're probably going to have to find a way to actually debug it instead of using trial and error like we have been.
Maybe there is like, a serial port or something on this thing.
klausef said:
Maybe there is like, a serial port or something on this thing.
Click to expand...
Click to collapse
Yes there is a UART on the OMAP3621.
Still, it's hard to get any info out of TI since it's an OEM part.
Does anybody have a real pinout?
Actually, unless somebody has a dead Nook that you can pull the processor off it would be hard to trace.
I guess the best bet would be to look for suspicious unused pc lands.
Can you toggle the charge light gpio as a progress indicator?
You don't need anything special.
As long as you can boot a kernel, which you can, you can do all your debugging over adb. Just enable adbd in the ramdisk.
The use for a serial console is for debugging KERNEL failures.
The firsts thing you really need to work on instead of just trying to boot CM7, is a compatible NST Kernel. Without a CM7 compatible kernel as far as I know it just won't boot. Once you know the kernel works you should start work on getting /system and such to work, as far as I know the major differences between the Nook Color and the Nook Touch are the input types and display types, which means you'll have to replace the drivers with ones that actually work.
GabrialDestruir said:
The firsts thing you really need to work on instead of just trying to boot CM7, is a compatible NST Kernel. Without a CM7 compatible kernel as far as I know it just won't boot. Once you know the kernel works you should start work on getting /system and such to work, as far as I know the major differences between the Nook Color and the Nook Touch are the input types and display types, which means you'll have to replace the drivers with ones that actually work.
Click to expand...
Click to collapse
Thanks for the direction, I kind of have been seeing that getting this working isn't as trivial as swapping a few files. I've been asking on some Freenode channels about what exactly makes a kernel 'CyanogenMod compatible.' There are clearly people out there who know exactly what facilities and stuff need to be backported, but such people are hard to find. Do you have any idea where this kind of stuff is documented? The CyanogenMod wiki seems a bit sparse, although maybe I haven't been looking in the right places...
If it is of any interest to anyone:
http://tldp.org/HOWTO/Remote-Serial-Console-HOWTO/configure-kernel.html
I've recompiled U-Boot to call our current N2E kernel with a new `console=[...]` parameter, and recompiled the kernel with USB serial support. I figure I should be able to plug this thing into a linux box and just use `minicom` to look at the kernel's output in this manner. I know this probably won't give too much information about userspace issues but at least hopefully it will give some info on why/if/when/where init fails.
It would be nice if a spare UART could be found directly on the board.
http://tldp.org/HOWTO/Remote-Serial-Console-HOWTO/configure-kernel.html said:
The USB subsystem is started rather late in the boot process, console messages printed during boot before the USB subsystem is loaded will be lost.
Click to expand...
Click to collapse
I should be more specific, it's not so much you need to make the current kernel CM7 compatible, as it is you need to make it Android Froyo Compatible, which usually involves porting features from the eclair, if you want to get specifics, try talking with people in #nookcolor or #nook-tablet on Freenode. They may be able to help point you in the right directions for porting the kernel.
Waiting for my NST to come from new continent.
Personally, I would start building original kernel source from b&n. When it works and device boots, then I would clone google repository for kernel 2.6.x and would compare its files with the files from original kernel. And then adding needed source files for booting, and needed device drivers.
I doubt I'll have free time and enough knowledge for that.
Sent from my GT-I9000 using XDA
seeing as we now have the uart http://forum.xda-developers.com/showthread.php?t=1702734 i feel its time to make a cm7 port. it would unlimit the device, and bring it into more compatible apps.
How goes it? Will fundraising speed things up by letting you concentrate more of your time on this project?
imachine said:
How goes it? Will fundraising speed things up by letting you concentrate more of your time on this project?
Click to expand...
Click to collapse
Sorry if you weren't asking me.
I don't write a single line of C code since almost twelve years. I'm a programmer in a very different environment, fact which makes me know that such a port needs a lot of dedication.
In the next weeks I'm gonna be father for the first time and this makes me set completely different goals in my life.
As far as I've understood of cyanogenmod, is that this world is made of brilliant volunteers, some accepting donations, some not. Maybe in the whole cm community, there is somebody with time and experience.
Sent from my GT-I9000 using XDA
I've been considering picking this up as a project, because I'm tired of 2.1, i would like some GB at least I doubt we will see cm9, but cm7 seems doable. I'll have to learn some to do it, but I don't see why it's not outside of reach; now that we have a serial port, and such.
tdcfpp said:
Sorry if you weren't asking me.
Click to expand...
Click to collapse
No problemas, I wasn't. I directed my message at klausef who started this thread, though anyone willing to help out would probably be beneficient from fundraising, were it to start funding a project, instead of a single developer.
If money's a problem, perhaphs starting a kickstarter (or similar) project might help out?
Donating via paypal works as well, but I don't think it's possible to allow public access to account levels in order to motivate the experience of funding, by letting people see how much the project has risen.
i can't wait to get CyanogenMod on my nook! Have you guys discovered anything new?
Cheers!
Soooo, any news? Come on, klausef, we can help! Let us know how the progress is coming along
imachine said:
Soooo, any news? Come on, klausef, we can help! Let us know how the progress is coming along
Click to expand...
Click to collapse
Bump. I've got a great use for a NST / N2E application, and the app is currently compiled for Android 2.2 only. I may not be able to get to the source (and may not be able to make it work in 2.1 even if I did!), so a NST with 2.2 would be ideal!
Okay so there are two multi-boot modifications flowing around XDA for a ton of various devices.. Has anyone ever considered porting one to the robin? lately with all these rock solid Roms it doesn't seem like too bad of an idea and I truly wish I had the experience to do it myself.
https://github.com/chenxiaolong/DualBootPatcher/
and
https://github.com/Tasssadar/multirom
and
https://github.com/efidroid/
Oh hell yes! I'd like to see this!
Desperately waiting for it!
Sounds cool, I can have Omni and XOSP at the same time ;P
https://github.com/efidroid/projectmanagement/wiki/[EFIDroid]-Porting-a-new-device
If you ask me, the lack of the need of the kexec-hardboot patch makes this project superior to multirom
Alexandroid99 said:
https://github.com/efidroid/projectmanagement/wiki/[EFIDroid]-Porting-a-new-device
If you ask me, the lack of the need of the kexec-hardboot patch makes this project superior to multirom
Click to expand...
Click to collapse
I'm taking a look at it and i'm gonna mess around with it and hopefully make an attempt to port it.. Hope all goes well
AnierinB said:
I'm taking a look at it and i'm gonna mess around with it and hopefully make an attempt to port it.. Hope all goes well
Click to expand...
Click to collapse
If you're lucky it's seriously easy, but it can become a very involved process fairly quickly when something doesn't work...
Alexandroid99 said:
If you're lucky it's seriously easy, but it can become a very involved process fairly quickly when something doesn't work...
Click to expand...
Click to collapse
Yeah but unfortunately for me repo is giving me a ton of problems and i've got to get to work. if someone else wants to try this, be my guest.
AnierinB said:
Yeah but unfortunately for me repo is giving me a ton of problems and i've got to get to work. if someone else wants to try this, be my guest.
Click to expand...
Click to collapse
I'm already syncing it. Someone got it to work partially on the Nexus 5X, which is the same arch. So fingers crossed...
Alexandroid99 said:
I'm already syncing it. Someone got it to work partially on the Nexus 5X, which is the same arch. So fingers crossed...
Click to expand...
Click to collapse
Let me know how it goes man :highfive:
Alexandroid99 said:
If you're lucky it's seriously easy, but it can become a very involved process fairly quickly when something doesn't work...
Click to expand...
Click to collapse
No dice. Tried to compile lk using msm8994 (SD810- same workaround as 5x) and was able to fastboot boot a nouefi lk.img but but once booted there was no device showing up in fastboot devices which unfortunately is key to the next step
A lot of Devs are getting into issues assuming that this device is similar to the 5X. No. It isn't. This device's implementation is completely different. Take a look at the two sources and you'll see it. NextBit's calls to device and storage are also different. Boot patches won't work the same way. The OmniROM Dev was the first to learn this which is why it took a lot of time. Also Robin doesn't seem to respond to slot switching though it has it. I may be wrong.
valhallen.282 said:
A lot of Devs are getting into issues assuming that this device is similar to the 5X. No. It isn't. This device's implementation is completely different. Take a look at the two sources and you'll see it. NextBit's calls to device and storage are also different. Boot patches won't work the same way. The OmniROM Dev was the first to learn this which is why it took a lot of time. Also Robin doesn't seem to respond to slot switching though it has it. I may be wrong.
Click to expand...
Click to collapse
I got lk to boot using the same lk_base as the 5x so there are a few thing in common because the aboot dump showed the same value. anyways I made some progress: Display to show, finalize_device to execute and was able to build uefi.img and boot it. upon booting uefi the kernel panics and reboots so I have to to figure that out before proceeding to the checklist.
valhallen.282 said:
A lot of Devs are getting into issues assuming that this device is similar to the 5X. No. It isn't. This device's implementation is completely different. Take a look at the two sources and you'll see it. NextBit's calls to device and storage are also different. Boot patches won't work the same way. The OmniROM Dev was the first to learn this which is why it took a lot of time. Also Robin doesn't seem to respond to slot switching though it has it. I may be wrong.
Click to expand...
Click to collapse
Alexandroid99 said:
If you're lucky it's seriously easy, but it can become a very involved process fairly quickly when something doesn't work...
Click to expand...
Click to collapse
I've got it to boot and run for the most part but I'm not the most experienced at porting and there are a few things left to do like configuring the fstab.multiboot correctly which is key to multi booting roms and installing the ota through efidroid app via github sever
AnierinB said:
So I've got efi-droid ported and working for the most part. I'm not the most experienced at porting and there are a few things left to do like testing multiboot roms and configuring a local ota sever to do so..
I'm making this post so that I can hand off my findings, config.ini, and my lk_inc.make to someone who has more experience/ someone who can get this done and wants to test multiboot and see if it's a go. Think you can do so and become the maintainer for this project?
Click to expand...
Click to collapse
I wish I was smart enough to do that. I can read code. I can test. Cannot write to save my life. Sorry. That's my truth.
valhallen.282 said:
I wish I was smart enough to do that. I can read code. I can test. Cannot write to save my life. Sorry. That's my truth.
Click to expand...
Click to collapse
As soon as I get these local ota server problems figured out and are able to actually test dual booting a rom I'll pm you with some goodies:good:
It's pretty easy to build yourself after you figure out what variables the lk.mk and config.ini need. Although I have been doing this for 3 days now with many trial and error. Pretty shocked it's even working as good as it is right now because there's been a lot of known issues with 64bit socs
delete
I'm gonna have to put this project behind me... I lack some knowledge on a few areas of the porting process and to configure it correctly is possible but I, myself can not do it. If a developer has the device, and wants to try porting/configuring it then go for it. The main thing is that we are able to get lk, uefi to boot and display screen (properly) so fixing the other issues like fstab.multiboot table should be easy for someone more experienced. At least theres hope with this modification. Sorry folks, I'll stick to my boot logos for now haha.
AnierinB said:
@ValHallen can you download the efi manager application off the play store and tell me what device it gives you an error for? then after doing so can you edit your build prop and add this line: efidroid.server_url=https://raw.githubusercontent.com/anierinbliss/efidroid_ota/master
then delete the app, reboot your phone and reinstall it.. Does it still fail?
Click to expand...
Click to collapse
I think you tagged the wrong person. But I'll try. In a short while.
It's probably best to put all thaz work out in the open including github repos and a separate thread so someone who's capable might stumble upon it and pick up qhere you left off.