CM10 Coming Soon For Galaxy SL i9003
Thanks To dhiru1602
{
"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"
}
He is a great developer.thanks dhiru
Sent from my GT-I9003 using xda app-developers app
Can't wait for JB :good::good:
I am doubtful that how much smoothly JB will run on our phone without kernel 3.x. Because JB has 60 fps which makes it faster & snappier but without kernel 3.x its not possible.
H/W acc should work
i think it will work without kernel 3.x, same as working in galaxy s i9000 with CM10. H/W acc also working in galaxy s i9000, i hope same will work for our phone galaxy sl i9003.
as many samsung and sony phones are working with ICS and JB on kernel 2.6.xx.
zerocool420 said:
i think it will work without kernel 3.x, same as working in galaxy s i9000 with CM10. H/W acc also working in galaxy s i9000, i hope same will work for our phone galaxy sl i9003.
as many samsung and sony phones are working with ICS and JB on kernel 2.6.xx.
Click to expand...
Click to collapse
buddy sony developers have backported nearly everything from kernel 3.x to kernel 2.6.xx. And galaxy i9000 has stable kernel 3.x thats why it has smooth h/w acceleration.
vishal24387 said:
I am doubtful that how much smoothly JB will run on our phone without kernel 3.x. Because JB has 60 fps which makes it faster & snappier but without kernel 3.x its not possible.
Click to expand...
Click to collapse
I believe instead of being pessimistic we should be optimistic....
Anyway Im desperately waiting for CM10..!!
project butter is the main feature,but we might be missing it till we get kernel 3.x:fingers-crossed:
TheDarkLord1997 said:
I believe instead of being pessimistic we should be optimistic....
Anyway Im desperately waiting for CM10..!!
Click to expand...
Click to collapse
i think he is just realistic...we need 3.x for jelly bean ( just like for ics ) =)
if sony can,then why we can't
vishal24387 said:
buddy sony developers have backported nearly everything from kernel 3.x to kernel 2.6.xx. And galaxy i9000 has stable kernel 3.x thats why it has smooth h/w acceleration.
Click to expand...
Click to collapse
if sony devices can run ICS and JB on kernel 2.6.xx, then why can't our phone????
zerocool420 said:
if sony devices can run ICS and JB on kernel 2.6.xx, then why can't our phone????
Click to expand...
Click to collapse
the devices working great with 2.6.x.x ,they dont need hardware codecs and so much **** to run smooth ics.. probably our chipset needs kernel 3.x to run ics smoothly.
Vishal is too negative lately
The kernel just makes it "easier", it doesn't make it "possible" or "not possible".
The only differences in Jelly Bean from ICS are:
1) A modified CPU Governor that responds with touch input
2) Triple Buffering
3) Improved Vsync
Most of these mods are at kernel level but isn't that hard to port to ICS, or even GB 2.3.6. Look at the Galaxy W forum, they had managed to backport Triple Buffering and VSync to one of their Gingerbread 2.3.6 Roms back in March. Check it here.
Skander1998 said:
Vishal is too negative lately
The kernel just makes it "easier", it doesn't make it "possible" or "not possible".
Click to expand...
Click to collapse
I am not sounding negative buddy We all have to understand that comparing our phone with other phones having complete different platform would be really a big mistake. Most of the sony phones have qualcomm chips which dont need kernel 3.x to smoothly run ICS. Without kernel 3.x they can backport most of the features to kernel 2.6.x which helps them to run ICS. But in our case omap 3630 has screwed everything. It needs specifically kernel 3.x to run ICS. Dhiru has already tried backporting but he also gave up because he came to know its screwing whole kernel stability.
So if we have to blame then we should not blame to samsung only but to omap 3630 TI platform also.
vishal24387 said:
I am not sounding negative buddy We all have to understand that comparing our phone with other phones having complete different platform would be really a big mistake. Most of the sony phones have qualcomm chips which dont need kernel 3.x to smoothly run ICS. Without kernel 3.x they can backport most of the features to kernel 2.6.x which helps them to run ICS. But in our case omap 3630 has screwed everything. It needs specifically kernel 3.x to run ICS. Dhiru has already tried backporting but he also gave up because he came to know its screwing whole kernel stability.
So if we have to blame then we should not blame to samsung only but to omap 3630 TI platform also.
Click to expand...
Click to collapse
No vishal ever since you got that title of yours, you've been more negative sad to say. I hope you can stop being so pessimistic and look on the bright side buddy, from what I can infer you absolute need video recording, so just wait patiently, till then being negative is of no help.
Sent from my GT-I9003 using xda app-developers app
+1 .vishal no offense but i have seen many of your posts n u do tend to look on the negative side of things.cheer up dude our phone is not as bad as u imagine.the only problem is a dearth of devs as our phone is not so well known
As regards to video recording, it partially works on cm9 alpha 10 n dhiru has assured it will get it working soon.n Cm10 is due for release!!
All's not lost
vishal24387 said:
I am not sounding negative buddy We all have to understand that comparing our phone with other phones having complete different platform would be really a big mistake. Most of the sony phones have qualcomm chips which dont need kernel 3.x to smoothly run ICS. Without kernel 3.x they can backport most of the features to kernel 2.6.x which helps them to run ICS. But in our case omap 3630 has screwed everything. It needs specifically kernel 3.x to run ICS. Dhiru has already tried backporting but he also gave up because he came to know its screwing whole kernel stability.
So if we have to blame then we should not blame to samsung only but to omap 3630 TI platform also.
Click to expand...
Click to collapse
I wouldn't agree with that...Qualcomm is proprietary, they don't have open source drivers, but they do release their source code because there is a big audience. OMAP is actually an easier platform to work with, we have so much information to work with, such as omappedia.org or omapzoom.org. If you look at Bam's github, you'll see that some of the mods he uses are from the omapzoom mailing lists. Its not that our platform is harder to work with, its just that we don't have lots of developers working on this phone since it was only released in a few countries. If anything, Qualcomm, Nvidia and Exynos are harder platforms to develop on since they are closed source, that is why codeworkx is working more on I9100G than I9100 (OMAP vs Exynos). Cheer up, as there are other phones on XDA with a stable CM on our 3630/PowerVR 530 SoC using kernels from Gingerbread or as far back as Froyo like the Motorola Defy with an Official Cyanogenmod. This hints that a stable CM is possible on our device.
Sorry guys. If I look like -ve personality. I really never want to become pessimistic. Actually other phone's development makes me really annoy. Till today (nearly after 1.5 yrs from release of our phone) everytime we have suffered alot. Incomplete cm7, miui, cm9, no voodoo, no dual boot, unstable low freq 120 mhz, 200 mhz & many other things etc all indicates that we are not getting a single complete aosp rom having good stability & good kernel features. I am not at all blaming developers here. I am frustrated because this phone is so complecated for implementation of kernel & other mods. You ask aditya, doomlord etc kernel developers. They have also mentioned same thing that if u do a single change & booooo....kernel wont boot at all. Codeworkx also tried alot to get kernel 3.x booting with UART but no success. As compare to our phone other phones are much easier to mod at kernel level. My point is that from development point of view our phone is a mess. Samsung + TI OMAP chip is really a worst combination. Keeping positive hopes is one thing but relying on positive hopes for a long time when world around us changing very fast with latest mods & updates is a different thing. And most imp thing that if any of us still get a chance to replace our phone with similar price phone having very good development like stable aosp roms with good kernels then I am damn sure that 70% of us will happily replace their phone. Also if ur frnd asked u that if he has 18000 Rs in hand & want to buy a good phone for daily use & development wise also then u will definitely not suggest this phone. Our phone has really good specifications but TI platform & samsung has screwed this like hell.
zerocool420 said:
if sony devices can run ICS and JB on kernel 2.6.xx, then why can't our phone????
Click to expand...
Click to collapse
Do u know what does "Legacy & Low Activity Devices" mean? We are the ass of android 4.X
What u all say is correct, but according to me satisfaction varies at individual level .take my eg-
These are the problem in current cm9-
1.Wi-Fi tethering- i live in hostel in rural area-no Wi-Fi no problem
2.video recording- hardly ever use
3.No YouTube hd playback- where i live i have 2g n lucky if the mobile xda site opens.YouTube not even in my reach.
So basically i can live with cm9 alpha ten for the rest of my phone days.i am happy with my cm9 as it is now.
All other things like dual boot n voodoo sound are personal preferences n i for one don't care about it.
I think we should b satisfied by what our devs give instead of moaning
Related
I tried looking for this, but wasnt able to get any hits.
Is the hardware between the SGS and SGS II so different that a stock rom of the SGSII cannot be used as a basis for an SGS rom?
krook1 said:
I tried looking for this, but wasnt able to get any hits.
Is the hardware between the SGS and SGS II so different that a stock rom of the SGSII cannot be used as a basis for an SGS rom?
Click to expand...
Click to collapse
They are totally different phones. different modems, cpu, screen, memory, size, chips, basically every way phones can be different. No way a transfer of a ROM between the two would work.
There is a 2.3.3 ROM that has some of the apps and features of the SGSII called SimplyGalaxyII i think, look in the dev section. THat is the closest we will get.
little8020 said:
There is a 2.3.3 ROM that has some of the apps and features of the SGSII called SimplyGalaxyII i think, look in the dev section. THat is the closest we will get.
Click to expand...
Click to collapse
Yep - http://forum.xda-developers.com/showthread.php?t=1076724 This as about as close as you will get for now.
Thank you.
I was hoping that there was some way based on the sources shared (by Samsung) that a kernel could be built for the Cappy. But it looks like there too many differences to be able to take advantage of the fixes that they've put in.
krook1 said:
Thank you.
I was hoping that there was some way based on the sources shared (by Samsung) that a kernel could be built for the Cappy. But it looks like there too many differences to be able to take advantage of the fixes that they've put in.
Click to expand...
Click to collapse
Do you use the same drivers on your computer for all ati cards just because their built by Ati?
Sent from my SGH-I897 using XDA App
bobtukin said:
Do you use the same drivers on your computer for all ati cards just because their built by Ati?
Click to expand...
Click to collapse
Actually yes. ATI calls their driver package catalyst you and download the same one no matter what ati card you are using.
Drivers are written with various choices in mind (I've written/modified a few myself).
Sometimes vendors create a family of "devices" that can be handled by the same driver. This is either controlled by compile time switches or even run time detection.
At other times, the vendor may develop a brand new hw architecture on a new device, and it may not be worth it to plumb an existing driver with code that runs across multiple device families.
Driver binaries will require device, target CPU arch and kernel APIs to be very close/exact match to be used across systems. Post #2 clarifies that this is not the case.
I did not have knowledge of the devices on the SGS II, and hence the OP: if they differ a lot.
So is the SGSII the next big development platform? That's what I'm hoping, as I'll probably get one come August, assuming they are out.
Just for arguments sake, lets say by some miracle we could get an sgs 2 rom on a cappy. How would it run? It would be expecting a dual core 1.2 ghz not a single 1 ghz, and double the ram. I doubt it would run at all.
krook1 said:
I tried looking for this, but wasnt able to get any hits.
Is the hardware between the SGS and SGS II so different that a stock rom of the SGSII cannot be used as a basis for an SGS rom?
Click to expand...
Click to collapse
Yes, the hardware is so different that ROMs designed for the GS2 will NEVER work on the GS1. Doesn't mean little parts here and there (like TW4 for example) can't be ported from one to the other, but as far as how the ROMs work at the driver level, it isn't possible to port the entire OS base.
</end>
neubauej said:
Just for arguments sake, lets say by some miracle we could get an sgs 2 rom on a cappy. How would it run? It would be expecting a dual core 1.2 ghz not a single 1 ghz, and double the ram. I doubt it would run at all.
Click to expand...
Click to collapse
Touchwiz 4 has already been ported and it runs fine, that's all you're going to get from that rom.
I am posting here as I am not allowed to do so in development subforum.
Anyway, I am the developer of the OpenFIMG project (formerly GLES6410), which is aiming to provide proper OpenGL support on devices with FIMG 3DSE 3D engine, found in S3C6410, S5PC100 and probably also in S5P6442. The project is in a pretty advanced state as it is already capable of running Android 2.3 with hardware acceleration. Still many OpenGL extensions and some core features (like lighting) are still missing. More info can be found here: https://github.com/tom3q/openfimg/wiki.
It is very likely (and almost confirmed) that the SoC used in Galaxy 3 (S5P6442) contains the same GPU as the one in S3C6410, which is the chip inside Galaxy Spica and similar phones, at least basing on what Quadrant and GLbenchmark show and on GL libraries supposed to be dumped from Galaxy 3.
What I am trying to say is that my project may also be useful on Galaxy 3, but I am the only developer working on it and I am doing it in my free time, so it does not progress as fast as one may expect. In other words, I am looking for some other developers interested in this project.
If you are interested, then do not hesitate to drop me a PM.
Mod EDIT : moving this to development
EDIT: Attached some documents about FIMG 3DSE (based on S3C6410 documentation and my reverse engineering)
EDIT: The project has been successfully used on G3. Builds of ICS for G3 use OpenFIMG as primary graphics driver currently and there are update packages for CM7.
Very interesting .. I send you PM.
Galaxy 3 has no GPU.
mpbm23 said:
Galaxy 3 has no GPU.
Click to expand...
Click to collapse
Based on what?
All my sources state that it has exactly the same FIMG 3DSE rev. 1.5 as in S3C6410.
Based on the fact that no site says that the I5800 has a GPU and that graphics on games are really laggy.
Unless you are not talking about a discrete GPU.
No mobile phone contains a discrete GPU. All of them are embedded inside some SoC chip, some are better (SGX, Adreno), some are worse (FIMG 3DSE).
It is exactly the same as with Spica and similar phones. Games are laggy because the hardware is not a speed daemon and the performance is even more impacted by really _broken_ drivers.
Then why nobody write that it has GPU like all the other phones like Galaxy S ,Nexus S etc?
mpbm23 said:
Then why nobody write that it has GPU like all the other phones like Galaxy S ,Nexus S etc?
Click to expand...
Click to collapse
Because it is a low end phone, software support for this GPU is very bad and the GPU itself is not a speed daemon.
tom3q said:
Because it is a low end phone, software support for this GPU is very bad and the GPU itself is not a speed daemon.
Click to expand...
Click to collapse
Okay..so your project involves developing real good drivers so that even the g3 low end gpu can perform better, right?
Sent from the 3rd Galaxy !
Yes. Of course, it will not work on par with Adreno 200 or similar GPUs, but should at least work a bit better. The main target is to run Android 2.3 (and future versions, which will not work will original drivers, because of missing extensions) with full hardware acceleration and without bugs found in Samsung drivers.
Hmmm.. Nice .. Good luck with your project.. One of our devs marcellusbe is working on porting CM7 to G3.. This would surely help him ..
Sent from the 3rd Galaxy !
cool... if so this is gonna make new benchmark .. pun intended ... best of luck man.... I had thought of throwing this phone a long time back but you guys always give hopes... and ofcourse result..
Wow interesting!
This should be moved to dev section I have sent a PM to haree
Cool. So what can others help with?
Too interesting
I'ld like to help with whatever i can
I'll back you up in spirit, sorry,i know nothing about programming
VERY intresting!
and yes the galaxy 3 does have a gpu and yes it has been confirmed (or atleast i heard) that it has this gpu..cant wait to see the outcome!
Actually, I will need some people who would compile, test and eventually fix the code for Galaxy 3, because the only phone with this GPU I have is a Galaxy Spica (i5700) and there may be some subtle differences between them. (Especially in the kernel part, where kernel modules may require changing of some addresses or some other fragments of code.)
Preferably, I would like someone to help me with the project, but I understand this is not an easy task, so not everyone can apply.
I don't mind being a tester
Edit: also will we be able to play gameloft games and nfs shift?
Sent from my GT-I5800 using XDA App
dilzo said:
I don't mind being a tester
Click to expand...
Click to collapse
Nice, thanks.
However, you have to understand that it is not a simple drop-in replacement of standard GL libs. This project replaces the whole graphics subsystem of the phone, including some kernel modules and this makes testing a bit more complicated as it needs pretty big modification of the phone software.
If it is not a problem for you then ok.
dilzo said:
Edit: also will we be able to play gameloft games and nfs shift?
Click to expand...
Click to collapse
It all depends if all the extensions required by these games will get implemented. Also, there may be some problems with screen resolution of Galaxy 3, which is a not standard one. I cannot give any claims regarding the performance as the real performance of this hardware is unknown.
Finally released the code for Ice Cream Sandwich!
The source code for Ice Cream Sandwich has finally been released, and already ahead of its predecessor, this Honeycomb. This Android 4.0 will operate as barriers accounted for 3.0 ROMs for developers and manufacturers of different products. Welcome to a new era.
In fact, the version released and available for download is 4.0.1, so that it is new face of which we have seen in some Galaxy Nexus surely debuggers or solution to a silly bug.
Currently this version is only available as a ready-made settings included, and settings for other devices will still have to wait. Needless to say, if you know what we talked about then is best to wait until they are released versions "for all", this is for high skills and developers.
It is a version almost embryonic but complete, for some technical problems they have had with your server, but also functional. You only have to download it (link is below) and in the source tree will have to find "full_maguro" that you can use to create a system image for Galaxy Nexus.
Just follow the instructions you will have once the download page (again, at the end of post), and for this use the following GIT:
repo init-u-b android-https://android.googlesource.com/platform/manifest 4.0.1_r1
We sure will be a long download and have patience, do not synchronize until we are sure it is fully completed or will have an unusable version.
This release includes all updates Android tree, including all of Honeycomb (care tablets manufacturers or rosemary), but insist that "everyone wants to focus on Ice Cream Sandwich" (words).
This discovery has published Jean-Baptiste Queru, Android Software Engineer in the Building Android group of AOSP. For questions, go to the source that we put down at all and do not hesitate to ask. Ice Cream Sandwich!
CM9, this is the truth
man, i can't wait to get my hands on ics!
We have a great community of developers working on this phone, it just hope it will last at least for another year. I've previously had a Samsung Galaxy Spica with great support from Samdroid but after some time they had some problems and stopped development till some while ago when tom3q started releasing GB for it (cm7). I've moved to LG p500 with also great support from XDA, but also the progress is kinda slow now, i have motorola defy (well not now, it's been a year) and i just love what progress is being made. I just hope it will last most than the two other devices mentioned.
I think after we have fully working ICS (if we encounter no major problems with the kernel <or maybe we'll have an unlocked bootloader to play with---fingers crossed>) maybe then the development can stop
I know this is a lot to ask the developers, since everyone moves to dual-core devices (and quad core soon)...but please stay with us on this one. You already have our deepest respect but we still need you guys
adi4motion said:
We have a great community of developers working on this phone, it just hope it will last at least for another year. I've previously had a Samsung Galaxy Spica with great support from Samdroid but after some time they had some problems and stopped development till some while ago when tom3q started releasing GB for it (cm7). I've moved to LG p500 with also great support from XDA, but also the progress is kinda slow now, i have motorola defy (well not now, it's been a year) and i just love what progress is being made. I just hope it will last most than the two other devices mentioned.
I think after we have fully working ICS (if we encounter no major problems with the kernel <or maybe we'll have an unlocked bootloader to play with---fingers crossed>) maybe then the development can stop
I know this is a lot to ask the developers, since everyone moves to dual-core devices (and quad core soon)...but please stay with us on this one. You already have our deepest respect but we still need you guys
Click to expand...
Click to collapse
Yeah I remember you. Even I was a member on samdroid forum and leshak made lot of development for spica but then he disappeared and then came tom3q. Now Tom3q is working on new kernel for spica. I remember even you had made some contribution for in making froyo possible for spica. And you know what even antibyte owns a defy. Hope he still owns it and helps the other devs develop ICS for defy.
im started to compiled for my nexus-s with 237.driver, for now we have the correct driver only for galaxy nexus, but if someone have an idea what driver for defy we can used i can try to porting to defy!
Great !!!
heck! my pc is 4 hours, which is downloading the various repo, now I read on the forum dev-google that are prerequisites hardware to compile ics :
24GB of ram / cpu intel xeon or dual i7, ADSL broadband or fiber optic ......
cardozclive said:
Yeah I remember you. Even I was a member on samdroid forum and leshak made lot of development for spica but then he disappeared and then came tom3q. Now Tom3q is working on new kernel for spica. I remember even you had made some contribution for in making froyo possible for spica. And you know what even antibyte owns a defy. Hope he still owns it and helps the other devs develop ICS for defy.
Click to expand...
Click to collapse
my contribution on spica was very small... insignificant (a lock key fix and the 315x315 mod) not "really" contributing but thanks for remembering
what a hell of specs to compile an ICS..
Sent from XDA-Developers Android Application
iaio72 said:
heck! my pc is 4 hours, which is downloading the various repo, now I read on the forum dev-google that are prerequisites hardware to compile ics :
24GB of ram / cpu intel xeon or dual i7, ADSL broadband or fiber optic ......
Click to expand...
Click to collapse
i think those are exaggerated like they sai that in order to run Battlefield 3 you need minimum Core 2 Duo at 3GHz and i run it on my Laptop (Pentium Dual Core 2GHz (sandy brigde)) with most settings on ULTRA)
keep up the good work
Those pre-requisites are to ensure you compile in a reasonable ammount of time
Sent from my MB525 using xda premium
adi4motion said:
i think those are exaggerated like they sai that in order to run Battlefield 3 you need minimum Core 2 Duo at 3GHz and i run it on my Laptop (Pentium Dual Core 2GHz (sandy brigde)) with most settings on ULTRA)
keep up the good work
Click to expand...
Click to collapse
its true, read on dev-cyanogen forum!
iaio72 said:
heck! my pc is 4 hours, which is downloading the various repo, now I read on the forum dev-google that are prerequisites hardware to compile ics :
24GB of ram / cpu intel xeon or dual i7, ADSL broadband or fiber optic ......
Click to expand...
Click to collapse
What the hell...???? Maybe someone with a supercomputer can do it... really???
Enviado desde mi MB525 usando Tapatalk
waiting for cyanogonmod to release cm9 for defy
I have an idea!
We can use Grid Computing method with CUDA video cards
http://boinc.berkeley.edu/
espaciosalter20 said:
What the hell...???? Maybe someone with a supercomputer can do it... really???
Enviado desde mi MB525 usando Tapatalk
Click to expand...
Click to collapse
---> link1
---> link2
my GOD! what's with that?! why? this is not good news. That means there will be less developers working on it
but really... why does it need that much ram?
iaio72 said:
heck! my pc is 4 hours, which is downloading the various repo, now I read on the forum dev-google that are prerequisites hardware to compile ics :
24GB of ram / cpu intel xeon or dual i7, ADSL broadband or fiber optic ......
Click to expand...
Click to collapse
24Gb of RAM.....bullsh*t that doesn't even exist xD. You may have meant 2,4Gb..or else your sources are wrong .
Honestly people, just stop and think....does 24Gb of Ram even SOUND believable?! NO x)
Sent from my CM7 Defy
my mac pro has 32gb of ram...so yeah, it's a 2006 model. I think it's possible.
Sent from my Transformer TF101 using xda premium
Ok so please forgive my noobness here but I'm dying to ask a few questions... I have been an android fan for years and always had lots of options for my phones, and now that I am switching phones I would like to help out more. I see that development is going slow on this phone and had a few questions...
What would it take to port over some roms from say the galaxy s (I'm thinking possibly CM7 or MIUI)? What is the closest phone to ours if not the galaxy?
If the kernel is open source (https://opensource.samsung.com) then is over/underclocking possible with much effort?
Is all I need to build a functioning rom available from the android sdk and the samsung open source website? (I understand this is no easy task, just wondering if I need more than this)
FM transmitter... I hear this phone has a FM transmitter, is this true? Oh man what I wouldn't give to get this working. I would love to hear any opinions/suggestions/comments on this subject as this interests me most.
I'm sorry once again for all the questions, I am looking forward to helping out however possible.
I suggest you look up the wiki's on cyanogenmod on building. You'll need some sorta POSIX environment (ie.. linux or OS X). Here's the one I used:
http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S_II_(AT%26T):_Compile_CyanogenMod_(Linux)
The SGS family largely uses samsung components (CPU's, GPU's, etc). The Blaze uses the qualcomm snapdragon stuff. The blaze is using the msm8660 arch, which isn't really present in the cm7 sources. The only thing kinda there is the sgs2 for at&t (skyrocket). Finding other examples using similar hardware has not been easy for me. The audio subsystems for sgs2 seems to be yamaha based, where as ours isn't. You'll want to be VERY careful to make sure all the partitions are set up properly in your work as otherwise you may end up wiping the radio or other supporting partitions, and that would be very, very bad. And etc... etc... etc...
It would help to have a working knowledge of unix/linux. You'll definitely want to root your phone (obviously) and install busybox so you have a decent toolset to go poking around the OS.
I wish you luck and I hope this helped!
---------- Post added at 02:00 PM ---------- Previous post was at 01:56 PM ----------
Oh, forgot about the Kernel.
The kernel itself is always open source (legally required). The changes and binary blobs for drivers aren't.
You apparently tweak the kernel seperately from a cm7 build. OC and UV are about playing with the timings inside the CPU and is not for the feint of heart. My understanding is that there is a whole series of equations and calculations you use to arrive to the frequency table for such things. Since other hardware uses our CPU, that's probably the place to start looking... i.e... the EVO 3D.
Thanks for quick reply! I currently dual boot ubuntu/win7 and have a small working knowledge of linux, so hopefully that helps there. I will start messing around with the phone in another week or so when my schedule allows, but will gladly help beta test until then! Please feel free to hit me up when you need something tested
Also, since you are the hardware man.... what about that FM transmitter? Is that only a receiver or is it a combo? I personally have never seen a FM transmitter in a phone and would love to have one.
dr4stic said:
The SGS family largely uses samsung components (CPU's, GPU's, etc). The Blaze uses the qualcomm snapdragon stuff. The blaze is using the msm8660 arch, which isn't really present in the cm7 sources. The only thing kinda there is the sgs2 for at&t (skyrocket). Finding other examples using similar hardware has not been easy for me. The audio subsystems for sgs2 seems to be yamaha based, where as ours isn't. You'll want to be VERY careful to make sure all the partitions are set up properly in your work as otherwise you may end up wiping the radio or other supporting partitions, and that would be very, very bad. And etc... etc... etc...
Click to expand...
Click to collapse
As far as being close to the Blaze, what about the Galaxy Note? It has a msm8660 while the Blaze has a msm8260. Both have the adreno 220 gpu, same ram, and release around the same time. I see there is a larger screen and a different camera, is there something we can use there?
I only ask as I ran across this thread: http://forum.xda-developers.com/showthread.php?t=1573568 and was wondering if maybe this phone would be the place to start a port.
Q&A for [Kernel] Shield Tablet Kernel Development [Incl. Guide]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Kernel] Shield Tablet Kernel Development [Incl. Guide]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
I have an EU LTE Nvidia Shield Tablet... Do i flash the EU LTE or the USA WiFi version of Phil'z?
Can this hack facebook?
When's the next update?
:angel:
Monoped said:
I have an EU LTE Nvidia Shield Tablet... Do i flash the EU LTE or the USA WiFi version of Phil'z?
Can this hack facebook?
When's the next update?
:angel:
Click to expand...
Click to collapse
Both
Yes
Just posted it about 5 minutes ago.
@twistedumbrella
So I just got my shield tablet today, but, being a PC gamer, I can't help but to be a benchmark whore when it comes to my devices, but I do like added performance in general for games that I KNOW can maintain a stable 60FPS with a slight overclock, e.g. Dead Trigger 2 runs at 50-60FPS. That being said, check out this Nexus 9 kernel. http://forum.xda-developers.com/nexus-9/orig-development/kernel-fire-ice-t2930451
I know the Nexus 9 and the Shield Tablet both have a K1, but theres also a slight diference, whereas the Nexus 9 has a Denver 64-bit dual core CPU vs our Quad Arm Cortex V15. Anyways, I was wondering, could we see the features in that kernel for our device any time soon? I'd really like to have them.
All in all though, it's just a question of would you be willing to give us features like that. I'm really happy with my device, but I wouldn't mind more functionality!
rejectedjs said:
@twistedumbrella
So I just got my shield tablet today, but, being a PC gamer, I can't help but to be a benchmark whore when it comes to my devices, but I do like added performance in general for games that I KNOW can maintain a stable 60FPS with a slight overclock, e.g. Dead Trigger 2 runs at 50-60FPS. That being said, check out this Nexus 9 kernel. http://forum.xda-developers.com/nexus-9/orig-development/kernel-fire-ice-t2930451
I know the Nexus 9 and the Shield Tablet both have a K1, but theres also a slight diference, whereas the Nexus 9 has a Denver 64-bit dual core CPU vs our Quad Arm Cortex V15. Anyways, I was wondering, could we see the features in that kernel for our device any time soon? I'd really like to have them.
All in all though, it's just a question of would you be willing to give us features like that. I'm really happy with my device, but I wouldn't mind more functionality!
Click to expand...
Click to collapse
All that kernel has that isn't already here is doubletap2wake and some GPU overclock written by a developer I've never heard of (read: cannot confirm stability). Everything else is from Faux and was merged.
twistedumbrella said:
All that kernel has that isn't already here is doubletap2wake and some GPU overclock written by a developer I've never heard of (read: cannot confirm stability). Everything else is from Faux and was merged.
Click to expand...
Click to collapse
Haha, those were the 3 features that I mainly wanted. DT2W, and GPU/CPU overclock.
If anyone ever comes out with a custom rom for our device, such as LiquidSmooth, I can't imagine the speed increases we could give this. But I'm sorta worried that maybe these roms, like LiquidSmooth, VanirAOSP, etc, won't exactly like Tegra K1.
There's just a binary file called shieldtablet.bin, not the usual packaged for flashing zip.
{
"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"
}
mezkalz said:
There's just a binary file called shieldtablet.bin, not the usual packaged for flashing zip.
Click to expand...
Click to collapse
I renamed it from shieldtablet and added .zip at the end and you can see some stuff inside that makes it seem like you can flash it. But, I haven't flashed it yet because I wasn't exactly sure if it was a kernel or not.
rejectedjs said:
I renamed it from shieldtablet and added .zip at the end and you can see some stuff inside that makes it seem like you can flash it. But, I haven't flashed it yet because I wasn't exactly sure if it was a kernel or not.
Click to expand...
Click to collapse
The folder was added to the export variable which meant shieldtablet was assumed a file name instead of a directory, but it is still StarKissed-LP50_12-28-2014_12.48-TN8-Auto.zip just named shieldtablet.
Overclocking our K1 gpu is pointless, our variant is faster than the Denver configuration in terms of performance.
Overlooking the CPU core would return very low gains too as the single threaded use cases which might see some benefit really need much larger performance boosts than any single overclock can offer. In those cases Denver's 64bit double wide register space offers much more performance - as proved in the Geekbench numbers comparing our K1 to Denver.
The only marginally useful feature of the three is DT2W and, frankly, I would be concerned with needless battery drain in keeping the digitiser active at idle. Our digitiser is more sensitive than what's equipped in the Nexus 9 due to our pen interface. It's no Wacom or similar active surface but it's definitely more sensitive than most other passive interfaces. Leave something light brushing on the screen like a droplet or piece of headphone cable and watch surface flinger go nuts trying to compensate for all that extra touch data.
If the power button is really that difficult, you can always pull the pen and click it back in like a pinball lever. That's how I deal. I did the touch2break stuff on Note 4 and with a pen it is rarely wake, just sleep.
Or get the smart cover. It wakes the screen on open.
mezkalz said:
Or get the smart cover. It wakes the screen on open.
Click to expand...
Click to collapse
I wanted to get that, but I didn't know what would be included in the package they sent and it's not available in any of the stores. I ended up buying a Note 4 instead lol.
mezkalz said:
Overclocking our K1 gpu is pointless, our variant is faster than the Denver configuration in terms of performance.
Overlooking the CPU core would return very low gains too as the single threaded use cases which might see some benefit really need much larger performance boosts than any single overclock can offer. In those cases Denver's 64bit double wide register space offers much more performance - as proved in the Geekbench numbers comparing our K1 to Denver.
The only marginally useful feature of the three is DT2W and, frankly, I would be concerned with needless battery drain in keeping the digitiser active at idle. Our digitiser is more sensitive than what's equipped in the Nexus 9 due to our pen interface. It's no Wacom or similar active surface but it's definitely more sensitive than most other passive interfaces. Leave something light brushing on the screen like a droplet or piece of headphone cable and watch surface flinger go nuts trying to compensate for all that extra touch data.
Click to expand...
Click to collapse
I get what you're saying, but features being "useless" is completely a matter of opinion. While these features don't sound fun or necessary to you, there are people out there that would enjoy to overclock the shield tablet and have DT2W and other features. Just go to the actual kernel thread and look at the amount of people who would like to see a Shield Tablet overclock.
It seems like preference versus practicality. In terms of necessity, it is useless. In terms of flexibility, it is desired. Either way, something was already done about it.
For those without a magnetic case I can reccomend this one:
http://forum.xda-developers.com/shield-tablet/accessories/case-screen-t2987462
https://github.com/StarKissed/stark...mmit/c2caf3aeb23d90bc682c31b35eebb01f1e88e9f8
Cheers on the OC option. I personally don't use it... But if I ever change the voltages or frequency... It's underclocked to save battery. The K1 is pretty sexy in and of itself and I appreciate your consistent dedication and learning material.
twistedumbrella said:
It seems like preference versus practicality. In terms of necessity, it is useless. In terms of flexibility, it is desired. Either way, something was already done about it.
Click to expand...
Click to collapse
Hm. I hate to pester you just in case I'm doing something wrong, but, using TricksterMOD, I don't see any intermediate GPU steps or CPU overclocking. Am I using the wrong app?
Yes you are using the wrong app. Come on man the developers own app is under the same goo.im folder tree, it's called starkissed as well. Install that you will guarantee get proper control of the settings you speak of. Faux doesn't work right I can verify.
berryman13 said:
Yes you are using the wrong app. Come on man the developers own app is under the same goo.im folder tree, it's called starkissed as well. Install that you will guarantee get proper control of the settings you speak of. Faux doesn't work right I can verify.
Click to expand...
Click to collapse
I just downloaded his app. Still no dice.