Related
So talking to my buddy about all the "junk" loaded on the Samsung, he kept raving about how his old Nexus One was just the way I would like it. I would like to have a "plain" version of Android 2.1 on my phone. I have a coworker friend that's a Linux guru that's willing to help. Here's my questions.
Can I take take the Samsung released source for the hardware drivers and compile it with a stock Android 2.1 platform? I'm not asking for step by step. More of a 10,000 foot how to. Is that possible?
Can you leave the CSC and Modem info the same and just install a PDA ROM with Odin? Or would you be overwriting all of that info on the phone?
Thanks and if this has been answered before, please fill free to say "search is your friend" and give me the links...
hallfleming said:
So talking to my buddy about all the "junk" loaded on the Samsung, he kept raving about how his old Nexus One was just the way I would like it. I would like to have a "plain" version of Android 2.1 on my phone. I have a coworker friend that's a Linux guru that's willing to help. Here's my questions.
Can I take take the Samsung released source for the hardware drivers and compile it with a stock Android 2.1 platform? I'm not asking for step by step. More of a 10,000 foot how to. Is that possible?
Can you leave the CSC and Modem info the same and just install a PDA ROM with Odin? Or would you be overwriting all of that info on the phone?
Thanks and if this has been answered before, please fill free to say "search is your friend" and give me the links...
Click to expand...
Click to collapse
I unfortunately haven't the answer but I'd like to add that I am curious about this too.
dalingrin said:
I unfortunately haven't the answer but I'd like to add that I am curious about this too.
Click to expand...
Click to collapse
I'll second this and ask that if you do figure it out, please share with the community.
I think that vanilla Roms are a little further away in the future. First step in the process right now would be for someone to be able to compile a kernel from the Samsung released source code that works. Unfortunately the current Captivate kernel source code, when compiled, causes issues (voices garbled, lag when waking up the phone) that are not present in the stock precompiled kernel. These bugs are apparently not present in the other versions of the source code. Once these initial bugs are ironed out, we can truly start down the path of having custom fixes, and the devs can start to focus on bigger challenges, like making the vanilla Eclair or Froyo Roms to start working with our kernel. Good thing about this phone is that there are going to be so many versions of it, that parallel development is happening on multiple platforms. This will likely produce independent breakthroughs that could be theoretically ported between the platforms, but unfortunately it also slows down the development of each platform due to the quirks that have to be overcome. I hope that, in the future, we get to a place where all the source codes are merged into master repository that has all the necessary improvements and the ability to overcome individual platform quirks, so that the development can proceed more rapidly.
hallfleming said:
So talking to my buddy about all the "junk" loaded on the Samsung, he kept raving about how his old Nexus One was just the way I would like it. I would like to have a "plain" version of Android 2.1 on my phone. I have a coworker friend that's a Linux guru that's willing to help. Here's my questions.
Can I take take the Samsung released source for the hardware drivers and compile it with a stock Android 2.1 platform? I'm not asking for step by step. More of a 10,000 foot how to. Is that possible?
Can you leave the CSC and Modem info the same and just install a PDA ROM with Odin? Or would you be overwriting all of that info on the phone?
Thanks and if this has been answered before, please fill free to say "search is your friend" and give me the links...
Click to expand...
Click to collapse
Check out this wiki from cyanogen:
http://wiki.cyanogenmod.com/index.php?title=Main_Page
On the bottom right you will see an advanced section that explains how to build from source code. (aosp)
Good luck!!! It's definitely not for me, not with kids and a full time job!
Good info. I haven't seen a post on people testing out the source code testing and their experience. Can you IM or point me to that?
Thanks!
rajendra82 said:
I think that vanilla Roms are a little further away in the future. First step in the process right now would be for someone to be able to compile a kernel from the Samsung released source code that works. Unfortunately the current Captivate kernel source code, when compiled, causes issues (voices garbled, lag when waking up the phone) that are not present in the stock precompiled kernel. These bugs are apparently not present in the other versions of the source code. Once these initial bugs are ironed out, we can truly start down the path of having custom fixes, and the devs can start to focus on bigger challenges, like making the vanilla Eclair or Froyo Roms to start working with our kernel. Good thing about this phone is that there are going to be so many versions of it, that parallel development is happening on multiple platforms. This will likely produce independent breakthroughs that could be theoretically ported between the platforms, but unfortunately it also slows down the development of each platform due to the quirks that have to be overcome. I hope that, in the future, we get to a place where all the source codes are merged into master repository that has all the necessary improvements and the ability to overcome individual platform quirks, so that the development can proceed more rapidly.
Click to expand...
Click to collapse
Also for clarification, when you bought a Nexus One straight from Google for AT&T, was it considered "Vanilla"? Is the build on that phone just like someone downloaded the source for 2.1 and compiled it with the hardware drivers and that's it? I'm wondering what all comes on a "basic" Andriod ROM straight from the source.
hallfleming said:
Also for clarification, when you bought a Nexus One straight from Google for AT&T, was it considered "Vanilla"? Is the build on that phone just like someone downloaded the source for 2.1 and compiled it with the hardware drivers and that's it? I'm wondering what all comes on a "basic" Andriod ROM straight from the source.
Click to expand...
Click to collapse
Nexus One is as Vanilla as it comes. Just straight up Android! I don't think there is anything added to stock 2.1 or 2.2 on the Nexus.
hallfleming said:
Good info. I haven't seen a post on people testing out the source code testing and their experience. Can you IM or point me to that?
Thanks!
Click to expand...
Click to collapse
Most of the kernel compiling struggles are documented here:
http://forum.xda-developers.com/showthread.php?t=740747
Mimocan himself has started some work on it here:
http://forum.xda-developers.com/showthread.php?t=747040
There are also people having success mixing Vibrant ROM on the Captivate with some GPS crash issues:
http://forum.xda-developers.com/showthread.php?t=746466
I am trying to follow those threads, and since I am not a developer, I can't personally contribute to the process. But it is interesting to me anyway.
I've seen these before. I thought they were just edited versions of ROM's sucked off a existing phone. Are these compiled from scratch?
rajendra82 said:
Most of the kernel compiling struggles are documented here:
http://forum.xda-developers.com/showthread.php?t=740747
Mimocan himself has started some work on it here:
http://forum.xda-developers.com/showthread.php?t=747040
There are also people having success mixing Vibrant ROM on the Captivate with some GPS crash issues:
http://forum.xda-developers.com/showthread.php?t=746466
I am trying to follow those threads, and since I am not a deveoper, I can't personally contribute to the process. But it is interesting to me anyway.
Click to expand...
Click to collapse
hallfleming said:
I've seen these before. I thought they were just edited versions of ROM's sucked off a existing phone. Are these compiled from scratch?
Click to expand...
Click to collapse
The first two are attempts to recompile the kernel to put in the ext3/ext4 mimocan fix. The third one I believe is a script for boot logo animation hack to achieve the same thing.
I forgot to mention one more thread:
http://forum.xda-developers.com/showthread.php?t=739823
So we've got the source code with drivers and know which ones to use from the T959 for fixing the voice issue. We've got the stock kernel. What's left to creat a plain jane captivate?
hallfleming said:
So we've got the source code with drivers and know which ones to use from the T959 for fixing the voice issue. We've got the stock kernel. What's left to creat a plain jane captivate?
Click to expand...
Click to collapse
I'm guessing not too much. There are somethings that would need to be edited such as handling the capacitive buttons. The i9000 roms handle buttons differently regardless of the kernel so, its apparently an OS level config.
I've been wanting to work on this but I've been neck deep in source code from work.
Here is a good how to: http://forum.xda-developers.com/showthread.php?t=704561
Thanks for the link. The US codes out there so we don't need i9000 port
Sent from my SAMSUNG-SGH-I897 using XDA App
hallfleming said:
Thanks for the link. The US codes out there so we don't need i9000 port
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
My point was that given the I9000 rom needs source level changes in order to work as expected(haptic feedback on certain buttons, etc) then running an AOSP build may require some source level changes as well. It may not be as simple as building and flashing.
So everybody knows, I have taken over as one of the Moderators for this forum.
Feel free to PM for questions,
Hit the report button if it's something you think I should take a look at.
Pax
EDIT FROM Moscow Desire,
Pax is now retired from FSM Duties. :crying:
MD
paxChristos said:
So everybody knows, I have taken over as one of the Moderators for this forum.
Feel free to PM for questions,
Hit the report button if it's something you think I should take a look at.
Pax
Click to expand...
Click to collapse
Welcome great job thanks for being a mod;-)
Welcome~!
welcome
http://forum.xda-developers.com/showthread.php?t=1711137
can u look at this thread and see if the thors kernel was ever present if it was fine if not can we get the thread reopened AOKP would be another good option for roms for the tablet.
Timelord83 said:
welcome
http://forum.xda-developers.com/showthread.php?t=1711137
can u look at this thread and see if the thors kernel was ever present if it was fine if not can we get the thread reopened AOKP would be another good option for roms for the tablet.
Click to expand...
Click to collapse
Why not just go get it from rootzwiki if you want it so bad?
bfranklin1986 said:
Why not just go get it from rootzwiki if you want it so bad?
Click to expand...
Click to collapse
I'll stick to XDA. Not everyone on here has social skills to participate in forum discussions but i find that this site has much more information and the groups of people are more eager to help troubleshoot. by unlocking the thread if its not thors kernel it opens it up to ALL of xda to help.
Timelord83 said:
I'll stick to XDA. Not everyone on here has social skills to participate in forum discussions but i find that this site has much more information and the groups of people are more eager to help troubleshoot. by unlocking the thread if its not thors kernel it opens it up to ALL of xda to help.
Click to expand...
Click to collapse
I'm not sure how many actually remember the events relating to this earlier this year... But it was a mess.
Thor decided to start developing a ICS rom providing (presumably under apache2) the device/vender tree to the build. Just two little tidbits were, how to say, off with his approach.
a) The device tree included his kernel still without the source code (so now we have some apache2 code.. nice but not required, and its poisoned with a closed source kernel)
b) he provided links to the github repo (now deleted and/or hidden) on XDA via adfly.
After this was reported, XDA closed the thread, Thor took down the git repo and tried to pan this off to his greater followers (probably successfully) as XDA not even allowing him in when him to work here even when his code is "open".
--
While the source was open blazingwolf, ProTekk, randomblame (and some others?) managed to get the repo and clone it (or parts of it) into their own projects.. Mostly with little or no credit, and not always properly removing all traces of Thors kernel (either the main kernel was replaced with blazingwolfs open kernel, but a second copy of Thors kernel in the repo was left, or they just used thors kernel as it existed in the device tree).
In addition to this there was a recovery that used blazingwolf's kernel but otherwise was a nearly unmodified thor recovery binary (simply a hex edit to change the title, and thus hide the upstream source)
--
AOKP is now using the CM9 base for the device and vender trees, so everything including the CM9 T20 kernel is open source. However I its up to the AOKP team to re-post here at this point and not someone just wanting a mirror with their own unrelated donate link.
Some locked threads to remember in relationship to this:
http://forum.xda-developers.com/showthread.php?t=1353252 - ProTekk bit of ICS locked
http://forum.xda-developers.com/showthread.php?t=1426617 - randomblame recovery - locked
http://forum.xda-developers.com/showthread.php?t=1524919 - original A500 AOPK thread - locked
Just to clear this up, roms are under Apache v2 license (which doesn't require source release) kernels are under GPL which does require source release.
Sent from my R800x using Tapatalk 2
ezterry said:
I'm not sure how many actually remember the events relating to this earlier this year... But it was a mess.
Thor decided to start developing a ICS rom providing (presumably under apache2) the device/vender tree to the build. Just two little tidbits were, how to say, off with his approach.
a) The device tree included his kernel still without the source code (so now we have some apache2 code.. nice but not required, and its poisoned with a closed source kernel)
b) he provided links to the github repo (now deleted and/or hidden) on XDA via adfly.
After this was reported, XDA closed the thread, Thor took down the git repo and tried to pan this off to his greater followers (probably successfully) as XDA not even allowing him in when him to work here even when his code is "open".
--
While the source was open blazingwolf, ProTekk, randomblame (and some others?) managed to get the repo and clone it (or parts of it) into their own projects.. Mostly with little or no credit, and not always properly removing all traces of Thors kernel (either the main kernel was replaced with blazingwolfs open kernel, but a second copy of Thors kernel in the repo was left, or they just used thors kernel as it existed in the device tree).
In addition to this there was a recovery that used blazingwolf's kernel but otherwise was a nearly unmodified thor recovery binary (simply a hex edit to change the title, and thus hide the upstream source)
--
AOKP is now using the CM9 base for the device and vender trees, so everything including the CM9 T20 kernel is open source. However I its up to the AOKP team to re-post here at this point and not someone just wanting a mirror with their own unrelated donate link.
Some locked threads to remember in relationship to this:
http://forum.xda-developers.com/showthread.php?t=1353252 - ProTekk bit of ICS locked
http://forum.xda-developers.com/showthread.php?t=1426617 - randomblame recovery - locked
http://forum.xda-developers.com/showthread.php?t=1524919 - original A500 AOPK thread - locked
Click to expand...
Click to collapse
sadly i do but the thread i linked is albeit messy with side stuff i made the assumption it was mod locked. after talking with the other people i have foudn out that the OP requested it be locked. i went and got the rom from AOKP website and as far as i can tell is Thor free and i run clockwork recovery and V8 ICS bootloader.
As for the motives for my request is i'd like to see more roms succeed for this tablet as it is "old" tech people are moving to the tegra 3 Tabs i am not ready to give up on my $567.87 less than year old purchase. I own the A501 ATT 4G LTE Variant i bought it from ATT without contract hence the price
Uhm... Hi paxChristos! Welcome to our slightly disfunctional family! I hope that you have a great time.:silly:
Timelord83 said:
As for the motives for my request is i'd like to see more roms succeed for this tablet as it is "old" tech people are moving to the tegra 3 Tabs i am not ready to give up on my $567.87 less than year old purchase. I own the A501 ATT 4G LTE Variant i bought it from ATT without contract hence the price
Click to expand...
Click to collapse
As do we all (want larger choices in roms).
But there-in lies the issue. We have an AOKP rom that has been through many hands, and at times, had some suspicious coding involved. Including getting closed on more than 1 occassion due to shady practices and non-GPL kernels. Might have been 3 seperate roms for all we know.
To post the rom now, would probably piss off quite a few people if enough credits were not given, even if the kernel proved to be legit. And even then, you would have several people claiming the rom was theirs and they were the original authors. That's the nature of these "KANG" roms and "MIUI" roms.
Well, we have polluted PaxChristo's welcome thread enough for now. I suggest we give it a rest, and probably open a new thread in the General Forum. I'll DL and install it, and see what's up with it. Post some results later.
MD
good job
paxChristos said:
So everybody knows, I have taken over as one of the Moderators for this forum.
Feel free to PM for questions,
Hit the report button if it's something you think I should take a look at.
Pax
Click to expand...
Click to collapse
t my a500wondering where to post question about how to root my tab. Sadly it is running 3.2 honey and I am very confused as what to do to get it rooted. I am in southern Louisiana, maybe there are folks close to me that could help.
Thanks everyone don
Hey thanks for being a mod' it is a lot of work I know. Listen I am knew as I just go
Ok, this is just something I have been playing with and thought I would share.
It is CyanogenMod 7.2, as close to stock as I can make it. I have taken a lot from Ezet and some stuff from Forumber.
This is not source based as I do not have a grunty enough system to build CyanogenMod from source.
Most importantly, I have started on a new kernel based on the TomGiordano source here:
https://github.com/TomGiordano/kernel_huawei
My Kernel Source:
https://github.com/PaulMilbank/kernel_huawei/tree/cm7-u8800-35
Will upload my source once I can sort out the sources on my computer. I am doing some mods on Aurora kernel too which I will release at some point.
After a few false starts, I compiled the source with their cyanogenmod_u8800_defconfig and it works pretty well for CM7.2.
I fixed atmel vibration using DZOs aurora commits as a guide.
Probably most broken stuff is defconfig related.
Bugs:
Keypad LED's do not work
Autobrightness does not work
Light sensors do not work- probably the cause of the above problems.
Camera force closes
You tell me
Working:
Wifi works
RIL works
Screen/video drivers work well, screen does not suffer annoying no wakeup for me like other kernels.
Atmel Virtual Key vibration works
You tell me
Get It Here:
http://www.mediafire.com/?b2dc7kdmixvas18
I will try and fix all these bugs, but I would be keen for some help too. I don't have time to be a full time dev.
As always, I am not responsible for any bricks, fires or nuclear wars that come about from installing this rom.
Please, please backup with CWM before flashing this.
Paul
PaulMilbank said:
Ok, this is just something I have been playing with and thought I would share.
It is CyanogenMod 7.2, as close to stock as I can make it. I have taken a lot from Ezet and some stuff from Forumber.
This is not source based as I do not have a grunty enough system to build CyanogenMod from source.
Most importantly, I have started on a new kernel based on the TomGiordano source here:
https://github.com/TomGiordano/kernel_huawei.git
Will upload my source once I can sort out the sources on my computer. I am doing some mods on Aurora kernel too which I will release at some point.
After a few false starts, I compiled the source with their cyanogenmod_u8800_defconfig and it works pretty well for CM7.2.
I fixed atmel vibration using DZOs aurora commits as a guide.
Probably most broken stuff is defconfig related.
Bugs:
Keypad LED's do not work
Autobrightness does not work
Light sensors do not work- probably the cause of the above problems.
Camera force closes
You tell me
Working:
Wifi works
RIL works
Screen/video drivers work well, screen does not suffer annoying no wakeup for me like other kernels.
Atmel Virtual Key vibration works
You tell me
Get It Here:
http://www.mediafire.com/?b2dc7kdmixvas18
I will try and fix all these bugs, but I would be keen for some help too. I don't have time to be a full time dev.
As always, I am not responsible for any bricks, fires or nuclear wars that come about from installing this rom.
Please, please backup with CWM before flashing this.
Paul
Click to expand...
Click to collapse
Camera issue??? Please, any issues but camera
»»Sent From My U8800««
This is just to see if I can get people interested in development. I will try document as much as possible what I do and see if we can get some people interested in building a kernel and getting a really good gingerbread cyanogenmod build out. If this goes nowhere, I will just focus on Aurora kernel and ICS. There are a few things I would like to try and include in Aurora to add some features.
We need good 2.6.35 source and this is a good source with a few small bugs, probably due to the config not being completely right. Hopefully they are minor and easily fixed. We have a lot of kernel development going on around the place and we can learn from commits to make a really good build hopefully.
Will try their 7x30_defconfig to make a kernel for my B528 rom too and see what works.
If you replace the boot.img in this rom with the boot.img in Forumber's latest cm7.2 build, it sould all work and give a 2.6.35 experience close to Ezet's 2.6.32 build. It will likely not be as stable because LEWA kernel on my phone at least, is crap.
PaulMilbank said:
This is just to see if I can get people interested in development. I will try document as much as possible what I do and see if we can get some people interested in building a kernel and getting a really good gingerbread cyanogenmod build out. If this goes nowhere, I will just focus on Aurora kernel and ICS. There are a few things I would like to try and include in Aurora to add some features.
We need good 2.6.35 source and this is a good source with a few small bugs, probably due to the config not being completely right. Hopefully they are minor and easily fixed. We have a lot of kernel development going on around the place and we can learn from commits to make a really good build hopefully.
Will try their 7x30_defconfig to make a kernel for my B528 rom too and see what works.
If you replace the boot.img in this rom with the boot.img in Forumber's latest cm7.2 build, it sould all work and give a 2.6.35 experience close to Ezet's 2.6.32 build. It will likely not be as stable because LEWA kernel on my phone at least, is crap.
Click to expand...
Click to collapse
You can use VictorTeam's source.
forumber2 said:
You can use VictorTeam's source.
Click to expand...
Click to collapse
Do you know where it is, I have not been able to find it. Thanks very much man. Keen top take a look at what they have been doing.
PaulMilbank said:
Do you know where it is, I have not been able to find it. Thanks very much man. Keen top take a look at what they have been doing.
Click to expand...
Click to collapse
They have github group https://github.com/Victor-android
.35 kernel based CM7.2 would be pretty dope to me, especially if tethering works
PaulMilbank said:
Do you know where it is, I have not been able to find it. Thanks very much man. Keen top take a look at what they have been doing.
Click to expand...
Click to collapse
here:https://github.com/Victor-android/kernel_huawei/tree/2.6.35-cm-u8800
Thanks, this will likely take a while longer than I thought it would as I am having trouble getting my sources synced locally and on github. If we can pull together all the sources into a kick ass kernel, we should have a really good CM7.2, I would like a rom with built in tethering too. It will just take some time. Running through DZOs excellent repo with a readymade .config and then making small changes is a lot easier than having to make it all up as we go and sort out sources and configs. Maybe I should not have been so cocky at the start!
PaulMilbank said:
Thanks, this will likely take a while longer than I thought it would as I am having trouble getting my sources synced locally and on github. If we can pull together all the sources into a kick ass kernel, we should have a really good CM7.2, I would like a rom with built in tethering too. It will just take some time. Running through DZOs excellent repo with a readymade .config and then making small changes is a lot easier than having to make it all up as we go and sort out sources and configs. Maybe I should not have been so cocky at the start!
Click to expand...
Click to collapse
Nice to hear that someone's still working on U8800's .35 kernel. Good job so far!
PaulMilbank said:
Thanks, this will likely take a while longer than I thought it would as I am having trouble getting my sources synced locally and on github. If we can pull together all the sources into a kick ass kernel, we should have a really good CM7.2, I would like a rom with built in tethering too. It will just take some time. Running through DZOs excellent repo with a readymade .config and then making small changes is a lot easier than having to make it all up as we go and sort out sources and configs. Maybe I should not have been so cocky at the start!
Click to expand...
Click to collapse
Do you use your vendor files for compiling CM7?
forumber2 said:
Do you use your vendor files for compiling CM7?
Click to expand...
Click to collapse
No, I am just using your and Ezets prebuilt binaries and apk's. I do not have the computer power or skill to build from source!
PaulMilbank said:
No, I am just using your and Ezets prebuilt binaries and apk's. I do not have the computer power or skill to build from source!
Click to expand...
Click to collapse
But you could compile kernel?
Compiling and downloading kernel is much smaller and faster. Also their are a lot of comments and files to follow.
Compiling cyanogenmod from source is a huge download and would take forever to compile on my computer. Plus nobody documents the process well and it us specialized to the phone.
Maybe if I can get a good kernel going, others can build cyanogenmod sources for .35 kernel. It all just takes time.
Sent from my U8800 using xda premium
PaulMilbank said:
Compiling and downloading kernel is much smaller and faster. Also their are a lot of comments and files to follow.
Compiling cyanogenmod from source is a huge download and would take forever to compile on my computer. Plus nobody documents the process well and it us specialized to the phone.
Maybe if I can get a good kernel going, others can build cyanogenmod sources for .35 kernel. It all just takes time.
Sent from my U8800 using xda premium
Click to expand...
Click to collapse
Will you try your luck with cm9/10?
PaulMilbank said:
Compiling and downloading kernel is much smaller and faster. Also their are a lot of comments and files to follow.
Compiling cyanogenmod from source is a huge download and would take forever to compile on my computer. Plus nobody documents the process well and it us specialized to the phone.
Maybe if I can get a good kernel going, others can build cyanogenmod sources for .35 kernel. It all just takes time.
Sent from my U8800 using xda premium
Click to expand...
Click to collapse
if you send vendor files to me,i can compile in my free time
forumber2 said:
if you send vendor files to me,i can compile in my free time
Click to expand...
Click to collapse
Maybe Ezets here:
https://github.com/ezeteze/android_device_huawei_u8800.
Not sure otherwise. I don't have any vendor files sorry.
Use these vendor files: click. I built CM 7.2 yesterday and it works just fine with those vendor files.
Unrealized said:
Use these vendor files: click. I built CM 7.2 yesterday and it works just fine with those vendor files.
Click to expand...
Click to collapse
but in this vendor,GPU can't run fully,has a little lag. If we solve this problem,we can make a good cm7 :good:
forumber2 said:
but in this vendor,GPU can't run fully,has a little lag. If we solve this problem,we can make a good cm7 :good:
Click to expand...
Click to collapse
Guess it has something to with the "new" Adreno drivers. Might do some benchmarking later with the older ones. I haven't really experienced lagging myself though. it's kinda the same as w/ .32 based CM7 (especially when using ADWLauncher)
Hi friends. Can you check this kernel source's is real or useless?
https://github.com/nofearnohappy/android_vendor_xiaomi_hermes
https://github.com/lbule/android_device_xiaomi_hermes
This isn't a kernel source, it's a device tree for build CyanogenMod
~ Xiaomi Redmi Note 2 Prime ~
SkiFire13 said:
This isn't a kernel source, it's a device tree for build CyanogenMod
~ Xiaomi Redmi Note 2 Prime ~
Click to expand...
Click to collapse
ho great so cyanogenmod is comming?
tailslol said:
ho great so cyanogenmod is comming?
Click to expand...
Click to collapse
We will see, it is very hard to port when kernel is not given. There are people working on it and doing a very good job!
Sadly, the complete kernel (custom kernel with drivers) was leaked for a short period and a few devs have it.. but they are afraid to use or publish it because they don't want to be sued.
tailslol said:
ho great so cyanogenmod is comming?
Click to expand...
Click to collapse
For now someone built it but it's very unstable
~ Xiaomi Redmi Note 2 Prime ~
Sad news about this device's kernel source.
is this usefull?
http://forum.xda-developers.com/cro...al/marshmallow-source-codes-mediatek-t3218602
chris5932 said:
We will see, it is very hard to port when kernel is not given. There are people working on it and doing a very good job!
Sadly, the complete kernel (custom kernel with drivers) was leaked for a short period and a few devs have it.. but they are afraid to use or publish it because they don't want to be sued.
Click to expand...
Click to collapse
Wow didnt know that, really the full source kernel was leaked??? And some devs have it D:?. If its true i hope they decide one day to make a nice ROM build, i guess everyone of us would wait for that
chris5932 said:
We will see, it is very hard to port when kernel is not given. There are people working on it and doing a very good job!
Sadly, the complete kernel (custom kernel with drivers) was leaked for a short period and a few devs have it.. but they are afraid to use or publish it because they don't want to be sued.
Click to expand...
Click to collapse
Sued? The ones to be sued are mediatek and/or xiaomi for not complying gpl license
adaltavo said:
Wow didnt know that, really the full source kernel was leaked??? And some devs have it D:?. If its true i hope they decide one day to make a nice ROM build, i guess everyone of us would wait for that
Click to expand...
Click to collapse
At least someone has it.. I am not so sure on how many have it. Don't be too excited yet, we might not get it (soon). The source can not just be published to the public, the one who does will face some problems.. (see what happened to incomplete source).
chris5932 said:
At least someone has it.. I am not so sure on how many have it. Don't be too excited yet, we might not get it (soon). The source can not just be published to the public, the one who does will face some problems.. (see what happened to incomplete source).
Click to expand...
Click to collapse
May i ask what happened?. And i know is not that easy, what i meant is that he (or they) could make a nice ROM build with that source, maybe as an anonymus guy or something like that, is not necesary to publish full source code. Our another hope is wait for MTK to release it , but it wont be soon, even could never happen
adaltavo said:
May i ask what happened?. And i know is not that easy, what i meant is that he (or they) could make a nice ROM build with that source, maybe as an anonymus guy or something like that, is not necesary to publish full source code. Our another hope is wait for MTK to release it , but it wont be soon, even could never happen
Click to expand...
Click to collapse
We can build roms ourselfs, just need proper kernel. Just let me say that much: I have a reliable source that told me someone has it. I don't think (anymore) it was leaked to the public ever, all kernel leaked on git were incomplete.
All kernel sources I've seen for X10 are not for our device. Another thing is the AOSP sources are very buggy and unfinished.
I finally made progress on my AOSP 5.1 and fixed the slow app launch (maybe you've seen one youtube video posted here - this is my build).
Unfortunately I don't have kernel source for Redmi Note 2 and it is impossible to build a custom kernel, so I'm trying to finish the ROM and will use prebuilt kernel.
If you think it is easy as porting, then you're wrong. Compiling something from source and fixing all bugs is completely different animal.
CM 12.1 also booted, but a lot of work needs to be done there too.
https://github.com/omlet05/MediaTek-HelioX10-Kernel
yay?
tailslol said:
https://github.com/omlet05/MediaTek-HelioX10-Kernel
yay?
Click to expand...
Click to collapse
Check the date and please stop posting same thing again and again. This is the original broken half source that was leaked over 2 months ago now.
I.nfraR.ed said:
All kernel sources I've seen for X10 are not for our device. Another thing is the AOSP sources are very buggy and unfinished.
I finally made progress on my AOSP 5.1 and fixed the slow app launch (maybe you've seen one youtube video posted here - this is my build).
Unfortunately I don't have kernel source for Redmi Note 2 and it is impossible to build a custom kernel, so I'm trying to finish the ROM and will use prebuilt kernel.
If you think it is easy as porting, then you're wrong. Compiling something from source and fixing all bugs is completely different animal.
CM 12.1 also booted, but a lot of work needs to be done there too.
Click to expand...
Click to collapse
What is time to wake? On miui time is long :/ On our last phone (A820) time to wake is much better.
How aboute "tap to wake"? What is result on antutu? When you publish rom?
AOSP boots up and works faster than MIUI and also has much much better ram management, although it would be good if we could make a custom kernel.
Tap to wake normally needs to be supported in kernel, so the answer is "no".
Antutu score is irrelevant, but normally I get about 48K with the basic model. I've seen higher, seen lower.
It also depends on kernel.
Don't forget that for A820 I have a custom optimized kernel.
Hello
When you share rom? How to progress?
Known XDA rule, don't ask for ETA He'll tell us when ready
bumcykcyk said:
Hello
When you share rom? How to progress?
Click to expand...
Click to collapse
It will be shared when it is done.. Ussd/BT working but camera still doesnt
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.