Database Info

Trying to port kernel 3.0 for i9003, please help

Hello,
I have been porting kernel 3.0 to i9003 since last month.
Now, platform specific codes and most of the drivers are ported.
Today, I am able to finish the kernel build with minor warnings.
but I have problems customizing the init scrits to be used with the kernel.
Any help from more experience devs would be appreciated
Current status:
- Platform specific code and all drivers except battery are ported.
- The kernel is built successfully
- trying to pack it into normalboot.img
I can release the source now due to its size. ( asking a guy at github to increase my storage space). But will do asap.
Sorry to post in the wrong forum but I dont have permission to post in the dev forum.

crackerizer said:
Hello,
I have been porting kernel 3.0 to i9003 since last month.
Now, platform specific codes and most of the drivers are ported.
Today, I am able to finish the kernel build with minor warnings.
but I have problems customizing the init scrits to be used with the kernel.
Any help from more experience devs would be appreciated
Current status:
- Platform specific code and all drivers except battery are ported.
- The kernel is built successfully
- trying to pack it into normalboot.img
I can release the source now due to its size. ( asking a guy at github to increase my storage space). But will do asap.
Sorry to post in the wrong forum but I dont have permission to post in the dev forum.
Click to expand...
Click to collapse
Thank u very much! You could contact dhiru
Sent from my GT-I9003 using XDA

Great...but main question is that whether device boot or not??? Because many people have successfully compiled kernel 3.0 but device doesnt boot.

vishal24387 said:
Great...but main question is that whether device boot or not??? Because many people have successfully compiled kernel 3.0 but device doesnt boot.
Click to expand...
Click to collapse
That what I'm going to find out. For now, I'm trying to modify the init script and looking for help from some devs here to speed it up.

my wish- that you release it as fast as you can

R u using
This?
i have also used this guide n compiled a kernel 3.0 successfully packed it using dhiru's boot.img from alpha 6
i have also modified sum codes
but still no luck i think these files need alot of config changes!!!!
n lastly best of luck i hope u get success

sachin sharma said:
R u using
This?
i have also used this guide n compiled a kernel 3.0 successfully packed it using dhiru's boot.img from alpha 6
i have also modified sum codes
but still no luck i think these files need alot of config changes!!!!
n lastly best of luck i hope u get success
Click to expand...
Click to collapse
sachin sharma, can you explain your procedure during your port? I'll compare with mine to see if we do the same thing.
After checking the boot script, I don't think we can just do a drop-in replacement. I think modifying the init script is needed (and i'm working on it). Also, There are some changes in the kernel which can cause problem with the ported code. I'm thinking about droping RFS and J4FS support in the new kernel (and probably abandon all samsung code).

crackerizer said:
sachin sharma, can you explain your procedure during your port? I'll compare with mine to see if we do the same thing.
After checking the boot script, I don't think we can just do a drop-in replacement. I think modifying the init script is needed (and i'm working on it). Also, There are some changes in the kernel which can cause problem with the ported code. I'm thinking about droping RFS and J4FS support in the new kernel (and probably abandon all samsung code).
Click to expand...
Click to collapse
I will suggest u to start ur thread in development thread. In general section developers mostly dont come here. Also u should upload ur source code to github. It will help to other developers to look into ur source code & find out the problem.

vishal24387 said:
I will suggest u to start ur thread in development thread. In general section developers mostly dont come here. Also u should upload ur source code to github. It will help to other developers to look into ur source code & find out the problem.
Click to expand...
Click to collapse
He needs to pump up his post count first buddy
Sent from my GT-I9100 using xda premium

ephraim033 said:
He needs to pump up his post count first buddy
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
oh...I forgot about that Anyway how many posts one has to do so that he can post a thread in development section?

vishal24387 said:
oh...I forgot about that Anyway how many posts one has to do so that he can post a thread in development section?
Click to expand...
Click to collapse
Not sure, i think it's 10?
Sent from my GT-I9100 using xda premium

ephraim033 said:
Not sure, i think it's 10?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Yes, 10!

crackerizer said:
sachin sharma, can you explain your procedure during your port? I'll compare with mine to see if we do the same thing.
After checking the boot script, I don't think we can just do a drop-in replacement. I think modifying the init script is needed (and i'm working on it). Also, There are some changes in the kernel which can cause problem with the ported code. I'm thinking about droping RFS and J4FS support in the new kernel (and probably abandon all samsung code).
Click to expand...
Click to collapse
all we need is config file in /arch/arm/config for kernel 3.0 for our devices
all we have now is config file for kernel 2.6.7 thats wats preventing our devices to boot
i followed same procedure mentiond in that blog after that i used zoom config file edit it at some places wer i thought shud be a change like device name to galaxy sl etc
renamed it latona_galaxy_sl
even then no benefit but i havn't givn hope m still trying!!!!
main problem is that we dont know how to configurate config file as "make config" command gives a hell lot of options!!!!

@crackeziner is your 3.0 kernel booting ?

anuraagkochar said:
@crackeziner is your 3.0 kernel booting ?
Click to expand...
Click to collapse
Probably not.
Booting itself is the main problem .. lol.
All my attempts to port this failed miserably.

Skander1998 said:
Probably not.
Booting itself is the main problem .. lol.
All my attempts to port this failed miserably.
Click to expand...
Click to collapse
what can do now??

Skander1998 said:
Probably not.
Booting itself is the main problem .. lol.
All my attempts to port this failed miserably.
Click to expand...
Click to collapse
Just give it try. Don't let it down guys
Sent from my GT-I9003 using XDA

sachin sharma said:
all we need is config file in /arch/arm/config for kernel 3.0 for our devices
all we have now is config file for kernel 2.6.7 thats wats preventing our devices to boot
i followed same procedure mentiond in that blog after that i used zoom config file edit it at some places wer i thought shud be a change like device name to galaxy sl etc
renamed it latona_galaxy_sl
even then no benefit but i havn't givn hope m still trying!!!!
main problem is that we dont know how to configurate config file as "make config" command gives a hell lot of options!!!!
Click to expand...
Click to collapse
I have gone far more than that . All latona specific codes are ported not only the defconfig file. Most drivers (LCD, power switch, camera, etc.) are also ported. I'm now modifying the init script to match what the kernel have now. Hopefully it will boot.

crackerizer said:
I have gone far more than that . All latona specific codes are ported not only the defconfig file. Most drivers (LCD, power switch, camera, etc.) are also ported. I'm now modifying the init script to match what the kernel have now. Hopefully it will boot.
Click to expand...
Click to collapse
u mentiond that u r getting errors while compiling right?
that means ur deconfig file is still not correct
all the codes needs to be changed according to "kernel 3.0"
not by porting codes from other kernels or previous kernels
n lastly all drivers are already given in the source code thers nothing to change in it except that u just have to compile!!!!!!

crackerizer said:
I have gone far more than that . All latona specific codes are ported not only the defconfig file. Most drivers (LCD, power switch, camera, etc.) are also ported. I'm now modifying the init script to match what the kernel have now. Hopefully it will boot.
Click to expand...
Click to collapse
But did it boot?? Did u test that? When do u think u will be able to test that?

Galaxy Y Stock Kernel compiled from source

Hello Guys, I would like to present you my first SGY kernel which I have compiled from source. This is only for Stock or Stock based ROMs.
Features :
1) Loads of governors like userspace,ondemand,powerspace,conservative etc. so that users will not get biased towards only one configuration
2) I/O schedulers like noop and cfq with cfq as a default scheduler
3) Max frquency 832 Mhz and min frequency 312 which I found the best in terms of battery and performance because Overclocking decreases the life of Phone.
I am currently lookoing forward to add Extra I/O Schedulers although cfq is best out there with Conservative governors in my opinion. CPU underclocking will be in my roadmap as well. I hope you guys will appreciate me.
Steps for Installing/Flashing :
1) First reboot into recovery and flash any CWM recovery(Note: don't flash it through stock recovery directly)
2) Go to mounts/Storage and mount everything system,cache,sd-card
3) Now flash the Zip I have provided
4) Now Wipe cache partition from Main menu
5) from Advanced option-> wipe dalvik cache and reboot
I have tested it myself.Please report in case you guys run into any issues.
Credits :
To me Of course
@google
@samsung for providing kernel source
GitHub :
https://github.com/lokesh3440/Galaxy_Y_Stock_Kernel
Kernel Sources :
https://github.com/lokesh3440/Galaxy_Y_Kernel_Source
Changelog:
V2 Build execution is in Progress.......I just checked. V1 works pretty well with Hyperion V9.
Initial Build
Here are few Screenshots :
Don't forget to submit logcats in case you run into any issues.

Testing now...
Sent from my GT-S5360 using Tapatalk 2

İ will test it
Sent from my GT-S5360 using xda app-developers app

Initial impressions
1)Performance seems decent.
2)No support for amarulzz a2sd
3)No CWM integrated
4)Deepsleep not working.
Cant talk about battery so soon.
Sent from my GT-S5360 using Tapatalk 2

Souroking said:
Initial impressions
1)Performance seems decent.
2)No support for amarulzz a2sd
3)No CWM integrated
4)Deepsleep not working.
Cant talk about battery so soon.
Sent from my GT-S5360 using Tapatalk 2
Click to expand...
Click to collapse
I will add amarullz a2Sd support and integrated CWM recovery very soon. I still need to check why deep sleep isn't working. Thanks for feedback.

lokesh.3440 said:
I will add amarullz a2Sd support and integrated CWM recovery very soon. I still need to check why deep sleep isn't working. Thanks for feedback.
Click to expand...
Click to collapse
İ'm waiting for CWM
Sent from my GT-S5360 using xda app-developers app

Hello,
According to XDA Rule on GPL and Apache Compilence
For kernel developers: You must provide FULL source code, not just the edits you made (reference here). Your source code must also be up-to-date with any binary releases. If in doubt, update your github first, then release the binary, NOT the other way round.
Click to expand...
Click to collapse
the stuff you have provided on your github is only the kernel.
You have to upload the whole source code you've used while compiling this kernel.Do it ASAP if you didnt knew it.Or your thread will be closed soon.
Take this as a suggestion :good:
Regards.

DC07 said:
Hello,
According to XDA Rule on GPL and Apache Compilence
the stuff you have provided on your github is only the kernel.
You have to upload the whole source code you've used while compiling this kernel.Do it ASAP if you didnt knew it.Or your thread will be closed soon.
Take this as a suggestion :good:
Regards.
Click to expand...
Click to collapse
Thanks for your suggestion brother. This is my first contribution,that's why i wasn't aware of it. Do you mean the Samsung open source update which i have used to compile it ?
can you guide me how exactly i need to update it ?

deep sleep is present in stock kernel too.
only states files is not enabled/present.
if cpu spy is displaying freq. usage and deepsleep is notshowing up then there is some problem.
else by default its enabled in stock kernel.

Nitzz said:
deep sleep is present in stock kernel too.
only states files is not enabled/present.
if cpu spy is displaying freq. usage and deepsleep is notshowing up then there is some problem.
else by default its enabled in stock kernel.
Click to expand...
Click to collapse
But CPU spy says "kernel is not compatible".......

lokesh.3440 said:
Thanks for your suggestion brother. This is my first contribution,that's why i wasn't aware of it. Do you mean the Samsung open source update which i have used to compile it ?
can you guide me how exactly i need to update it ?
Click to expand...
Click to collapse
in simple words,upload your whole directory i.e common and modules of your modified samsungopensource folder :good:

DC07 said:
in simple words,upload your whole directory i.e common and modules of your modified samsungopensource folder :good:
Click to expand...
Click to collapse
Thanks, I will upload it on my github in the evening.

Well anybody tried compiling the kernel on Ubuntu 14.04? Gonna try it today! xD

lokesh.3440 said:
But CPU spy says "kernel is not compatible".......
Click to expand...
Click to collapse
check again.
its says- states file not found.
kernel is not compatible with that app cz freq. states file is disabled by default.
but deepsleep is enabled in kernel.
also the kernel u build is having old source.
latest kernel from samsung in update like dxmj is best n having many changes.
just add init.d support in it and compare the battry life with ur kernel.
and that stock one is far more stable than urs.
no offense
but untill and unless u add some more features in it, stock kernel will still be my preferred choice.
add more featrs into it to make it better than stock one.

aniket.lamba said:
Well anybody tried compiling the kernel on Ubuntu 14.04? Gonna try it today! xD
Click to expand...
Click to collapse
I have built it on ubuntu 14 only
Sent from my GT-I9505 using Tapatalk

lokesh.3440 said:
I have built it on ubuntu 14 only
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
You serious?
That's good.Gonna try soon!

Good one... :good:
the problem is it seems to have update2 source.... :-/
can run newer firmwares (ddmd,dxmj, etc).
Looking forward to this one. Please use update3 in the next one. Best of luck
P.S. As @Nitzz Said, Deep sleep is pre-included. if u have used the defconfig command, it is included in the kernel. try adding cpu_stats file...

Nachiket.Namjoshi said:
Good one... :good:
the problem is it seems to have update2 source.... :-/
can run newer firmwares (ddmd,dxmj, etc).
Looking forward to this one. Please use update3 in the next one. Best of luck
P.S. As @Nitzz Said, Deep sleep is pre-included. if u have used the defconfig command, it is included in the kernel. try adding cpu_stats file...
Click to expand...
Click to collapse
@nachiket,,,I have used Update 3 only,,,,but i forgot to add cpu stats file i guess.......It will be included in the next build. Thanks for your suggestion

lokesh.3440 said:
@nachiket,,,I have used Update 3 only,,,,but i forgot to add cpu stats file i guess.......It will be included in the next build. Thanks for your suggestion
Click to expand...
Click to collapse
see..
told ya.
u can ask anyone of us(senior membrs of sgy section) or anyother kernel dev for help or any doubt if u want.

[KERNEL][3.10 PORTING][DEVS ONLY][S4][VILLE]

FOR DEVS ONLY
THIS IS A DEVELOPMENT THREAD FOR PORTING THE LINUX 3.10 KERNEL TO THE HTC ONE S (VILLE) S4 EDITION
MODERATORS PLEASE DELETE ANY POSTS THAT ARE NOT RELATED TO THE DEVELOPMENT OF THE KERNEL (OTHER THAN THESE FIRST POSTS USED TO CREATE SOME DOCUMENTATION)
XDA:DevDB Information
3.10 Kernel for the HTC One S, Kernel for the HTC One S
Contributors
javelinanddart
Kernel Special Features:
Version Information
Status: Testing
Created 2015-01-15
Last Updated 2015-01-15

This thread is a development thread for porting the Linux 3.10 Kernel to the HTC One S
All Devs are welcome to step forward
https://github.com/javelinanddart/android_kernel_3.10_ville
This will be done from the CM 12 Source Code
This IS NOT an easy task, it will take a lot of time and lot of things will need to be changed
CyanogenMod might have to be rebuilt from source to have this work properly
Look at the mergeconflicts.txt to look for things to fix, look at the fixedconflicts.txt for things that are fixed

Advantages:
-Officially Supported (3.10 is what the Nexus 6 & 9 and Android Wear Devices are Using)
-Future Android Compatibility (Android Framework and Kernel are Decoupled but Still Matters)
-Better Performance (Somewhat)
-Bragging Rights (xD this is a joke)
-Better and Newer Drivers
-More Features
-More Optimized
-Longer Support Date (Most Likely)
-Most Future Devices will Run 3.10 Kernel (Keeps our Device Current)
-Lower RAM Usage
-Support for F2FS (a faster file system for nand flash storage devices)

Contributor List
@intervigil (Ethan Chen)
@AKToronto
@mikronac.ns (Mikronac)

FAQ
Why?
Because I can (lol)
Check the Advantages list

Changelog
Initial Upload of Source
Merge tag v3.10

Resources
http://elinux.org/Kernel_3.4_to_3.10_porting_guide

A lot of the Kconfigs I fixed I just used the 3.10 ones and they're missing a lot of drivers it seems. We might have to readd those Kconfig Options. Also the defconfig will be a pain in the ass to maintain until we have a final product

javelinanddart said:
A lot of the Kconfigs I fixed I just used the 3.10 ones and they're missing a lot of drivers it seems. We might have to readd those Kconfig Options. Also the defconfig will be a pain in the ass to maintain until we have a final product
Click to expand...
Click to collapse
yeah, I am just looking in it...

mikronac.ns said:
yeah, I am just looking in it...
Click to expand...
Click to collapse
1 sec then, I'm merging with the aosp source rather than mainline linux because it includes some android specific changes
Look at the mergeconflicts.txt or try compiling it.....
My god... never seen THAT many errors in the Kconfigs

wow @javelinanddart nice, hope to port this to the m7 soon in time for lollipop, If you are having problems with drivers try taking a look at the evita kernel source, due to its similar hardware

dd98 said:
wow @javelinanddart nice, hope to port this to the m7 soon in time for lollipop, If you are having problems with drivers try taking a look at the evita kernel source, due to its similar hardware
Click to expand...
Click to collapse
Sounds good, but does Evita have a 3.10 kernel? Hopefully HTC will do that because usually they're pretty OK at updating their kernels (if not android versions)
Also @dd98, this is from the Cm12 source so if you want to help, it can possibly be compatible with the M7 @phoenixita if you'd like to help that'd be great too

javelinanddart said:
Sounds good, but does Evita have a 3.10 kernel? Hopefully HTC will do that because usually they're pretty OK at updating their kernels (if not android versions)
Also @dd98, this is from the Cm12 source so if you want to help, it can possibly be compatible with the M7 @phoenixita if you'd like to help that'd be great too
Click to expand...
Click to collapse
I'll gladly help but still only getting there on the kernel development, hope I have some free time

dd98 said:
I'll gladly help but still only getting there on the kernel development, hope I have some free time
Click to expand...
Click to collapse
What's your github username? I'll add you as a collaborator rather than pull requests. It works faster

@javelinanddart F2Fs already works on Ville I already ported it [emoji1]

Flashalot said:
@javelinanddart F2Fs already works on Ville I already ported it [emoji1]
Click to expand...
Click to collapse
I know but this is meant to be like a CM kernel (i.e. no backported features unless absolutely necessary
On a completely unrelated note, how can I build a rom and recovery with f2fs support?

javelinanddart said:
I know but this is meant to be like a CM kernel (i.e. no backported features unless absolutely necessary
On a completely unrelated note, how can I build a rom and recovery with f2fs support?
Click to expand...
Click to collapse
Ahh I see my bad also if I told you I would have to kill you [emoji88]
Jk
I'll be making a thread some time this weekend with full documentation on how to do so especially recovery since we have 3 different types just on twrp

Flashalot said:
Ahh I see my bad also if I told you I would have to kill you [emoji88]
Jk
I'll be making a thread some time this weekend with full documentation on how to do so especially recovery since we have 3 different types just on twrp
Click to expand...
Click to collapse
Thanks. If we can switch to F2FS and use a Universal TWRP, developers will have a better time on source-based ROMs. It will also help speed up the file system actions. I tried compiling twrp but I couldn't figure it out

What source are you editing the 3.4 kernel source or the 3.10 kernel source ?

Wahaj.47 said:
What source are you editing the 3.4 kernel source or the 3.10 kernel source ?
Click to expand...
Click to collapse
"3.10 porting"

[KERNEL][SOON] HakyKernel 3.1.2

Will be updated soon
Issues:
Settings app: closed automatically when activate Bluetooth.
Kernel information: still appear on 3.0.101, i guess modules of MoshKernel should be updated too.
Android rebooting each 10/15 minutes.
Wifi: not working.
Code:
[*]22/04/2015:
-initial build.
-I will make zImage and use as prebuilt kernel in my roms after add arch-capri drivers.

haky 86 said:
After done some google search about to find similar devices to our phone and some guys on Whatsapp group give me some useful information about Samsung Galaxy S Duos 2 that device share same broadcom chipshet but the kernel is more updated (3.4.5), so I decide to port this version to our phone Samsung Galaxy S2.
I start some tests witnout arch-capri drivers in kernel/samsung/3.4/arch/arm just to see if Android boot or not, the result was really fantastic so from today we can port 3.4 kernel without any problems.
Issues:
Settings app: closed automatically when activate Bluetooth.
Kernel information: still appear on 3.0.101, i guess modules of MoshKernel should be updated too.
Android rebooting each 10/15 minutes.
Wifi: not working.
Code:
[*]22/04/2015:
-initial build.
-I will make zImage and use as prebuilt kernel in my roms after add arch-capri drivers.
Click to expand...
Click to collapse
Okey. Is this for stock or asop based roms?

rs tony said:
Okey. Is this for stock or asop based roms?
Click to expand...
Click to collapse
for both roms :good::good:

thanks @haky 86
I think in future u make this phone work so much better than iphone6
your one of the best developer for this phone

SmzAmir said:
thanks @haky 86
I think in future u make this phone work so much better than iphone6
your one of the best developer for this phone
Click to expand...
Click to collapse
Sure once finish 5.1.1 i can recall other devs to share experience and make 3.4 work perfect:thumbup::thumbup:
Sent from my GT-I9105P using XDA Free mobile app

haky 86 said:
for both roms :good::good:
Click to expand...
Click to collapse
amazing work :good: only a question, i am a newbie on android so what will be the difference betwen them?

cracker12 said:
amazing work :good: only a question, i am a newbie on android so what will be the difference betwen them?
Click to expand...
Click to collapse
the differences are:
-roms will be more stable.
-kernel new and updated instead of old stock and slow 3.0.101.
-antutu test result about 13000 points with some fixes may get better result.
-fast booting.
-this version could be useful for android 6 when will out.

haky 86 said:
the differences are:
-roms will be more stable.
-kernel new and updated instead of old stock and slow 3.0.101.
-antutu test result about 13000 points with some fixes may get better result.
-fast booting.
-this version could be useful for android 6 when will out.
Click to expand...
Click to collapse
Thanks... Keep up

[*]23/04/2015:
-drivers are imported without problem.
-now i'm fix compilation errors to see if will done or not.

Hey u make this
It awesome
---------- Post added at 03:40 AM ---------- Previous post was at 03:37 AM ----------
Hope you will fixed the issues in future
Do it have enhanced gpu

Man, you do a lot of great work.

thanks guys but may i wil discontinued this project since no devs are interested to port newer kernel like galaxy w where started from 2.6 and updated up to 3.4..

left it open haky..maybe they are busy for now..we need it bro

haky 86 said:
thanks guys but may i wil discontinued this project since no devs are interested to port newer kernel like galaxy w where started from 2.6 and updated up to 3.4..
Click to expand...
Click to collapse
sad news!
I was really looking forward if someone can port a new kernel, but as you said it's not an easy job and no devs are intrested

haky 86 said:
thanks guys but may i wil discontinued this project since no devs are interested to port newer kernel like galaxy w where started from 2.6 and updated up to 3.4..
Click to expand...
Click to collapse
So this one is really down? Hey, man, we need you, continue your work

why me? the best succeed I got is integrate part of capri's kernel archecture into 3.4 and entire code should be readpted to work on our phone. in case of even ported, I will not release the source coz I will not do the homeworks of others

3.1.2 Kernel
-update patch like 3.0.31 -> 3.0.32 is adapted as well.
-now im apply the patch to update the code see ya.

3.1.2 in progress
I have a question dear @CoolDevelopment I manage to update the kernel of this phone from 3.0.101 to 3.1.2 using the patch of kernel.org's website.
here my questions:
-if got failed patch, should skip them in case can't found it code?
-I saw there are a lot of detected commit that already patched, should be skipped too and apply only the new code?
-is enough just downloading 3.1.2.patch and use patch -p1 method or should download kernel source too.
https://www.kernel.org/pub/linux/kernel/v3.x/
now I'm compiling a zImage seems no errors for now, if boot I will continue the port :good:
thanks in advance

haky 86 said:
I have a question dear @CoolDevelopment I manage to update the kernel of this phone from 3.0.101 to 3.1.2 using the patch of kernel.org's website.
here my questions:
-if got failed patch, should skip them in case can't found it code?
-I saw there are a lot of detected commit that already patched, should be skipped too and apply only the new code?
-is enough just downloading 3.1.2.patch and use patch -p1 method or should download kernel source too.
https://www.kernel.org/pub/linux/kernel/v3.x/
now I'm compiling a zImage seems no errors for now, if boot I will continue the port :good:
thanks in advance
Click to expand...
Click to collapse
Upload your source man, else noone can help you
I hope you don't have just changed the version numbers...

no i didn't, here my new branch
https://github.com/hak86/android_kernel_samsung_galaxys2plus-common/tree/3.1.2-lp
Compilation is work fine, now i will try to compile with make -j4 bootimage to get the modules and use them on nebula's flashable.

[rom][d2303] pac-rom

PAC ROM for D2303
https://onedrive.live.com/redir?res...19&authkey=!AIAixlfmiDf-uR8&ithint=folder,zip
(unfortunately, I have no idea what happened with my Ubuntu, the build process doesn't create a .zip file, you'll have to flash it with fastboot boot/userdata/system)
of all the main things: wifi, mobile data, gps, voice calls working...camera not

installed on d2303 things that do not work.
Camera
proximity sensor
.During the call screen does Not turn off
handsfree speaker
* The data connection works 3G and 4G
themes CM WORKING FINE
everything else PERFECT
great job

Try putting this and the other roms in the right xda section shouldn't they be in the original Android development forum with cm+omni ect just a thought like few screenshots wouldn't go amiss either
D2303 5.1 deodexed z2 port+z5+X apps+themes, be,xr,sv,ad,XZRt2urecovery,xposed,z5 cam2.0,xLOUD,S-Force,viperaudio+more

[email protected] said:
Try putting this and the other roms in the right xda section shouldn't they be in the original Android development forum with cm+omni ect just a thought like few screenshots wouldn't go amiss either
D2303 5.1 deodexed z2 port+z5+X apps+themes, be,xr,sv,ad,XZRt2urecovery,xposed,z5 cam2.0,xLOUD,S-Force,viperaudio+more
Click to expand...
Click to collapse
well, yeah, i honestly didnt know where to put them, because i didnt actually 'develop' them...the build process has errors that need to be fixed but i didnt think it is 'development' so i post them here

quake73 said:
well, yeah, i honestly didnt know where to put them, because i didnt actually 'develop' them...the build process has errors that need to be fixed but i didnt think it is 'development' so i post them here
Click to expand...
Click to collapse
So many roms..i bet your workspace is a mess right now
Local manifest you used for that rom? And can you post the errors? (use the "code" tag or paste them in pastebin and put link here)

Konstantinosj77 said:
So many roms..i bet your workspace is a mess right now
Local manifest you used for that rom? And can you post the errors? (use the "code" tag or paste them in pastebin and put link here)
Click to expand...
Click to collapse
xexe
about the errors that I had, I am more than glad to share them (I have a simple text file and write reminders there, to remember them and not "reinvent the wheel" every time)
For this one, PACROM, I think the only error was 'unsupported relloc 43', the cure is:
cp /usr/bin/ld.gold prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.6/x86_64-linux/bin/ld
(for a long time, i thought the cure was WITHOUT_HOST_CLANG=true)
the manifest is a mess but here it is...i also have created a file in vendor/pac/products and added cm.mk in device/sony/eagle...built it with "build-pac.sh eagle"

quake73 said:
xexe
about the errors that I had, I am more than glad to share them (I have a simple text file and write reminders there, to remember them and not "reinvent the wheel" every time)
For this one, PACROM, I think the only error was 'unsupported relloc 43', the cure is:
cp /usr/bin/ld.gold prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.6/x86_64-linux/bin/ld
(for a long time, i thought the cure was WITHOUT_HOST_CLANG=true)
the manifest is a mess but here it is...i also have created a file in vendor/pac/products and added cm.mk in device/sony/eagle...built it with "build-pac.sh eagle"
Click to expand...
Click to collapse
oh good old "unsupported relloc" i use arch linux and got it in every build.
It's fixed on AOSP master branch https://android-review.googlesource.com/#/c/223100/
CM13 uses this patch too

Konstantinosj77 said:
oh good old "unsupported relloc" i use arch linux and got it in every build.
It's fixed on AOSP master branch https://android-review.googlesource.com/#/c/223100/
CM13 uses this patch too
Click to expand...
Click to collapse
(mine is virtual Ubuntu 16)
i must admit, the 6.0 roms are building 'more flawlessly' than the 5.1 variants....and it seems that 5.1s are not getting any more fixes.
i dont know if you are trying to build any but...i tried building cm12.1 for 2 weeks, with every possible combination of device tree and vendor (SonyAOSP/SonyCM/xperiadev/CM, sony vendor files/Benevolent) and there is no mobile data connection, any ideas?

quake73 said:
(mine is virtual Ubuntu 16)
i must admit, the 6.0 roms are building 'more flawlessly' than the 5.1 variants....and it seems that 5.1s are not getting any more fixes.
i dont know if you are trying to build any but...i tried building cm12.1 for 2 weeks, with every possible combination of device tree and vendor (SonyAOSP/SonyCM/xperiadev/CM, sony vendor files/Benevolent) and there is no mobile data connection, any ideas?
Click to expand...
Click to collapse
Not a single idea...did you checked logcat or something?

Konstantinosj77 said:
Not a single idea...did you checked logcat or something?
Click to expand...
Click to collapse
nope but while building roms, I slowly dig deeper and deeper into the source code files, checking logs is what i fear will be next .
I already got too much addicted to this, my pc is building roms almost 24/7

quake73 said:
nope but while building roms, I slowly dig deeper and deeper into the source code files, checking logs is what i fear will be next .
I already got too much addicted to this, my pc is building roms almost 24/7
Click to expand...
Click to collapse
haha i suggest you to install ubuntu natively using dualboot
It's a lot faster

Konstantinosj77 said:
haha i suggest you to install ubuntu natively using dualboot
It's a lot faster
Click to expand...
Click to collapse
hehe, i had that crazy idea, too but....i'm a windows guy, the current setup is quite good...16gb ram (8 for ubuntu),
4 HDs, home/cache/out/swap distributed on different HDs, what more can I ask? It's an old pc, AMD x64 x4, 7-8 years but it serves me well...My heart doesnt let me replace it

What is jumpin in rom
quake73 said:
nope but while building roms, I slowly dig deeper and deeper into the source code files, checking logs is what i fear will be next .
I already got too much addicted to this, my pc is building roms almost 24/7
Click to expand...
Click to collapse
Quake that is not taking in Rom?

i think the thing make this rom has no camera working is boot.img 3.10.x because every rom using this kernel has no camera working and please show me how to make 3.4.x kernel is working inside this rom

vinz156 said:
i think the thing make this rom has no camera working is boot.img 3.10.x because every rom using this kernel has no camera working and please show me how to make 3.4.x kernel is working inside this rom
Click to expand...
Click to collapse
thats a good idea. I'll try to build again with one of the older kernels from sonyxperiadev.

quake73 said:
thats a good idea. I'll try to build again with one of the older kernels from sonyxperiadev.
Click to expand...
Click to collapse
It's not gonna work...
Only stock kernel and stock camera blobs can make camera work....

Konstantinosj77 said:
It's not gonna work...
Only stock kernel and stock camera blobs can make camera work....
Click to expand...
Click to collapse
How about cm12.1 what's make camera inside that rom is fully working
Sent from my Xperia M2 (AOSP) using XDA-Developers mobile app

vinz156 said:
How about cm12.1 what's make camera inside that rom is fully working
Sent from my Xperia M2 (AOSP) using XDA-Developers mobile app
Click to expand...
Click to collapse
Stock kernel and stock modules....
These are used for omni 5.1.1 with working camera
Code:
https://github.com/erikcas/android_kernel_sony_msm/tree/5.1-3.4
https://github.com/erikcas/vendor-sony/tree/r13-cam
https://github.com/erikcas/vendor-qcom/tree/r13-cam
Sometimes you have to make changes to the framework files of the ROM and to the device tree