Related
edit: problem solved, patch attached. i also made an update.zip with the new kernel, see here.
there is a vncserver for android out there. so far it works fine, but there is no keyboard or mouse control for the host (android). this being a kernel limitation it can be patched. unluckily for us the patch is available only for the magic kernel version 2.6.23, not for the hero kernel version 2.6.27. i would kindly ask all the developers out there to have a look at the links below, and at least comment about the possibility to "port" (don't know the right expression) the patch to the heros kernel, or teknologists version. i can do the compiling and testing myself, just need someone to have a look at the patch, this is way beyond my skills for now. just compiled the teknologist kernel successfully, as my first compiled kernel ever!
the vncserver project
the patch
htc kernel source
teknologist kerne git
thank you in advance.
i think i managed to apply the patch manually, once i looked into it it turned out that there where only a few lines in 3 files, plus one completely new file, so it seemed pretty easy. yet to be tested, but first i figure out why the kernel won't boot at all, not even with teks sources...
so stay tuned for the kkernel, with full vnc support!
kendong2 said:
i think i managed to apply the patch manually, once i looked into it it turned out that there where only a few lines in 3 files, plus one completely new file, so it seemed pretty easy. yet to be tested, but first i figure out why the kernel won't boot at all, not even with teks sources...
so stay tuned for the kkernel, with full vnc support!
Click to expand...
Click to collapse
I thought Tek's kernel was based on the GSM hero kernel, not the CDMA one, which might be one of the reasons.
thecodemonk said:
I thought Tek's kernel was based on the GSM hero kernel, not the CDMA one, which might be one of the reasons.
Click to expand...
Click to collapse
uhm, i have only the gsm hero, no cdma in germay...
anyway, i forgot the --base 0x19200000 in my script, so the boot.img was faulty. it is working now, fbvncserver recieves keyboard inputs, but mouse does not do anything
maybe i can figure that out somehow, already posted in google code of the project.
i will release an update.zip this afternoon, containing the kernel and fbvncserver for easy installation, but now i gotta get some sleep
kendong2 said:
i will release an update.zip this afternoon, containing the kernel and fbvncserver for easy installation, but now i gotta get some sleep
Click to expand...
Click to collapse
who needs sleep anyway here's the kkernel-1.0
could one of the mods please set a [SOLVED] in front of the titel? if i am supposed to do this myself please tip me of how, i don't get it...
Great work. Will you share the Patch ?
kendong2 said:
could one of the mods please set a [SOLVED] in front of the titel? if i am supposed to do this myself please tip me of how, i don't get it...
Click to expand...
Click to collapse
You can do it editing your first post
i will, was going to do it tonight anyway, please be patient for a few more hours...
Lox_Dev said:
Great work. Will you share the Patch ?
You can do it editing your first post
Click to expand...
Click to collapse
patch is there. thx, i think i forgot to click on "go advanced" when i tried...
kendong2 said:
patch is there. thx, i think i forgot to click on "go advanced" when i tried...
Click to expand...
Click to collapse
Great thks a lot for the patch. I'll apply it to next community kernel release.
There's a fork of android-vnc that works without patching, android-vnc-server (both kbde and touch events).
rejser said:
There's a fork of android-vnc that works without patching, android-vnc-server (both kbde and touch events).
Click to expand...
Click to collapse
lol although it makes my work on the patch completely obsolete it sounds really good. i will look into that this evening, thanks for the hint.
nevertheless, it was interesting to find out how kernel-compiling and cross-compiling works, i actually had fun doing it
too bad, doesn't work for me
console output shows that keys are received, but no action
rejser said:
There's a fork of android-vnc that works without patching, android-vnc-server (both kbde and touch events).
Click to expand...
Click to collapse
thx for the hint, doesn't work for me either though... gonna try it with another kernel, but not before next week, having the gf over the weekend... no kernel baking then
***this thread is made strictly for development purposes so that any developer can join up and help the development of a working port of this for the Galaxy Wonder***
Okay at this point in time I'm trying to make an hard port (the easy way) of CM7 by trying to make a generic build of CM7, then bundling it with Arco68's kernel and afterwards fix the libs and whatnot.
I've already managed to compile the generic build and am now playing around to create a working .ZIP file.
Update 1 : ZIP install fine, but no boot, at least for now. Time to play a little
Update 2: Hm, weird. I was convinced this was gonna work. I'm most likely missing some Samsung patches and **** that generic builds don't have. Going back to the drawing board.
Update 3: While I go into theories about how I should go about CM7, I'm also downloading the sources for Oxygen, because I prefer it over CM7. That way I can study both.
Right on bring it on !
Sent from my GT-I8150 using xda premium
KP, as always I can test whatever firmware you are working on, even if it doesn't boot on your device I can try on mine to see if it works
fender90 said:
KP, as always I can test whatever firmware you are working on, even if it doesn't boot on your device I can try on mine to see if it works
Click to expand...
Click to collapse
Same for me!
Inviato dal mio GT-I8150 usando Tapatalk
i appreciate it and waiting for good news....
i can help by trying it on mi thone
KP....any updates
Sent from my GT-I8150 using xda premium
Since hard porting was getting me nowhere, I decided to try the hard way and I'm currently making a vendor and device config manually. I'm basing it on YardE's awesome work on the Galaxy S Plus front. At least it saves me some work, but there is still a whole lot to do.
Sent from my GT-I8150 using XDA App
Will u make this compatible with the exhibit II
via Dan swagger
How's it going KP? We're starving for updates
Got stuck, waiting for feedback from Arco.
KezraPlanes said:
Got stuck, waiting for feedback from Arco.
Click to expand...
Click to collapse
For a moment when I saw KP replied to this thread I went "yes! yes! he made it!" and when I read your post I just went "aaaawwwwwww...."
Sorry, could not help it. LOL!
It seems Arco's been busy too.
wiseless said:
For a moment when I saw KP replied to this thread I went "yes! yes! he made it!" and when I read your post I just went "aaaawwwwwww...."
Sorry, could not help it. LOL!
It seems Arco's been busy too.
Click to expand...
Click to collapse
yeah me too
Waiting Mode : ON
Really really am hungry for this thread's updates.
SyzwnFrzRdz said:
Really really am hungry for this thread's updates.
Click to expand...
Click to collapse
me too, i can't wait for this thread's updates
Any updatee?
Kezra i want to try by using this http://www.droidforums.net/forum/steel-droid/196475-guide-how-build-your-own-rom-cm7-source.html guide
DarthJonathan said:
Kezra i want to try by using this http://www.droidforums.net/forum/steel-droid/196475-guide-how-build-your-own-rom-cm7-source.html guide
Click to expand...
Click to collapse
Good luck with that considering we have zero basis to work on and building a ROM from source. If you achieve the miracle of building a 'vendor' folder that actually compiles, tell me. That tutorial assumes you have a vendor config that works for your device.
Anyways good luck. I'm still trying to make a working vendor folder.
KezraPlanes said:
Good luck with that considering we have zero basis to work on and building a ROM from source. If you achieve the miracle of building a 'vendor' folder that actually compiles, tell me. That tutorial assumes you have a vendor config that works for your device.
Anyways good luck. I'm still trying to make a working vendor folder.
Click to expand...
Click to collapse
He says i should take out the make files?? but how?? where is our device setup folder where i can excecute the . setup-makefile.sh command? THX A TON KEZRAAA
EDIT : and the have not the vendor for I9001 either so we are starting from zero i do what i can to help you
DarthJonathan said:
He says i should take out the make files?? but how?? where is our device setup folder where i can excecute the . setup-makefile.sh command? THX A TON KEZRAAA
EDIT : and the have not the vendor for I9001 either so we are starting from zero i do what i can to help you
Click to expand...
Click to collapse
You might be able to find those files at Arco's Github.
https://github.com/arco/android_device_samsung_ancora
The above link does contain a file called " setup-makefiles.sh"
You might also want to look at the following:
https://github.com/arco/android_vendor_samsung_ancora
I am not sure if this is what you are looking for, but Hopefully this will help you.
As you all know "Ubuntu for phones" has been released for the Galaxy Nexus, Nexus 4, Nexus 7 and Nexus 10. Lets discuss about this being a possiblity to port on our device.
A porting guide will be posted on Ubuntu website on 22nd (which is today in India).
https://wiki.ubuntu.com/Touch/Porting#Stay_tuned.21
Great my fingers-crossed hope we can take advantage of Ubuntu in our phone
Sent from my MB526 using xda premium
Dual Boot
Just curious, the porting guide says that Ubuntu runs over the stock kernel, if it's right, would it be possible to run it in dual boot?
Samsung Galaxy S (I9000) is having official support and currently the port is work in progress. Apart from the system partition size issue, if samsung galaxy s can run it, so can defy. This is very early stage and we can only presume such thing.
https://wiki.ubuntu.com/Touch/Devices
Floydroider said:
Just curious, the porting guide says that Ubuntu runs over the stock kernel, if it's right, would it be possible to run it in dual boot?
Click to expand...
Click to collapse
So no problem with locked bootloader ?
Sent from my MB526 using xda app-developers app
Marmotte51 said:
So no problem with locked bootloader ?
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
Should not be, most of the phones which can run cm 10.1 can easily handle this. Building it too doesn't look much difficult. "Ubuntu for phones" is surprisingly based on CM sources.
I've not enough speed for syncing sources, maybe Kayant or m11kkaa can build it for us.
brajesh.sharma87 said:
Should not be, most of the phones which can run cm 10.1 can easily handle this. Building it too doesn't look much difficult. "Ubuntu for phones" is surprisingly based on CM sources.
I've not enough speed for syncing sources, maybe Kayant or m11kkaa can build it for us.
Click to expand...
Click to collapse
Till it gets stable enough to worth porting, we will probably have CM 10.1 and kernel 3.0 working perfectly
A little update
I have successfully compiled the the ubuntu zip for our defy however, am facing a major issue at the moment which is the prebulit image that is needed to flash before installing the defy zip is not being installed for some reason Am currently trying to find why this is but no luck so far...... I think I may be something to do with our data partition..... maybe the preimage is too big for it??? that am not sure but I have just reduced it by deleting some images and videos included in the demo..... Hopefully it will decide to work this time
Edit - that did the trick it's working now ^_^
Link to thread ----> http://forum.xda-developers.com/showthread.php?t=2174544
Kayant said:
I have successfully compiled the the ubuntu zip for our defy however, am facing a major issue at the moment which is the prebulit image that is needed to flash before installing the defy zip is not being installed for some reason Am currently trying to find why this is but no luck so far...... I think I may be something to do with our data partition..... maybe the preimage is too big for it??? that am not sure but I have just reduced it by deleting some images and videos included in the demo..... Hopefully it will decide to work this time
Edit - that did the trick it's working now ^_^
Link to thread ----> http://forum.xda-developers.com/showthread.php?t=2174544
Click to expand...
Click to collapse
what is the version of kernel?
sorry for my bad english
Hello!
I am an ubuntu user since 2006 or so and was quiet happy to see the news about it on phones but the hardware requirements are a bit stronger than what our device has. I remember something about minimum dualcore processors and 1 Gb ram. But if someone manages that'd be fun
Keboid said:
Hello!
I am an ubuntu user since 2006 or so and was quiet happy to see the news about it on phones but the hardware requirements are a bit stronger than what our device has. I remember something about minimum dualcore processors and 1 Gb ram. But if someone manages that'd be fun
Click to expand...
Click to collapse
That's for the high end.... low spec our defy matches most of the requirements.....
Let's Go ^_^
I've tried it and the screen does not work
rol525 said:
I've tried it and the screen does not work
Click to expand...
Click to collapse
What exactly do you mean Is the phone not booting pass the black screen after the moto logo.... if so you need to make sure you have wipe data if not the quantal-preinstalled-phablet-armhf.zip won't be installed and flashed the quantal-preinstalled-phablet-armhf.zip first or it will never boot.
Kayant said:
What exactly do you mean Is the phone not booting pass the black screen after the moto logo.... if so you need to make sure you have wipe data if not the quantal-preinstalled-phablet-armhf.zip won't be installed and flashed the quantal-preinstalled-phablet-armhf.zip first or it will never boot.
Click to expand...
Click to collapse
passes the logo and came to the screen of 14 tweets
sorry for my bad english
pd: i restore cm9
rol525 said:
passes the logo and came to the screen of 14 tweets
sorry for my bad english
pd: i restore cm9
Click to expand...
Click to collapse
Then it works .... I think I see what you mean now..... yh it q Ubuntu bug u have to switch off the phone by removing the battery....
Let's Go ^_^
i have a mb525 green lens
Well, i had time to watch the videos and what to say as an old ubuntu user... its just awesome!!
This is a test build I made for the Z1c.
It is based on 23.5.A.0.575 firmware,don't know if it even boots yet,because I do not own a Z1c unfortunately.
Everything what you need to know is in the readme file of the zip that you downloaded.
Make sure your bootloader is unlocked,and I apologize if this soft-bricks your phone.
http://d-h.st/r1o2
From which device it was?
munjeni said:
From which device was it?
Click to expand...
Click to collapse
I believe it was from the Z3c,they have almost the same specs,I know about the SD800 and SD801,and people will say they are different but they are basically the same,only the SD801 has a bump in clock speed
Hmm I don't think it will go
munjeni said:
Hmm I don't think it will go
Click to expand...
Click to collapse
I don't think either,I was bored and decided to try this,maybe if someone is brave enough to try it out
Tried right now only boot image, result was no boot loop but device powering off imediatelly!
munjeni said:
Tried right now only boot image, result was no boot loop but device powering off imediatelly!
Click to expand...
Click to collapse
Can you get into recovery or flash mode?
Dinkec27 said:
I don't think either,I was bored and decided to try this,maybe if someone is brave enough to try it out
Click to expand...
Click to collapse
I don't mind trying, but can you say for sure that it will not hard brick?
levone1 said:
I don't mind trying, but can you say for sure that it will not hard brick?
Click to expand...
Click to collapse
Don't try it,I will modify the kernel a bit and then you can try to give it a shot,for now don't flash
Better idea, start with its stock kernel opensource, modify it for z1c and in same time make it working with an for example recovery, till after you get that kernel working in combination with for example recovery on our z1c than probably you can start patching its androod part
levone1 said:
I don't mind trying, but can you say for sure that it will not hard brick?
Click to expand...
Click to collapse
Yes since its only system and boot image.
munjeni said:
Better idea, start with its stock kernel opensource, modify it for z1c and in same time make it working with an for example recovery, till after you get that kernel working in combination with for example recovery on our z1c than probably you can start patching its androod part
Click to expand...
Click to collapse
Will do,expect an update hopefully tomorrow,my internet isn't the best and I am busy
Dinkec27 said:
Don't try it,I will modify the kernel a bit and then you can try to give it a shot,for now don't flash
Click to expand...
Click to collapse
munjeni said:
Better idea, start with its stock kernel opensource, modify it for z1c and in same time make it working with an for example recovery, till after you get that kernel working in combination with for example recovery on our z1c than probably you can start patching its androod part
Click to expand...
Click to collapse
Thanks for your work. I've had these thoughts, but it's way over my head. More than happy to test, though. Keep posted...
munjeni said:
Better idea, start with its stock kernel opensource, modify it for z1c and in same time make it working with an for example recovery, till after you get that kernel working in combination with for example recovery on our z1c than probably you can start patching its androod part
Click to expand...
Click to collapse
Just a quick question,could I use something from the AOSP Z1c kernel to put in the Z3c kernel to make it possibly compatible?
Dinkec27 said:
Just a quick question,could I use something from the AOSP Z1c kernel to put in the Z3c kernel to make it possibly compatible?
Click to expand...
Click to collapse
What version is that stock kernel from z3c?
munjeni said:
What version is that stock kernel from z3c?
Click to expand...
Click to collapse
23.5.A.0.570,Android 6.0.1
I mean kernel version, e.g. 3.4 or 3.10 ?
munjeni said:
I mean kernel version, e.g. 3.4 or 3.10 ?
Click to expand...
Click to collapse
Oh,sorry.
It is 3.4.
Dinkec27 said:
Just a quick question,could I use something from the AOSP Z1c kernel to put in the Z3c kernel to make it possibly compatible?
Click to expand...
Click to collapse
Ok, 3.4. Than I think better idea is using stock kernel 3.4 from z1c for imports into that kernel instead of aosp...
munjeni said:
Ok, 3.4. Than I think better idea is using stock kernel 3.4 from z1c for imports into that kernel instead of aosp...
Click to expand...
Click to collapse
Edit:
the best idea is having booth stock kernels lolipop source code on hard disk and making an git diff just for finding diferencies in kernel source, than by that knownledge starting optimising z3c marchmallow kernel for z1c, at least I would be do that way.
Hello fellow XDA members, I recently purchased a Le Pro 3 and a Le S3 during the flash sale and would like to use Cyanogenmod on my devices. I was wondering if anyone on this forum has ever ported a ROM before as I have not, and only know about the CM porting guide and opensource.le.com for the kernel source. If anyone has any tips or would like to assist me in porting CM13 to the Pro 3 please reply to this thread or PM me. Thanks, and let's hope LeEco releases the source soon!
Love to help but this isn't my department ????. But we should probably see more support in a couple more days once they start arriving here
Just out of curiousity, what exactly had you hoped to achieve with this post? If you're interested in porting, ideally you should at least be able to build a rom (for another pre-existing device)... and then you'll have to hunt down help on the CM forums and then eventually IRC.
Talking about this on XDA is pointless.
dr4stic said:
Just out of curiousity, what exactly had you hoped to achieve with this post? If you're interested in porting, ideally you should at least be able to build a rom (for another pre-existing device)... and then you'll have to hunt down help on the CM forums and then eventually IRC.
Talking about this on XDA is pointless.
Click to expand...
Click to collapse
The purpose of my post was to see if anyone in the XDA community had experience porting a ROM to a new device, and if they'd be interested in helping me. I have read through a few guides and understanding building a ROM, but am struggling to find what I must "merge." From what I've found so far, I'll need to edit/merge the directories in /system/libs and edit the kernel?
limitlesscodes said:
The purpose of my post was to see if anyone in the XDA community had experience porting a ROM to a new device, and if they'd be interested in helping me. I have read through a few guides and understanding building a ROM, but am struggling to find what I must "merge." From what I've found so far, I'll need to edit/merge the directories in /system/libs and edit the kernel?
Click to expand...
Click to collapse
No, it's far more complicated than that. You'll need a copy of the kernel for sure, but you'll also need a device definition. You can use the op3's device as a template, it's probably the best example of an msm8996 device you can have.
You really should be checking into the CM forums. CM people are pretty uppity about not supporting things on XDA. They also don't tend to help. Even as a developer I find it difficult sometimes to get their attention. Your best bet is to go to them if you want their help. Good luck.
dr4stic said:
No, it's far more complicated than that. You'll need a copy of the kernel for sure, but you'll also need a device definition. You can use the op3's device as a template, it's probably the best example of an msm8996 device you can have.
You really should be checking into the CM forums. CM people are pretty uppity about not supporting things on XDA. They also don't tend to help. Even as a developer I find it difficult sometimes to get their attention. Your best bet is to go to them if you want their help. Good luck.
Click to expand...
Click to collapse
Yeah, I understand. I also found out that it will be about a month until LeEco officially releases all of the source.
limitlesscodes said:
Yeah, I understand. I also found out that it will be about a month until LeEco officially releases all of the source.
Click to expand...
Click to collapse
Where did you get that information from? They "accidentally" released kernel sources not too long ago and seemingly withdrew it. I got a copy of them and that's what I've been working with. I don't have a device to verify if any of it works.
dr4stic said:
Where did you get that information from? They "accidentally" released kernel sources not too long ago and seemingly withdrew it. I got a copy of them and that's what I've been working with. I don't have a device to verify if any of it works.
Click to expand...
Click to collapse
I asked on this forum. Also my S3 is coming tonight, and my Pro tomorrow. I have a copy of the Pro 3 kernel source as well but as of now don't know what to do. What have you worked on so far?
limitlesscodes said:
I asked on this forum. Also my S3 is coming tonight, and my Pro tomorrow. I have a copy of the Pro 3 kernel source as well but as of now don't know what to do. What have you worked on so far?
Click to expand...
Click to collapse
Not a lot. I've identified the CAF tag the sources are based on and have been working to separate the relevant LeEco mods from the less relevant ones. I've also been attempting to remove the leeco specific things from the drivers that i'm keeping since they're a horrible mess and CM won't be able to make use of them anyway. I've also been finding the appropriate open versions of the drivers and taking the latest ones instead.
The mods from LeEco seem to be a mess, the dmesg output I got from a user on the chinese model (the x720) had segfaults from the modifications just after boot. The logcats are so full of errors I was unable to get the user to send me a full logcat from boot.
Interestingly enough, the chinese system rom looks like it came from a Le Max2. This makes sense since it's LeEco's first msm8996 device, and the Le Pro3 is the second one. I imagine the kernel sources work across a number of the 8996's.
Can you send me the link to where you got the open drivers.
limitlesscodes said:
I asked on this forum. Also my S3 is coming tonight, and my Pro tomorrow. I have a copy of the Pro 3 kernel source as well but as of now don't know what to do. What have you worked on so far?
Click to expand...
Click to collapse
Please share the sources.
Sent from my LEX727 using Tapatalk
ceo.mtcl said:
Please share the sources.
Sent from my LEX727 using Tapatalk
Click to expand...
Click to collapse
here
limitlesscodes said:
here
Click to expand...
Click to collapse
Thank you so much!
limitlesscodes said:
here
Click to expand...
Click to collapse
This is not a International version? Its USA version? Where is the International source code?
Here's a mega mirror in case the drive link goes down.
https://mega.nz/#!7Ek3HYaB!1H0WibOjwlg1P0vaaJ2qcrAAsl-PjruB9-_X1ECqfnw
Wish i could help more, but it looks like the kernel source is in there too, perhaps that means a fully functional cm13 rom that works AT LEAST as well as the stock rom. VERY EXCITE!
+1
I'm also waiting for CM13.
csyann said:
I'm also waiting for CM13.
Click to expand...
Click to collapse
:good:
csyann said:
I'm also waiting for CM13.
Click to expand...
Click to collapse
giogio1 said:
:good:
Click to expand...
Click to collapse
Waiting for CM 14.1
http://opensource.le.com