//opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=GT-P6200
I notice maybe we are using Tab2 source code with some inconvenience. There is a P6200 source code wish it can help you.:victory:
The eagle has landed
ICS source GT-P6200!!!
https://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=GT-P6200
Looks like the same crap we are dealing with with the HC sources. No device driver source. Weak.
Seriously, Damn. Still no Wifi. Those weasels.
looks like it says Update1? maybe there will be a 2 or 3?
Devs: Can we Haz Project Butter??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Been wondering when you guys would discover this, been playing with it for a day and a half now .
It does have wifi source, but Samsung modified wpa_supplicant as well, which you can tell by looking at the init.rc and seeing that they don't pass any of the required arguments for wpa_supplicant (them not releasing these modifications is breaking wpa_supplicant's GPL). Because of this, and because they probably included an interface for wpa_supplicant to load (not necessarily licensed under the GPL), you can't just use the wifi modules with ASOP based builds, but you can use them in stock based builds.
Also, just as an FYI, this kernel is prone to the superbrick. There are a number of instances of the superbrick using stock recovery with the ICS release on the GT-P6800, so beware of wiping/factory resetting using the stock ICS recovery.
Thanks locerra, youre all over this stuff.
So what are our options for wifi for say an ASOP ICS/JB? Find source code somewhere? Is it possible to mod/hack together something?
I would be content with a jellybean with no wifi.
Thanks for everything guys.
chrisrotolo said:
So what are our options for wifi for say an ASOP ICS/JB? Find source code somewhere? Is it possible to mod/hack together something?
Click to expand...
Click to collapse
Hack something together, I'm looking through the differences between the wifi driver and the upstream linux kernel's wifi driver -- that one worked except for the fact that the signal range was awful and the battery performance was terrible. JB is a ways off -- probably not until there is at least a leak from samsung for some exynos4210 device, as there are some huge changes in audio and the audio chip in the tab is extremely funky.
Thanks.
Yeah im still upset about incall earpiece volume. Speaker is fine.
Damn. There must be something else we can do about audio for jellybean.
Thanks for your help and info.
6210 ICS source is live!
Its named update2
6200L ICS source is available.
according to samfirmware 6200L is indonesia and trinidad & tobago.
I think this is a model without IR port.
Probably nearly identical to ATO release
LATIN JB Source for P6200L up... http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=GT-P6200
And I dont see any JB update for 6200L on samfirmware.. weird.
GT-P6200 JB source live.....http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=GT-P6200
Does it has much meaning to our developer?
Especially for bluetooth driver??
Sent from my GT-P6200 using xda premium
For the Developers:
Galaxy Tab 3 7.0 Source Code: http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=SM-T210
Related
I'm using MIUI rom for my Nexus S. I have tested Netarchy kernel, the most complete of his genre, but it give me stability issues.
I want take the default android kernel and add some non-invasive features like overclock, bln, etc. wich let's MIUI run stable.
My problem is that i don't know how i can edit a kernel. Unpack .img files, decompile and recompile them.
Anyone can help me with a small introduction?
Thanks a lot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
dario3040 said:
Click to expand...
Click to collapse
seems like a reasonable request :S
I have to laugh?
fede91it said:
I'm using MIUI rom for my Nexus S. I have tested Netarchy kernel, the most complete of his genre, but it give me stability issues.
I want take the default android kernel and add some non-invasive features like overclock, bln, etc. wich let's MIUI run stable.
My problem is that i don't know how i can edit a kernel. Unpack .img files, decompile and recompile them.
Anyone can help me with a small introduction?
Thanks a lot.
Click to expand...
Click to collapse
first of all, wrong section..even though it is about "development"...still a question
anyways, there is no way to "edit a kernel" they have to be built from source. changes need to be made before you compile it.
there are many threads here on xda with tutorials -search >compile kernel<
a simple way to start is seach >mkbootimg< normally this would be compiled from source as well but there are a few threads that people have posted tutorials of the ins and outs and have packages for download.
basically with that you can "split" a boot.img separating the ramdisk (specific to the rom) and the kernel...then merge "your" miui ramdisk with a working (or built for other rom) kernel
You can start here:
http://forum.xda-developers.com/showthread.php?t=1039854
Moved to Q&A.
Samsung has oppened a GIT repository for our phone 2 days ago (more convenient than the usual sources tarballs), as you can see on this page : https://opensource.samsung.com/guest/listMyCommunity.do
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is the repository : git://opensource.samsung.com/p_411
I am sorry buddy but can u tell me that how it will be beneficial for us??? Sorry I have dont have knowledge about this but want to know eagerly about this.
Instead of messing with the tarballs used by Samsung to provide the GPL parts of kernel & co, they opened a git repository, which is more convenient to retrieve the source code. (Try Google if you want more informations )
It's good for the kernel devs, and source on the repository might be more up to date than the actual tarball provided by Samsung (can't verify, I'm at work)
means now kernal coding will be more convinient to kernal coders??
can add TV-OUT with this source code?
As I understand, the stuff in there is already spreaded in the web. It's just a repository good for starters, isn't?
Does coderworkx can find anything relevant for CM (that he does not already have/know)?
u mean to say that we have the access to the opencore, kernels and rom now? thats a great thing if thats what happend.
I think this can be of very good help...i see some omap3 stuff and camera stuff
This isn't helping !
These files do we have a 4 months now.
Oh then the same old source files
Sent from my GT-I9003 using XDA App
thanks a lot!
I think code has already had most of the files created/grabbed before this was released. Which is somewhat depressing :\ because this may be considered useless
How can you tell if it was the same exact files? Maybe it just looks the same for the most part because it is the source after all but maybe the official release has some more stuff or some updated files that will make the kernels and roms work properly...
Just hoping for that CM7 to work flawlessly. hehe
Same date of old fiorano.. Same files
Inviato dal mio GT-I9003 usando Tapatalk
I think skin will explain this better.
I'm running cm10 4.1.1
Just wondering what kernels are compatible with cm10. I have used the app sgs flasher to flash a kernel in the past. Would this work now? And I'm looking for a kernel that would improve battery.
Here's my exact info:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SGH-I997 using xda app-developers app
Dr_Nacho said:
I'm running cm10 4.1.1
Just wondering what kernels are compatible with cm10. I have used the app sgs flasher to flash a kernel in the past. Would this work now? And I'm looking for a kernel that would improve battery.
Here's my exact info:View attachment 1390927
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
About a month ago. I was able to use sgs-kf in gb to flash a cm9/cm10 kernel while in GB. I think it failed in cm9/cm10 when I tried to flash a gb kernel.
idk if the author has updated the app or not.
You can flash up, but not down.
For the most part, Scott and jt has been the only ones working on cm10 - jt's cm10 kernel in buried in the thread somewhere a few months back. I made a shell to flash a cm10 kernel in there too, a few posts after jt dropped his kernel. I packed that kernel into a cwm flashable shell for cwm 5.x and 6.x.
You can use that shell to flash your cm10 kernels. CM10 flavors will be Scott's work or Jt's work.
i dont think you can flash an mtd cm10 kernel, i dont really know how the mtd conversion scripts work and sgskf says unsuported kernel type or something. non mtd, early cm10 or current cm9 should be aboe to use it but like qkster said might not downgrade....
but about kernel selection use whats in the rom thread. in general different aosp kenrels can be somewhat compatible but there is soo much going on with aosp development and things are constantly changing with feature support and drivers (i think the wifi drivers are mostly being used from the galaxy tab or something).. and partitions that most kernel only partially work with other roms, so stick to matching the kernel to the rom by developer and release date.
I want to port Firefox OS to our i9001 and I want to try a different approach this time:
I Instead of compiling a working build, I will try to take a Firefox OS rom and I will port it. After taking a few roms apart, it appears to me that a B2G rom doesnt contain many things different from android. I found a S2 rom that is like a modified version of CM.
But I dont have got that much time atm, so you will have to be patient
If anybody is interested in helping me, I would be very happy
Hints:
- B2G is based on AOSP, not on CM
- Use CM9 (arco) as base (it's the most stable ICS rom available imo)
- Use the CM9 stock kernel along with some files of this ramdisk (of course you will have to modify it): https://github.com/mozilla-b2g/initramfs-galaxy-s2-ics
- Use CM9 as many /bin and /lib files of CM9 as possible, the ones generated for the S2 are incompatible.
- If it doesn't boot try using the libandroid_runtime.so file from B2G
- Use DDMS or Android Monitor to explore the errors
Good Luck! It's not an easy job ^^
You can read this thread, maybe help you
http://forum.xda-developers.com/showthread.php?t=1799287
_suke_ said:
You can read this thread, maybe help you
http://forum.xda-developers.com/showthread.php?t=1799287
Click to expand...
Click to collapse
He is the one that started that other thread...xD
broodplank1337 said:
Hints:
- B2G is based on AOSP, not on CM
- Use CM9 (arco) as base (it's the most stable ICS rom available imo)
- Use the CM9 stock kernel along with some files of this ramdisk (of course you will have to modify it): https://github.com/mozilla-b2g/initramfs-galaxy-s2-ics
- Use CM9 as many /bin and /lib files of CM9 as possible, the ones generated for the S2 are incompatible.
- If it doesn't boot try using the libandroid_runtime.so file from B2G
- Use DDMS or Android Monitor to explore the errors
Good Luck! It's not an easy job ^^
Click to expand...
Click to collapse
This will help that much! Thank you!
Azrael^^ said:
He is the one that started that other thread...xD
Click to expand...
Click to collapse
That´s true...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CM start CM13 Branch
One S get Android M?
Maybe we can build it now from source?
It's too soon. I doubt there's even one device working on this branch. Just check http://review.cyanogenmod.org/#/q/status:merged+branch:cm-13.0 regularly.
No Lollipop rom is enought stable to be daily for now, so not sure Android 6.0 rom is usefull if not fully working too...
I know for a fact Evita has booted on M, Lots of broken stuff I bet, only a matter of time before CM starts fixing stuff up
Good news. I try to build for Ville almost every week. Wait & see, nothing really new on Gerrit for our device these days; but 8960 related sources are updated daily.
Maybe now?
Hi, does anyone have news for cm13 on our old htc one s ?
Thanks
No, not ready and almost no work for our device. There's a makefile circular dependency problem I can't figure out.
Hi all,
I found this file :
https://www.androidfilehost.com/?fid=24407100847292564
So it seems that there is a CM13 build for our Ville... Has anyone tried this build ? I couldn't find any info on this build and I can't boot in recovery using buttons on my device so I need feedbacks before I attempt to flash this rom... Thanks!
Edit : I had a mail from the developer who told me it's a project but it doesn't boot yet...
My wife has a galaxy note 2. There's no official cm 13 for it like ours but there's already marshmallow ROMs out for it. How is that possible? Anyone have any insight or can point me in the right direction of getting a build for our ville?
Now we can download CM 13
Download
Only 2.16 HBOOT
Any bugs revealed?
Installed CM13 on hboot 2.16. It seems everything is ok. 3 Hours runtime... no errors or crashes.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've been running it since this morning. Haven't had any crashes or reboots. Fm Radio doesn't work. Had to download new adb drivers for adb or fastboot to work.
Fm Radio works fine for me
FM working well. ( of course with headphones )
Things that make you go hmmm. Downloaded and flashed again and still get this. My headphones work on any other app or phone.
What radio are you guys using?
I use stock fm radio apk from cm13