[Q] Any devs take a look at the kernel yet? - AT&T Samsung Galaxy Note I717

Since we just got the kernel source released I was wondering if any devs had taken a look at it yet. Moreover, if it is similar to the kernel in the skyrocket. Im sure there will be some differences considering the slight difference in hardware but it would be nice to know how close we would be to getting a solid, quick kernel mocked up for release.
I was also wondering if this kernel could be used as well. From what I can see it is hacked from Samsung GB source, so should work with any one still running Sammy GB
http://forum.xda-developers.com/showthread.php?t=1437563

Related

[Q] [ICS] vanilla AOSP ROM devs - anyone doing?

Hi all,
First of all, I'm amazed and gobsmacked at how much work all the devs put into their respective ROM's, it's amazing the effort and hard work ppl put in. Passion is alive and well on XDA
Now, to business. I have my Galaxy SII, a Galaxy S, and an Acer Iconia A500. I've flashed them all with their respective ICS. I would think (and hope) that probably out of all of them, the SII has the biggest dev base and most power. The ICS ROMs for the A500 and S are almost perfect. They run completely vanilla with no or almost no bloat, they look and behave the same (icons for network activity inside the bars for example, contacts app looks the same) and have had no hiccups whatsoever.
Come the SII, the only ROMs I've seen are cooked from Samsung sources with their phone and contacts apps, they crash and reboot and if it weren't that I have gone past the point of no return in regard to effort I'd have gone back to Gingerbread days ago.
Is anyone out there developing a completely vanilla "Google" rom that isn't themed to look like ICS, but actually uses the ICS apps etc. I can't understand how the Iconia and SI can have this while the SII seemingly doesn't.
Can anyone open my eyes on this? I'd love to get something as stable onto my SII as I have with my other devices, ICS is brilliant to use on them...and barely bearable on my beloved SII.
Cheers
<:3)~
Ummmm correct me if I am wrong but that's exactly what the CM team are trying yo to do....
And you can already download and install that, so long as you are happy with the bugs at present.
Unless you meant something else???
Sent from my GT-I9100 using XDA App
You miss reading the cm9 thread. Check it out....its still alpha.
Sent from my GT-I9100 using Tapatalk
I'm more curious about the fact I would have thought the SII having a bigger user and dev base...certainly more than the A500 I thought it would have the most stable and mature code base - yet it seems the opposite is true.
I've been running 4.0.3 on my SI for weeks now and its never bugged out. Installed the A500...and Oh wow its like a brand new tablet!! I wonder is it because of Exynos or some other reason we can't have the same stability and performance right now.
Sent from my Acer Iconia A500 using Tapatalk
Your ignorance and disrespect is pretty bad (even if you don't mean it). I think you should do some reading for a while and get yourself acquainted with what's involved.
I didn't ask this to be dissed by someone...I'm sure even you would agree the development cycle and challenges for all three devices would be similar given they all use different processors. So is it easier to compile for the A8 and Tegra than the A9?
I have been looking and downloading a number of ROMs...and if someone has created a ROM in a similar vein to Thor's on the A500 and Onecosmic's on the SI, well I'd be grateful for the heads up...in fact I'm just about to download and test the Pure ROM I just spied over in dev...so see how that goes. Still I'd be happy for someones *constructive* input.
Of course I'm claiming ignorance...if I knew I wouldn't ask...geez lol
Sent from my Acer Iconia A500 using Tapatalk
It's a wonder no one bothers doing a straight AOSP compile for any device, really. CyanogenMod comes the closest. There are a few people who played with doing a straight AOSP, but they base it off CM's work and strip out the extras.
When I wanted the AOSP experience with Gapps, I installed CM7 on my SGS and installed the stock Gingerbread launcher. It was the closest I got.
Trebuchet is basically the stock ICS launcher with features added, so it won't be so bad. You can also replace it with the stock launcher as well.
Try Airbus 360s ics rom that's aosp and is fantastic he should be releasing beta 2 tonight.
sent from my iPhone 4S.
haha I bet that confused ya
You're question is a bit noob so don't expect much answers.
Here is a short one to sum it for you:
AOSP - Pure android base without modification.
CM - almost pure with modifications.
STOCK - Hardware Manufacturer (eg. Samsung's) "official originated" release.
Stock - can have it all. CAUSE - Samsung has sources and support/docs for ALL hardware API of the device.
CM/STOCK - While there are some changes BOTH use the same origin.
To sum it, for proper functionality BOTH use SAME kernel/libs base.
So if some hardware functionality broken in one it'll be broken in other =
If CM9 haz no h/w decoding === APPLIES for AOSP.
Another thing to keep in mind, CM9 currently is in the process of adding CM features so current builds are very close to AOSP with functionality.
SUM IT UP:
if (CM9 != working) AOSP.isNotWorking()!
ttg said:
if (CM9 != working) AOSP.isNotWorking()!
Click to expand...
Click to collapse
That's a piece of horrible code, dude

ICS source code realeased by Samsung!

What does this mean for the galaxy player 5.0/4.0? Will we be able to finally get a stable rom with ICS? i really hope so
Charlielx said:
What does this mean for the galaxy player 5.0/4.0? Will we be able to finally get a stable rom with ICS? i really hope so
Click to expand...
Click to collapse
What are you talking about?
Samsung has released no source code other than I9100 kernel sources, which are basically useless on Hummingbird-based devices.
Nexus S source code is more applicable and has been out for ages - but getting that to support the G70 is a lot of work, more work than it's worth to be honest. I haven't been particularly impressed with ICS so far. It's not awful - but it's not the major improvement over Gingerbread that GB was over Froyo.
Entropy512 said:
What are you talking about?
Samsung has released no source code other than I9100 kernel sources, which are basically useless on Hummingbird-based devices.
Nexus S source code is more applicable and has been out for ages - but getting that to support the G70 is a lot of work, more work than it's worth to be honest. I haven't been particularly impressed with ICS so far. It's not awful - but it's not the major improvement over Gingerbread that GB was over Froyo.
Click to expand...
Click to collapse
Well, technical know-hows aside, I would like to comment on the ICS Vs GB thing. I loved using GB but since moving over to ICS on my Cappy and HP Touchpads, there is no comparison on the polish the ICS brings to these devices. Granted ICS did not bring anything earth shattering to the Android OS game, but the latest Google has to offer seems just right for my devices. GB just felt still being worked on but... ICS has more thoughtful features... simple things as the way gallery presents the photos, just seem right. Of course, some, if not most, would be differences in personal taste, but for me, I am happy with ICS and can't wait for all my devices to be upgraded to them.
Now, having said that... I certainly appreciate all the hard work by all the devs. I have no doubt, for a moment, that it's an aweful amount of work... For that... I Thank you.
@Entropy - That is kind of my gut feeling without having spent much time with ICS.
Is it fair to say the ICS is much more about glitter than new functional features or power?
Mrktmind said:
@Entropy - That is kind of my gut feeling without having spent much time with ICS.
Is it fair to say the ICS is much more about glitter than new functional features or power?
Click to expand...
Click to collapse
Yeah I think ICS was meant to be more user friendly. Less technically overbearing to the standard end user.
Sent using Tapatalk on my Samsung Galaxy SII running CM9
Awh dammit nevermind, i misread, it wasnt the full source it was just the ics kernel source

[Q] What kind of ROM would you prefer for running on your SGS3?

Will it be MIUI, Cyanogenmod or something else? Share your desires and maybe devs will listen
Definately MIUI.
Using it on my EVO 3D atm, and I loooooove it!
Definitely Cognition Rom
Will be happy to see custom ROMs, but as long as they incorporate the awesome samsung features
I am only looking to put ROMs on this phone that are proven stable - and keep the features of the SGSIII intact. I don't want a phone that needs this workaround to get a feature to work.
I hope BootManager PRO works for this phone because I do like to keep several ROMs at hand at once. I really love the ICS blues and I have seen some amazing things evolve from a stock AOSP 4.0.X ROM over at the GNex forums. So we just need to wait and be amazed with the features that will be introduced to the world of Android via this phone's development section
Kernels on the other hand - this is where I am mostly concerned. We know pretty much NOTHING about the way a quad core kernel should be dealt with... These will be the main subject of my attention as we get into early development stages.
We shall see what some of our amazing developers who have proven they make kernels their bi***es can do with a new kernel. I am also interested in the kernel that Samsung has developed for it and how exactly this works in our favor here at XDA.
The main point is while most ROMs can be considered close... Kernels will be quite different and will be everyone's main focus - making our quad core beasts run with optimal battery life!
Checkrom
Skickat från min GT-I9100 via Tapatalk 2
I'd like to see a CM9 hybrid\tablet mode rom with per-app dpi capabilities that comes with a free high class escort.
I will use any "rooted" rom that is stable enough .... so far we don´t know is it possible to change bootloader.
Cyanogenmod of course
Probably..... stock rom, bloatware removed (will keep all the good stuff), custom kernel and custom themes
Sent using TCP/IP
CheckRom 100% the most popular and best ever ROM for the SGSII no other ROM comes close, i still use it and have used nothing else for a long time, SGSII ICS ROM's still nowhere near as good as CheckRom although i hear CheckRom ICS will be landing shortly for the SGSII although ill be selling my phone and getting the Galaxy S3
Slim ICS, as don't see much need for all the extra stuff apart from eye tracking to keep the screen on, S-Voice functionality goes in one ear and out the other, NFC not for me, Social tagging can leave me alone, shame the screen is sub standard to the SGS2.
Still loving my SGS 1 but am due an upgrade so may as well get this, hopefully the GPS is not as ****e as the SGS is. ended up buying an iPhone 3GS just to use with TomTom.
Now if you could give me TomTom on the SGS3 then you'd be talking.
Definitely checkrom with a new kitchen. And if we can get a siyah kernel then its over!!!!!!!!
cm9
miui
slim
aokp

Been wondering this for a while.....

Please help me to understand this..........
If android runs on top of lunix
and all android versions eclair gb, ics etc start off as basically aosp then get maufacturer specific things like blur and sense.
Why is it so hard for CM9 and 10 to fully work on the E3D when CM7 worked perfectly on the Evo4g which are both htc phones?
Its a random question and even though I just recently became a member here, ive been with XDA since i hade the original moto click which was 2 yrs ago.
Also,
What do I need to do to create themes? Ive been wanting to for a while.
Thx in advance
Deep breath. It basically comes down to the huge variety of hardware. Linux has to support hardware in it's kernel (basically a software layer that tells the operating system how to use that hardware) and each new variant of the kernel is supposed to be backward compatible (though support for very old hardware is dropped so the kernel doesn't get out of control). Now Android is a completely different branch of linux (at the moment), and each manufacturer further branches aosp and creates a different kernel for every mobile phone with different hardware. The manufacturers have to release the kernel back to the community after they upgrade but this is slow and even when they do the kernel only supports the variant of android (in this case sense). Finally if they don't release an OS upgrade at all then the kernel becomes outdated and won't support features in the new OS.
Devs feel free to correct me...
Sent from my Evo 3D GSM using xda app-developers app
CM7 is by now quite old, meaning developers have had A LOT of time to test, modify, run and perfect it, even several years ago a lot of phones had perfect CM7 ports/builds.
Both CM9 and CM10 are still quite new, and thus developers have not had that much time to modify it to run as well as CM7, but in time it'll get there, no doubt about it.
And it also depends on which developers are actively working on developing for a specific phone. As for example we now have Agrabren working on a CM10 build (GSM side) doing amazing work, while other phones do not have such developers, thus it will take longer time for those phones to get perfected.
As for the themes, it depends on what ROM you're using. There are several different ways to theme something, and they're very different if you're running either Sense 3, Sense 3.6, Sense 4, CM7, CM9, CM10 or MIUI 2.3 or MIUI 4 (etc.), so you'll have to be more specific. But it would be a good start to look in the "Themes and Apps" sub forum.
grrratt said:
Deep breath. It basically comes down to the huge variety of hardware. Linux has to support hardware in it's kernel (basically a software layer that tells the operating system how to use that hardware) and each new variant of the kernel is supposed to be backward compatible (though support for very old hardware is dropped so the kernel doesn't get out of control). Now Android is a completely different branch of linux (at the moment), and each manufacturer further branches aosp and creates a different kernel for every mobile phone with different hardware. The manufacturers have to release the kernel back to the community after they upgrade but this is slow and even when they do the kernel only supports the variant of android (in this case sense). Finally if they don't release an OS upgrade at all then the kernel becomes outdated and won't support features in the new OS.
Devs feel free to correct me...
Sent from my Evo 3D GSM using xda app-developers app
Click to expand...
Click to collapse
Moonbloom said:
CM7 is by now quite old, meaning developers have had A LOT of time to test, modify, run and perfect it, even several years ago a lot of phones had perfect CM7 ports/builds.
Both CM9 and CM10 are still quite new, and thus developers have not had that much time to modify it to run as well as CM7, but in time it'll get there, no doubt about it.
And it also depends on which developers are actively working on developing for a specific phone. As for example we now have Agrabren working on a CM10 build (GSM side) doing amazing work, while other phones do not have such developers, thus it will take longer time for those phones to get perfected.
As for the themes, it depends on what ROM you're using. There are several different ways to theme something, and they're very different if you're running either Sense 3, Sense 3.6, Sense 4, CM7, CM9, CM10 or MIUI 2.3 or MIUI 4 (etc.), so you'll have to be more specific. But it would be a good start to look in the "Themes and Apps" sub forum.
Click to expand...
Click to collapse
Hey thx guys, I got a better understanding now. I appreciate you taking the time to explain that to me.
As far as themes, i will look into that thread.
BTW this site is awesome. You guys have done a great job making all of this accessible for people who refuse to hampered by the limits of a locked s-on phone.

Jelly Bean Sense

Any odds of some dev porting this ROM to our phone? http://goo.gl/U2GMQ
onex+ uses tegra 3 processor
nearly impossible
odds are so slim it cannot be seen
I'm well aware of the processor differences, that tends to be more kernel sided though, does it not. Look at the EVO 3D, sense 4 and ICS were ported to that in just a couple of weeks and at that time there wasn't even anything close to a functional ICS ROM or kernel. Here we already have a fully functional JB ROM and kernel.
Your comparing a qualcomm device which had a port most likely from another qualcomm device to porting from a tegra device to a qualcomm device. It's not impossible but it's damn time consuming. Especially if anything is proprietary, it would have to be reverse engineered. It's sense and it's similar hardware but the rom is built around the way the hardware works, changes to the kernel to support our phones will most likely break other things in the rom since it is two different chipsets
Yeah I'm not sure what device that pretty was from, I think it was the One S though. Still the S4 and S3 SoCs are vastly different.
Alright though, I just thought it was worth bringing up while waiting for an official build for our device or a leak for ours, or I suppose the One S or AT&T.
Maybe the ROM can help toast with porting the imagesense libraries though at least. Last I heard he we was still working on finishing that up, wasn't he?
A backport on similar architecture is still easier then porting between 2 different architectures
it could be done but odds of fully functional are not promised mostly sound calls wifi etc would be broken, not to mention you'd need a sense kernel built for the port specifically. It can be done but porting something over that wouldn't work completely and spending hours, day's months getting things to work. it would most likely be abandoned.

Categories

Resources