Develop Bugs

Light sensor level mod - no dev?

Hello guys, I've made the question, but the Q&A section is not very visited so...
http://forum.xda-developers.com/showthread.php?t=776871
Is there a DEV that can make the light sensor become adjustable in the SENSE UI roms? like on AOSP (i think open desire has it or cyanogen)
http://twitpic.com/2k4qjz

+1 really love to have one

casca said:
Is there a DEV that can make the light sensor become adjustable in the SENSE UI roms? like on AOSP (i think open desire has it or cyanogen)
http://twitpic.com/2k4qjz
Click to expand...
Click to collapse
Which one exactly? I'm willing to take a look at it as the issue annoys me too, if someone points me to the source (but no guarantees that I might have the time or be able to do anything about it).
EDIT: Found the CM source for it.

+1 I would love to see this as well.

martino2k6 said:
Which one exactly? I'm willing to take a look at it as the issue annoys me too, if someone points me to the source (but no guarantees that I might have the time or be able to do anything about it).
EDIT: Found the CM source for it.
Click to expand...
Click to collapse
you were faster than me searching, i was out lunching and haven't saw the topic reply e-mail
if you need assistance on testing, just PM me or let me know at the topic.
It would be nice to have this working, it's so annoying...
Why the f*ck do they include a light sensor if it doesn't work properly?!even after releasing fixes!?lol
Although I think I might know the answer...
"OK, so we gave them the hardware with buggy software to keep them busy...let them(users) figure out a fix, and this way we have time to develop some even nicer phones..."

The main problem here is that since we don't have HTC Sense sources, as they are proprietary, we can't modify system settings with an application which doesn't run as part of the system.
My understanding therefore is that this can be done in two ways:
1) Writing a kernel module which sets the appropriate/specified values on boot (I don't have enough experience to do that) or modifying the default kernel values.
2) Modify values in /sys (wherever they may be hiding) which will be reset any time you reboot, and also may get overwritten by the system at will.
That's my limited understanding anyway. If anyone would like to shed more light on this then please feel free to, or any other ways how this could be achieved...

Moved to Q&A. Please don't post question threads in Development.

fair enough
could we simply start an "official light sensor level developement for sense UI" thread or something like that ?

+1 guys we really neeeed that **** ;p
tks for your work !

Porting Roms from *** To the Evo

I assume this is the correct forum otherwise please move this.
What is the best article(s) to read if you want to start learning how to port roms from other android phones to the Evo? I've been searching on here and on google and it seems most articles are either outdated or only talk about editing existing cooked roms so I finally broke down and posted this. Yes I do use Linux and I do program in Java and .NET and do have a bachelors in software development but I have just never looked into doing this type of work until now.
Thank you, any direction I'm pointed in is appreciated.

I'll direct to you the Q&A forum.

Side Note:This goes in General,but im nice so ill answer you question.
There is no real BOOK to read, a java book is a good start, but you say you know java, so you can probably skip that.
Basically, this is all you have to do.
Download "Dsixda's Kitchen" to your linux distro(amazing software)
Grab a rom from another device.
Grab one of our(evo)stock roms(deodexed Stock 3.70 is good for froyo port,4.12 for gingerbread)
Open the kitchen, and find the option(#19 i think it is), and follow the steps to port it(hold on, your not done yet)
From there you will need do some manual work by tinkering with libs,tinkering with the boot.img, bascally just tinkering with everything related to booting(libs,ramdisk,hw-libs,etc.) untill you can get it to boot or bootloop.
If it boots, thats great, if it bootloops, youlle need to logcat it then debug it.
If you need help with something, pm me, other than that, thats basically(*note: i said basic, more complexed roms like sense 3.0 and non-htc device rom may require extra work)(*note2:alot of times, its going to be a no-booter, but just keep trying.)

sirmx said:
I'll direct to you the Q&A forum.
Click to expand...
Click to collapse
Thanks sirmx, I did do a search there but again came up short.

ThatSmartB0y said:
Side Note:This goes in General,but im nice so ill answer you question.
There is no real BOOK to read, a java book is a good start, but you say you know java, so you can probably skip that.
Basically, this is all you have to do.
Download "Dsixda's Kitchen" to your linux distro(amazing software)
Grab a rom from another device.
Grab one of our(evo)stock roms(deodexed Stock 3.70 is good for froyo port,4.12 for gingerbread)
Open the kitchen, and find the option(#19 i think it is), and follow the steps to port it(hold on, your not done yet)
From there you will need do some manual work by tinkering with libs,tinkering with the boot.img, bascally just tinkering with everything related to booting(libs,ramdisk,hw-libs,etc.) untill you can get it to boot or bootloop.
If it boots, thats great, if it bootloops, youlle need to logcat it then debug it.
If you need help with something, pm me, other than that, thats basically(*note: i said basic, more complexed roms like sense 3.0 and non-htc device rom may require extra work)(*note2:alot of times, its going to be a no-booter, but just keep trying.)
Click to expand...
Click to collapse
Sounds good, what I'll do is go ahead and start one, nothing special maybe even ones that already been done just to get the experience under my best.

ThatSmartB0y said:
Side Note:This goes in General,but im nice so ill answer you question.
There is no real BOOK to read, a java book is a good start, but you say you know java, so you can probably skip that.
Basically, this is all you have to do.
Download "Dsixda's Kitchen" to your linux distro(amazing software)
Grab a rom from another device.
Grab one of our(evo)stock roms(deodexed Stock 3.70 is good for froyo port,4.12 for gingerbread)
Open the kitchen, and find the option(#19 i think it is), and follow the steps to port it(hold on, your not done yet)
From there you will need do some manual work by tinkering with libs,tinkering with the boot.img, bascally just tinkering with everything related to booting(libs,ramdisk,hw-libs,etc.) untill you can get it to boot or bootloop.
If it boots, thats great, if it bootloops, youlle need to logcat it then debug it.
If you need help with something, pm me, other than that, thats basically(*note: i said basic, more complexed roms like sense 3.0 and non-htc device rom may require extra work)(*note2:alot of times, its going to be a no-booter, but just keep trying.)
Click to expand...
Click to collapse
Don't forget some of the most important stuff is in the build.prop and update-script.
Word of advice, look at a sense 2.1 and check out the base that was used. You can also use beyond compare and basically skip Linux all together. Using kitchen to deodex the ruu is a good first step. Choose option 11 in the menu.
Personally, I would start off with a working port and changing apps and moving stuff around. Also get a good list at which libs are associated with what. But use stock bins, etc, xbin, hw libs, and ported apks, framework, and software associated libs. Stock boot.img and a good updater-script. Also know key
Things like the EVO density is 160, vold_stab is usb, amkd is rotation, gsl hw accel stuff like that.
But first things first, Google is ur friend and use the q&a section.
Sent from my PC36100 using Tapatalk

Leoisright said:
Don't forget some of the most important stuff is in the build.prop and update-script.
Word of advice, look at a sense 2.1 and check out the base that was used. You can also use beyond compare and basically skip Linux all together. Using kitchen to deodex the ruu is a good first step. Choose option 11 in the menu.
Personally, I would start off with a working port and changing apps and moving stuff around. Also get a good list at which libs are associated with what. But use stock bins, etc, xbin, hw libs, and ported apks, framework, and software associated libs. Stock boot.img and a good updater-script. Also know key
Things like the EVO density is 160, vold_stab is usb, amkd is rotation, gsl hw accel stuff like that.
But first things first, Google is if friend and use the q&a section.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
ah yes, forgot about build.prop,and i think the kitchen takes care of updater script(unless the device has specific mount pointsor you want text or to clear cache and system). i was just getting the basics to boot, from ther he can debug the errors out of the log.

What about something A LOT simpler like adding the CRT animations to a ROM? any pointers? Any TUT you can point me to?

ThatSmartB0y said:
ah yes, forgot about build.prop,and i think the kitchen takes care of updater script(unless the device has specific mount pointsor you want text or to clear cache and system). i was just getting the basics to boot, from ther he can debug the errors out of the log.
Click to expand...
Click to collapse
Oh I hear ya. Just throwing in my 2 cents. Found that having a clean updater-script is half the battle.
Sent from my PC36100 using Tapatalk

I'm actually glad this thread is still here we don't get to learn much from the devs here. I mean its mostly do it yourself but a getting started guide isn't a bad thing. Mods are quick to move and people are quick to flame but I say leave it, where else is the knowledge pool? Can you really learn this stuff in Q and A seems like it would be mostly help my phone doesn't boot...
Sent from my PC36100 using XDA App

Check out the APKTool, APKManager threads. Lots of great valuable information in there.
I sometimes wish XDA focused more on the "HOW TO" and less on the delivery aspect. The more folks developing, the further we will be along
Another great way to get started is to mentor with another established developer.

evomattnc said:
I'm actually glad this thread is still here we don't get to learn much from the devs here. I mean its mostly do it yourself but a getting started guide isn't a bad thing. Mods are quick to move and people are quick to flame but I say leave it, where else is the knowledge pool? Can you really learn this stuff in Q and A seems like it would be mostly help my phone doesn't boot...
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Well said. People love to flame anyways and XDA is famous among other Android forums for being so harsh. This thread helped me out big time, and it's especially nice to see Leoisright and myn in here giving up a few pointers, because I too was curious about porting. I never worked up the confidence to ask, just too worried about it being passed over or getting flamed because I'm young and curious.
Sent from my PC36100 using XDA App

Yah, Q&A never got me anywhere, i learned off of trial and error, still learning now.
EDIT:OP:IF you want you can ombine mine and leo's tuts together, to make this thread permanent.

Subscribed!!!!!!!!
Good stuff!
Sent from my PC36100 using Tapatalk

Yeah I want to thank the devs that have stopped by so far and gave tips, already using them . Hopefully most of them drop In at least once and leave one tid bit that would make this thread awesome!
Sent from my PC36100 using XDA App

Ha, you taking applications for an apprentice myn?
myn said:
Check out the APKTool, APKManager threads. Lots of great valuable information in there.
I sometimes wish XDA focused more on the "HOW TO" and less on the delivery aspect. The more folks developing, the further we will be along
Another great way to get started is to mentor with another established developer.
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App

Yes I was afraid to post this at first which isn't good, you shouldn't be afraid to ask questions but I get that sometimes the same questions have been answered 100 times prior so I understand the quick to judge portion of it. But I want to thank everyone who has contributed tips, advise and places to start. Thank you.

Leoisright said:
Don't forget some of the most important stuff is in the build.prop and update-script.
Word of advice, look at a sense 2.1 and check out the base that was used. You can also use beyond compare and basically skip Linux all together. Using kitchen to deodex the ruu is a good first step. Choose option 11 in the menu.
Personally, I would start off with a working port and changing apps and moving stuff around. Also get a good list at which libs are associated with what. But use stock bins, etc, xbin, hw libs, and ported apks, framework, and software associated libs. Stock boot.img and a good updater-script. Also know key
Things like the EVO density is 160, vold_stab is usb, amkd is rotation, gsl hw accel stuff like that.
But first things first, Google is ur friend and use the q&a section.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
So I've been looking at beyond compare, did you use this from everything and just edit all the non evo files to match existing evo ones from within windows?

Kindle Fire bluetooth driver?

Found this via Google tonight, anyone have any insights?
Did someone get bluetooth working?
pastebin.com/YgRKdpej

intel352 said:
Found this via Google tonight, anyone have any insights?
Did someone get bluetooth working?
pastebin.com/YgRKdpej
Click to expand...
Click to collapse
Loading the drivers doesn't mean anything, show me working hciattach and I'll believe it.
If someone wants to donate a broken KF I can find if it's connected in a useable way and if so make it work. Really broken is ok, as in mauled by wild dogs and drowned in the ocean broken. All I need is the mainboard to be physically intact even if it doesn't work.

pokey9000 said:
Loading the drivers doesn't mean anything, show me working hciattach and I'll believe it.
If someone wants to donate a broken KF I can find if it's connected in a useable way and if so make it work. Really broken is ok, as in mauled by wild dogs and drowned in the ocean broken. All I need is the mainboard to be physically intact even if it doesn't work.
Click to expand...
Click to collapse
I hate that my device is not broken but at the same time I'm glad it's working
Glad to see that some people gladly help with the development for the Kindle Fire though.

A pastebin by the same user shows dmesg output showing bluetooth loaded (just fyi):
http://pastebin.com/a4m6jc7T

intel352 said:
A pastebin by the same user shows dmesg output showing bluetooth loaded (just fyi):
http://pastebin.com/a4m6jc7T
Click to expand...
Click to collapse
That looks like output from the diagnostic boot mode (bootmode 8000, DON'T DO THIS WITHOUT FFF INSTALLED). Not sure if BT is in the kernel out of laziness or if there's something else to be found...

pokey9000 said:
That looks like output from the diagnostic boot mode (bootmode 8000, DON'T DO THIS WITHOUT FFF INSTALLED). Not sure if BT is in the kernel out of laziness or if there's something else to be found...
Click to expand...
Click to collapse
Considering bt hardware is on board and in kernel, would be nice if it could be easily enabled/used

Would running a Linux distro on the device pick up Bluetooth hardware and allow you to do something with it? I have Debian running via debootstrap loop file (installed with app called Linux installer on market) but i don't use any ui and don't know how to check for it in a terminal

I'm trying to get up to speed to look at bluetooth too - from what I understand of what I've found so far, it seems like it kinda has to be there and be usable unless they went out of the way to disable it. I suspect making hardware changes to disable something they could just not build into the OS to disable would have been unnecessarily expensive.
I am thinking this because:
1) Wikipedia shows the Kindle Fire is based on the OMAP4430 PandaBoard
2) Pages 36 of the PandaBoard System Reference Manual:
The PandaBoard provides a module (LS Research Inc. P/N LS240-WI-01-A20) that provides a Bluetooth interface, a 2.4 GHz 802.11b/g/n interface, and an FM interface. This module may be found on sheet 14 of the schematics (reference designator U4). It uses Texas Instruments’ WiLink TM 6.0 solution.
Click to expand...
Click to collapse
3) According to the Mouser page for part #LS240-WI-01-A20, they share the same antenna:
Both WLAN and Bluetooth share the same antenna port.
Click to expand...
Click to collapse
So the functionality is there - it's all on the same chip and uses the same antenna as the wifi...
What I'd like to do is get to where I can build CM7 and poke around the code - I've got an OS dev (Windows) background but I've never done anything on Linux so it's taking some time to get the build setup. I've got ICS (not for the Fire) setup to build, just because the directions I was following were for that. Now working on CM7 for the Fire.
If I can get where I can build and flash my own CM7, I'm willing to spend some time doing some trial and brick/fix and trial again...

sweet @LanceDiamond looks like you did some homework
so you have a linux distro up and running with stock asop synced?
cyanogenmod has a wiki on how to compile from their source http://wiki.cyanogenmod.com/wiki/Building_from_source its pretty massive and as far as i know, you need the whole frigging thing. as far as I can tell, the info for each device is pretty much the same until it comes to specifying which device your building for. you will probably need to git clone extra stuff into the source and probably edit... something in order to build specifically for the kindle fire... its been a while sense I messed with the source and I never manage to make it to these forums until im tired, so sorry if im kinda all over the place

if someone can develop an app that actually turns bluetooth on in kindle fire, I will be the first one to commit buying the app. since we are in this topic, does kindle fire has microphone that can be enabled as well?

jendol said:
if someone can develop an app that actually turns bluetooth on in kindle fire, I will be the first one to commit buying the app. since we are in this topic, does kindle fire has microphone that can be enabled as well?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1363215

jendol said:
if someone can develop an app that actually turns bluetooth on in kindle fire, I will be the first one to commit buying the app. since we are in this topic, does kindle fire has microphone that can be enabled as well?
Click to expand...
Click to collapse
No built in microphone but http://forum.xda-developers.com/showthread.php?t=1363215
Doesn't seem to work with Skype etc. though.

Well....yes and no lol.
I have an Ubuntu VM using VirtualBox with somewhere around 30GB of stuff. I think I actually built some form of stock (non KF non cm7) Android. Then I started reading up on CM7 and Jackpot/Whistlestop work. Git cloned CM7KF tree from Whistlestops Git page. Followed directions to link in directories in spite of being a Linux idiot.
I now have a build that builds a bunch of stuff but eventually stops with a multi paragraph message about how my code is including something not normally included or something like that. Not home again till Monday so can't get the exact error... I may rebuild the VM from scratch when I do get back to it just to eliminate any weirdness from my not knowing what I was doing first time.
Also got a little sidetracked playing with cm7 once I flashed it
One slightly strange thing - in whistlestops cm7 directions for linking in the CM7KF tree, if I follow those steps to the letter I wind up with a dir like this:
/vendor/amazon/amazon/blaze
I assumed that was wrong and I want the tree to look like the others there, ie:
/vendor/amazon/blaze
So I didn't mkdir amazon first and that seems to give me the desired structure....
Sent from my GT-P1000 using Tapatalk (and apparently Taps thinks my kindle is a GT-1000 now with cm7/new build.prop)

Really ?? I dont know KF has bluetooth. Why Amazon put Bluetooth there without software to use ???

I've got my build working and I've spent a lot of time digging...
It looks like, as someone said up above in this thread, the kernel needs to be built with bluetooth enabled. And you need the driver and the firmware files put in the right place in your android build tree. Then you'd need to do something to cause the driver and firmware to actually wind up in an image when you build.
I have the files and I have a working CM7 build. I *think* the CM7 kernel has bluetooth enabled so I am thinking it might be possible to hack this around to work without having to actually build the linux ARM7 kernel.
I'm at least encouraged...
FYI, I found the driver here - not sure if it'll work, but easy enough to try - the hard part is going to be figuring out the editing to get it in an image...

awesome work, thank you

Bluetooth would be awesome!
Hopefully the driver is compatible with wiimote and similar programs.

Lance you are teasing me! i like what i am hearing... if theres anything i can do please let me know got a research junction you want to pass off let me know im good with rooting people on...
well you should definitely toouch base with Whistlestop the dev running the cm7 build if you didnt know. im going to google my eyeballs out on your details. This thing has bluetooth i can just smell it.
Sent from my HTC Vision using xda premium

So let me get this straight? Bluetooth is possible, but not supported by the kernel?? This is simular to the iPhone 2G/iPod Touch 2G having bluetooth radios. But no supported by the kernel.
Sent from my HTC myTouch_4G_Slide using Tapatalk

Kindle Fire Bluetooth
someone asked why Amazon would put bluetooth in the Fire but not have it active? i think the answer is simple. "introducing the KF2. one of the new features is bluetooth". i'm sure Amazon has other features built in but not turned on. would make bringing in the next version cheaper for them, imo.

Unfinished Business - I'm done, have at it.

Ok, I've come to realise, after some prodding from my wife, that I've been just way to focused on all of these projects I've begun, searching for a way to create that next great thing, and always managing to fall just short of achieving it. At this point, I've decided to take a step back, and calm down on working with my A100.
So, I put everything I've been working on into 1 zip file, so anyone who wishes may begin their own work on anything in there.
The projects that are currently in there in various forms:
Jellybean ROM, yeah, I was working on getting a jellybean ROM for us A100 users. Never got it to boot all the way, worked on it for probably 6 hours yesterday. Thanks to randomblame for this.
AOKP A500 port, also semi completed, it never booted all the way, stuck on boot animation.
Extracted A100 CM9 boot.img folder, with the ramdisk and kernel, for use with the above two projects, or any other porting you wish to do.
DSIXDA Kitchen for linux, useful abilities include extracting and building boot.img files. Can be used for any number of things that I never used it for, however its included anyways. Try out modding some stock ROMs or something, just play around with it.
Morfic's Bin Tools, a full set of every tool you could ever want, for use with ADB or any number of things, if you can think of it, Morfic included it. Huge thanks to Morfic for this.
CWM Touch Recovery .img I created this as an experiment for/with another user, and its actually posted up in my Nightly Builds posting, however its been reported SD card doesn't mount on it. The partitions are all correct so it won't brick, but enjoy playing with it. Includes all of the files for it, as well as the ready to flash .img file.
Couple of documents, 1 being a complete partition map as reported by TWRP Recovery, useful for knowing which device blocks are which partition.
Other document is cat /proc/partitions and cat /proc/cmdline, output is from my working device, and can be used to verify bootloader information as well as raw partition information, if available. Comes from my bootloader flashed and unlocked A100, and as you can see, reports A200, and as far as I can tell, the wrong CPUID.
Anyone can feel free to take a look, and see what they may want to finish, or not. I give full consent to use anything in this zip file, as I didn't really create it, but I give it anyways. Anything in this zip is, I think, GPL compliant (such as the CM9 kernel and aokp with CM9 kernel, jellybean with CM9 kernel, etc).
CWM Touch was created by the bot, so I hold no credit for this either, only the 2 document files are truly created by me, and I give full consent for their use.
If you do manage to create something out of any of this, all I ask is a thanks somewhere in the post :good:
So whats next for me?
Well, I'm taking a break for awhile. I'll continue the Nightly CM9 Builds until official nightlies begin, and I'll keep updating the Guides as I have the time, and I'll fix any releases (like my scripts) as I find issues or issues are reported. The only thing I am actively pursuing is the bricking issue. I'm still looking for, and hoping to get, a bricked A100 for testing, as my request post mentions, I would love a donated unit (or loaned) for some testing. Also, the battery issue, as it does occur somewhat often, I would love a chance to work on one of the A100s with the battery charge issue.
Oh, and I'll still be around XDA, helping where I can as always. Anyone can feel free to add me for gtalk, twitter, google+ or whatever else, and feel free to ask questions, for help, or just say what's up and chat! I also tend to visit #iconia-dev on freenode.
Ok enough blabbing gimme your shiz!
Unfinished Business 421 MB zip file, with zips and random ish inside.

:'(
Sent from my A100 using Tapatalk 2

Thanks for all the hard work, man. I've seen soo many posts from you helping people on here.
I see where your coming from, sometimes I get sucked into what I'm doing too, whether it be mobile, or desktop pc's. I hear about it too from the wife too, and like you said you have to step back and enjoy the little things..

Romman0 said:
Thanks for all the hard work, man. I've seen soo many posts from you helping people on here.
Click to expand...
Click to collapse
Thank you for noticing but I do intend to keep helping on the forums, I'm just not doing anymore projects for awhile.
Tapatalked from my A100 - CM9 unsecured tester.

Thanks for your effort and work to bring custom ROM and lots of support on this tablet. Life always comes first. Good luck to you pio.
Sent from my Nexus S using xda premium

Thanks for all your efforts. They are greatly appreciated.

You have helped the community in tremendous amounts. Hopefully someone takes up these projects.
Sent from my A100 using xda app-developers app

You have been a huge contribution to the A100 scene. Thank you so much.
Sent from my A100 using Tapatalk 2

Multirom? Dual-Boot patcher?

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.