yashsingh1/xdaforums huggingface dataset:
[HTC Desire 510] pattyboi:):
im pretty sure shinrus device tree has a unified irl,its here https://github.com/shinru2004/android_device_htc_a11 ,also,did you update the kernel you were using? our kernel doesnt have support for loli,all tho rbhero has a branch in his kernel tree that he said works on loli
[HTC Desire 510] OnlySomeDood:
Im working on all that, I'm looking into using the msm8974 kernel, from what I have read it's practically identical to the 8226, I am also using the a5 (desire 816) as a template since the two devices are so similar. Little by little I am getting there, having to figure out these errors as they come.
[HTC Desire 510] pattyboi:):
rbhero has a modded a5 tree up if you wanna take a look at it,and just since your here..

have you gotten a error to something along the lines of:

make: *** No rule to make target `/home/pattyboi/source/out/target/product/a11/obj/SHARED_LIBRARIES/libqdutils_intermediates/export_includes', needed by `/home/pattyboi/source/out/target/product/a11/obj/SHARED_LIBRARIES/libsurfaceflinger_intermediates/import_includes'. Stop
[HTC Desire 510] OnlySomeDood:
I actually just did, thanks for the heads up. I am going to look at / try his configs and see where it goes.

Yeah I have gotten a few of those errors, but not on surfaceflinger, mine are mostly on bionic and libcutils
[HTC Desire 510] pattyboi:):
gonna be trying that myself,let me know if you get anywhere
[HTC Desire 510] OnlySomeDood:
for sure, that's what this thread is for afterall
[HTC Desire 510] dip_spit:
You might wanna PM a mod and ask them to move this over to the development area: Desire 510 Android Development.
[HTC Desire 510] OnlySomeDood:
Well the reason I posted this here is because I don't have the required ten posts yet. So I wouldn't have been able to make this thread to post anything. This is #9 and I am making progress so i will go ahead and contact a mod soon to have it moved over.
[HTC Desire 510] dip_spit:
Gotcha. I didn't even know that was a rule. I was just giving you the heads up lol.
[HTC Desire 510] OnlySomeDood:
no worries. yeah you need 10 posts in order to post anything in the development subforums for the devices.

I just pm'd a mod and asked to have the thread moved to the appropriate subforum. Also I am making a LITTLE Progress, it does feel like two steps forward and one step back however. I'm confident that between those of us who are wanting it that it will happen.

Not sure if anyone is interested but I created another slack room under my account if anyone developing for the 510 wants to join and collaborate in order to (hopefully) let this device see its potential. Just pm me and i'll send you an invite.

Quickie update, I keep running in to the same set of errors and I know the answer is right in front of my face but im just not seeing it. I have a sneaking suspicion that I may be missing some headers and libraries on my machine but I can't be sure.

Also I've forgotten how much I dislike working with kernels lol
[HTC Desire 510] pattyboi:):
whats up with the kernel? im good in that department for the most part,roms are...eh,not my specialty
[HTC Desire 510] OnlySomeDood:
I can't get any kernel to compile, I keep getting failures while making the drivers.

Currently using a pre compiled image to at least try to get the rom built, I can solve these errors, i've done it before on other devices. How's progress on your end if any?
[HTC Desire 510] pattyboi:):
can you post one of the errors when you get a sec?

& none,got so angry at the stupid libqdutils thing i had last night i havent even attempted anything yet,been working on setting zswap/vnswap up so we have some leeway when it comes to ram..you got github at all?
[HTC Desire 510] OnlySomeDood:
I was fighting with libcutils for about two days, stupid friggin unicode strings....but I got past that, right now it's mostly "no rule to make target" stuff which is easy enough after you go digging around to find the right file/line to edit. Right this very second though I am working on getting the mkbootimg.mk properly set up and get a recovery image cooked.
[HTC Desire 510] pattyboi:):
i think rbheros last twrp works with loli,never tested it,all tho he should me screenshots of him running it,so you might just wanna save the time and use it
[HTC Desire 510] dip_spit:
The TeamYAR TWRP doesn't, not to my knowledge. He had one built locally but he didn't send it to me. I have a CM12 kernel that he built that boots (rom is still ****) but needs default encryption disabled amongst other things.
[HTC Desire 510] pattyboi:):
well sh*t..i think there is a way to disable encryption from the ramdisk..not entirely sure how tho
[HTC Desire 510] OnlySomeDood:
It's kind of a "me" thing, If I am going to go thru the effort to port cyanogenmod to an unsupported device then I'll take the extra time to compile every bit, including the recovery.
[HTC Desire 510] pattyboi:):
i dont blame you,makes sense to me
[HTC Desire 510] rbheromax:
No. The code is pretty much incompatible. ??
[HTC Desire 510] pattyboi:):
i can do basic hardware stuff,like tear it apart lmao,software im only "decent" with kernels,built a rom one time and it didnt even boot lol,i really wish i could help
[HTC Desire 510] OnlySomeDood:
Ok so I removed ril and libril folders from the device tree, set use own ril to false and it seems to be building

It's building the app apks and if my memory serves that means it's almost done ill see if I can let it finish and test a bit in the morning

Oh and don't forget to vote in the poll, YOU can help shape OSA's development

SOOOOOOOO FREAKING CLOSE

https://gist.github.com/OnlySomeDood/705df53d743994529b63

Edit:

I've got some good news and some bad news.

The good news

building image from target_files BOOT...
running: mkbootfs -f /tmp/targetfiles-KG2b_C/META/boot_filesystem_config.txt /tmp/targetfiles-KG2b_C/BOOT/RAMDISK
running: minigzip
running: mkbootimg --kernel /tmp/targetfiles-KG2b_C/BOOT/kernel --cmdline console=ttyHSL0,115200,n8 androidboot.hardware=qcom user_debug=31 ehci-hcd.park=3 --base 0x00000000 --pagesize 2048 --kernel_offset 0x00008000 --ramdisk_offset 0x02008000 --dt device/htc/a11/dtb --tags_offset 0x01e00000 --ramdisk /tmp/tmpzQ4wOi --output /tmp/tmpiiR6qo
boot size (6881280) is 41.02% of limit (16777216)
running: openssl pkcs8 -in build/target/product/security/testkey.pk8 -inform DER -nocrypt
running: java -Xmx2048m -jar /home/somedood/Kitchen/Android/Omni-KK/out/host/linux-x86/framework/signapk.jar -w build/target/product/security/testkey.x509.pem build/target/product/security/testkey.pk8 /tmp/tmp9t0RUx /home/somedood/Kitchen/Android/Omni-KK/out/target/product/a11/omni_a11-ota-eng.somedood.zip
done.
Running Chromium prebuilt setup script...
Copying files...
Generating Makefiles...
Done!
Package complete: /home/somedood/Kitchen/Android/Omni-KK/out/target/product/a11/omni-4.4.4-20150702-a11-HOMEMADE.zip

real 7m16.656s
user 6m21.347s
sys 1m31.610s

The bad news

Flash failed executing makelinks.sh
[HTC Desire 510] rbheromax:
Awesomeeeee

I just bought a 5th Gen i5 laptop and my Commander has given the base a 4 day weekend. I'll be here to help if needed
[HTC Desire 510] Droid187:
Maybe some MIUI love one day.
[HTC Desire 510] OnlySomeDood:
well it doesn't boot at all, I can't even get a logcat, perhaps you can compile and shoot me a kernel? Besides that i'm going to run another build soon. Some time tonight i'll upload all my current sources to github

Edit:

.....
[HTC Desire 510] pattyboi:):
that alone has just really made my night
[HTC Desire 510] OnlySomeDood:
There are some 'quirks' I'm uploading the zip now and will be shooting a few of you a pm here shortly
[HTC Desire 510] MrMike2182:
Looks good bro!!
[HTC Desire 510] OnlySomeDood:
So as some of you may know already i'm getting a new laptop in the near future. So until I get it development is going to pretty much halt. Well anything major anyway, there's no reason to start syncing new repos and doing major changes when i'm just going to have to re download it all anyway.
[HTC Desire 510] knoober:
I was on the edge of my seat! Then this ^^^^

I deflated like a baloon :) I hope you get your new machine soon! Until then I'm willing to help (even if just for the ability to complain) but I'll warn you now, I do think know how to do anything so...... I can flash and test for you :) I'm on the boost variant. I do t know if you have one of those yet, but I'll be perched like a buzzard, waiting g for this one to drop! ;) thanks for working with this device
[HTC Desire 510] OnlySomeDood:
Well then if you know all figure out why in getting no sound lol I'm running a build now with some enhancements and tweaks

I've also come across some interesting commits i'll be testing out.
[HTC Desire 510] rbheromax:
Is audio still in the device tree how its supposed to be?
[HTC Desire 510] knoober:
It was supposed to say "I don't know how to do anything" I blame the keyboard on mobile devices! :) anyway, can flash a rom and kernel and install twrp. Anything more complicated than that is in the future still. If push came to shove I could take a logcat too. I'm still happy for the work you guys are doing though, so thanks.

To recap, count me in to complain when stuff doesn't work (although I'm sure it will)
[HTC Desire 510] OnlySomeDood:
as far as I know, but i'm not going to worry about it till I get my new machine, it's coming with several repos pre synced lol

In the mean time I am going back go my roots, details hopefully soon......

Edit: :)
[HTC Desire 510] miniandroidp:
cant wait for android 5.1 if someone can
[HTC Desire 510] pattyboi:):
you just made me so very happy
[HTC Desire 510] OnlySomeDood:
Working on it my goal is to have a booting lollipop by my bday on the 27th

Got access to a much better build box now...
[HTC Desire 510] pattyboi:):
congrats broski,im playing with wifi rn,think ill have it ready tonight
[HTC Desire 510] Flash_Aholic:
Mann mad props to you man!! I ran the PAC rom on my HTC evo 3d for virgin before I bricked it and it was dope! I'm always willing to test anything if you need a tester on virgin as well! Keep up the good work homie!
[HTC Desire 510] OnlySomeDood:
Will it also be able to boot lolli?
[HTC Desire 510] pattyboi:):
im not sure,maybe? did you fork from rbheros cm12 branch?
[HTC Desire 510] OnlySomeDood:
the one you forked was from shinru's repo

here is the other

https://github.com/OnlySomeAndroid/android_kernel_htc_a11-L
[HTC Desire 510] pattyboi:):
alright,ill see what i can do then :)
[HTC Desire 510] alphase:
Can you build a rom from a kernel ?
[HTC Desire 510] OnlySomeDood:
Huh?
[HTC Desire 510] CSP III:
Next
[HTC Desire 510] sevanoaks2005:
No. A kernel is part of the ROM, it's the foundation.
[HTC Desire 510] alphase:
the kernel contains the drivers of the roms ? or just the boot images ?
[HTC Desire 510] Satori80:
The kernel itself interacts with system hardware within certain parameters. It also includes certain drivers and provides APIs for other drivers, as well as providing APIs for system and userland software.

A ROM is generally all of the above.

Hope that helps.
[HTC Desire 510] knoober:
Even more so it is the middle man between the hardware and the firmware and software. So far as I can tell every bit of interaction between hardware and software is regulated by the kernel. For instance even though a driver is your OS's instruction manual for using the hardware, it still must operate through the kernel (but to my knowledge is not contained in it as the driver is a specialized "software")

FWIW I read the question about roms and kernels to be more like" if you have only the kernel, is it possible to make a working rom from it" and then "what is the kernel made of" I think these are a little different questions than the answers? Maybe not :)
[HTC Desire 510] Electric2491:
Is there any more progress with this project. Onlysomedood?
[HTC Desire 510] MrMike2182:
He hasn't been on for awhile because his laptop got stolen so he can't exactly work on his rom right now.
[HTC Desire 510] Electric2491:
Oh wow! Sorry to hear that. Thnx MrMike for the info.
[HTC Desire 510] yacinhenni:
hi sorry to bother but i really have this problem

my htc desire 510 is unlocked so when i treing to install frimwere 1.11.506.8 my phone reboot and enter to the recovery mode and i cant install it from there so plzzzzzzzz help me

ohhh i m new on this xda so i really dont know how to post my thread to the orhers just so i can get help soon
[HTC Desire 510] Xendrix:
if you want to install normal update you have to fully unroot your device and lock bootloader. then update and reroot if you want. you should be able to inti SuperSU to unroot. and to make things easy download the windroid minitoolkit soo much easier to use lol
[HTC Desire 510] OnlySomeDood:
Oh I know, I was just sayin'

Just wondering. What's required to get a kernel booting on lollipop and cyanogenmod in general
[HTC Desire 510] dip_spit:
It's a flag in the arch/arm/configs/a11whatever. HW_ENCRYPTION=FALSE or something similar.
[HTC Desire 510] pattyboi:):
pretty sure for loli its just a couple framebuffer commits

---------- Post added at 06:33 PM ---------- Previous post was at 06:33 PM ----------

well thats just a simple rebuild,thats alot easier than i thought
[HTC Desire 510] OnlySomeDood:
Well hell, I was expecting much more than that. At least that gives me options now.

WOOOOOO, got the kernel compiled finally
[HTC Desire 510] pattyboi:):
awesome!! Your putting in major work bro thank you
[HTC Desire 510] OnlySomeDood:
ain't no thang dood

Update:

I am getting stuck at "no rule to make target dt.img ... required by recovery-ramdisk.img" there is something either in the core build or the mkbootimg.mk file and it doesn't know how to build the recovery image. I have tried with the cyanogenmod recovery and with twrp sources.
[HTC Desire 510] MrMike2182:
Try this, go into the mkbootimg.mk and look for this line

remove "CM" from it so it would become

DTBTOOL := $(HOST_OUT_EXECUTABLES)/dtbToolCM$(HOST_EXECUTABLE_SUFFIX)

this without the "CM"...

DTBTOOL := $(HOST_OUT_EXECUTABLES)/dtbTool$(HOST_EXECUTABLE_SUFFIX)

That may help or it might not but that's how I got past that same error before.
[HTC Desire 510] OnlySomeDood:
yeah I saw that in one of the sony threads and I have tried it with no effect, i'll try it again after a TOTAL clean (clear ccache, make clobber, rm -r out folders) and see if it helps. Right now I'm sort of working around it by manually creating the out folder and copying dtbTool into it before I initiate the build.
[HTC Desire 510] MrMike2182:
It's a serious pain in the rear for real lol!!!
[HTC Desire 510] OnlySomeDood:
this whole adventure is lol, but fun to me
[HTC Desire 510] MrMike2182:
Yeah definitely, it is fun!
[HTC Desire 510] OnlySomeDood:
Ok, looking over my failure logs I see that Kernel.mk under build/core/tasks is looking for the defconfig in $HOME/your/source/kernel instead of $HOME/your/source/kernel/$vendor/$device, placing the defconfig under the kernel directory allows it to continue.
[HTC Desire 510] MrMike2182:
You think you'll be able to get the cameras working? Because I have been messing with them and rebuilding the kernel over and over again to try and get it to work but no luck at all on CM11.
[HTC Desire 510] OnlySomeDood:
Can't say, I need to get this thing compiled and booting before anything else, i'll certainly try to get as much of it as I can. Right now I am getting stuck on an undeclared function in libunwind.
[HTC Desire 510] pattyboi:):
If he's still aiming for loli,cameras wont work unless we A:port some proprietary blobs or B: get new ones targetted for us specifically,B is more likely as afaik nothing uses the same lenses/sensors+ the difference in cameras alone between the variants,so that's gonna be the biggest hurtle after getting it to boot
[HTC Desire 510] MrMike2182:
I think the camera drivers are just gonna have to be totally rebuilt from the ground up... I just don't see any other way around it...
[HTC Desire 510] OnlySomeDood:
porting the drivers or compiling an updated kernel is also possible, its what we had to do with my old optimus.

incaft my next project is going to be a CAF updated AOSP build

I may have located a 3.5 kernel for our board with working cameras

update: i never claimed to be smart, in my board config i had TARGET_KERNEL_SOURCE := kernel thats why it was looking in the wrong place
[HTC Desire 510] smiley45:
Good ideal bro. I read about this fix some time ago an do believe it would work. And yes you are smart this takes brains.
[HTC Desire 510] OnlySomeDood:
heh, that was sarcasm, I just know how to use google.....an uncommon skill it seems.
[HTC Desire 510] miniandroidp:
I cant wait .

Hope boot soon :)
[HTC Desire 510] pattyboi:):
3.5? That would be sort of drawback..3.5 is older than 3.4 in terms of Linux itself

And I know upgrading the kernel drivers for the camera is possible,that's not the issuse. What IS the issue is that our proprietary libraries for the camera "shouldn't" and probably won't work on lollipop because they aren't updated for the changes loli incorporated. and the for sure won't work with custom roms that pull camera stack updates because they won't have the same functions.. afaik at least.
[HTC Desire 510] OnlySomeDood:
Progress report. I had a snafu with my hdd. Re synced sources and running build now. Been going for about 3 hours with no errors yet. My fingers are crossed. This laptop takes about 7-9 hours for an initial build (45 min or so after that)
[HTC Desire 510] smiley45:
Good luck bro. Did you get the kernel figure out. Kernel are hard to do with HTC low end phones
[HTC Desire 510] OnlySomeDood:
I'll know more of what I need after it compiles. Right now I have no reason to believe it won't work.

I had some selinux stuff to sort out. Also shifting focus to aosp. Currently running a build for aospa
[HTC Desire 510] icy_gt:
by running do you mean compiling?
[HTC Desire 510] OnlySomeDood:
Yes

Just want to say I hate selinux lol it's the reason I stopped using suse and fedora. Anyway things are progressing
[HTC Desire 510] SGS3VMU:
Pretty cool man, pretty cool. :good:
[HTC Desire 510] OnlySomeDood:
anyone have knowledge on selinux?

device/htc/a11/sepolicy/akmd.te:2:ERROR 'duplicate declaration of type/attribute' at token ';' on line 17634:
type akmd, domain;
#line 1 "device/htc/a11/sepolicy/akmd.te"
checkpolicy: error(s) encountered while parsing configuration
make: *** [/home/onlysomedood/Kitchen/AOSPA-L/out/target/product/a11/obj/ETC/sepolicy.recovery_intermediates/sepolicy.recovery] Error 1
make: *** Waiting for unfinished jobs....
[HTC Desire 510] pattyboi:):
clueless...i think it deserves to be burned with fire.
[HTC Desire 510] VigiDroid:
I tried countless times to get CM12 to compile and Selinux f-ed with it all the time... I ended up deleting the make files that commanded it to be used, and it somehow got rid of that error ... I honestly can't remember anything about it any more though, since I gave up a long time ago due to plenty of other errors popping up
[HTC Desire 510] OnlySomeDood:
i have recovery and kernel both compiled and have gotten past the selinux errors, only thing standing in my way is dealing with the caf/non caf stuff.

Edit:

Qcom common and qcom power were conflicting, 90% of the system is built.

Big update:

The way the build is going I'm confident I'll have a ROM by the end of today, June 8th. I'll need a couple people to help test. Specifically need people who can test Bluetooth, WPA and WPA connections since I'm unable. I've asked pattyboi already and need one or two more. Also you need to be able to gather and send logcats of anything major. Reply to this thread or pm me if interested as I want this tested by at least a couple knowledgeable people before it's released.
[HTC Desire 510] bote2345:
Htc desire 510 eu

I can help . :) please :D
[HTC Desire 510] koobie777:
Willing to test here
[HTC Desire 510] MrMike2182:
I'll do some testing for you with logcats and all. I'm on Virgin Mobile just so you know.
[HTC Desire 510] alphase:
it work on 64 bit model ?
[HTC Desire 510] miniandroidp:
Can wait for new rom HTC desire 510 got afew rom .
[HTC Desire 510] pattyboi:):
nope,64 bit isnt available here.
[HTC Desire 510] OnlySomeDood:
Couple minor setbacks, if anyone has any previous knowledge in porting or java hit me up via pm, i'm trying to learn as I go and a group effort will help this move along much quicker. In my signature click on the github link and you'll find the current device tree, kernel and other things I am using for this build.

Edit:

SO...FREAKING...CLOSE it started packing the zip and all that but it seems my recovery.fstab somehow got corrupt so I am re writing it and hopefully get this done.

Install system fs image: /home/onlysomedood/Kitchen/Omni/out/target/product/a11/system.img
/home/onlysomedood/Kitchen/Omni/out/target/product/a11/system.img+ maxsize=2466410496 blocksize=135168 total=395096516 reserve=25006080
Package target files: /home/onlysomedood/Kitchen/Omni/out/target/product/a11/obj/PACKAGING/target_files_intermediates/omni_a11-target_files-eng.onlysomedood.zip
Traceback (most recent call last):
File "./build/tools/releasetools/add_img_to_target_files", line 327, in
main(sys.argv[1:])
File "./build/tools/releasetools/add_img_to_target_files", line 321, in main
AddImagesToTargetFiles(args[0])
File "./build/tools/releasetools/add_img_to_target_files", line 246, in AddImagesToTargetFiles
OPTIONS.info_dict = common.LoadInfoDict(input_zip)
File "/home/onlysomedood/Kitchen/Omni/build/tools/releasetools/common.py", line 173, in LoadInfoDict
d["fstab"] = LoadRecoveryFSTab(read_helper, d["fstab_version"])
File "/home/onlysomedood/Kitchen/Omni/build/tools/releasetools/common.py", line 248, in LoadRecoveryFSTab
raise ValueError("malformed recovery.fstab line: \"%s\"" % (line,))
ValueError: malformed recovery.fstab line: "/boot emmc /dev/block/mmcblk0p40 flags=backup=1"
make: *** [/home/onlysomedood/Kitchen/Omni/out/target/product/a11/obj/PACKAGING/target_files_intermediates/omni_a11-target_files-eng.onlysomedood.zip] Error 1
make: *** Deleting file `/home/onlysomedood/Kitchen/Omni/out/target/product/a11/obj/PACKAGING/target_files_intermediates/omni_a11-target_files-eng.onlysomedood.zip'

Looks like that error was caused by running out of ram during the build. I set up an additional 2gb swap file
[HTC Desire 510] Muhff:
Also willing to test the lolli ;) i like sweet things.

Tested most of Shinru's builds, if that helps.
[HTC Desire 510] dragonhart6505:
I would absolutely love to tear into your Lollipop build. Sign me up!
[HTC Desire 510] pattyboi:):
[MENTION=6524867]OnlySomeDood[/MENTION] you can fastboot flash the .img if you need to
[HTC Desire 510] OnlySomeDood:
....yes? am I missing something?
[HTC Desire 510] pattyboi:):
noo i read the post wrong bro my bad
[HTC Desire 510] OnlySomeDood:
hehe no worries. I was re reading the thread and scratching my head lol
[HTC Desire 510] sevanoaks2005:
I would be more then willing to test what ya got so far.

I hate Jellybean, with HTC taking their sweet time with Lollipop 5.1, and not a 100% chance of the 510 getting it, I might as well assume the worst.
[HTC Desire 510] OnlySomeDood:
Which is nothing at the moment lol, personal issues have slowed down development, I am still working on it however, I haven't stopped.
[HTC Desire 510] sevanoaks2005:
Well you do what you gotta do man. It isn't 100% a necessity. I'm continuing my research. I saw a working build but I have a feeling that the build I saw elsewhere was not legit.
[HTC Desire 510] OnlySomeDood:
Are you talking about that stupid post on that site "lollirom" or some crap? LOL yeah it's not legit, i'd put money on that.
[HTC Desire 510] pattyboi:):
does your device tree work bro? gonna be trying something again
[HTC Desire 510] sevanoaks2005:
Yeah. I knew it was bs by looking at it.