Develop Bugs

[W.I.P][PORT] Sense 5 for Vision

Hi guys,
Some progress are made.
Finished building kernel :victory:
Tryed on Sense 4 (by @coolos ) BOOTS
Tryed on ported Sense 5 BOOTLOOP :crying:
Thanks to @coloured_chalk for his kernel source and begin and important dev for this project :highfive:
Thanks to @coolos for teach me porting Sense 5 and some more useful things :good:
Best Regards,
Marco Marinho

Please mention others devs. I don't know very much the HTC Desire Z community

I'll try this like... next year or something. heheheh
(can we get an MIUI port instead? much needed by now.)
---------- Post added at 12:03 AM ---------- Previous post was at 12:00 AM ----------
Also, does this work on an rom with sense 4.1? because I'm currently running a sense rom...

@_MarcoMarinho_ good idea, although I think it would be a hard undertaking:
* Other members and I have tried porting JellyBean ROMs but we don't yet know of a way to get the hardware keyboard fully working (lights, auto rotate, etc.);
* That ROM you linked still appears to be in alpha state, perhaps it's best to wait until everything is functioning on that first or look for Sense 5 on another similar device (although the Desire HD has the advantage of being the same resolution which makes everything much easier);
* All of the Desire Z developers working on JellyBean pretty much abandoned 4.1.2 in order to start work on 4.2.2 so unless Sense 5 can be ported to 4.2.2 this could cause problems because I know that many improvements were made, for example in cn.fyodor's AOSP JB, between these two versions;
* The Desire Z has limited RAM and Sense is very heavy, although HTC may have remedied this in Sense 5 so it may run fine;
* I wouldn't even know where to begin on the kernel, all I know is that Sense kernels can't run AOSP ROMs and AOSP kernels can't run Sense ROMs. I have no idea why though. I would have thought all it takes is some small modification of the Andromadus 3.x kernel.
On a positive note, this would be awesome and I'd much rather use Sense 5 than previous Sense versions, namely because I can't live without gapless playback which ICS lacks. I would like to help but I currently lack a booting computer although I hope this is remedied soon!

HTCDreamOn said:
@_MarcoMarinho_ good idea, although I think it would be a hard undertaking:
* Other members and I have tried porting JellyBean ROMs but we don't yet know of a way to get the hardware keyboard fully working (lights, auto rotate, etc.);
* That ROM you linked still appears to be in alpha state, perhaps it's best to wait until everything is functioning on that first or look for Sense 5 on another similar device (although the Desire HD has the advantage of being the same resolution which makes everything much easier);
* All of the Desire Z developers working on JellyBean pretty much abandoned 4.1.2 in order to start work on 4.2.2 so unless Sense 5 can be ported to 4.2.2 this could cause problems because I know that many improvements were made, for example in cn.fyodor's AOSP JB, between these two versions;
* The Desire Z has limited RAM and Sense is very heavy, although HTC may have remedied this in Sense 5 so it may run fine;
* I wouldn't even know where to begin on the kernel, all I know is that Sense kernels can't run AOSP ROMs and AOSP kernels can't run Sense ROMs. I have no idea why though. I would have thought all it takes is some small modification of the Andromadus 3.x kernel.
On a positive note, this would be awesome and I'd much rather use Sense 5 than previous Sense versions, namely because I can't live without gapless playback which ICS lacks. I would like to help but I currently lack a booting computer although I hope this is remedied soon!
Click to expand...
Click to collapse
Yes, but we can build the kernel with ION support. Then we only need to take the files from HTC Desire HD e replace some to make it work on our device. The only thing we need to create/build is the kernel, so won't be difficult right?
BTW, @HTCDreamOn , I saw that you took the kernel for saga and make it work on vision, so you can do the same right? They had the kernel source in the thread :good:
Regards,
Marco Marinho

As mentioned, I think sense 5 is too heavy for our device. The desire HD has an additional 256 MB of ram over our device. A fully functional CM11 is probably the best we can ask for our device.

sharptv said:
As mentioned, I think sense 5 is too heavy for our device. The desire HD has an additional 256 MB of ram over our device. A fully functional CM11 is probably the best we can ask for our device.
Click to expand...
Click to collapse
Sense 5 is not so heavy, and I am pretty sure it will work great on DZ. Only problem is kernel and drivers (biggest problem).

sharptv said:
As mentioned, I think sense 5 is too heavy for our device. The desire HD has an additional 256 MB of ram over our device. A fully functional CM11 is probably the best we can ask for our device.
Click to expand...
Click to collapse
The only thing that is impossible is the impossibility As @coolos said the only problem is the kernel and drivers :highfive:
coolos said:
Sense 5 is not so heavy, and I am pretty sure it will work great on DZ. Only problem is kernel and drivers (biggest problem).
Click to expand...
Click to collapse
But if others do it, so we can do it
Regards,
Marco Marinho

Ok first of all most people are having difficulties booting Dr.Globs Sense5 atm,
so I suggest either trying Unimaginable (IncS section) or Imaginable (DHD section), both confirmed booting fine, or of you want Sense4+, link to AceTify is in my sig. Obviously you need ION kernel to boot any of these. Of course that's for testing/debuging only, you need a permission if you choose to release re-ported ROM
sharptv said:
As mentioned, I think sense 5 is too heavy for our device. The desire HD has an additional 256 MB of ram over our device. A fully functional CM11 is probably the best we can ask for our device.
Click to expand...
Click to collapse
Desire 300 has 512MB and is running Sense5 lite.

-SmOgER said:
Ok first of all most people are having difficulties booting Dr.Globs Sense5 atm,
so I suggest either trying Unimaginable (IncS section) or Imaginable (DHD section), both confirmed booting fine, or of you want Sense4+, link to AceTify is in my sig. Obviously you need ION kernel to boot any of these. Of course that's for testing/debuging only, you need a permission if you choose to release re-ported ROM
Desire 300 has 512MB and is running Sense5 lite.
Click to expand...
Click to collapse
I'm not saying to port from snese 5 Dr.Globs, I only quoted a thread that he opened, I only quoted to show that the differences BTW Desire Z and Desire HD aren't much. We only need to change a little things to make it work on our device.
The first step is porting the kernel with ION support. I'm currently working on it :highfive:
I will facing unkown problems. I already tryed to change the source code, update the toolchain and is the same
-SmOgER, can you help me with this. Look at the attachments please
Regards,
Marco Marinho

Ask @coloured_chalk or @tweakos,
I'am not very big expert on kernels.

_MarcoMarinho_ said:
I'm not saying to port from snese 5 Dr.Globs, I only quoted a thread that he opened, I only quoted to show that the differences BTW Desire Z and Desire HD aren't much. We only need to change a little things to make it work on our device.
The first step is porting the kernel with ION support. I'm currently working on it :highfive:
I will facing unkown problems. I already tryed to change the source code, update the toolchain and is the same
-SmOgER, can you help me with this. Look at the attachments please
Regards,
Marco Marinho
Click to expand...
Click to collapse
you use wrong make syntax the proper should look something like
Code:
make ARCH=arm CROSS_COMPILE=$CROSS_COMPILE -j`grep 'processor' /proc/cpuinfo | wc -l`
You set CROSS_COMPILE var with the path to yours toolchain but didnt use it later. Another missed part is ARCH . Also -j with CPU thread num will decrease compilation time
Look at http://oldwiki.cyanogenmod.org/wiki/Building_Kernel_from_source for more info
ps ION support is kind of easy if the kernel sources are with proper drivers for it. When I have time to work over my kernel I should update the drivers to be able to add ION support.
Cheers

Neo2SHYAlien said:
you use wrong make syntax the proper should look something like
Code:
make ARCH=arm CROSS_COMPILE=$CROSS_COMPILE -j`grep 'processor' /proc/cpuinfo | wc -l`
You set CROSS_COMPILE var with the path to yours toolchain but didnt use it later. Another missed part is ARCH . Also -j with CPU thread num will decrease compilation time
Look at http://oldwiki.cyanogenmod.org/wiki/Building_Kernel_from_source for more info
ps ION support is kind of easy if the kernel sources are with proper drivers for it. When I have time to work over my kernel I should update the drivers to be able to add ION support.
Cheers
Click to expand...
Click to collapse
Now works *-* Thnks bro, really thnks :highfive:
Once again, error -_-
Regards,
Marco Marinho

_MarcoMarinho_ said:
Now works *-* Thnks bro, really thnks :highfive:
Once again, error -_-
Regards,
Marco Marinho
Click to expand...
Click to collapse
Try different toolchain. If you use linaro 4.8 try older version 4.7 or 4.6

Good news guys,
Kernel - BOOTS :victory:
And I get it the drivers :good:
So the next step it's port it. I will check if the ion support it's enabled
Check op for more information.
Happy new year to everyone

Ok, first try porting sense 5.
At the begin graphics glitches and then black screen, reboots and do the same :crying:
Gona try with a different kernel :highfive:
Feedback soon.

FAILED!
Trying to do a clean kernel now. I will build ASAP. Keep your Eyes Open

As I don't know anything about that kind of stuff, all I can do is wish you good luck and thank you for keeping our dear old device alive
All the best for 2014 man !

_MarcoMarinho_ said:
FAILED!
Trying to do a clean kernel now. I will build ASAP. Keep your Eyes Open
Click to expand...
Click to collapse
is there any Navigation Bar option available in this upComing ROM?

try porting this unless you found a D300 one already o.o
http://forum.xda-developers.com/showthread.php?t=2584435

Can we fix Cyanogenmod12(cm12) bugs with the help of cyanogenmod11(cm11)?

I have been practicing c,c++,java,php,html since 5 years now i am making android apps its been 5 months doing that.I also have been rooting android devices and flashing custom roms since 2 years now I want to get my hands into porting Custom Roms for various devices. Since I dont know anything so I just want to know about how can I do this. Well making a complete rom will be not possible way to learn completely at once this is what I think. But now I am having two custom roms Cyanogenmod11 and Cyanogenmod12 for a low end device named Samsung galaxy fame gt-s6812 somebody has ported these roms for this device.Now, cm11 is working really very fine but cm12 having lot of bugs : 1.Microphone not working 2.Speaker not working 3.Unkown Baseband and IMEI number etc. I just thought that by just replacing some of the things like folders or files from cm11 to cm12 will work for this. Because many people are porting roms by just copying folders from one into another.
If this can be happened then which folders will get me rid of these bugs. Please help me out Links , explanations, videos anything which can give knowledge about all these stuffs. Thank you

Try to send @wulsic or @corsicanu a message, those two are main developers for out Galaxy Fame section.

dushyant30suthar said:
I have been practicing c,c++,java,php,html since 5 years now i am making android apps its been 5 months doing that.I also have been rooting android devices and flashing custom roms since 2 years now I want to get my hands into porting Custom Roms for various devices.
Click to expand...
Click to collapse
Well, its not as easy as copy and pasting because in the cm12.1 repository there are made some changes which removes compatibility with jellybean 4.1 based binaries so we are using patches to add back that compatibility and also for telephony etc. So we are on the way to get a good working cm12.1 the build with which I am busy with should work much better as the cm12 alpha0.1 as the dpi,sound,performance,security,telephony, microphone, video playback should be fixed. The only problem I still have to find out is why the rom is stuck at starting apps. If you want you can help to get it fully working as I dont own the device and the fame from corsicanu is still broken I believe. If you want to start compiling cm12.1 for the fame then you can look in the general section there is a compiling tutorial but beware I must edit it/ make a new one for cm12.1 so if you want more help or info just contact me. I am not a pro with all these things but I can give you the basics :good:
Sent from my LG-D802 using Tapatalk

@dushyant30suthar
appreciate u want to help
u can follow instruction to download cm12.1 from guide made by wulsic
change repo init to. ... https://github.com/cyanogenmod/android (at that link u can find the guide to download the source code)
u also can check the device tree https://github.com/wulsic/android_device_samsung_nevisp
https://github.com/wulsic/android_vendor_samsung_nevisp
kernel : https://github.com/wulsic/Hyper_CM11
and the patches from pawitp who working cm11-12.1 for broadcom chipset (grand duos) : https://gist.github.com/pawitp/88a1d4514a0734c866c7 ( try to change some line to work with our hardware phone)
good luck :*
*i am stuck at building the rom with external hdd,it will change all the file (git status modfied)

I hope that the developers could fix a lot of bugs in cm12.1, faizauthar12 and wulsic are doing a great job!

There's already a good-working ROM out (at least for S6810):
http://forum.xda-developers.com/showthread.php?p=63426739

faizauthar12 said:
@dushyant30suthar
appreciate u want to help
u can follow instruction to download cm12.1 from guide made by wulsic
change repo init to. ... https://github.com/cyanogenmod/android (at that link u can find the guide to download the source code)
u also can check the device tree https://github.com/wulsic/android_device_samsung_nevisp
https://github.com/wulsic/android_vendor_samsung_nevisp
kernel : https://github.com/wulsic/Hyper_CM11
and the patches from pawitp who working cm11-12.1 for broadcom chipset (grand duos) : https://gist.github.com/pawitp/88a1d4514a0734c866c7 ( try to change some line to work with our hardware phone)
good luck :*
*i am stuck at building the rom with external hdd,it will change all the file (git status modfied)
Click to expand...
Click to collapse
Do anyone have cm12.1, Cm13 cm14 for Samsung Galaxy fame Gt-s 6812 please give me a link :good:

Abu Swalih 1 said:
Do anyone have cm12.1, Cm13 cm14 for Samsung Galaxy fame Gt-s 6812 please give me a link :good:
Click to expand...
Click to collapse
Did you check the link for CM12.1 in the post above yours?

:confused
BenjyTec said:
Did you check the link for CM12.1 in the post above yours?
Click to expand...
Click to collapse
Nop but I don't see name Samsung Galaxy fame Gt-s 6812 show me link please

I'm using cyanogenmod 12.1 on my samsung galaxy fame everything working only SIM card no when I was instaling that say SIM card no detected bat I have it inserted so I don't know what do?

AOSP ROM?

What would it take to see a base AOSP ROM put together for the LG G4? I know there's some folks working hard at bringing CM to the G4, but what about an AOSP unmodified ROM with drivers, of course? I've always wondered if that is a better option than say a ROM like CM which has loads of known bugs and issues.
Maybe an AOSP super-stock setup which we could modify after via Xposed / Mods to add in what we want would be a better option?

CJ-Wylde said:
What would it take to see a base AOSP ROM put together for the LG G4? I know there's some folks working hard at bringing CM to the G4, but what about an AOSP unmodified ROM with drivers, of course? I've always wondered if that is a better option than say a ROM like CM which has loads of known bugs and issues.
Maybe an AOSP super-stock setup which we could modify after via Xposed / Mods to add in what we want would be a better option?
Click to expand...
Click to collapse
After we finish the device tree and everything is working, it can be then used to build whatever Rom you desire

You rock, thank you for the quick response! I'm not even sure what kind of rom I desire. I just know it would be neat to go full on basic AOSP and add from there without some of the clutter and bugs introduced with CM's stuff, although CM has always been an enjoyable experience. Whoot for guys like you!

I know this is old thread... but what source tree are we talking about here? Obviously not AOSP itself, i think... right?
CM source?
Maybe i'm missing something about branches of AOSP... and other trees..
many thanks
mythos234 said:
After we finish the device tree and everything is working, it can be then used to build whatever Rom you desire
Click to expand...
Click to collapse

thenextdon13 said:
I know this is old thread... but what source tree are we talking about here? Obviously not AOSP itself, i think... right?
CM source?
Maybe i'm missing something about branches of AOSP... and other trees..
many thanks
Click to expand...
Click to collapse
They talked about device tree here. An example for a pure AOSP one for the device LG H815 is here:
https://github.com/cile381/android_device_h815
See this for an explanation :
http://wp.me/p6ZeCY-3p
AOSP source contains the sources to build a ROM which are the same for all devices and a device tree is a device specific description on how to build or as the above link states:
“A device tree is a tree data structure with nodes that describe the physical devices in a system”
.
Sent from my LG-H815 using XDA Labs

Thank you, steadfasterX.
That provides some clarity, although I think there is still a bit missing for me--
Ugh, i can't post links because of spam rules.. :-/ makes describing things harder.
How did you find the github cile381/android_device_h815 as being the AOSP tree for that phone? My understanding was that the AOSP main repo is here:
android.googlesource.com
And so related to my question previously.. i guess i'm confused specifically who the 'we' is that mythos234 references, and where that source would be located...
many thanks!

Kernel 3.4.0_1.52.1540.5

I'm aiming to build kernel 3.4.0 (1.52.1540.5) from the Source Code Released by www.htcdev.com last year
I Need your help, Can't do it all alone. So, please if anyone have some time,
do spare it here sharing the knowledge about building it from Source Code, once we get the New Kernel we can Easily Compile the New ROM for Example Android 4.4.2 for the Device.
Hoping to have some Assistance
Thanks
V_Singh

Hello my friend, please send me the CWM backup
Please I'm Begging

tanaydin123 said:
Hello my friend, please send me the CWM backup
Please I'm Begging
Click to expand...
Click to collapse
You Want the ROM backup or Just the CWM?

Unfortunately, you don't have backup ROM nice and fast ROM you are using please, I want to backup my ROM please don't Flash ROM HTC 616 quick and useful mod please ...I'm so boring
Sent from my HTC 616 Dual Sim using XDA Free mobile app

Hey bro, as i know you cannot compile rom without device and vendor tree but if you have a device and vendor tree you can compile rom and for kitkat rom required 3.4.67 kernel if i remember true also i am working compile 3.4.67 kernel for d616 and trying the find or create a new device and vendor tree with my friend but i don give 100% guarantee if i make a kitkat rom for d616 i will share at xda-developers and i will build cyanogenmod for d616 but i dont give any 100% guarantee because i am student and i have a exams but i try @v_singh and i have a d616

I too was thinking to do that , but was busy for last few months . Maybe we can build up a team first (Development is faster that way) .

Forget about it i will not make kitkat for we device because yesterday i received a call from htc and says to me "kitkat for desire 616 will get but now in development proccess" and if kitkat release for we device i will port cm11 for we devices but with a little bugs (video recording, second... sim etc.)

ritikchanna said:
I too was thinking to do that , but was busy for last few months . Maybe we can build up a team first (Development is faster that way) .
Click to expand...
Click to collapse
Nice !dea @ritikchanna , but Sometimes I really Don't have time, and also its gone complicated Since I Upgraded my PC to WIN10, things aren't working on it as expected
Ozanerd said:
Forget about it i will not make kitkat for we device because yesterday i received a call from htc and says to me "kitkat for desire 616 will get but now in development proccess" and if kitkat release for we device i will port cm11 for we devices but with a little bugs (video recording, second... sim etc.)
Click to expand...
Click to collapse
Well, that's their Job Bro but, I'm not really sure they will spare time on our Device, and I don't have money to Buy new phone, so i'm just trying to do things on my own with your help, I'm still not sure I can manage it, but its always good to give a shot!
Ozanerd said:
Hey bro, as i know you cannot compile rom without device and vendor tree but if you have a device and vendor tree you can compile rom and for kitkat rom required 3.4.67 kernel if i remember true also i am working compile 3.4.67 kernel for d616 and trying the find or create a new device and vendor tree with my friend but i don give 100% guarantee if i make a kitkat rom for d616 i will share at xda-developers and i will build cyanogenmod for d616 but i dont give any 100% guarantee because i am student and i have a exams but i try @v_singh and i have a d616
Click to expand...
Click to collapse
Thanks, for the Information bro, its good to know what n what I can do with the available resources, and of now, I have Downloaded the SOURCE CODE from www.htcdev.com for HTC 616D and I also have the Device with me, now can you tell me, what n what I need next?
tanaydin123 said:
Unfortunately, you don't have backup ROM nice and fast ROM you are using please, I want to backup my ROM please don't Flash ROM HTC 616 quick and useful mod please ...I'm so boring
Click to expand...
Click to collapse
Hey Pal! don't get stressed, and also pardon me for getting so late, if I upload my whole rom backup, it would be long and idk if my slow internet can handle that much big file to Upload, well well! just make your ROM DE-ODEXED and download this and follow the README inside :good:
Sent from my HTC 616 Dual Sim using XDA Free mobile app[/QUOTE]

You need the vendor, device and kernel source for desire 616 but kernel must be 3.4.67 if i know true for kitkat @v_singh

Update: Success on compiling
I got Success On Compiling the New Kernel (zImage) from the Source Code (Special thanks to @op3n_sourc3), and Building the BOOT.IMG,
but the Problem is When I'm flashing it, the Device doesn't boots up,
a little help would be Appreciated, Anyone?

v_singh said:
I got Success On Compiling the New Kernel (zImage) from the Source Code (Special thanks to @op3n_sourc3), and Building the BOOT.IMG,
but the Problem is When I'm flashing it, the Device doesn't boots up,
a little help would be Appreciated, Anyone?
Click to expand...
Click to collapse
Please share the download links or PM me I will look into it

v_singh said:
I got Success On Compiling the New Kernel (zImage) from the Source Code (Special thanks to @op3n_sourc3), and Building the BOOT.IMG,
but the Problem is When I'm flashing it, the Device doesn't boots up,
a little help would be Appreciated, Anyone?
Click to expand...
Click to collapse
That's a great news. Does it show the htc logo or stuck on black screen? Could you capture the log? If yes, capture the Log with ALV(Advanced Logcat Viewer) and upload it here.

We are too lucky to get Devs like you guys 
 @arun483 please check the attached file :good:
 @abhatia1435 actually I have messed up with my boot logo, so I can't see if anything going on underneath, but when I power on, it shows the broken boot n then reboots again (same like bootloop) but will try to capture the log.
And also I have a Question "do we need newer Rom to boot newer version of Kernel?"
Caution: for the other users , this file is only for Development Purpose, Do Not Flash it until you Know what you are doing. BE SMART, STAY SAFE.

Any Update @arun483 ?

v_singh said:
We are too lucky to get Devs like you guys
@arun483 please check the attached file :good:
@abhatia1435 actually I have messed up with my boot logo, so I can't see if anything going on underneath, but when I power on, it shows the broken boot n then reboots again (same like bootloop) but will try to capture the log.
And also I have a Question "do we need newer Rom to boot newer version of Kernel?"
Caution: for the other users , this file is only for Development Purpose, Do Not Flash it until you Know what you are doing. BE SMART, STAY SAFE.
Click to expand...
Click to collapse
Sorry I just got busy in some family functions I will look into it and let you know what we can do.
---------- Post added at 06:47 PM ---------- Previous post was at 06:39 PM ----------
@v_singh so first things first you messed up with boot and stuck in boot loop? NP you can easily find stock boot.img flash it using spflashtool
Need boot logo? I can make one and link you through pm
"do we need newer Rom to boot newer version of Kernel?" No it's actually visa versa, you need newer kernel to boot newer rom. We can port upto Android MarshMallow based on 3.4.67 kitkat kernel but not on jelly bean kernel. I can port some mediamods based on jellybean if you want

arun483 said:
Sorry I just got busy in some family functions I will look into it and let you know what we can do.
---------- Post added at 06:47 PM ---------- Previous post was at 06:39 PM ----------
@v_singh so first things first you messed up with boot and stuck in boot loop? NP you can easily find stock boot.img flash it using spflashtool
Need boot logo? I can make one and link you through pm
"do we need newer Rom to boot newer version of Kernel?" No it's actually visa versa, you need newer kernel to boot newer rom. We can port upto Android MarshMallow based on 3.4.67 kitkat kernel but not on jelly bean kernel. I can port some mediamods based on jellybean if you want
Click to expand...
Click to collapse
the boot logo is another Cause that i have solved already
but the Kernel is not Still Booting, Did you guys found anything ?

v_singh said:
the boot logo is another Cause that i have solved already
but the Kernel is not Still Booting, Did you guys found anything ?
Click to expand...
Click to collapse
I don't have device in my hands right jow so I am waiting till device arrives so that I can start work on kernel

hello v singh
Hello v singh have u got the reason of why the kernel is not booting

Good

How can i port rom

@bigsupersquid , can you tell me how can i port a rom for a5dwg like miui 8 or LOS 13
And secondly, how can i change RIL in sense7prerooted by xxminiwhooperxx. I am not abpe to get signals in that rom can you please help!

@rjcool1999

singhjot0020 said:
@bigsupersquid , can you tell me how can i port a rom for a5dwg like miui 8 or LOS 13
And secondly, how can i change RIL in sense7prerooted by xxminiwhooperxx. I am not abpe to get signals in that rom can you please help!
Click to expand...
Click to collapse
https://forum.xda-developers.com/chef-central/android/guide-tool-projekt-scribt-v1-33-t3503018
And second question, nobody did it that I'm aware of.
RIL has to be different in init in ramdisk like chl built-from-scratch rom, probably.

bigsupersquid said:
https://forum.xda-developers.com/chef-central/android/guide-tool-projekt-scribt-v1-33-t3503018
And second question, nobody did it that I'm aware of.
RIL has to be different in init in ramdisk like chl built-from-scratch rom, probably.
Click to expand...
Click to collapse
For example, when you compile a rom for a5dwg and the same rom for chl, what is the difference between them!
And what shall i do to do the same

singhjot0020 said:
For example, when you compile a rom for a5dwg and the same rom for chl, what is the difference between them!
And what shall i do to do the same
Click to expand...
Click to collapse
For what you want, look at the device github (link in rom thread first post) and compare device_htc_a5ul and a5dwg, especially init and ril C files.
I can tell you the RIL binaries from the stock rom work on the whole little family of devices in marshmallow, so no need to mess with the ones in system/vendor.
I can't get more detailed, like I said, nobody already did it. No specific guide.