Develop Bugs

[DEV][DEV-ONLY] Honeycomb Progress

[This is not the place to say "this is awesome" or "thanks!"]
[DEVS ONLY]
I want to start this thread to keep up the progress on the port.
the bad news is that the SDK is incomplete for now, so (like other devices)
we will have to write our own code for the OS, the nook community
has done a wonderful job writing their own libraries and stuffs, so we will have to do the same.
Instead of pursuing different goals, let's focus on one thing at a time.
since GSM and CDMA versions are already out, it seems we suffer the same bugs, so for now let's unite strength and knowledge to overcome these.
I propose that the first goal to fix is the SurfaceFlinger, so we could at least see the apps, the buttons and the notifications.
it is currently throwing this:
04-06 22:01:35.495: ERROR/Surface(2960): dequeueBuffer failed (Out of memory)
this could lead us that it might coudln't start because of some malloc malfunction or something.
also that pvrsrvinit bugs me a lot.
update:
8/APR/2011
since DiP7 could fix SurfaceFlinger and other things using a different build from the GSM kernel, we have to dig deeper
======================================
CURRENT GOAL
Rebuild Kernel
======================================​
Current approaches:
*none
Post any finding, guessing or anything, and please, please don't be afraid to ask anything you have a doubt, as a Dev you should not know everything, so we can help us each other
------------------------------------------
Google Easter egg:
while searching some info about the android.mk file , I put it on the chrome bar to search for that term, but instead I went to
http://android.mk
an easter egg web page from google lol

******TOOLS*********
How to send text and Keystrokes via ADB
http://bradchow.blogspot.com/2011/02/send-intent-and-key-event-by-adb.html
use DroidExplorer to easily access your device from your computer and makes changes from it
http://de.codeplex.com/
The Android Boot Process
http://www.androidenea.com/2009/06/android-boot-process-from-power-on.html
---Kernel Tools----
CPU Datasheet
http://forum.xda-developers.com/showthread.php?t=745877
Samsung GIT
http://android.git.kernel.org/?p=kernel/samsung.git;a=summary
PowerVR SDK
http://www.imgtec.com/powervr/insider/powervr-sdk.asp
Source code of samsung firmwares(keep and eye on this)
http://opensource.samsung.com/
Asus pad honeycomb Kernel Source
http://forum.xda-developers.com/showthread.php?t=1026528

ellokomen said:
======================================
CURRENT GOAL
Find why SurfaceFlinger is not working
======================================​
Click to expand...
Click to collapse
Mmmk.. Let me tell you a story.
A long time ago in a galaxy far away... No, that will take too long. In a nutshell, one third of the answer is here, another third is here and the rest is here. I'm not trying to be intentionally vague, I just haven't figured out how these three fit together yet.
Of course, there could also be some bit of code that I missed... some telling line in a debug log that I overlooked or some driver or library that I could have decompiled to sift through its juicy secrets. There could easily be a fix that would take seconds to add and make the whole thing fall in line...
Or we might have to work it from the ground up.
Either way it will happen. It's just a matter of whether it will happen next week, or next month.
(Watch it be a misplaced semi-colon, or a bad symlink... that's how these things go.)

updated approaches and new tools have been added

spacemoose1 said:
Mmmk.. Let me tell you a story.
A long time ago in a galaxy far away... No, that will take too long. In a nutshell, one third of the answer is here, another third is here and the rest is here. I'm not trying to be intentionally vague, I just haven't figured out how these three fit together yet.
Of course, there could also be some bit of code that I missed... some telling line in a debug log that I overlooked or some driver or library that I could have decompiled to sift through its juicy secrets. There could easily be a fix that would take seconds to add and make the whole thing fall in line...
Or we might have to work it from the ground up.
Either way it will happen. It's just a matter of whether it will happen next week, or next month.
(Watch it be a misplaced semi-colon, or a bad symlink... that's how these things go.)
Click to expand...
Click to collapse
The kernel source that you have linked to is 2.6.35.7 for the Nexus S gingerbread and is not fully maintained by samsung but rather by google.
However I do not think you are wrong that there is a problem somewhere in the kernel. The kernel that has been released for the galaxy tab is a mess of horrid code, I have had to re-write parts of kernel drivers just to get them to work under linux, I would not be surprised if similar patches are needed for honeycomb

lilstevie said:
The kernel source that you have linked to is 2.6.35.7 for the Nexus S gingerbread and is not fully maintained by samsung but rather by google.
However I do not think you are wrong that there is a problem somewhere in the kernel. The kernel that has been released for the galaxy tab is a mess of horrid code, I have had to re-write parts of kernel drivers just to get them to work under linux, I would not be surprised if similar patches are needed for honeycomb
Click to expand...
Click to collapse
you mean that you made a port of a Linux Distro into the tab?

ellokomen said:
you mean that you made a port of a Linux Distro into the tab?
Click to expand...
Click to collapse
yes click here for the thread on the port of ubuntu

Current kernel source
Do you guys have another link to the current spacemoose kernel source? The download link seems to be corrupted and won't untar. I want to get in on the fun

noobporter said:
Do you guys have another link to the current spacemoose kernel source? The download link seems to be corrupted and won't untar. I want to get in on the fun
Click to expand...
Click to collapse
here it is, bear in mind that this is for CDMA devices

Unfortunatey, we have 4 other honeycomb threads.
Not trying to be rude but spacemoose updates us in the cdma forums AND we have russian rom updates in the gsm forums.
I really dislike the idea of this thread, there is enough clutter amongst the other threads. Do we really need one more place to browse..
The first posts in the roms thread are kept updated by devs.. Is this not enough??

daml said:
Unfortunatey, we have 4 other honeycomb threads.
Not trying to be rude but spacemoose updates us in the cdma forums AND we have russian rom updates in the gsm forums.
I really dislike the idea of this thread, there is enough clutter amongst the other threads. Do we really need one more place to browse..
The first posts in the roms thread are kept updated by devs.. Is this not enough??
Click to expand...
Click to collapse
yeah but we need a place for the other devs to share their milestones, here is a place for technical discussion amongst us, to share the knowledge etc...
the other threads are flooded from non devs messages, so it´s kind of difficult to read 14 pages of information when the 80% is people complaining not making it boot

lilstevie said:
The kernel source that you have linked to is 2.6.35.7 for the Nexus S gingerbread and is not fully maintained by samsung but rather by google.
Click to expand...
Click to collapse
Yes, and it contains some support for our device (s5pc110), and some more that can be added (pvr) and the architecture necessary to fully support HC without patching the build itself. If we work only towards patching the system build to communicate with the hardware, we won't be able to run AOSP hc versions when the source drops without going through the same painstaking process of hacking the system to function (while creating numerous faults causing FCs in the process). If we build a new kernel, we can get the hardware to communicate in the way future android versions want it to and we can then do what we want with ease.

noobporter said:
Do you guys have another link to the current spacemoose kernel source? The download link seems to be corrupted and won't untar. I want to get in on the fun
Click to expand...
Click to collapse
D'oh! Nobody told me, LOL... I'll get another copy up.

spacemoose1 said:
D'oh! Nobody told me, LOL... I'll get another copy up.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1026528
hey spacemoose! the first portion of honeycomb source... The kernel source of the Asus EEE Pad Transformer... maybe it helps you with a few kernel issues, even if it's for another device... It's honeycomb!

Flokey said:
http://forum.xda-developers.com/showthread.php?t=1026528
hey spacemoose! the first portion of honeycomb source... The kernel source of the Asus EEE Pad Transformer... maybe it helps you with a few kernel issues, even if it's for another device... It's honeycomb!
Click to expand...
Click to collapse
Digging through it now.

spacemoose1 said:
Yes, and it contains some support for our device (s5pc110), and some more that can be added (pvr) and the architecture necessary to fully support HC without patching the build itself. If we work only towards patching the system build to communicate with the hardware, we won't be able to run AOSP hc versions when the source drops without going through the same painstaking process of hacking the system to function (while creating numerous faults causing FCs in the process). If we build a new kernel, we can get the hardware to communicate in the way future android versions want it to and we can then do what we want with ease.
Click to expand...
Click to collapse
Not enough really, PVR kernel module sources have been released from samsung for our device, and is available in update1 zip.
The kernel panics and we have no framebuffer from the nexus s, believe me that is the kernel I want to be running for my project, it is cleaner nicer and things are implemented overall better. unless you know of a solution for kernel debuging over usb

lilstevie said:
Not enough really, PVR kernel module sources have been released from samsung for our device, and is available in update1 zip.
The kernel panics and we have no framebuffer from the nexus s, believe me that is the kernel I want to be running for my project, it is cleaner nicer and things are implemented overall better. unless you know of a solution for kernel debuging over usb
Click to expand...
Click to collapse
Kernel debugging over USB = adb shell cat /proc/kmsg
You can make any kernel work for any device as long as you add the **** it needs. Just takes time. Working on it now.

Goal and tools updated*

spacemoose1 said:
Kernel debugging over USB = adb shell cat /proc/kmsg
You can make any kernel work for any device as long as you add the **** it needs. Just takes time. Working on it now.
Click to expand...
Click to collapse
You don't know what a kernel panic is do you?

lilstevie said:
You don't know what a kernel panic is do you?
Click to expand...
Click to collapse
I thought that linux throws a dump log when it makes a kernel panic specifying the memory address and the cause of crash

[Q] Compile kernel

I thought of developing a kernel so that i can use it with my CM11 that im going to port shortly. I thought I'll compile the stock kernel from source itself. I use android pre-built tool chain (arm-eabi-4.6)
I get a lot of compiler errors on stock kernel without any modifications itself...
Do i need to change my tool chain?
Sent from my One V using XDA Free mobile app

I never tried to build the stock kernel, but I think they did it with the android 4.0 toolchain.
To run CM, you need a CM-Kernel. You have to port things from the stock or a custom kernel (like Hellboy by maxwen) to the cm11 kernel.
Try to use rastomanchiks kernel sources (https://github.com/rastomanchik/android_kernel_htc_primou). This kernel is mostly working, stable and has a good battery life now.
I'd also like to build cm11, but my download speed is to slow to download the sources.

Exactly. Even my download speed is slow. And i have a cap also. After 8GB, my download speed drastically decreases. It takes ages to sync the sources...
Sent from my One V using XDA Free mobile app

How different is Cm kernel from stock? I mean what changes should i make?
Sent from my One V using XDA Free mobile app

Cm needs many features which aren't included in the stock kernel and also you should get ION memory allocator working.

Help
jonas2790 said:
Cm needs many features which aren't included in the stock kernel and also you should get ION memory allocator working.
Click to expand...
Click to collapse
Yeah. How do I port?
What happened to your CM12 project?

hehaichi said:
Yeah. How do I port?
What happened to your CM12 project?
Click to expand...
Click to collapse
I started working on cm12 again yesterday and finally have cm11 sources now, so expect a cm11 build in some days
I can't help you with porting, because all the porting work was done by rastomanchik and I chatted with him. You'd have to ask him about this, but he wasn't online the last weeks and can't speak english without google translator.

jonas2790 said:
I started working on cm12 again yesterday and finally have cm11 sources now, so expect a cm11 build in some days
I can't help you with porting, because all the porting work was done by rastomanchik and I chatted with him. You'd have to ask him about this, but he wasn't online the last weeks and can't speak english without google translator.
Click to expand...
Click to collapse
Actually I insist on porting myself so that I can learn building properly.
Actually these things are also interesting.. fixing bugs and all...
Have series of exams till May end. I cant build properly until then. I thought why not learn something..
Where did you learn about building and other stuff. Also I want to build the device tree on my own.
If you could specify some sources to learn, that would be grateful!

hehaichi said:
Actually I insist on porting myself so that I can learn building properly.
Actually these things are also interesting.. fixing bugs and all...
Have series of exams till May end. I cant build properly until then. I thought why not learn something..
Where did you learn about building and other stuff. Also I want to build the device tree on my own.
If you could specify some sources to learn, that would be grateful!
Click to expand...
Click to collapse
This is exactly the same point of view I had when I started some months ago
Sadly, there isn't much documentation about own device trees and own kernels out there.
There also is no reference device tree, so every dev does it in his own way. I'm always trying to have a clean, easy device tree and use the CM ones as a reference.
You can find some tutorials about building cm, but only with downloading a ready-to-use device config and kernel.
I just played around with it one or two weeks and learned the most.
If you have enough time, please at least try to get into this stuff, maybe we can get cm12 running.
You can reach me on irc in the channel #hov on freenode.

jonas2790 said:
This is exactly the same point of view I had when I started some months ago
Sadly, there isn't much documentation about own device trees and own kernels out there.
There also is no reference device tree, so every dev does it in his own way. I'm always trying to have a clean, easy device tree and use the CM ones as a reference.
You can find some tutorials about building cm, but only with downloading a ready-to-use device config and kernel.
I just played around with it one or two weeks and learned the most.
If you have enough time, please at least try to get into this stuff, maybe we can get cm12 running.
You can reach me on irc in the channel #hov on freenode.
Click to expand...
Click to collapse
I have sufficient time only after May. Till then I'll have to do some research and learn the basics.
I saw on the CM wiki page, it says you can run a prebuilt kernel also... So would it work if we could tweak the stock kernel a bit?
And how do I apply patches to the kernel?

hehaichi said:
I have sufficient time only after May. Till then I'll have to do some research and learn the basics.
I saw on the CM wiki page, it says you can run a prebuilt kernel also... So would it work if we could tweak the stock kernel a bit?
And how do I apply patches to the kernel?
Click to expand...
Click to collapse
Yes you can use a prebuilt kernel, but it will only work if the kernel supports you cm version.
You apply patches to a kernel by changing files or directories in the kernel. For example you can use another fs module (maybe with more functions) by copy and pasting the folder for the module from another kernel. The problem is, the new module may require some functions your kernel does not have so it won't compile.

Hey i had mailed rastomanchik and he said 3.4.x kernel is an impossibility for cm11? Why?
Sent from my One V

hehaichi said:
Hey i had mailed rastomanchik and he said 3.4.x kernel is an impossibility for cm11? Why?
Sent from my One V
Click to expand...
Click to collapse
1. It would be much, much, much work.
2. I think there are some device-specific drivers that only work with 3.0

I'm ready to do that work only if i knew how to...
Sent from my One V

hehaichi said:
I'm ready to do that work only if i knew how to...
Sent from my One V
Click to expand...
Click to collapse
Try to get into it yourself or talk with people who know about kernel developement, I'm also new to android developement.

Device tree ready for marshmallow

Hey guys its devut again informing you that HOX's Device tree is nearlyready!!!
UPDATE: DEVICE TREE IS NOW COMPLETE
Nearly
Yes Nearly because libdgv1 is still taking time
libdgv1
http://dmitry.gr/index.php?r=06. Thoughts&proj=04. Android M on Grouper
Here it states that we get a lot of problem because
Code:
dlopen()
is a POSIX COMPLAINT:crying::crying:
So here it is nearly perfect Marshmallow device tree
https://github.com/DevUt/android_device_htc_endeavoru/tree/Marshmallow-begins-part-1

I also have not tested it for new layout
If you are a developer then please check it
[ Do not go for storage_list.xml (as it is deleted , go for fsatb)]

Another issue (damn it)
Proprietary-files.txt has a problem ! Will fix it soon

DevUt said:
Another issue (damn it)
Proprietary-files.txt has a problem ! Will fix it soon
Click to expand...
Click to collapse
*finger crossed*

bopung said:
*finger crossed*
Click to expand...
Click to collapse
I think it will take alot of time cause it is verrryyyy confusing

Added issue section in my github repo
1 issue added
you guys also help me by telling me the issues in code

Should i add wiki to my repo to guide other developer?
Or should leave them on their own to figure out how to make libnvos and other thing works ( cause just looking at the tree you wont be able to understand because the patches are also in proprietary files )?

And another great news the device tree wil be ready till Monday!! :laugh: :good: ????????????

Device tree complete now no monday
DevUt said:
And another great news the device tree wil be ready till Monday!! :laugh: :good:
Click to expand...
Click to collapse
(After this many ppl)
Critic : Monday ? What! You are so slow DevUt!
DevUt : Sorry , Thats the way im!
DevUt : But for other HOX DEVS
DEVICE TREE IS NOW COMPLETE
NOW NO MONDAY
DEV GET THEIR HANDS ON!

Awesome!I was planning to get an s4 but since the hox will actually get mm I will stick to it.Great work,you are awesome dude

MaRtYy01 said:
Awesome!I was planning to get an s4 but since the hox will actually get mm I will stick to it.Great work,you are awesome dude
Click to expand...
Click to collapse
My pleasure dude
I predict you will see mm till mid may cause my net is slow
Thanks for Patience and all your support
But if you wanna try to make a rom from this tree you can (please check the issue section if there are none then please proceed to building if there is even 1 Stop ; I will fix it )

Guys i just found out that we need to have a newer version of twrp to flash marshmallow on our hox. So here's my thought
First i will Fix the device tree ( yes i will be adding some more. Patch files which are on my local pc)
Then as we already have the kernel available for marshmallow.
And then i will build the new twrp and it all in a post

Guys fact of the matter : HOX doesn't runs well on newer roms! And yes thats the bitter truth for every Phone once its old it losses its powet
But why
Here's a logical answer : It is in the way the developer makes the newer roms!
What !
Yes ! Actually the devs just patch some existing files and add some new ones and release it !
And i dont blame the devs for it cause nobody will waste his/her time in writing everything from kernel , Device tree ,proprietary files they sum upto millions and millions of files
Thats causes the problem.
So whats the solution
The solution is nothing! But as a HOX lover i would love to take this whole summer for HOX
So whats your plan
My plan is after releasing marshmallow i would work to write the whole thing scratch (not exactly scratch) but i will make it the most stable rom for HOX
I know im making many promises but believe me i would make them true :highfive:

Thank you for your work, I'm looking forward to marshmallows for HOX.

I'm out of the station for 10 days will come and back to work ASAP

Is this a rom?

sagor1 said:
Is this a rom?
Click to expand...
Click to collapse
The ROM is nearly ready ! Source code has been downloaded tweaks have been made to the device tree ( necessary for ROM ) so you will see the ROM soon . This thread was made to keep updated my fellow friends with my status

Guys bad news my laptop screen has disturbed it is showing vertical lines I will send to soon for repairs and continue until then see my github progress ! You have surprise in both the kernel and my own profile

DevUt said:
The ROM is nearly ready ! Source code has been downloaded tweaks have been made to the device tree ( necessary for ROM ) so you will see the ROM soon . This thread was made to keep updated my fellow friends with my status
Click to expand...
Click to collapse
With sense or without sense?

sagor1 said:
With sense or without sense?
Click to expand...
Click to collapse
Without, its based on cm13
Sent from my Nexus 7 using XDA-Developers mobile app

[KERNEL] -> tegra-3.18_unified_dragon_kernel_11_v201218 (DISCONTINUED)

Due to several reasons I have stopped the deployment of the "monthly Update.Zip packages" !
Thanks for your understanding.
This thread will be used for the unified tegra-3.18 kernel only.
Twelve:
tegra-3.18_unified_dragon_kernel_12_v211213.zip
Eleven:
tegra-3.18_unified_dragon_kernel_11_v201218.zip
Ten:
tegra-3.18_unified_dragon_kernel_10_v201010.zip
Pie:
tegra-3.18_unified_dragon_kernel_p_v200310.zip
Oreo:
tegra-3.18_unified_dragon_kernel_o_v200310.zip
Changes/Features:
- Upstream to kernel version 3.18.140
- Various patches and security updates
- Added Wireguard support
- Added/Enabled various file systems (exFat, NTFS, Network Filesystems .. etc.)
- Changed kernel config to enable/improve support for varioius services (tethering .. etc.)
- Added "fix cpu frequency limitation"
- etc.
Installation:
1. Boot into TWRP
2. Install the Kernel Update.Zip file
3. Reboot into system .. no need for SuperSU / Magisk !
The package contains an Image.fit kernel binary only - and no ramdisk part !
This way the kernel should run on all available Android Oreo/Pie/Ten ROMs for the dragon device.
And there is no need for a new SuperSu/Magisk installation afterwards, unlike to "full boot.img" installation.
Sources:
https://github.com/followmsi/android_kernel_tegra
https://github.com/followmsi/lazyflasher/tree/followmsi-dragon
https://github.com/followmsi/AnyKernel2/tree/dragon
Download:
https://drive.google.com/drive/folders/18cqluw7lp1S720QdV0p-OtHfY9MNpSwn
Big thanks to @NYCHitman1 (Dirty Unicorn), @cheep5k8 (xceed), @Vartom and updateing from Team Mokee for the nice kernel sources !
Big thanks to @osm0sis (Anykernel2) and @jcadduono (lazyflasher) for the nice tools !
Enjoy

flashed your system image
devices does not boot
flashed back to stock
boots
edit: further details
every boot just dumps me into recovery.

dmitrygr said:
flashed your system image
devices does not boot
flashed back to stock
boots
edit: further details
every boot just dumps me into recovery.
Click to expand...
Click to collapse
Thanks for feedback .. no good news.
Sorry, I can not reproduce your problem.
Tested the system_vendor udapte.zip several times on my Pixel C.
No problem so far ...
You flashed the complete .zip via TWRP ?
What was your previous firmware level ?
Did you upgrade bootloader as well ?
What kernel do you have in use ?
EDIT:
Which Version of TWRP ?
Pls use xceed version for now.
The NYChitman1 version seems to have problems.
http://forum.xda-developers.com/pix...ock-bootloader-install-custom-t3307183/page14

followmsi said:
The NYChitman1 version seems to have problems.
http://forum.xda-developers.com/pix...ock-bootloader-install-custom-t3307183/page14
Click to expand...
Click to collapse
Only the latest one I released because I didn't put the proper flag in place -- the previous one works perfectly fine as indicated by myself and others.
Also, I find it interesting that you've created a development thread while you aren't actually developing anything.

Thanks for the update.
Still like to test your version.
Ok, the version from here is recommended .. http://forum.xda-developers.com/showpost.php?p=66557703&postcount=101
In the one from yesterday you fixed vendor image flashing via TWRP.. sounds nice.
When do you re-release this version ?
You may open a new thread for your TWRP releases ..
Thanks a lot for all your work!

New kernel released ... pls test
Update.ZIP_Nexus_Ryu_chromeos-3.18-kernel_v160519_followmsi.zip
There are lot of changes in compare to latest stock kernel .. https://chromium.googlesource.com/chromiumos/third_party/kernel/+log/chromeos-3.18/
Cheers

followmsi said:
New kernel released ... pls test
Update.ZIP_Nexus_Ryu_chromeos-3.18-kernel_v160519_followmsi.zip
There are lot of changes in compare to latest stock kernel .. https://chromium.googlesource.com/chromiumos/third_party/kernel/+log/chromeos-3.18/
Cheers
Click to expand...
Click to collapse
Many thanks for your work The kernel is for stock / AOSP roms? Running Dirty Unicorns and I think it´s not compatible :/

redukt said:
Many thanks for your work The kernel is for stock / AOSP roms? Running Dirty Unicorns and I think it´s not compatible :/
Click to expand...
Click to collapse
There are so many fixes since MXC89F kernel .. which was commited on Arpil 5th .. even it's the May release. Ok, was tagged on May, 4th.
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/MXC89F
Last changes .. 6 weeks ..
https://chromium.googlesource.com/c...+log/9c052efad6e651d33334b84c8f1feaf8945e8e7a
I am running the new kernel on latest M stock release .. MXC89F.
No problems so far .. really stable.
The kernel should run on all stock M releases for PixelC.
Used latest stock ramdisk to build the kernel .. maybe the dirty unicorn ramdisk is different.
But the actual kernel should work as well ..it's a dragon kernel.
Repack DU ramdisk with my kernel and it will most probably work as well .. maybe even with the same ramdisk, without repacking. Needs to be tested ..
Give it a try .. it will not hurt.
Cheers

Any chance of getting a port of multirom? Let me know if there's any interest, and what I can do to help.

nic. said:
Any chance of getting a port of multirom? Let me know if there's any interest, and what I can do to help.
Click to expand...
Click to collapse
Sounds good .. have it running on Nexus 7 flo .. really like it.
MultiROM for PixelC would be really nice .. the chromeos is part is maybe tricky.
But like SuperSU .. automatic chromeos image unpack and repack, if required at all.
It seems Tassadar is not around anymore .. not sure if he will come back.
Some new guys have taken over .. they just made a new update release for TWRP and MultiROM..
Works fine
Are you able to port it to Pixel C ?
Thanks

followmsi said:
Give it a try .. it will not hurt.
Cheers
Click to expand...
Click to collapse
Bootloop
Restored my Nandroid and device is up
DU is CM based and unfortunately incompatible :/

followmsi said:
Sounds good .. have it running on Nexus 7 flo .. really like it.
MultiROM for PixelC would be really nice .. the chromeos is part is maybe tricky.
But like SuperSU .. automatic chromeos image unpack and repack, if required at all.
It seems Tassadar is not around anymore .. not sure if he will come back.
Some new guys have taken over .. they just made a new update release for TWRP and MultiROM..
Works fine
Are you able to port it to Pixel C ?
Thanks
Click to expand...
Click to collapse
I am wanting to dig into the Linux4Tegra side of this, and was hoping that some of the work for multirom could or had been done. I don't know anything about the chromeos bootloader. Looking into it, Chrubuntu might be a viable path for this. I feel like this device is gimped with Android.

redukt said:
Bootloop
Restored my Nandroid and device is up
DU is CM based and unfortunately incompatible :/
Click to expand...
Click to collapse
Thanks for the test ..
Restore DU boot.img and you are back to normal ..yep
I will unpack the DU boot.img and have short look .. just to check it.

nic. said:
I am wanting to dig into the Linux4Tegra side of this, and was hoping that some of the work for multirom could or had been done. I don't know anything about the chromeos bootloader. Looking into it, Chrubuntu might be a viable path for this. I feel like this device is gimped with Android.
Click to expand...
Click to collapse
Sounds like a lot of work .. but if you have the right people involved ..
Maybe xceed or nychitman will know better how to "manage" the bootloader ..
As I know, until today, "nobody" knows how to remove the 30 second warning time beep sound ****.
Right now I am happy to "manage" the layer above .. boot.img and recovery.img

redukt said:
DU is CM based and unfortunately incompatible :/
Click to expand...
Click to collapse
What are you talking about? We're not CM based.
followmsi said:
There are so many fixes since MXC89F kernel .. which was commited on Arpil 5th .. even it's the May release. Ok, was tagged on May, 4th.
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/MXC89F
Last changes .. 6 weeks ..
https://chromium.googlesource.com/c...+log/9c052efad6e651d33334b84c8f1feaf8945e8e7a
I am running the new kernel on latest M stock release .. MXC89F.
No problems so far .. really stable.
The kernel should run on all stock M releases for PixelC.
Used latest stock ramdisk to build the kernel .. maybe the dirty unicorn ramdisk is different.
But the actual kernel should work as well ..it's a dragon kernel.
Repack DU ramdisk with my kernel and it will most probably work as well .. maybe even with the same ramdisk, without repacking. Needs to be tested ..
Give it a try .. it will not hurt.
Cheers
Click to expand...
Click to collapse
I had been keeping up with the chromeos-3.18 branch upstream, but I realized that a majority of the commits do not even apply to Dragon -- so it wasn't all that worthwhile to have in the majority of cases. With that said, I decided to go back to the MXC89F source until the next batch of source is released in June.

NYCHitman1 said:
What are you talking about? We're not CM based.
Click to expand...
Click to collapse
Well my bad...DU is AOSP based. I get mixed up with all several custom roms on my devices :silly:

NYCHitman1 said:
What are you talking about? We're not CM based.
I had been keeping up with the chromeos-3.18 branch upstream, but I realized that a majority of the commits do not even apply to Dragon -- so it wasn't all that worthwhile to have in the majority of cases. With that said, I decided to go back to the MXC89F source until the next batch of source is released in June.
Click to expand...
Click to collapse
You are right .. there also many fixed not relevant for dragon at all.
But it´s a fresh kernel .. upstream
I was so free .. and made a new DU kernel now .. used your ramdisk and my fresh chomeos-3.18 build from today.
@redukt, please test this kernel again .. on DU
Update.ZIP_PixelC_Ryu_chromeos-3.18-kernel_DU_v160519_followmsi.zip
https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Thanks .. still bootloop ?

redukt said:
Well my bad...DU is AOSP based. I get mixed up with all several custom roms on my devices :silly:
Click to expand...
Click to collapse
Please test this one ... Update.ZIP_PixelC_Ryu_chromeos-3.18-kernel_DU_v160519_followmsi.zip
https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Thanks !

followmsi said:
Please test this one ... Update.ZIP_PixelC_Ryu_chromeos-3.18-kernel_DU_v160519_followmsi.zip
https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Thanks !
Click to expand...
Click to collapse
!!! Device is booting!!!
Meh... forget to install SU lol.... Will have a look in kernel auditor
Many thanks
edit: I have to flash the latest supersu (beta v2.74-2) to get root again. Will test your kernel til the next DU weeklie as dd. I´ll have a look at the frequency overview and kept stock settings / governor. System runs fluid with no hickups or so. Great work!

Looks also very interessting ..stabilize-smaug-7897.B-chromeos-3.18
https://chromium.googlesource.com/c...kernel/+/stabilize-smaug-7897.B-chromeos-3.18
Will see .. today they released the 3rd N preview ... maybe it´s time for some N testing.
As I understand correct .. using N ramdisk and the same kernel from today should work on N as well.
We will see ...
Cheers

General Finally! RM8P kernel code source is already released

(Dear Valued RedMagic Customer,
Thank you for your patience,
Please check the source code at https://github.com/ztemt. If you cannot access the connection, please refresh the interface and try again the next day. Thank you for your understanding.)
Edit :
It's already released.
Now I hope the developers start creating fantastic roms for this beast phone

salahomer said:
(Dear Valued RedMagic Customer,
Thank you for your patience,
Please check the source code at https://github.com/ztemt. If you cannot access the connection, please refresh the interface and try again the next day. Thank you for your understanding.)
Click to expand...
Click to collapse
Isn't our device NX729J? I don't see kernel source released for this... Sounds like they giving you the run around. They would sell a lot more phones if they did release. I almost didn't buy one due to this.. Hopefully they will release it soon.
Edit: Cool! It's finally released!

JWnSC said:
Isn't our device NX729J? I don't see kernel source released for this... Sounds like they giving you the run around. They would sell a lot more phones if they did release. I almost didn't buy one due to this.. Hopefully they will release it soon.
Click to expand...
Click to collapse
Very soon, not now...so let us wait a few more days or weeks

JWnSC said:
Isn't our device NX729J? I don't see kernel source released for this... Sounds like they giving you the run around. They would sell a lot more phones if they did release. I almost didn't buy one due to this.. Hopefully they will release it soon.
Click to expand...
Click to collapse
I see there are 7S and 6S kernels, but I don't see any custom ROMs for them, so idk if we will see any for this phone too.

The repo is now available, however, it's empty by the time of me posting this now. It took them two weeks just to create the repo, that's insane. Well, at least it finally happened. Waiting for sources to be uploaded, they probably have to use slow vpn or something to do that, so it might take quite a bit of time.

What can we do with the kernel source?

So it is here.

JWnSC said:
Isn't our device NX729J? I don't see kernel source released for this... Sounds like they giving you the run around. They would sell a lot more phones if they did release. I almost didn't buy one due to this.. Hopefully they will release it soon.
Click to expand...
Click to collapse
Edit :
It's already released, check again.
Now I hope the developers start creating a new fantastic roms for this beast phone

Well, apparently we'll have to write drivers for our device:
Code:
# nubia driver
drivers/nubia
arch/arm64/configs/vendor/nubia
arch/arm64/configs/vendor/NX729J_diff.config
arch/arm64/configs/vendor/NX729J-perf_diff.config
arch/arm64/configs/vendor/NX729J_driveronly.config
This is from .gitignore, so we can't build this kernel and run it i.e. on stock rom.

aaa.bbb111222 said:
Well, apparently we'll have to write drivers for our device:
Code:
# nubia driver
drivers/nubia
arch/arm64/configs/vendor/nubia
arch/arm64/configs/vendor/NX729J_diff.config
arch/arm64/configs/vendor/NX729J-perf_diff.config
arch/arm64/configs/vendor/NX729J_driveronly.config
This is from .gitignore, so we can't build this kernel and run it i.e. on stock rom.
Click to expand...
Click to collapse
So... What does that mean for new custom roms

gwenmillett said:
So... What does that mean for new custom roms
Click to expand...
Click to collapse
We're not gonna see them until someone writes these drivers or zte publishes them. Both are very unlikely, so...

Seems like they uploaded it again, on zips. I checked and it seems to contain several things inside the /drivers/nubia folder so we probably have now a full workable kernel source