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

I am sick of HTC delaying source code

I just sent them this
Code:
Hello,
kernel source for 1.29 and 2.05 for HTC One X is still not available.
These delays are hindering community efforts to fix your inept software and are in breach of GPL. Please provide me the link to the source to to those 2 kernels and make sure that you release the source at the same time as the binary form.
I am ready to escalate this via gpl-violations.org unless your response satisfies me.
Regards
Jan Schermer
If anybody wants to chime in, you're welcome.

Samsung is just better at this.. look at the SIII it was released after the OneX but it has many many more custom truly cocked roms!

And i'm sick of such useless posts. They will release it when they will release it. Get a life.

Why would they publish the source for a test RUU? 1.29 OK but not 2.05 yet

zvieratko said:
I just sent them this
Code:
Hello,
kernel source for 1.29 and 2.05 for HTC One X is still not available.
These delays are hindering community efforts to fix your inept software and are in breach of GPL. Please provide me the link to the source to to those 2 kernels and make sure that you release the source at the same time as the binary form.
I am ready to escalate this via gpl-violations.org unless your response satisfies me.
Regards
Jan Schermer
If anybody wants to chime in, you're welcome.
Click to expand...
Click to collapse
you forgot one main thing
2.05 is unreleased and leaked

And now no more leaked test releases lol.
Well done!!! Demand source codes for versions that aren't even released yet.
Lmao what is going on here
Sent from eXoDiZeD rom

They have to provide source code for every binary to those who got the binary. So I assume those 2.05 testers have the source for their kernels, don't they? if they did, it would leak, and we would profit from it (it's our right because so does HTC!).
Also, what devs here do is illegal - I could demand the source code from them but they don't have it - is it okay to force them into illegality just because HTC are being ignorant?
And those posts are not meaningless, they are violating GPL and withholding source code for no real reason. All source-built kernels are still based on 1.28, but they fixed a lot of stuff on 1.29, and for me (a linux professional) those hacks show in lots of places.
What are you doing here if you really want HTC-built Sense then? Do you want to run slapped-together binary ROMs because there is no source for the latest update? This is called Android Development for a reason.

zvieratko said:
They have to provide source code for every binary to those who got the binary. So I assume those 2.05 testers have the source for their kernels, don't they? if they did, it would leak, and we would profit from it (it's our right because so does HTC!).
Also, what devs here do is illegal - I could demand the source code from them but they don't have it - is it okay to force them into illegality just because HTC are being ignorant?
And those posts are not meaningless, they are violating GPL and withholding source code for no real reason. All source-built kernels are still based on 1.28, but they fixed a lot of stuff on 1.29, and for me (a linux professional) those hacks show in lots of places.
What are you doing here if you really want HTC-built Sense then? Do you want to run slapped-together binary ROMs because there is no source for the latest update? This is called Android Development for a reason.
Click to expand...
Click to collapse
you can not demand anything from an internal leaked file! in fact your possession of the leaked rom might be illegal lol

hamdir said:
you can not demand anything from an internal leaked file! in fact your possession of the leaked rom might be illegal lol
Click to expand...
Click to collapse
That might be true. But AFAIK the 2.05 RUU was provided to some public testers as well.
I just opted to demand 2.05 as well in case it takes them a month to respond and it will be released by then, it did no harm in any case.
Also, we wouldn't have to have this debate if the development was actually transparent (that means - HTC working with community, not just pushing uncompilable sources for their old kernels). But I guess most managers can't grasp that concept without the proper buzzwords.
Sorry, I'm pissed at many more things than just HTC right now, but I directed my anger here

zvieratko said:
They have to provide source code for every binary to those who got the binary. So I assume those 2.05 testers have the source for their kernels, don't they? if they did, it would leak, and we would profit from it (it's our right because so does HTC!)....
Click to expand...
Click to collapse
You can demand open source codes not closed source and to get open source android, simply get AOSP sources. HTC will publish their sources when they want and after they finish.
EOT.

AdamLange said:
You can demand open source codes not closed source and to get open source android, simply get AOSP sources. HTC will publish their sources when they want and after they finish.
EOT.
Click to expand...
Click to collapse
You know that kernel is GPL and what that means, right? Or are you just trolling? HTC is obliged to provide source code - it's not a goodwill gesture, and they consistently fail to do that.
Or are you talking just about 2.05? In that case, the first tester outside HTC should get the source code and would be free to release it to us - closed beta or not.

Some parts of kernel may be closed (for example modules). They can post kernel without them. Its like AOSP android, you can download it, and compile and use, but you will not get Android Apps (gmail,youtube etc) included. cause they are CLOSED.

AdamLange said:
Some parts of kernel may be closed (for example modules). They can post kernel without them. Its like AOSP android, you can download it, and compile and use, but you will not get Android Apps (gmail,youtube etc) included. cause they are CLOSED.
Click to expand...
Click to collapse
Yes, but they don't even post the sources without blobs...

sorr932 said:
Samsung is just better at this.. look at the SIII it was released after the OneX but it has many many more custom truly cocked roms!
Click to expand...
Click to collapse
Pmsl
TRULY COCKED ROMS

pro tip, if you don't act like a self-entitled brat when asking for something which they are required todo you are more likely to get an informed helpful response.
if that really is the email that you sent I wouldn't be surprised if it was just moved to the email bin

AdamLange said:
And i'm sick of such useless posts. They will release it when they will release it. Get a life.
Click to expand...
Click to collapse
+1:good:
Patrick Volkerdings: Its finished if its finished

sorr932 said:
Samsung is just better at this.. look at the SIII it was released after the OneX but it has many many more custom truly cocked roms!
Click to expand...
Click to collapse
Frankly ,they can have x3 more custom rom`s but we have one who is better then all SIII ROM`s together , we are so lucky and really need to be proud with our original developers like Venom Team , so S3 performance without ROM like our ViperX is in vain.
Don`t worry be happy! :victory:

Thread now closed. This thread has become off topic. I have had to remove a couple of posts that had bad language. Remember people to follow XDA rules when posting.

[Q] Official Cyanogen Mod rom. How soon?

Hello, everyone!
Dunno if it was asked before or is it thу right place to ask this, but anyway:
Is CM team going to release official CM rom? May be even someone know how soon it will be? I don't like samsung stock rom because of the bloatware it has, but I think I am not the only one.
Thanks in advance!

kortik9 said:
Hello, everyone!
Dunno if it was asked before or is it thу right place to ask this, but anyway:
Is CM team going to release official CM rom? May be even someone know how soon it will be? I don't like samsung stock rom because of the bloatware it has, but I think I am not the only one.
Thanks in advance!
Click to expand...
Click to collapse
Don't know if there will be an official build, but unofficial build by crpalmer works great.

Rutr said:
Don't know if there will be an official build, but unofficial build by crpalmer works great.
Click to expand...
Click to collapse
Yup, I saw that, just wondering if we will get official anytime soon.

kortik9 said:
Hello, everyone!
Dunno if it was asked before or is it thу right place to ask this, but anyway:
Is CM team going to release official CM rom? May be even someone know how soon it will be? I don't like samsung stock rom because of the bloatware it has, but I think I am not the only one.
Thanks in advance!
Click to expand...
Click to collapse
I've never quite figured out why people get so hung up on "official"... When there is an official build of CM, it will still be me maintaining it and the only differences will be that:
* you'll get nightly and M builds which makes them more frequent
* you'll get slower device specific updates to the core software (right now I change it and build it, when it's official it can take weeks to get a change in the frameworks approved and you won't see it until it's approved).
that said, it will be official but doing so takes effort from me and from other people that are very busy and so all I can say is it isn't official yet.

crpalmer said:
I've never quite figured out why people get so hung up on "official"... When there is an official build of CM, it will still be me maintaining it and the only differences will be that:
* you'll get nightly and M builds which makes them more frequent
* you'll get slower device specific updates to the core software (right now I change it and build it, when it's official it can take weeks to get a change in the frameworks approved and you won't see it until it's approved).
that said, it will be official but doing so takes effort from me and from other people that are very busy and so all I can say is it isn't official yet.
Click to expand...
Click to collapse
Actually before creating this thread I saw your "unofficial" build thread and checked your profile to see if you are somehow connected to CM dev team, but you have no information in your profile. I don't like unofficial builds because often they have something tuned\installed\uninstalled, but I like how CM works and I don't want anything else, this is why I want official build. But in this case I think I should try your build, as you maintain official ones anyway.
Thanks for clarifying this!

kortik9 said:
Actually before creating this thread I saw your "unofficial" build thread and checked your profile to see if you are somehow connected to CM dev team, but you have no information in your profile. I don't like unofficial builds because often they have something tuned\installed\uninstalled, but I like how CM works and I don't want anything else, this is why I want official build. But in this case I think I should try your build, as you maintain official ones anyway.
Thanks for clarifying this!
Click to expand...
Click to collapse
Not necessarily having visibility into any framework changes I've made is a pretty reasonable concern. There's only one change that I have already submitted for review so nothing too magical going on behind the scenes. Everything else is available in my public git repos for anyone to verify.

Most of the time official builds start out as unofficial builds. At least that's what I've noticed.

Did Google release all the code for the 5X yet?

Just curious since I'm wondering when development on ROMS and kernels will begin. Thanks!

lysm bre said:
Just curious since I'm wondering when development on ROMS and kernels will begin. Thanks!
Click to expand...
Click to collapse
So far after looking at the Nexus binaries page, and the sources for device trees, and kernel repositories found here Google hasn't updated it yet. I imagine they will shortly as more devices are shipped to people.

Don't think so. Once they do it should show up here: https://android.googlesource.com/

shimp208 said:
So far after looking at the Nexus binaries page, and the sources for device trees, and kernel repositories found here Google hasn't updated it yet. I imagine they will shortly as more devices are shipped to people.
Click to expand...
Click to collapse
Ah ok makes sense. Can't wait for development to start!

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