Related
Hello everyone,
I am trying to get the camera work on CM9 but it doens't work! so if anyone can help me that would be Great and one last question can we use the camera drivers from the official TAB 7.7 ICS firmware?
using also this: http://forum.xda-developers.com/showthread.php?t=1651530
EDIT:
First fix doesn't work
EDIT:
Trying to do the kernel work now!
EDIT:
There is no boot.img file in the official samsung rom! (4.0.4)
Decompile the 7.7 kernel, find the driver for the camera, pull that section of code, recompile the cm9 kernel with the new driver.
FlanFlinger said:
Decompile the 7.7 kernel, find the driver for the camera, pull that section of code, recompile the cm9 kernel with the new driver.
Click to expand...
Click to collapse
Downloading 7.7 Firmware now after that i will decompile kernel and find the driver for the camera i will pull that to the cm9 kernel and recompile it wish me luck! PS Where to find the kernel in the Boot.img Or am i wrong?
You've got the source code for ICS on the 7.7 ?
FlanFlinger said:
You've got the source code for ICS on the 7.7 ?
Click to expand...
Click to collapse
No can you give me?
Yeah sure, here you go
FlanFlinger said:
Yeah sure, here you go
Click to expand...
Click to collapse
You don't know what you are saying man! im just trying something and you do this
I will never come back on this thread again (Galaxy Tab 8.9)
You guys are just Crazy To say im having ADHD you don't know what that means i think so im the calmest person here now
No need for that language
But lets just clear a few things up shall we......
You are going to reverse engineer (as you have no source code) about 6mb of data from the 7.7 kernel, find all the relevant parts that drive the camera and then use that to recompile the CM9 kernel to get the camera working.....
This is you whose only dev experience is taking a few apps out of a stock rom, repacking it, releasing it WITH NO CHANGELOG and then shortly after deleting the contents of your release post.
FlanFlinger said:
No need for that language
But lets just clear a few things up shall we......
You are going to reverse engineer (as you have no source code) about 6mb of data from the 7.7 kernel, find all the relevant parts that drive the camera and then use that to recompile the CM9 kernel to get the camera working.....
This is you whose only dev experience is taking a few apps out of a stock rom, repacking it, releasing it WITH NO CHANGELOG and then shortly after deleting the contents of your release post.
Click to expand...
Click to collapse
Im now busy with Porting Bindroid rom from galaxy tab 10.1 section i have permission from him is that also not good or can i do that?
safariking said:
Im now busy with Porting Bindroid rom from galaxy tab 10.1 section i have permission from him is that also not good or can i do that?
Click to expand...
Click to collapse
What I've just put in bold is what's really important. Sure, as long as you're willing to fix bugs the community reports because ports usually contain bugs since they are mostly not using native code.
nirogu325 said:
What I've just put in bold is what's really important. Sure, as long as you're willing to fix bugs the community reports because ports usually contain bugs since they are mostly not using native code.
Click to expand...
Click to collapse
Off coarse i will do that
I just wanna save you the trouble since it's not doable, especially not by you. Stop trying and wait for an official 8.9 ICS, only then we would be able to get the camera working.
http://www.androidpolice.com/2013/0...or-sprint-and-us-cellular-galaxy-s4-variants/
Let the custom ROMs begin.
agentfazexx said:
http://www.androidpolice.com/2013/0...or-sprint-and-us-cellular-galaxy-s4-variants/
Let the custom ROMs begin.
Click to expand...
Click to collapse
roms have nothing to do with kernel source, just kernels
luckily enough the other variants had kernel source out already and were close enough so i already know the new tricks samsung included it the source
shabbypenguin said:
roms have nothing to do with kernel source, just kernels
luckily enough the other variants had kernel source out already and were close enough so i already know the new tricks samsung included it the source
Click to expand...
Click to collapse
Kernel sources do indeed help in ROM creation though. Helps so one does not have to hack up a kernel to use.
agentfazexx said:
Kernel sources do indeed help in ROM creation though. Helps so one does not have to hack up a kernel to use.
Click to expand...
Click to collapse
you can make a rom without ever touching the kernel. and without kernel source all you can do is unpack it and edit the text files in the ramdisk. its not really hacking.
Hi,
I would like to build kernel based on novafusion github sources. I want to look at some btle and NFC stuff, so i wondered if anyone is building from there? And if so how do i get all sources cloned? I figured most things i would look at is kernel, so building that would be a perfect start. But eventually i would like to do complete builds.. So a full guide to getting the correct sources would be great
I am a newbie to building Android, have done it for my defy+ though.
Sent from my GT-I8190 using xda app-developers app
Lightis said:
Hi,
I would like to build kernel based on novafusion github sources. I want to look at some btle and NFC stuff, so i wondered if anyone is building from there? And if so how do i get all sources cloned? I figured most things i would look at is kernel, so building that would be a perfect start. But eventually i would like to do complete builds.. So a full guide to getting the correct sources would be great
I am a newbie to building Android, have done it for my defy+ though.
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
google how to build android kernel
efaustino84 said:
google how to build android kernel
Click to expand...
Click to collapse
Yeah, I am trying to get source from novafusion's github, but I have trouble figuring out how the Novafusion repo's are tied together and once kernel builds I will need to figure out the same for CM11 I think. I would have expected to get a manifest from one of their repo's but that does not seem to exist? (As noted I am a newbie to android and the repo tool, but I am no stranger to coding)
So I wondered if anyone have cloned and built the sources.. If so I would be gratefull for a guide to how I get a local build up and running.
P.s. I have not yet had time to try and put together a manifest myself - Or ask one of the novafusion guys to share theirs, but I thought there might be a general interest in this.. And I figured that there must be someone having it up and running.
So I just installed this today, how often do security updates come out? It currently has Patch level May 1 2016. I'm guessing there are no OTA updates.
What about nightly updates? I guess I would have to use CM 13? I really dont know anything about this stuff besides what I learned today to install it.
10pmStalker said:
So I just installed this today, how often do security updates come out? It currently has Patch level May 1 2016. I'm guessing there are no OTA updates.
What about nightly updates? I guess I would have to use CM 13? I really dont know anything about this stuff besides what I learned today to install it.
Click to expand...
Click to collapse
I think Google updates the Android source code (AOSP) every day, anyone can take that code and build it for their devices. Custom ROMs are created by enthusiasts in their free time, and only they can update it. CM is a full time project that is maintained by a large team who work on it 24/7, and so, they can update it almost nightly.
Gus Ghanem said:
I think Google updates the Android source code (AOSP) every day, anyone can take that code and build it for their devices. Custom ROMs are created by enthusiasts in their free time, and only they can update it. CM is a full time project that is maintained by a large team who work on it 24/7, and so, they can update it almost nightly.
Click to expand...
Click to collapse
Alright thanks, so is the nexus experience the same as CM with it getting the same updates as everyone else, or is this more like a separate thing with separate updates? Are you on nexus experience? I'm not even sure if it's that popular.
10pmStalker said:
Alright thanks, so is the nexus experience the same as CM with it getting the same updates as everyone else, or is this more like a separate thing with separate updates? Are you on nexus experience? I'm not even sure if it's that popular.
Click to expand...
Click to collapse
NX ROM is based on AOSP, basically unmodified from what Google releases, which is similar to what comes on Google's Nexus Phones. CM modifies the AOSP code, adding it's own features and bug fixes to it. All Android ROMs use the same source code from Google, but each developer/maintainer has to do their own updates to their own ROM. Yes, NX and CM are seperate, and different. The NX maintainer has to keep adding the updates from the Google source code himself/herself, and that depends on the person having the time to do it. The same with CM, the developers/maintainers have to keep adding their own and Google's updates to it.
I've been using CM exactly because it's the most well maintained, supported, and updated version of Android you can get.
Gus Ghanem said:
NX ROM is based on AOSP, basically unmodified from what Google releases, which is similar to what comes on Google's Nexus Phones. CM modifies the AOSP code, adding it's own features and bug fixes to it. All Android ROMs use the same source code from Google, but each developer/maintainer has to do their own updates to their own ROM. Yes, NX and CM are seperate, and different. The NX maintainer has to keep adding the updates from the Google source code himself/herself, and that depends on the person having the time to do it. The same with CM, the developers/maintainers have to keep adding their own and Google's updates to it.
I've been using CM exactly because it's the most well maintained, supported, and updated version of Android you can get.
Click to expand...
Click to collapse
When you flash every new update, does it reset everything?
10pmStalker said:
When you flash every new update, does it reset everything?
Click to expand...
Click to collapse
No, it doesn't. I update to every nightly as soon as it's available from the built-in CM updater. All your installed apps, and settings remain as they were. After every update you will see app optimization during boot, but after the phone finishes booting, everything will be the same as it was.
Gus Ghanem said:
No, it doesn't. I update to every nightly as soon as it's available from the built-in CM updater. All your installed apps, and settings remain as they were. After every update you will see app optimization during boot, but after the phone finishes booting, everything will be the same as it was.
Click to expand...
Click to collapse
Awesome thanks. I might look into straight up CM and ditch this nexus experience.
Here is my build of LineageOS 13.0 for the Galaxy S4 LTE A. It is based on the pure LineageOS code unless indicated otherwise.
* IMPORTANT *
Please note that these builds are based on nothing else than the unchanged official code from LineageOS. So every credit goes to the ones providing the code.
I will not and cannot make any changes to the code. The only thing I can do and will do is build the ROM.
Also, it should be understood that I take no responsibilities whatsoever if anything goes wrong when you install the ROM. Like any custom ROM this is completely at your own risk!
However, you can expect that any ROM I share has been installed on my own GT-I9506 (starting with the latest official Samsung firmware 5.0.1) and runs without obvious issues. Your mileage may vary.
https://www.mediafire.com/?c8q4lqh675hc97b,7dhley6dl6j9dnb
Based on LineageOS official code up to https://review.lineageos.org/154230
Which modem and boot loader can you recommend?
audianer said:
Which modem and boot loader can you recommend?
Click to expand...
Click to collapse
I flashed the latest official Samsung firmware to prepare for LineageOS 13.0
I'm trying to build the latest version, which does build without error, but upon booting gets stuck at starting the apps, i.e. just before showing the lock screen. The latest working build was from January 5th 2017 and I experienced the error first on a build of January 8th 2017. So I suspect the commit in question is one from January 6-8.
Before I'm forced to manually investigate commit-by-commit from the latest working version, does anyone know what has changed that causes this error? I was not able to get any output from adb logcat either, so I have no idea what went wrong... which is rather frustrating.
What device tree and kernel did you use?
DualJoe said:
What device tree and kernel did you use?
Click to expand...
Click to collapse
The same as the working previous build: LineageOS/android_kernel_samsung_ks01lte & LineageOS/android_device_samsung_ks01lte. As far as I can see nothing in the kernel or device tree has changed, thus it must be some incompatibility with the rest of the LineageOS code.
I just tried another build just an hour ago, same result: stuck at the final starting apps (before the vibration). I also tried reverting to a working state of the source (of January 5) by using "repo forall -c 'git checkout `git rev-list --all -n1 --before=", but that one didn't even build.
I would appreciate any help here. It's not like there were some exhaustive documentation about how to build LineageOS. And anyway, apparently building is not the issue here.
If that's still Solk2's stuff it might be very old indeed.
DualJoe said:
If that's still Solk2's stuff it might be very old indeed.
Click to expand...
Click to collapse
No. It seems that @solk2 has started to develop the ks01lte again. See the github commits:
https://github.com/LineageOS/android_kernel_samsung_ks01lte/tree/cm-13.0
https://github.com/solk2/android_kernel_samsung_ks01lte/commits/cm-13.0
https://github.com/LineageOS/android_device_samsung_ks01lte/tree/cm-13.0
https://github.com/solk2/android_device_samsung_ks01lte/commits/cm-13.0
(Note: There is no cm14.1 branch on @solk2's github repo yet.)
WeirdSoup said:
No. It seems that @solk2 has started to develop the ks01lte again. See the github commits:
https://github.com/LineageOS/android_kernel_samsung_ks01lte/tree/cm-13.0
https://github.com/solk2/android_kernel_samsung_ks01lte/commits/cm-13.0
https://github.com/LineageOS/android_device_samsung_ks01lte/tree/cm-13.0
https://github.com/solk2/android_device_samsung_ks01lte/commits/cm-13.0
(Note: There is no cm14.1 branch on @solk2's github repo yet.)
Click to expand...
Click to collapse
Uhm... There are cm-14.1 branches too.
zardak said:
Uhm... There are cm-14.1 branches too.
Click to expand...
Click to collapse
I said "@solk2's repo".
And as you can see, there are no additional commits on CM14.1 branch in LOS's ks01lte device repo, compared to cm13.
WeirdSoup said:
I said "@solk2's repo".
And as you can see, there are no additional commits on CM14.1 branch in LOS's ks01lte device repo, compared to cm13.
Click to expand...
Click to collapse
Well, solk2 started to push changes on his kernel's repo days ago, even on cm-14.1 branch.
Anyway, I think is just a matter of time. We'll get official builds sooner or later.
I just don't understand why solk2, kyasu, and possibly gugu0das and others don't collaborate all together to only one kernel/device for this phone
zardak said:
Well, solk2 started to push changes on his kernel's repo days ago, even on cm-14.1 branch.
Anyway, I think is just a matter of time. We'll get official builds sooner or later.
Click to expand...
Click to collapse
Oh, I'm sorry. I misstated. I mean, the "device" repo. (https://github.com/solk2/android_device_samsung_ks01lte/commits/cm-13.0)
zardak said:
Well, solk2 started to push changes on his kernel's repo days ago, even on cm-14.1 branch.
Anyway, I think is just a matter of time. We'll get official builds sooner or later.
I just don't understand why solk2, kyasu, and possibly gugu0das and others don't collaborate all together to only one kernel/device for this phone
Click to expand...
Click to collapse
It looks like a waste of time and work, doesn't it? There is no point in having 3 or more different builds with no particular differences. Devs might want to join the official repos instead and make their changes there.
zardak said:
It looks like a waste of time and work, doesn't it? There is no point in having 3 or more different builds with no particular differences. Devs might want to join the official repos instead and make their changes there.
Click to expand...
Click to collapse
You are absolutely right. I dont know, maybe they have reasons not to join the LineageOS team, but when I got my S4 I was rather confused with all this different versions. I mean for many devices you get unofficial builds with extra features/improvements, but for the I9506 its hard to tell the differences. However at the moment I would say the build by gugu0das is the best, but it looks like he is not going to update it anymore. So yes, it would be great to have all those talented developers out there working on the same repos.
PixelChris95 said:
So yes, it would be great to have all those talented developers out there working on the same repos.
Click to expand...
Click to collapse
I believe this is some sick "if you don't figure it out yourself, you're not supposed to know how to do it" attitude of some (most?) developers. Or another symptom of "not invented here" syndrome.
If LineageOS official builds are available I will surely not waste time to build it myself, but in the meantime I would like to be up-to-date. So still, anyone pointing me to information how to do it is very welcome.
zardak said:
Well, solk2 started to push changes on his kernel's repo days ago, even on cm-14.1 branch.
Anyway, I think is just a matter of time. We'll get official builds sooner or later.
I just don't understand why solk2, kyasu, and possibly gugu0das and others don't collaborate all together to only one kernel/device for this phone
Click to expand...
Click to collapse
I think the same of you. It could be better for all of us to make a ROM with the best of their ROMs.
JohnMcClane1htc said:
I think the same of you.
Click to expand...
Click to collapse
What do you think? That I do not share what I do? I have provided a ROM for i9506 based on cyanogenmod 11.0 for a long, long time, as well as one for Nexus 7. And I have always made clear from where the sources for those builds came. Perfect transparency, don't you think?
It is because of disrespectful people like you that developers (and people like me, because I am not a developer) stop sharing!
NeuDLi said:
What do you think? That I do not share what I do? I have provided a ROM for i9506 based on cyanogenmod 11.0 for a long, long time, as well as one for Nexus 7. And I have always made clear from where the sources for those builds came. Perfect transparency, don't you think?
It is because of disrespectful people like you that developers (and people like me, because I am not a developer) stop sharing!
Click to expand...
Click to collapse
If my comment has offended you, I apologize. My comment doesn't want to disparage anyone. And I recognize the effort of the developers because, although I am not, I know how difficult it must be to develop a ROM.
If my comment has offended you, I apologize. I am sorry.
I also create content in Htcmania and always share and show the sources. I only would want to say that sometimes, when finding so many ROMs based on CM, it can be difficult to decide for one or the other, since the changes between them are very subtle.
Regards
Maintaining/creating roms is usually the way people learn Linux, Android, compiling, git and such. That's why there are so many one-man projects. Once they are into it most vanish again/go over to other stuff though. Only few people keep over long time like Temasek. In the end there can't be enough roms. More options are always better than none. As long as people are posting the source code for other people to pick up they do work together already.