Database Users

CyanogenMod 7.0 for eLocity ?

Check this out !
Anyone in relation with those guys ? How could we get out tablet to support it ?
Pretty amazing !
Link here : http://www.engadget.com/2011/04/11/cyanogenmod-7-0-is-now-final-ready-for-your-consumption/
I know Dexter is the eLocity king atm, but it must be tirering to be a one man army !

Again and again and again...
Without kernel source we unable to do custom ROMs. Only modifications over stock.
Not a development topic...

5[Strogino] said:
Again and again and again...
Without kernel source we unable to do custom ROMs. Only modifications over stock.
Not a development topic...
Click to expand...
Click to collapse
maybe I should put my old signature back on? lol

the Synergy Bluetooth implementation is nowhere close to standard implementation, so although we might get a CM6/7 on this tablet, even without 2.6.36.3 kernel maybe, we still need more coding done to support the BT implemention otherwise the port will be without Bluetooth support..
I got, as example, the FolioMod ported easily, but Bluetooth did not work, same with the Blur port.. and since our kernel has no real loopdevice or devicemapper support and modules needs to be specifically compiled with the revisions used in our kernel, the "move2sd" function is also missing here, and other nice function as optimized filesystems using loopdevice for faster database updates etc..
it will be hard! , and the drivers without any source, makes its practically impossible to do a kernel based on nvidia's git tree alone..

Moved to proper forum

Kernel available??
Mr. Clown said:
Moved to proper forum
Click to expand...
Click to collapse
See on http://www.elocitynow.com/downloads/open-source.tar
and chacksum http://www.elocitynow.com/downloads/.checksum.md5

ming_a said:
See on http://www.elocitynow.com/downloads/open-source.tar
and chacksum http://www.elocitynow.com/downloads/.checksum.md5
Click to expand...
Click to collapse
Yep. Did you find it here:
http://www.elocitynow.com/developers.shtml
Billy

[REQUEST] N8000 Kernel Source

I am about to build a kernel for N8000. But my problem is I can not download from samsung open source site (Very Slow Connection).
Can someone please mirror the update7(MD1) for me on a fast server like dev-host, android file host, mediafire or etc...?
Here's the Samsung open source site:
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=GT-N8000
Thanks in advance.

You may use my GitHub repository, which has a branch "merge-to-ss-jb" that is just the vanilla Samsung kernel, backed by the complete Linux tree.
Also, if you're interested in a complete, up-to-date tree (and what I'm running on my own GNote) you may browse my "kernel-forward" branch.

kcrudup said:
You may use my GitHub repository, which has a branch "merge-to-ss-jb" that is just the vanilla Samsung kernel, backed by the complete Linux tree.
Also, if you're interested in a complete, up-to-date tree (and what I'm running on my own GNote) you may browse my "kernel-forward" branch.
Click to expand...
Click to collapse
Thanks.
I have two questions if you don't mind.
1. Merge-to-ss-jb is the latest source (MD1)? Is it a good to go for a kernel to be based upon?
2. Is it alright with you that I base my kernel on your own kernel?
I appreciate it if you can help me with some kernel stuff as I am new to this.
Sent from my HTC One X using Tapatalk 4 Beta

csec said:
"merge-to-ss-jb" is the latest source (MD1)?
Click to expand...
Click to collapse
Yeah, it's essentially the official Linux kernel source up to version 3.0.31, overlaid with a cleaned-up version of the 1st Samsung JB kernel release, then each subsequent Samsung Open-Source Release (latest is "#7") is overlaid on top of that. If you build the HEAD of that branch, you'll have a vanilla Samsung kernel as of XXMCD1.
Is it alright with you that I base my kernel on your own kernel?
Click to expand...
Click to collapse
Of course! The entire Linux kernel is built upon Public collaboration; we all share from each other. My kernel has a few selected bits here and there from diverse places like CyanogenMod, Francisco Franco, Xstacy, the upstream kernel, Qualcomm, NVidia ...
I used to post my built kernel up in the ROM threads I used to use on my GNote, but someone complained and I don't really feel like being bothered with my own thread (don't have time for the inevitable newbie SPAM) so until if/when I do go "public" with it, the "kernel-forward" branch on GitHub is the best place to get what I'm running now.

kcrudup said:
Yeah, it's essentially the official Linux kernel source up to version 3.0.31, overlaid with a cleaned-up version of the 1st Samsung JB kernel release, then each subsequent Samsung Open-Source Release (latest is "#7") is overlaid on top of that. If you build the HEAD of that branch, you'll have a vanilla Samsung kernel as of XXMCD1.
Of course! The entire Linux kernel is built upon Public collaboration; we all share from each other. My kernel has a few selected bits here and there from diverse places like CyanogenMod, Francisco Franco, Xstacy, the upstream kernel, Qualcomm, NVidia ...
I used to post my built kernel up in the ROM threads I used to use on my GNote, but someone complained and I don't really feel like being bothered with my own thread (don't have time for the inevitable newbie SPAM) so until if/when I do go "public" with it, the "kernel-forward" branch on GitHub is the best place to get what I'm running now.
Click to expand...
Click to collapse
Great!
Thanks again.
Sent from my GT-N8000 using Tapatalk HD

csec said:
Great!
Thanks again.
Sent from my GT-N8000 using Tapatalk HD
Click to expand...
Click to collapse
Heard that the published sources have different wi-fi drivers than preinstalled stock kernel.
This is the main reason of allshare cast not working with custom kernels (on the contrary, some s3 custom kernels DO SUPPORT allshare cast), even if status=official and flash counter=0.
Anyone can confirm?
Anyone has the proper ones or know which one (i.e. from a different samsung device) to use?

gitHub link dead

12.0.A.2..254 kernel sources

Maybe I missed some annoucement... does anyone know if Sony will release sources for 12.0.A.2.254?
Seems to me that development for custom kernels (like Doomlord's) have stalled because there are no sources available.

omoithesane said:
Maybe I missed some annoucement... does anyone know if Sony will release sources for 12.0.A.2.254?
Seems to me that development for custom kernels (like Doomlord's) have stalled because there are no sources available.
Click to expand...
Click to collapse
Not available yet... :crying::crying::crying::crying::crying::crying::crying:

Rajeev said:
Not available yet... :crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
I know :crying:
But does anyone know if Sony will release the sources? How long does this usually take? I think FW .254 was released a month ago...

omoithesane said:
I know :crying:
But does anyone know if Sony will release the sources? How long does this usually take? I think FW .254 was released a month ago...
Click to expand...
Click to collapse
As I understand it they have no choice but to release the kernel source as it's linux and the licensing requires that it be made available. That said, the proprietary blobs for the cameras, wifi, etc. aren't generally licensed the same way so they don't normally get released, at least in source form.

I've requested Sony to provide the source and they will do that really soon

eagleeyetom said:
I've requested Sony to provide the source and they will do that really soon
Click to expand...
Click to collapse
Nice! :good: :fingers-crossed:
Just out of curiosity:
I had an Xperia Arc. My perception was that Sony released the kernel sources (including proprietary modules and everything else which is necessary to build a working custom kernel) relatively quickly and without anyone asking for it. Has this policy changed, did they just forget in case of the Xperia SP/.254 kernel sources or did I just perceive this wrong?

Finally Sony releases .254 kernel sources
Sent from my C5303 using Tapatalk

Here is a diff if anyone wants to view
Siddhesh said:
Finally Sony releases .254 kernel sources
Sent from my C5303 using Tapatalk
Click to expand...
Click to collapse
I know. I was the one who asked the right person to do it
https://github.com/uberlaggydarwin/...mmit/0dd49c41698a82b77f32ac80e8caef80eba09142
GitHub may have derped.
Here is a diff between previous kernel sources and now
That's the most recent kernel source
https://github.com/uberlaggydarwin/sonystockkernelxperiasp

uberlaggydarwin said:
I know. I was the one who asked the right person to do it
https://github.com/uberlaggydarwin/huashan-kernel/commit/1c8ff356025e1e66142d0ce431c73cc2a57f4e58
GitHub may have derped.
Here is a diff between previous kernel sources and now
That's the most recent kernel source
https://github.com/uberlaggydarwin/huashan-kernel
Click to expand...
Click to collapse
So that means, the CM 10.1 kernel will be updated, right? :good:

sarkar1990 said:
So that means, the CM 10.1 kernel will be updated, right? :good:
Click to expand...
Click to collapse
Yes
Sent from my C5303 using Tapatalk

Probably not, the kernel used for 10.1is not related to the Sony kernels as I ported the drivers to a newer kernel version. We already have any changes that may be in the 2.254 kernel and more. (I didn't notice any changes to the Sony drivers).
Sent from my C5303 using XDA Premium 4 mobile app

Won't rebase off this.
sarkar1990 said:
So that means, the CM 10.1 kernel will be updated, right? :good:
Click to expand...
Click to collapse
Finally had a chance to look at them as I got home from work only just before...
Just left my computer to push them today so didn't get a chance to check them but adfad666 is right and not much actual changes changed though which are useful for us.
Just some general CAF / kernel updates so not too important.
A panel driver was updated but I'm doubt we we will use it as our kernel is not based off stock.
Probably not. . Let's wait for 4.3 kernel from Sony as it will be worth rebasing off that

Thanks for the link to sources....

[KERNELSOURCE] MT6755 Sony XA DUAL Discussion: Is it possible to port?

Hi out there!
Today i've looked another time for kernel sources of our loved (and hated) phone.
The only full source i've found was this one on the Sony Website:
http://developer.sonymobile.com/downloads/xperia-open-source-archives/open-source-archive-for-33-2-a-2-37-and-33-2-b-2-37/
I don't have the time nor the knowledge of kerneldevelopment to check this out.
My question is:
Is it possible to port this Sony kernel, to have a working p9000 kernel, with the goal to have let's say DirtyUnicorn running?
greetings
vsrookie

vsrookie said:
Hi out there!
Today i've looked another time for kernel sources of our loved (and hated) phone.
The only full source i've found was this one on the Sony Website:
http://developer.sonymobile.com/downloads/xperia-open-source-archives/open-source-archive-for-33-2-a-2-37-and-33-2-b-2-37/
I don't have the time nor the knowledge of kerneldevelopment to check this out.
My question is:
Is it possible to port this Sony kernel, to have a working p9000 kernel, with the goal to have let's say DirtyUnicorn running?
greetings
vsrookie
Click to expand...
Click to collapse
Kernel and ROM are 2 different things. We could get DU working on stock kernel, but we need valid device and vendor trees. Sometimes you can make them yourself, other times the manufacturers provide them.

Jonny said:
Kernel and ROM are 2 different things. We could get DU working on stock kernel, but we need valid device and vendor trees. Sometimes you can make them yourself, other times the manufacturers provide them.
Click to expand...
Click to collapse
Ok. But an android system need functions from the kernel, don't they?
What do you exactly mean with device tree and vendor tree? The drivers for the components? If it is so, then can't we "just take them" and integrate in the kernel source?
greetings
vsrookie
Ps: Basically i need to read sonething about Android development. [emoji12]
Sent from my P9000 using XDA-Developers mobile app

vsrookie said:
Ok. But an android system need functions from the kernel, don't they?
What do you exactly mean with device tree and vendor tree? The drivers for the components? If it is so, then can't we "just take them" and integrate in the kernel source?
greetings
vsrookie
Ps: Basically i need to read sonething about Android development. [emoji12]
Sent from my P9000 using XDA-Developers mobile app
Click to expand...
Click to collapse
Vendor tree example >>> https://github.com/omnirom/android_vendor_omni
Device tree example >>> https://github.com/omnirom/android_device_sony_kitakami-common
The Android system does use functions from the kernel but its not really "aware" of doing so, you can run custom ROM's like DU, Omni etc from stock kernels most of the time without any issues.

So basically: When/If Elephone decides to release CM13, it's still possible they won't give us the vendor/device tree? So that's basically a byebye to porting roms?
Sorry, I'm a nub too.

Boristruyens said:
So basically: When/If Elephone decides to release CM13, it's still possible they won't give us the vendor/device tree? So that's basically a byebye to porting roms?
Sorry, I'm a nub too.
Click to expand...
Click to collapse
Tbh that is a massive probability, making device and vendor trees is not non-trivial and is a lot of work. For instance the HTC 10 still doesn't have a stable CM build, and there are some hard hitters in the AOSP dev world that own that device. I'll have a look and see what I can do but I'm an app developer and an apk editor (i.e. Java and Smali are more my languages than C/C++) more than a source builder so I might not be able to do much.

Can i use it for making recovery for moto m

The P9000 has a kernel on github anyway ...

3.10.33 kernel from Nvidia Shield ported to Mi Pad

Hello from Moscow, Russia. I can't write in Firmware section, so I write here.
I'm and my teammate(Dblm) ported 3.10.33 kernel from Nvidia Shield. TWRP works fine with this kernel. But android don't work cuz our graphical blobs are very very old. So may be somebody can find necessary blobs and run android.
zImage: https://drive.google.com/open?id=0B2...nhPdlJkWkdYQjg
TWRP recovery with this kernel: https://drive.google.com/open?id=0B2...FhQTHJIa2xVems

reserved

Artemka2008 said:
Hello from Moscow, Russia. I can't write in Firmware section, so I write here.
I'm and my teammate(Dblm) ported 3.10.33 kernel from Nvidia Shield. TWRP works fine with this kernel. But android don't work cuz our graphical blobs are very very old. So may be somebody can find necessary blobs and run android.
zImage: https://drive.google.com/open?id=0B2ALf4H-2aBrZnhPdlJkWkdYQjg
TWRP recovery with this kernel: https://drive.google.com/open?id=0B2ALf4H-2aBrZFhQTHJIa2xVems
Click to expand...
Click to collapse
Thanks a lot for posting this. It would be more helpful if you could post your source code for the port and the source (the original shield kernel).

drakonizer said:
Thanks a lot for posting this. It would be more helpful if you could post your source code for the port and the source (the original shield kernel).
Click to expand...
Click to collapse
At the moment my teammate does not want to publish the source code.
CPU fixed in this build(all 4 cores work)

Artemka2008 said:
At the moment my teammate does not want to publish the source code.
CPU fixed in this build(all 4 cores work)
Click to expand...
Click to collapse
I really appreciate your work. Don't get me wrong. But Linux is licensed under GPL. The law requires you to open source your work, and so does XDA. This is why we didn't have a Mi Pad forum till now. To avoid problems and to prevent XDA from banning you or closing this thread, I suggest you either publish your source or remove the link.
None of the devs can help you if you don't release the source code. Please co operate with the open source community.
Thanks for understanding.

drakonizer said:
I really appreciate your work. Don't get me wrong. But Linux is licensed under GPL. The law requires you to open source your work, and so does XDA. This is why we didn't have a Mi Pad forum till now. To avoid problems and to prevent XDA from banning you or closing this thread, I suggest you either publish your source or remove the link.
None of the devs can help you if you don't release the source code. Please co operate with the open source community.
Thanks for understanding.
Click to expand...
Click to collapse
ok, I will delete this thread.

Artemka2008 said:
ok, I will delete this thread.
Click to expand...
Click to collapse
You don't have to delete the thread. It can be used for discussions. You can upload your kernel whenever you feel its appropriate to release your source code.
On a more helpful note: I can't say much without seeing the source code, but if you have ported the kernel drivers as well from shield, you can try using the blobs from Shield itself. You'll probably need to use blobs that match the version of the kernel you are trying to port.

so does that mean that there is a chance for cm12+?

Jahhhhhhh said:
so does that mean that there is a chance for cm12+?
Click to expand...
Click to collapse
Without camera and sound now. I tried to run Android 5.1.1 with our kernel. But I can't find working graphical blobs. I need help with it.
This is my last logcat https://drive.google.com/open?id=0B2ALf4H-2aBrX3dCRkthR21wM1U

This is going nowhere until you share the source code with the community as per GPL. How long does your teammate want to drag the process? Release the source code today and start getting feedback from other devs - what's the hold up?

Palm Trees said:
This is going nowhere until you share the source code with the community as per GPL. How long does your teammate want to drag the process? Release the source code today and start getting feedback from other devs - what's the hold up?
Click to expand...
Click to collapse
God, the source code will not help here. You just need to pick up the blobs to run android. With the kernel of today there are no problems.

Artemka2008 said:
God, the source code will not help here. You just need to pick up the blobs to run android. With the kernel of today there are no problems.
Click to expand...
Click to collapse
Blobs are heavily linked to the kernel drivers. Without even knowing what kernel you have used as a source for the port (the one for Shield), how can we randomly test blobs and somehow magically fix this? I really don't want to piss you guys off, but the reason why you can do the work you do is because the Linux kernel is open source. And it's stayed that way because people have followed the GPL (with only a few exceptions like Xiaomi). I do not understand why you don't want to release the source code. Nobody is trying or will try to steal your work and claim credits. In the end we all want the same thing - stable Android 5/6/7 on the Mi Pad. Let other people help too.

drakonizer said:
Blobs are heavily linked to the kernel drivers. Without even knowing what kernel you have used as a source for the port (the one for Shield), how can we randomly test blobs and somehow magically fix this? I really don't want to piss you guys off, but the reason why you can do the work you do is because the Linux kernel is open source. And it's stayed that way because people have followed the GPL (with only a few exceptions like Xiaomi). I do not understand why you don't want to release the source code. Nobody is trying or will try to steal your work and claim credits. In the end we all want the same thing - stable Android 5/6/7 on the Mi Pad. Let other people help too.
Click to expand...
Click to collapse
That's my point exactly. Have you tried asking in the Nvidia Shield xda thread: http://forum.xda-developers.com/shield-tablet/development. There's plenty of development going on, you might be able to get some tips and tricks.

Palm Trees said:
That's my point exactly. Have you tried asking in the Nvidia Shield xda thread: http://forum.xda-developers.com/shield-tablet/development. There's plenty of development going on, you might be able to get some tips and tricks.
Click to expand...
Click to collapse
Not the point. The shield developers will not be able to help us. Things will become very easy if this shield kernel port works. We will probably be able to use the newer blobs meant for the Shield, which makes development very easy, if this becomes bootable/stable. I really hope the OP manages to get it working. We either need newer blobs from Xiaomi or we need to write wrappers to use the current kitkat blobs (not easy, since Nvidia documentation is nowhere near as detailed as say, Qualcomm) or we need to get this port working well, which would enable us to use most of the blobs from the Shield (provided Xiaomi hasn't gone out of their way to screw with their blobs). The first two ways are practically impossible, which leads me to rest all my hope on this port. Unfortunately without the source code, we will just have to be silent spectators, waiting for some news.

Here's my effort for asking sheild developer- http://forum.xda-developers.com/shield-tablet/help/help-support-xiaomi-mipad-custom-rom-t3512695
I also posted a xiaomi forum link where Sheild Lollipop kernel is accessible for developers. It's available in Xiaomi forum.
Here's the link - http://en.miui.com/thread-439620-1-1.html
I have just shared the information available. Not taking any credit away from developer from 4pda.ru.
Thanks

rocky869 said:
Here's my effort for asking sheild developer- http://forum.xda-developers.com/shield-tablet/help/help-support-xiaomi-mipad-custom-rom-t3512695
I also posted a xiaomi forum link where Sheild Lollipop kernel is accessible for developers. It's available in Xiaomi forum.
Here's the link - http://en.miui.com/thread-439620-1-1.html
I have just shared the information available. Not taking any credit away from developer from 4pda.ru.
Thanks
Click to expand...
Click to collapse
I asked LuckyMeAgain to publish on the official website, so it's the same thing. I am ArtemkaVZM on 4pda and arttt on en.miui.com MiuiSmokeRom dev team.

Presumably the easiest way is to go through TheMuppets repo and testing them at different points in time by checking commit history.
https://github.com/TheMuppets/proprietary_vendor_nvidia

Harrynowl said:
Presumably the easiest way is to go through TheMuppets repo and testing them at different points in time by checking commit history.
https://github.com/TheMuppets/proprietary_vendor_nvidia
Click to expand...
Click to collapse
I think that we have to make a new build. Current builds are useless for us now. I mean available android 5 roms.
This is my last logcat with 5.1.1 Vartom's SlimRom: https://drive.google.com/open?id=0B2ALf4H-2aBrX3dCRkthR21wM1U

Artemka2008 said:
I think that we have to make a new build. Current builds are useless for us now. I mean available android 5 roms.
This is my last logcat with 5.1.1 Vartom's SlimRom: https://drive.google.com/open?id=0B2ALf4H-2aBrX3dCRkthR21wM1U
Click to expand...
Click to collapse
looks like hwcomposer is the broken blob. Have you tried using the hwcomposer.tegra.so from a Sheild ROM to boot it?

drakonizer said:
looks like hwcomposer is the broken blob. Have you tried using the hwcomposer.tegra.so from a Sheild ROM to boot it?
Click to expand...
Click to collapse
All the necessary blobs were taken from Shield. More no such files, which could be replaced.