Guys,
Seems like there are lots of threads popping up with new 'packages'. I thought we should create a thread solely for the discussion of kernel hacks/patches so that we can separate the two:
For those of you who dont know, http://gitorious.org/linux-on-qualcomm-s-msm/linux-msm-xdadev is the repo were are working on.
Just to clarify, this topic is ONLY for discussion regarding Kernel patches. Thanks to vdelf's headset patch it seems sensible to focus on:
1. Backlight always on problem FIXED 01/05/10 (vdelf)
2. Battery Issue FIXED 11/05/10 (drlucky)
3. Camera
4. USB
5. GPS
Makes sense. Lets add USB to the list. While charging works, data transfer does not. Also USB might allow us to debug kernel/android on the x1 and that is what dev's always dream of
:suggestion: why not add the latest kernel as download in the 1st post if there is progress. So everyone know where to download the latest updates u ppl do
dexteral said:
:suggestion: why not add the latest kernel as download in the 1st post if there is progress. So everyone know where to download the latest updates u ppl do
Click to expand...
Click to collapse
It will be great to do this, and stick it
@dexteral,
Anyone can checkout the kernel from the above repo I posted. To do what you require we would need to upload the Kernel everytime someone adds a patch...
vdelf said:
Makes sense. Lets add USB to the list. While charging works, data transfer does not. Also USB might allow us to debug kernel/android on the x1 and that is what dev's always dream of
Click to expand...
Click to collapse
Is data transfer even possible in haret? I mean how would system unmount sdcard if it's running from sdcard itself?
not fast data but normal will work
love it
vietdoan20062006
Hi, Lets add fm-radio to the list
Great idea ... otherwise we are creating such a mess with lots of different kernel versions in different threads.
If anyone is interested in compiling the kernel as well as the wifi modules, I have setup a VMWare debian appliance containing all necessary tools and scripts to compile everything. Since this is a few hundes MB, I haven't got a place to upload ... need to check this first. If you are interested, let me know.
@drlucky
Have you had a chance to look at the backlight issue? I am almost out of ideas
Can you post your modifications on the microp-module and what you found out until now?
_Sensible said:
Guys,
Seems like there are lots of threads popping up with new 'packages'. I thought we should create a thread solely for the discussion of kernel hacks/patches so that we can separate the two:
For those of you who dont know, http://gitorious.org/linux-on-qualcomm-s-msm/linux-msm-xdadev is the repo were are working on.
Just to clarify, this topic is ONLY for discussion regarding Kernel patches. Thanks to vdelf's headset patch it seems sensible to focus on:
1. Backlight always on problem
2. Battery Issue
3. Camera
4. USB
5. GPS
Click to expand...
Click to collapse
hey could you post the steps involved for compiling the kernel i am able to comile the kernel but it is not running
Wich toolchain do you use? arm-2008q1 or arm-2009q3?
X1iser said:
Wich toolchain do you use? arm-2008q1 or arm-2009q3?
Click to expand...
Click to collapse
arm-2010q1
could u write all the commands used by you
the way i have written
Personally I'll start to see how to compile the kernel. Can you share the link to download arm-2010q1?
Have you read this post ?
X1iser said:
Personally I'll start to see how to compile the kernel. Can you share the link to download arm-2010q1?
Have you read this post ?
Click to expand...
Click to collapse
http://www.codesourcery.com/downloa...-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
but may be it is not the right one it has got 202 in it insted of 67
ya i read that post only
i was able to compile the kernel but it is giving some errors
_Sensible said:
@drlucky
Have you had a chance to look at the backlight issue? I am almost out of ideas
Click to expand...
Click to collapse
Sorry, haven't had the time. Could you push your changes to the git repo, I will try to have a look at it this week ...
okay i tried to make the kernel bt following the guide above by fatsal...
but i got stuck at
make htckovsky_defconfig ARCH=arm
htckovsky_defconfig doesn't exist (in the new repo anyway, i believe)
any help? which defconfig to use? :S
drlucky said:
Sorry, haven't had the time. Could you push your changes to the git repo, I will try to have a look at it this week ...
Click to expand...
Click to collapse
Just played with the klt-driver a bit. I always get version 0x0000, which on a hero means "bootloader mode". I have tried to migrate the hero code, but with no luck. It seems that the microp-klt needs a "reset", which shoudl be done by using a magical GPIO (on hero: 76), but this doesn't currently work at all. Kernel boots up, but still gets no valuable version number.
Related
Hello,
Developers, I really need help to get the ubuntu-touch port working again!
After the first release of Ubuntu-Touh I tried to port it again to our devices, but I don't get them booting. I only get a black screen. I have updated all sources on github and made the appropriate changes. You can find all relevant sources and information on my new website http://danwin.github.io/ubuntu-touch.html where I have uploaded the non-bootng builds for developers.
I still have the old builds available for those, who want a booting ubuntu-touch, but without any functionality: http://danwin.github.io/ubuntu-touch.html
it is so laggy on mini Dude :/
screenshot please
rod555 said:
screenshot please
Click to expand...
Click to collapse
there is already a video available, but I have made some Photos of my Neo V, sorry for bad quality: http://ubuntuone.com/6keWFpFBG0kEsVF7mBF54D
Can you add the screenshots in the op as pic
slimmer2 said:
Can you add the screenshots in the op as pic
Click to expand...
Click to collapse
I don't think this is really necessary, as I have a video from kakalko4 embedded there, which has a lot better quality than my screenshots. You can download the zip provided above and unzip the pictures inside, if you really want to see them.
can you make a more understandable guide how to install it because i try to follow your guide and my phone boots to kernel logo and for couple of second phone turns off
MarioJerkovic said:
can you make a more understandable guide how to install it because i try to follow your guide and my phone boots to kernel logo and for couple of second phone turns off
Click to expand...
Click to collapse
ok, updated.
You have to created an ext4 partition with CWM of another kernel or Linux and flashed then my kernel to use the ext4 partition on your SD-Card as /data, because ubuntu is to big for the internal storage. Have you really done that step?
DanWin1210 said:
ok, updated.
You have to created an ext4 partition with CWM of another kernel or Linux and flashed then my kernel to use the ext4 partition on your SD-Card as /data, because ubuntu is to big for the internal storage. Have you really done that step?
Click to expand...
Click to collapse
Yep done it and working ubuntu is working it lags a lot :/ but i dont care i am happy that we got Ubuntu on our old devices
I take it this a the same one as we already have? (crappy demo with no gsm)
replicant101 said:
I take it this a the same one as we already have? (crappy demo with no gsm)
Click to expand...
Click to collapse
For now yes, but hopefully officiallysonyrebel can make the kernel patches in one or two days available, so I can rebuild all images to make the daily builds of ubuntu booting, which have a lot of improvements.
Kernel patches related to what? I can help out. And I remember officiallysontrebel saying that he doesnt know much about kernels on the ray thread that was removed.
emwno said:
Kernel patches related to what? I can help out. And I remember officiallysontrebel saying that he doesnt know much about kernels on the ray thread that was removed.
Click to expand...
Click to collapse
The daily images of ubuntu aren't booting and officiallysonyrebel said that this is related to some kernel patches that have to be made, you can PM him and ask if you can help him with patching, so we can make the daily images also booting, which have a lot improvements in stability and usability.
DanWin1210 said:
The daily images of ubuntu aren't booting and officiallysonyrebel said that this is related to some kernel patches that have to be made, you can PM him and ask if you can help him with patching, so we can make the daily images also booting, which have a lot improvements in stability and usability.
Click to expand...
Click to collapse
thats strange.... It cant be kernel related, if you had added the new configs to the source code. It could be with the lastest CM10.1 changes for the 2011 devices. Take a look at http://github.com/cm42semc , here you will find the latest commits. I say this because if there was a problem with the Ubuntu Images, i.e something new needed to be added to get the build to boot, then it wouldn't boot on my n7100 either (as i made the same changes as prescribed on the guide). Either way its just a hunch. Give it a go.
With kernel patches, can performance be addressed?
emwno said:
thats strange.... It cant be kernel related, if you had added the new configs to the source code. It could be with the lastest CM10.1 changes for the 2011 devices. Take a look at http://github.com/cm42semc , here you will find the latest commits. I say this because if there was a problem with the Ubuntu Images, i.e something new needed to be added to get the build to boot, then it wouldn't boot on my n7100 either (as i made the same changes as prescribed on the guide). Either way its just a hunch. Give it a go.
Click to expand...
Click to collapse
I'm already using these sources and the daily images only get a black screen. A lot of other people report the same issue for their devices (not Xperia), too. You can have a lock at my changes on https://github.com/DanWin and maybe you find the mistake I made, if I made any.
replicant101 said:
With kernel patches, can performance be addressed?
Click to expand...
Click to collapse
Maybe, but the daily builds of ubuntu have a lot better performance and stability than the mwc-demo image, which is currently the only booting version.
DanWin1210 said:
I'm already using these sources and the daily images only get a black screen. A lot of other people report the same issue for their devices (not Xperia), too. You can have a lock at my changes on https://github.com/DanWin and maybe you find the mistake I made, if I made any.
Click to expand...
Click to collapse
Yes, others did have a blackscreen, even the n7100 users did. But some, including myself got it to boot.
This is what I did:
1. Wipe system / data / dalvik
2. install device part
3. install ubuntu image
NOTE: You made a new partition on the sdcard where ubuntu was to be installed. I recommend you to WIpe your sdcard, create a new partition and try again. Also try with try flashing with a different recovery / kernel then flashing the ubuntu kenrel in the end. Sometimes recoveries mess up.
Thx for the job but i had some problemes with the ARc S when i flash the Ubuntu systeme it's abortes whith the statu 0 what i have to do ?
d4k-pho3nix said:
Thx for the job but i had some problemes with the ARc S when i flash the Ubuntu systeme it's abortes whith the statu 0 what i have to do ?
Click to expand...
Click to collapse
Normally status 0 means success, can you go in CWM to advanced -> show log and enter the output of this here, maybe I can help you.
UnityROM-2 v.2.5.0
*****Discontinued.... No way to test actively till I have a functional build.*****
HTC One M7 Sprint Edition ( m7spr )
Development Section...
Want to contribute to the project or become team member?
Contact Me by PM here or leave a post detailing what you can and are willing to do for the projects' advancement.
My Github: https://github.com/LiquidSmokeX64
All current project sources can be found there .
ALSO MY FOOL-PROOF BUILD GUIDE & SCRIPTS ARE THERE FOR THOSE TOO IMPATIENT TO WAIT FOR MY NEXT RELEASE .
**Sources current as of version 2.5.0**
**10/06/2014**
Direct link to guide:
https://github.com/LiquidSmokeX64/Guides-Scripts
Note: Noob Friendly. If you're new to building ROMs or have never done it at all. I will help for as long as you maintain civility and focus on the project goals.
Installation errors out. Here is a pastebin of log saved after error
http://pastebin.com/fz15gwwn
Edit: I was able to install after removing that set perm line from updater. I will let ya know how it goes.
gruesomewolf said:
Installation errors out. Here is a pastebin of log saved after error
http://pastebin.com/fz15gwwn
Edit: I was able to install after removing that set perm line from updater. I will let ya know how it goes.
Click to expand...
Click to collapse
Ok. I just removed it too. My bad adaptation from Evo LTE. Nothing too bad luckily.
Reuploading the fixed version now.
LiquidSmokeX64 said:
Ok. I just removed it too. My bad adaptation from Evo LTE. Nothing too bad luckily.
Reuploading the fixed version now.
Click to expand...
Click to collapse
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
gruesomewolf said:
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
Click to expand...
Click to collapse
So. You're a kernel dev... Got a question for you. How do I add more CFLAGS to the makefile without it not booting or whatever? I've tried adding -O3 to the 2 places I know to put CFLAGS. Same place I put the -w so it would work with GCC 4.8
gruesomewolf said:
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
Click to expand...
Click to collapse
Will you be releasing this kernel for the Evo 4G? [emoji14] Evo4gnoob here
LiquidSmokeX64 said:
So. You're a kernel dev... Got a question for you. How do I add more CFLAGS to the makefile without it not booting or whatever? I've tried adding -O3 to the 2 places I know to put CFLAGS. Same place I put the -w so it would work with GCC 4.8
Click to expand...
Click to collapse
I wouldn't say Im a kernel dev....more of a dabler...lol. I sent you a pm with my makefile so you can see adjustments I made for my kernels latest build (not yet publicly released)
Notorious said:
Will you be releasing this kernel for the Evo 4G? [emoji14] Evo4gnoob here
Click to expand...
Click to collapse
Umm....no I dont have any plans for that ATM
gruesomewolf said:
I wouldn't say Im a kernel dev....more of a dabler...lol. I sent you a pm with my makefile so you can see adjustments I made for my kernels latest build (not yet publicly released)
Umm....no I dont have any plans for that ATM
Click to expand...
Click to collapse
Was joking lol
Notorious said:
Was joking lol
Click to expand...
Click to collapse
So you're allowing the integration of it? Just to be clear.
So I'm not sure why but the kernel borked again. Maybe I need to go through one flag at a time? Or maybe forgot something....?
gruesomewolf said:
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
Click to expand...
Click to collapse
Hey. Im having nothing but issues building it in the ROM so I was curious if you could tell me what I need to do after copying the msm8960 folder to a new place and adding in the makefile changes? Ive never built a kernel independently before but would like it to be a boot.img like normal so I can just replace the one in the ROM zip with the new one. Im sure it's pretty easy, just figured I'd ask you rather than comb through 80 guides saying different stuff lol.
LiquidSmokeX64 said:
Hey. Im having nothing but issues building it in the ROM so I was curious if you could tell me what I need to do after copying the msm8960 folder to a new place and adding in the makefile changes? Ive never built a kernel independently before but would like it to be a boot.img like normal so I can just replace the one in the ROM zip with the new one. Im sure it's pretty easy, just figured I'd ask you rather than comb through 80 guides saying different stuff lol.
Click to expand...
Click to collapse
Could you pm me with more info. Exact process of building, errors during build, any changes made to source, etc.
I'm gonna download your source later, together we should be able to figure this out.
gruesomewolf said:
Could you pm me with more info. Exact process of building, errors during build, any changes made to source, etc.
I'm gonna download your source later, together we should be able to figure this out.
Click to expand...
Click to collapse
I'm not seeing errors. Hell I removed everything but the -O3 spots and it still refused to boot. I dont know what the deal is....
Anytim I do ANYTHING to the kernel its dead, no matter how stupid it is.
gruesomewolf said:
Could you pm me with more info. Exact process of building, errors during build, any changes made to source, etc.
I'm gonna download your source later, together we should be able to figure this out.
Click to expand...
Click to collapse
BTW. The makefile is borked. And was curious if you knew how to build AOSP for this device? CM was pretty easy, I'd figure AOSP isn't too different. Then I can try to get Android L running once I have a working Android K to cross-reference to and make the version specific changes in device, kernel, vendor, qcom-common, and s4-common
LiquidSmokeX64 said:
So. You're a kernel dev... Got a question for you. How do I add more CFLAGS to the makefile without it not booting or whatever? I've tried adding -O3 to the 2 places I know to put CFLAGS. Same place I put the -w so it would work with GCC 4.8
Click to expand...
Click to collapse
When certain flags or 03 is added it creates a larger zImage. In order to compensate the boot.img needs needs modified, either by kernel installer or if baked in the rom hex edited. To change the ramdiskaddr.
Sent from my HTCONE using Tapatalk
thicklizard said:
When certain flags or 03 is added it creates a larger zImage. In order to compensate the boot.img needs needs modified, either by kernel installer or if baked in the rom hex edited. To change the ramdiskaddr.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Absolutely correct. And to elaborate on this just a bit more. Since your source building here, you can actually adjust the ramdiskadd with the scripts, considering it uses mkbootimg commands to build the boot.img.
An additional line in your devices board config, to give it a new ramdiskaddr size. Then an additional line in the build folder factory_ramdisk.mk , to handle the command for a new ramdiskaddr size should do the trick.
As for your other question about building aosp. I'm afraid that would be beyond my area of expertise. You would have significantly modify aosp code to allow for caf. It would be much harder then building cm, cause cm already has all the adjustments needed for caf devices
thicklizard said:
When certain flags or 03 is added it creates a larger zImage. In order to compensate the boot.img needs needs modified, either by kernel installer or if baked in the rom hex edited. To change the ramdiskaddr.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
gruesomewolf said:
Absolutely correct. And to elaborate on this just a bit more. Since your source building here, you can actually adjust the ramdiskadd with the scripts, considering it uses mkbootimg commands to build the boot.img.
An additional line in your devices board config, to give it a new ramdiskaddr size. Then an additional line in the build folder factory_ramdisk.mk , to handle the command for a new ramdiskaddr size should do the trick.
As for your other question about building aosp. I'm afraid that would be beyond my area of expertise. You would have significantly modify aosp code to allow for caf. It would be much harder then building cm, cause cm already has all the adjustments needed for caf devices
Click to expand...
Click to collapse
I read this and my eyes glaze over. But you are in good hands with these two helping you. :highfive:
Yeah I'm working on it guys. Read the integrated kernel building guide and trying that. But if I could just get it to build me the boot.IMG and get my ramdisk sizes and whatever I'm looking at where to edit it in the device/BoardConfig changed the defconfig to a custom one I made based off the original one from the working boot.IMG but changed the I/O scheduler & CPU governed defaults. Gave it a local name (UnityKernel-x.x.x) and am fighting its last issues. So if nothing else help building it independently might be the most useful now. So if nothing else I can push a new boot.img
My bad. It just says the boot partition size so I think I might be almost there
Hi! I'm currently making a somewhat desperate attempt at porting cm12 to the d950. I know some basic things, I once tried to make a custom kernel. I have the device and vendor trees set up, with the cm12 source and the files from the flex source, and I've been making some changes. Can anyone help point me in some direction from here?
dongdong6968 said:
Hi! I'm currently making a somewhat desperate attempt at porting cm12 to the d950. I know some basic things, I once tried to make a custom kernel. I have the device and vendor trees set up, with the cm12 source and the files from the flex source, and I've been making some changes. Can anyone help point me in some direction from here?
Click to expand...
Click to collapse
Okay, so now I need to run extract-files.sh, only problem is it doesn't exist. and from my understanding, I have to already be running cm12 to do this, which obviously is not possible. Can anyone help me get the proprietary blobs?
You're better off looking at the g2 proprietary blobs as when I was trying I had the most success with them on CM11, its a good starting point
So should I take those, then make changes to suit the flex?
Yeah, its a good place to start, but it won't suddenly make it compile, it helped sort a couple of issues once we'd got it compiling in the first place....
Try msg playfulgod and see if he will point you in the right direction
Alright, I've got something that looks pretty good going, but I can't do anything without a working kernel. And as I don't know much about kernels, could Someone possibly try to make one for cm12? Also, I have the blobs from my boyfriend's g2, and I've made a lot of changes, but I might need a little more guidance. Any help is appreciated.
Do you have coding experience though thats the question.
Either Build a dummy kernel or modify the original kernel from cm11 roms that your device has and built it alongside the system images.
CyanogenMod doesnt allow Building of only the system.
Youll need to modify the following:
Kernel Source
Device Trees
Vendor Files
A good way to look at what is required for a cm12 bringup is to check other similar devices with the same architecture and compare the changes and the sources you have on your pc.
Regards
Sent from my Xperia SP using xda Forum
I took programming classes, and there were a few units on android.
So I just forked the blobs from playfulgods repo, and I've made a lot of changes to tbe devices folder, as well as 'POSSIBLY' do something good as for a kernel, but I doubt that will work. How does one build the kernel to test it? Using linux btw. I have all of the dependencies and everything, could someone explain breakfast/brunch/lunch?
HEY SO I THIN K I HAVE SOMETHING THAT MIGHT WORK AFTER HAVING SOME REALLY SMART PEOPLE HELP sorry for caps, but now I have something in the out folder for zee, what do i do with this, and how do i make it flashable? could someone do it for me? and also, kernels?
dongdong6968 said:
HEY SO I THIN K I HAVE SOMETHING THAT MIGHT WORK AFTER HAVING SOME REALLY SMART PEOPLE HELP sorry for caps, but now I have something in the out folder for zee, what do i do with this, and how do i make it flashable? could someone do it for me? and also, kernels?
Click to expand...
Click to collapse
I can write and add the meta-inf folders to make it flashable. But I don't do kernels
mattwheat said:
I can write and add the meta-inf folders to make it flashable. But I don't do kernels
Click to expand...
Click to collapse
I would really appreciate that! What means should I take of sending you the output?
dongdong6968 said:
I would really appreciate that! What means should I take of sending you the output?
Click to expand...
Click to collapse
I see 2 things with the Out Folder having problems.
1) What has the Build System Generate in the out folder?
2) CM12 will generate a pre configured Zip File if it doesn't, the build failed
Sent from my Huashan Device utilizing RR Milestone 1
Furrydaus said:
I see 2 things with the Out Folder having problems.
1) What has the Build System Generate in the out folder?
2) CM12 will generate a pre configured Zip File if it doesn't, the build failed
Sent from my Huashan Device utilizing RR Milestone 1
Click to expand...
Click to collapse
If anyone wants to take a look I zipped the out folder.
So you're going to tell us you zipped the folder but you're not going to tell us where it is? Lol
Sent from my Huashan Device utilizing RR Milestone 1
dongdong6968 said:
So I just forked the blobs from playfulgods repo, and I've made a lot of changes to tbe devices folder, as well as 'POSSIBLY' do something good as for a kernel, but I doubt that will work. How does one build the kernel to test it? Using linux btw. I have all of the dependencies and everything, could someone explain breakfast/brunch/lunch?
Click to expand...
Click to collapse
The device tree repos found in lg-devs github are the correct ones just change kernel source to our stock kernel and edit z.mk and verndor files can be extracted with the ./extract-fikes.sh script . But our kernel needs to be updated a little which i am working on mostly caf header need to be added to include/Linux for media and display. I trued using msm8974 kernel but our kernel has specific blobs we use which is easier to use stock kernel.
---------- Post added at 06:26 PM ---------- Previous post was at 06:16 PM ----------
dongdong6968 said:
HEY SO I THIN K I HAVE SOMETHING THAT MIGHT WORK AFTER HAVING SOME REALLY SMART PEOPLE HELP sorry for caps, but now I have something in the out folder for zee, what do i do with this, and how do i make it flashable? could someone do it for me? and also, kernels?
Click to expand...
Click to collapse
What you mean you got something lol. We just need to update our stock kernel which you can have a better understanding. Of what i mean visit lg-devs for z repos . we should stick to stock kernel doe.
dongdong6968 said:
I would really appreciate that! What means should I take of sending you the output?
Click to expand...
Click to collapse
Upload it to drive then message me with a link
mattwheat said:
Upload it to drive then message me with a link
Click to expand...
Click to collapse
https://www.dropbox.com/s/dx3sjp8bq720bkn/out.zip?dl=0
Furrydaus said:
So you're going to tell us you zipped the folder but you're not going to tell us where it is? Lol
Sent from my Huashan Device utilizing RR Milestone 1
Click to expand...
Click to collapse
Sorry, completely forgot. https://www.dropbox.com/s/dx3sjp8bq720bkn/out.zip?dl=0
Since this thread is no longer just about me trying to get lollipop running on this phone (I AM still doing that though) I decided to 'rebrand' it as a general development thread for OSA. What's OSA? It stands for Only Some Android...ok so whats that? A team name I came up with to make myself feel more important (btw we're always looking for contributors).
So instead of focusing on just lollipop I will be discussing pretty much anything and everything I am doing in regards to the Desire 510.
Original Post Below:
Hi all, I am currently working on getting lollipop working on the Desire 510. So far I had a successful compile of LiquidSmooth 5.1.1 a couple nights ago but not a successful boot. I am currently 97% done syncing the CyanogenMod 12.1 sources (5.1.1 r3) and am now using the omni twrp sources to ensure a higher compatibility for the recovery, I am hoping for a successful boot soon.
I have the virgin mobile cdma model of the device and that's what I will be targeting although I will do my best to make sure the device tree is universal. If anyone has any insight or advice I am all ears.
I am going to use this thread as a development thread until I get the required 10 posts and I get a booting rom.
OnlySomeDood said:
Hi all, I am currently working on getting lollipop working on the Desire 510. So far I had a successful compile of LiquidSmooth 5.1.1 a couple nights ago but not a successful boot. I am currently 97% done syncing the CyanogenMod 12.1 sources (5.1.1 r3) and am now using the omni twrp sources to ensure a higher compatibility for the recovery, I am hoping for a successful boot soon.
I have the virgin mobile cdma model of the device and that's what I will be targeting although I will do my best to make sure the device tree is universal. If anyone has any insight or advice I am all ears.
I am going to use this thread as a development thread until I get the required 10 posts and I get a booting rom.
Click to expand...
Click to collapse
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
pattyboi:) said:
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
Click to expand...
Click to collapse
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.
OnlySomeDood said:
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.
Click to expand...
Click to collapse
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
pattyboi:) said:
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
Click to expand...
Click to collapse
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
OnlySomeDood said:
I actually just did, thanks for the heads up. I am going to look at / try his configs and see where it goes.
Click to expand...
Click to collapse
gonna be trying that myself,let me know if you get anywhere
for sure, that's what this thread is for afterall
OnlySomeDood said:
for sure, that's what this thread is for afterall
Click to expand...
Click to collapse
You might wanna PM a mod and ask them to move this over to the development area: Desire 510 Android Development.
dip_spit said:
You might wanna PM a mod and ask them to move this over to the development area: Desire 510 Android Development.
Click to expand...
Click to collapse
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.
OnlySomeDood said:
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.
Click to expand...
Click to collapse
Gotcha. I didn't even know that was a rule. I was just giving you the heads up lol.
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
OnlySomeDood said:
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
Click to expand...
Click to collapse
whats up with the kernel? im good in that department for the most part,roms are...eh,not my specialty
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?
OnlySomeDood said:
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?
Click to expand...
Click to collapse
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?
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.
OnlySomeDood said:
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.
Click to expand...
Click to collapse
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
pattyboi:) said:
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
Click to expand...
Click to collapse
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.
dip_spit said:
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.
Click to expand...
Click to collapse
well sh*t..i think there is a way to disable encryption from the ramdisk..not entirely sure how tho
pattyboi:) said:
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
Click to expand...
Click to collapse
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.
OnlySomeDood said:
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.
Click to expand...
Click to collapse
i dont blame you,makes sense to me
Hi all:
This is a thread for my alternative LineageOS 14.1 roms for suzuran.
I'm building these roms from time to time for my own needs and I think other people should participate.
Since the "official" development of LineageOS 14.1 has been stopped, I decided to build a new version only if the Android security patch level has been changed or I've changed anything.
Download 2021-07-19
This is a 7z archive with the zip'ed rom and the md5 file in it. Please unpack this archive, copy the included two files somewhere to your device, reboot into TWRP and flash this zip file. Enable zip verification and md5sum checking. Maybe you have to rename the md5 file to *.md5sum; depending on the TWRP version you are using.
Kernel sources
Tree sources
Features:
OS Version: 7.1.2 Nougat
Kernel: Linux 3.10
New: Android security patch level: 5 June 2021
Using sony blob's from stock version 32.4.A.1.54
Important informations:
You should be familiar with general installation of custom roms.
Required for installation: TWRP 3.1.1 (or newer).
OR use my self built TWRP-version 3.5.2!
No need for making a clean install, but sometimes it helps a lot!
This rom is pre-rooted. For those who want to use magisk or any other rooting tool, you can easily remove this by flashing this file.
Use this rom at your own risk! It comes without any warranty! I'm not responsible for any damage! If you don't agree with that, don't try to flash this rom in any way.
Differences between my version and the "official" one:
Kcal Display Driver - Thanks to @GreyLeshy and @Sony user 16
Voltage Control - Thanks to @GreyLeshy and @Sony user 16
OMS-Support - Thanks to @nathanchance
Added F-Droid and UnifiedNLP! If you don't want this, simply de-install it.
I've included some little extensions like changelog and volume adjustment.
I've set maximum speaker volume to a higher value.
I've increased microphone gain.
I've increased all volume steps from 7 to 15.
I've changed the microfone gain to avoid echo in phone calls.
I've enabled data for MMS.
I've enabled MHL.
Not working:
VoLTE, VoWiFi
If you want to use encryption, you have to disable SIM PIN first!
One (last) request: Please don't ask for including any app. I won't do this, because I want to keep this rom as clean as possible.
Changelog
Troubleshooting:
If you're running into an error, please search in this thread if this error is already posted, before you post it again!
If not, I need a LOG to see what went wrong. Without a LOG I can't help you!
A LOG can be fetched by connecting the device with an USB cable to your PC and then by typing these commands line by line:
Code:
adb root
adb shell logcat -b all -d > logcat
Send my this LOG file via PM.
If you think this could be a SELinux related issue, please try to set the device to permissive mode first.
If the issue is gone, I need the policy file too (plus LOG). Fetch it by typing this line in a terminal:
Code:
adb pull /sys/fs/selinux/policy
If you stuck in a bootloop you can fetch a LOG with this trick:
Press the power button and the volume up button together until the device shuts down.
HOLD the power button.
Release the volume up button and press the volume down button immediately after releasing the volmue up button.
The device should start into TWRP recovery.
Tap on "Advanced", then on "Terminal" and enter these commands line by line:
Code:
cd sys/fs/pstore
cp * /sdcard
Send me the copied file(s), if any, via PM.
Nice
Berni-0815 said:
Hi @all:
First of all, please excuse my bad english... :angel:
They said I should create my own thread for my alternative LineageOS 14.1 roms for suzuran. Here it is.
I'm building these roms from time to time for my own needs and I think other people should participate.
Download
Kernel sources
Tree sources
OS Version: 7.1.2 Nougat
Kernel: Linux 3.10
Required for installation: TWRP 3.1.1
Important informations:
You should be familiar with general installation of alternative roms.
I've included some little extensions like changelog and volume adjustment.
There is no need to make a clean install, but sometimes it helps a lot!
Use it at your own risk!
Click to expand...
Click to collapse
Hi ! It would be great if u put out the advantage of yours vs with the official LOS
Berni i said before and i m saying again please make this topic a lineage based rom..
İnclude minimal app for google play store.
And maybe can add substratum inside.. or can be a default diffefent theme ..
I believe you can..
Thx bro.
ROBNX85 said:
Hi ! It would be great if u put out the advantage of yours vs with the official LOS
Click to expand...
Click to collapse
As I wrote: "I've included some little extensions like changelog and volume adjustment."
emosis said:
İnclude minimal app for google play store.
Click to expand...
Click to collapse
As I said a few days before: I don't want to include gapps! If somebody wants to use gapps, feel free to flash them separately. You can download them here. You need arm64 and 7.1 for suzuran.
And maybe can add substratum inside..
Click to expand...
Click to collapse
Substratum support is not longer available, because the devs have stopped their development for Nougat since august.
Berni-0815 said:
As I wrote: "I've included some little extensions like changelog and volume adjustment."
Click to expand...
Click to collapse
Add a basic ad-blocker too ?
Berni-0815 said:
As I said a few days before: I don't want to include gapps! If somebody wants to use gapps, feel free to flash them separately. You can download them here. You need arm64 and 7.1 for suzuran.
...
Click to expand...
Click to collapse
I agree gapps should not be included. It is easy enough to just flash it right after flashing the rom
I am thinking about official vs rom, I think the two roms are probably nearly identical. Probably the most important factor will be the frequency of updates.
PeppeBove said:
Add a basic ad-blocker too
Click to expand...
Click to collapse
You can use AdAway which is an open source host list based ad blocker. See https://adaway.org
PeppeBove said:
Add a basic ad-blocker too
Click to expand...
Click to collapse
I don't see a reason to bake something into the ROM when there are many apps that can do it.
I think something like Xposed-type tweaks being put into settings would be more appropriate. Alleviating the need for xposed. But I don't think it makes sense to load random apps into the ROM.
New version; please have a look at the first post
Berni-0815 said:
New version; please have a look at the first post
Click to expand...
Click to collapse
Awesome work, thank you so much! Flashing it now.
Just 1 question - do you know if encryption works on your builds?
I've never tried it. I've not so good experience with encryption on a stock rom; so I've decided not to use this feature at all!
Hi Bernhard.
Thanks for your hard work!
i have a question for you.... As i understand it you take all the changes/updates from the offifcial lienage and implement them into your own build. And add the changes as described in post 1.
Am i right about this?
I think that battery life is bad on the official compaired to the version you do.
Do you add battery improvements in your build?
Thanks in advance.
Torben 5247
torben5247 said:
Thanks for your hard work!
Click to expand...
Click to collapse
Oh, it is not so hard to do this, but, thank you! Sometimes I have to search a few hours or try (and revert) something, but in the end I've gotten everything to work as I like it to work.
As i understand it you take all the changes/updates from the offifcial lienage and implement them into your own build.
Click to expand...
Click to collapse
I'm using the LineageOS repositories from github as they are, that's right. I don't use my own repo's; nzzane is doing this AFAIK (Klick). A few weeks ago I'm using other repo's, because LineageOS had bad (will say: not working) sources for our devices.
And add the changes as described in post 1.
Am i right about this?
Click to expand...
Click to collapse
Yes! :good: One or two of my changes should be implemented into the "official" builds, but until now I don't understand how to use "commitments". Maybe in a few days... :angel:
I think that battery life is bad on the official compaired to the version you do.
Do you add battery improvements in your build?
Click to expand...
Click to collapse
No. Nothing like this.
On my own device battery life is about three days...
Hi,
PeppeBove said:
Add a basic ad-blocker too
Click to expand...
Click to collapse
emosis said:
İnclude minimal app for google play store.
And maybe can add substratum inside..
Click to expand...
Click to collapse
Like other persons, I don't want to have a lot of applications include in the rom. I want to choose the ones I use. This is one reason that made me come to alternative rom.
Another reason is that Lineage use less google s"hit" than stock rom.
So if you have the vision of more app and google stuff include, you better stay on stock. Alternative Roms offers me more freedom; but that's just my opinion...
This is prerooted? There are some of us out there that need to install certain apps before rooting.
Cerhio said:
This is prerooted?
Click to expand...
Click to collapse
Yes.
Berni-0815 said:
One or two of my changes should be implemented into the "official" builds, but until now I don't understand how to use "commitments".
Click to expand...
Click to collapse
I've just committed three of my changes. We'll see if they will be merged...
Berni-0815 said:
I've just committed three of my changes. We'll see if they will be merged...
Click to expand...
Click to collapse
The brightness settings? I hope so
What else?
Berni-0815 said:
I've just committed three of my changes. We'll see if they will be merged...
Click to expand...
Click to collapse
That's so great to hear, let's hope they get accepted.
Huge thank you for keeping this device alive Berni!