Anxiously awaiting working cameras (at least front facing camera) on my Galaxy tab 10.1, I was wondering why one can't use the source from some of the other models that allready have got source released.
Sure, the Galaxy tab 2 series use a different cpu, but are the camera modules different? Is there no other phone/tablet with source code released that use either the same camera, or a phone running tegra 2 and ics with a similar setup?
nai1sirk said:
Anxiously awaiting working cameras (at least front facing camera) on my Galaxy tab 10.1, I was wondering why one can't use the source from some of the other models that allready have got source released.
Sure, the Galaxy tab 2 series use a different cpu, but are the camera modules different? Is there no other phone/tablet with source code released that use either the same camera, or a phone running tegra 2 and ics with a similar setup?
Click to expand...
Click to collapse
Pershoot will try to adapt the driver from the 10.1v for the 10.1, however we should also get our own source soon enough so try to be patient a bit. It can get very tiresome to see so many people asking for camera. Please try to understand the feelings of people who read a lot of posts about the camera. Asking won't help. I know you tried to help with your suggestion, but it will be done when its done, so please be patient.
Thanks for the reply
I used to have a Xperia Arc earlier, and I saw alot more porting of firmware back and forth from related phones on that forum. I just haven't seen the same method beeing used on the galaxy 10.1 part of XDA, but of course, the xperia range is made up of a bunch of (almost) identical phones with different screen sizes.
I guess the only samsung phone with Tegra 2 is the Galaxy R, which hasn't got a ICS build either yet, and all of the other tegra based tablets from samsung are also still awaiting ICS.
I am getting a bit annoyed with samsung though, what's the big holdup? This tablet was also given away on Google IO for dogs sake! You would think that they would prioritize it a wee bit since they know that several thousand android developers own one of these tablets.
Porting roms is not the same as porting drivers.
Also, there is a thread for such complaints.
Related
There is a great description of the ways to get ICS on Atrix from crnkoj:
crnkoj said:
So lets try to get some light into it, the issue about hw acceleration for the atrix is that, even now that nvidia released proper ICS binaries, those are made for recent kernel versions (post 2.6.39 and 3.x versions), those libs are floating around and are accessible to most people who would want to build stuff with hw acceleration, the problem on the atrix however is we only have 2.6.32 kernel sources from motorola, which in term means all the libs floating around are incompatible and useless. Now there would be two general ways of fixing this: 1. get libs that work with 2.6.32 kernels but are ics compatible (most improbable, except if moto leaks them and is still to lazy to move on from the 2.6.32 kernel) 2. get or make post 2.6.39 kernel sources that have the atrix's proprietary drivers including or rewritten (actually more probable, but still quite low chances, except if moto releases and ICS build for the photon/atrix or someone knows, has the time and will to write these code from scratch for the newer kernel versions). So as you can see this is quite a grim outlook, its still being worked on by community devs as far as my information are up-to-date, but i dont know which aproach they are choosing. There is however a minor glimpse of hope, since the move to integrate android drivers in the mainline/mainstream linux kernel is happening in the 3.3 kernel version (there are 3.2.x versions as of now), so this might be actually the best bet, hoping that most of the atrix proprietary drivers will be supported in it, one could just use the "nvidia libs floating around", another thing is nvidia is maintaining their own tegra2/3 kernel sources, so combined with the 3.3 move to android drivers and nvidia implementing support for tegra into their sources, it might not look so grim for us anymore, but this is all a developing story.
Click to expand...
Click to collapse
Also, there is another comment from one of the CM developers:
OK, since so many people are asking: The reason I'm doing the OMAP devices first is because the fine folks at Texas Instruments have, as before, published their reference code. (and Google's current reference device, the SGN, is an OMAP4, which also helps considerably).
The Optimus 2X (and its TMoUS brother, the G2x) is a Tegra2, and nVidia has, as always, published a total amount of zero useful lines of code; at this point, my time is better employed at getting CM9 off the ground with devices in which I can write code than it would be at figuring out how the hell to support old tegra binaries. It'll happen, but not in the near future.
Click to expand...
Click to collapse
According to this, there are some plans of CM-developers to make some kind of wrapper to use GB tegra binaries for ICS on GB kernel. Great!
Also, a question from me. LG has announced ICS on O2X. Will this release help us? I saw that some developers used O2X GB binaries for Atrix, and it worked even better Can we do the same trick with ICS binaries and get fully working ICS on ICS kernel?
v.k said:
Also, a question from me. LG has announced ICS on O2X. Will this release help us? I saw that some developers used O2X GB binaries for Atrix, and it worked even better Can we do the same trick with ICS binaries and get fully working ICS on ICS kernel?
Click to expand...
Click to collapse
You can never be sure on the software world, but I hope so. A Motorola ICS release would definitely be better though.
Interesting information, thank you!
Easier said than done...
But thanks for sharing the info.
Sent from my Atrix 4G using Tapatalk
Hopefully something will get worked out. I have no plans on leaving this phone as I love the FP scanner too much
if i'm correct, samsung's galaxy r and captivate glide are both tegra 2 phones and they run on the 2.6.36 kernel, which supports hw acceleration to a certain degree, does this help us?
i'm wondering what would be the best choice of CM9 from other devices to get the port from?
SGSII? NOTE?
please advice.
Seems note has the near the same hardware spec with 7.7, but s2 has the official 4.03 from samsung
Sent from my GT-P6800 using XDA Premium HD app
I started from the s2 source (see the thread in the dev-section), unfortunately I have gotten really busy with work so I won't really be able to put much time into it right now. If you are interested in working on it, go look at the repos I posted in that thread. I've most recently been trying to get the touch to work properly, however, the driver for it in the 7.7 source code is a complete mess, and more complicated than other drivers that have been fixed for ics.
I have GT-P6800, does same repository apply to it?
All but the android_device_samsung_p6810 should, and that last one should be easy to convert. If you are interested in working on it, I would suggest forking the common ones so that we can share our work easily.
I'm interested in working on a P6800 too.
Hello Folks,
I am a Recognized XDA Developer and I work on Cyanogenmod for Samsung Galaxy SL I9003 which is an exact similar device to Galaxy Tab P1010 (TI OMAP3630).
We have got fully working CM9 and CM10 on Galaxy SL, with few minor issues with video recording and laggy interface. However, we are working on porting the new 3.0.8 kernel that was released on omapzoom. This new kernel would help us resolve issues that we have been affecting ICS and JB releases.
So far, we have managed to get the kernel booting with few basic stuff like Touchscreen, Panel, Audio, Keypad, Vibrator working. Galaxy SL is exactly similar to Galaxy Tab P1010 WIFI and it essentially shares the same kernel and I suspect that most of the userspace stuff also should be the same. I was informally asked by cdesai if I was interested to develop for this device, but I had to turn my back since I wasn't really having the time for it.
However, since we are working on a new kernel for Galaxy SL from scratch, I would really like to take the initiative of making something useful for P1010 too, keeping in mind the small user base for Galaxy SL, we thought our work could be useful for P1010 and would benefit more people.
We would like developers working on P1010 to come forward and let us know the current status of development on this device (Kernels, Custom Roms, Attempts at CM, etc), so that we could plan something accordingly. Also, we would be interested to know how many people actually own this device and would like to have CM over it. Let's use this topic as a playground!
Sources for Galaxy SL
Stable CM9 and CM10
Kernel: https://github.com/teamhacksung/android_kernel_samsung_latona
Device: https://github.com/teamhacksung/android_device_samsung_galaxysl
Experimental 3.0 Kernel
https://github.com/dhiru1602/android_kernel_samsung_latona
Thank you!
Let's do it people, I'm willing to help dhiru as well.
I'm in too
@dhiru (Y)
This is fantastic news, and thanks for considering the P1010 as everywhere else I've looked hasn't really got anywhere. While I'm afraid I won't be able to help with any of the development (I wish I could, but I'm too busy as it is), I can use my device for testing. Keep it up, and I can't wait until it's all sorted.
Personally, I'd love to have any version of CM on this tablet, as Android 2.3.6 is looking really dated now, and the interface is laggy compared to that of Android 4.1 devices. I've upgraded to CM10 on my Galaxy S and it's so much smoother than it was, I can only hope the same is possible for this device, as it's certainly capable.
Also, I know Motofoca over on the MadTeam forums was working on it (which you already know, most likely), but he's not mentioned anything towards progress in a while. I can't post a link though, considering I've got less than 10 posts, so you'll have to google it.
Any help I can give is gladly offered, now when it comes to coding I am rusty... In fact I think the rust has extra layers of rust but know what I am looking at and can spot the bugs and offer suggestions.
I have two of these and still think the actual build of them is excellent so would love to have some decent internals
Sent from my LT26i using xda app-developers app
Seems like there are not many who own this device. That's sad.
dhiru1602 said:
Seems like there are not many who own this device. That's sad.
Click to expand...
Click to collapse
I'm owning a P1000 too (as per the question of the OP) and I would really like to have a current CM 10.1 release with kernel 3.0 on it... I'm a java developer with some C++ background but I didn't have the time yet to dive into android development (neither high nor low level)..
If there is anything to test or provide info about just ask..
dhiru1602 said:
Seems like there are not many who own this device. That's sad.
Click to expand...
Click to collapse
P1010 here !
Greets from Perú
dhiru1602 said:
Seems like there are not many who own this device. That's sad.
Click to expand...
Click to collapse
I have a P1010 and I also like to help!!!
I wanna help too!
P1010 here! Can't Dev but will gladly test!
Sent from Razr Maxx running Full Throttle Killer Bean
I've got a 1010. I'm a themer, not a dev though..
i have it too. i'am an Indonesian.
friesoft said:
I'm owning a P1000 too (as per the question of the OP) and I would really like to have a current CM 10.1 release with kernel 3.0 on it... I'm a java developer with some C++ background but I didn't have the time yet to dive into android development (neither high nor low level)..
If there is anything to test or provide info about just ask..
Click to expand...
Click to collapse
I don't know whether this was a typo or not, but you can get CM10 or CM9.1 (stable) for the P1000 already. Just look on the cyanogenmod site for the P1. This is for the P1010 which is the WIFI only version of that tab and doesn't yet have a release of cyanogenmod for it.
dhiru1602 said:
Seems like there are not many who own this device. That's sad.
Click to expand...
Click to collapse
I've been waiting for this, I can test on my p1010
dhiru1602 said:
I am a Recognized XDA Developer and I work on Cyanogenmod for Samsung Galaxy SL I9003 which is an exact similar device to Galaxy Tab P1010 (TI OMAP3630).
..
Also, we would be interested to know how many people actually own this device and would like to have CM over it. Let's use this topic as a playground!
..
Thank you!
Click to expand...
Click to collapse
Hi, I have it. I also have some experience with kernel on Omap4 (I developed for 3.0.x and 3.2.x), but very little time to share at the moment.
Please post here in this thread any update or request.
Thanks
P1010 here also. Plenty of processing power and a website for storage and distribution...
Sent from my VM "Evo 3D" using 2ʞןɐʇɐdɐʇ .
I'm also willing to test. These tabs are great, just not many developers working with them.
p1010 with cm10
Looking forward to trying their huge creations from Ecuador ... CMs for the P1010, do not let this device die. Sorry for my English, I hope this well written ..
Hello guys, I also have a P1010! maybe I can help you as a tester, I have experience with flashing and rooting
Hi there!
Currently thinking of grabbing a Oppo Find 5, but I won't make the same mistake again I did with the Galaxy S2 - updates, quite no doc/source for custom ROMs etc.
So, how open is the Oppo?
I see, that CM has landed, but how much is open sourced or are at least the interfaces docuemented?
Thanks for clarification!
Didn't find much on that subject...
aliander said:
Hi there!
Currently thinking of grabbing a Oppo Find 5, but I won't make the same mistake again I did with the Galaxy S2 - updates, quite no doc/source for custom ROMs etc.
So, how open is the Oppo?
I see, that CM has landed, but how much is open sourced or are at least the interfaces docuemented?
Thanks for clarification!
Didn't find much on that subject...
Click to expand...
Click to collapse
almost everything is open.CM10.1 took less than a month to move from alpha to nightly.The other AOSP and AOKP roms took just days.It's an open device with source available!!
hackarchive said:
almost everything is open.CM10.1 took less than a month to move from alpha to nightly.The other AOSP and AOKP roms took just days.It's an open device with source available!!
Click to expand...
Click to collapse
Thanks for the fast reply!
Could you give me some details on what is open/working and what gives us trouble?
I assume that the sound part is difficult to get by, as they claim to have some Dirac HD licensed - given I don't know Dirac HD and their licensing policy...
aliander said:
Hi there!
Currently thinking of grabbing a Oppo Find 5, but I won't make the same mistake again I did with the Galaxy S2 - updates, quite no doc/source for custom ROMs etc.
So, how open is the Oppo?
I see, that CM has landed, but how much is open sourced or are at least the interfaces docuemented?
Thanks for clarification!
Didn't find much on that subject...
Click to expand...
Click to collapse
Do note that two former GS2 CM maintainers have this device, and we both like it.
The real key is that it's Qualcomm-based (qcom has excellent documentation), and Oppo doesn't deviate far from Qualcomm's CAF reference sources.
We also now have access to a technical contact who can answer some questions for us - many of the camera issues in CM should have been improved last weekend thanks to a tip from Oppo.
For me right now, the big question is how hard it is to get to the UART port of the device, since I think I'm going to need it for an upcoming effort.
They had wifi, bluetooth and soon camera working on Cyanogenmod 9 because the Broadcom drivers were released, why can't there be Cyanogenmod 11? Even the Galaxy Mini had it so it wouldn't be a hardware problem.
1 - because there are no drivers - the drivers that were released were for ics and still very buggy and needed alot of fixes
2 - would need a brand new kernel not currently possible
3 - qualcomm released all their sources for mini
4 - questions ironically go in question and answer section NOT general section
5 - this has been covered so many times and is now boring
6 - use the search next time
galaxyYtester said:
They had wifi, bluetooth and soon camera working on Cyanogenmod 9 because the Broadcom drivers were released, why can't there be Cyanogenmod 11? Even the Galaxy Mini had it so it wouldn't be a hardware problem.
Click to expand...
Click to collapse
...
Galaxy Mini and Galaxy Mini Plus have different hardware. Galaxy Mini uses Qualcomm chipsets whereas Galaxy Mini Plus have the Broadcom BCM21553 chipset, which is the same as the Galaxy Y chipset. You clearly mixed the two up.
Also, the reason why we only have a buggy CM9 is because we do not have the necessary libraries (drivers, in a sense) to build CM9. The libraries Broadcom provided us at the end of February needs to be developed upon for it to be usable for CM9. These libraries, however, are only compatible with up to 4.0.4 which is CM9.1. These libraries cannot be used for JellyBean (CM10) or KitKat (CM11).
Please read the current state of things carefully before posting. We already have a lot of threads asking the same thing.
Ok thanks, I'm not so much into coding but thanks for answering!
Why can't they release all the drivers? What are they losing when doing it, it only helps people?
galaxyYtester said:
Why can't they release all the drivers? What are they losing when doing it, it only helps people?
Click to expand...
Click to collapse
Cause broadcomm as known as un-Open Source
They have their own reasons. Though some workers of Broadcom have assisted us in a few ways (I heard).
And don't bother with petitions either. There was one or two and only the first one actually succeeded in getting 10000 sigs but it was ignored by Broadcom so...