I've done a few firmware upgrades to H8 and currently planning an I5 one. Do we have to wait for Samsung to release a full Donut firmware before we're going to be able to get all the goodness therein?
Root doesn't help and the kernel source for the galaxy hasn't been released by samsung yet. The only way you'll get donut now is by making your own mix of the htc donut roms with samsung drivers and what not. From what I read, donut is quite different from cupcake in the lower layers so I doubt the current drivers in our current build could help much either.
Ahh ok i see your point. I don't expect we could implement core changes from 1.6 into what we have. I know people are looking at it tho. If i have time i'll join the effort.
Anyone know if Samsung plans to release Donut or other future Android versions for this phone? As far as I have read, second hand, they don't plan to. It will remain an Android 1.5 phone.
Anyone know if Samsung plans to release Donut or other future Android versions for this phone? As far as I have read, second hand, they don't plan to. It will remain an Android 1.5 phone.
Anyone know if Samsung plans to release Donut or other future Android versions for this phone? As far as I have read, second hand, they don't plan to. It will remain an Android 1.5 phone.
It doesn't look like too probable they'll let the Galaxy an Android 1.5 phone. We are talking about a phone that is '3 months old', and even if there are plenty of problems with it, they are working hard to improve it.
If you were talking about Android 2.0, I'd have my doubts.
To be fair to Samsung, they've actually been creating new firmware at least once a month, and with a couple of new handets coming with fairly similar hardware to the Galaxy, you'd expect them to be working hard on getting it ready.
Ideally we'd be getting OTA updates which would be the perfect solution to the crap that is NPS
OTA updates would be great , but AFAIK thats only for full 'Google Experience' phones which the Samsung isnt.
To be honest Id be quite happy with a working NPS ...
OTA updates would be great , but AFAIK thats only for full 'Google Experience' phones which the Samsung isnt.
To be honest Id be quite happy with a working NPS ...
OTA isn't just for google experience phones. Yes, only google experience phones currently have OTA support, but it's in no way limited to them. Google has the framework and tools to do OTA updates and it'll take quite a bit of work to create them elsewhere too.
I'm not sure if galaxy will support OTAs anytime soon, but saying that OTAs are just for google experience phones is wrong.
I'm in the UK, on I5 firmware and latest NPS, but it still says that my device is unsupported.
I'm hoping this isn't because I'm not flashing a CSC (I bought an unlocked handset), because that would be like a big f*ck you to people who have given Samsung a lot of cash.
As soon as NPS can be used to upgrade the firmware in the UK there will be a proper thread about it, I very much doubt it will slip under the radar so you'll soon know if your CSC is an issue or not.
I cannot see the reason for that hurry to obtain Android 1.6.
Early 2010 sound good to me, that way Samsung will get the chance and time to elaborate a good firmware version for it, and with more Samsung Android mobiles on the market, the result can only be better than just releasing an early version.
Device(s): htc sensation
nokia n8
samsung galaxy (broken - waterdamage)
Thanks: 46
Thanked 87 Times in 73 Posts
i kinda agree with bitxboi here - at least now we have confirmation that it's coming, and even a timetable
on the otherhand 2.0 is supposed to be coming out possibly this year, so it seems like the galaxy (or samsung in general) might always be one pastry behind
Wow Samsung, you clearly don't care about the "open" part of the open handset alliance. Just want to check the box that says GPL compliance and move on.
My initial impression was, where is the git repo? Ok, what about a tarball then...a zip file...really...ok it will have to do.
Lets unzip it. Its not a zipbomb, there is only one top level path, score one for Samsung. Ok, a poorly named kernel_2.6.27 path, a scripts path, a src file, and a stgloc file. stgloc is empty, src just says 'kernel_2.6.27_TW'.
In scripts we have a whole bunch of "interactive", yes, interactive build scripts, complete with paths that don't exist within the provided zip. And even some binaries that have no source provided with them, such as gen_verdate, mkheader, and merge.
Ok, lets look at the kernel source. The first thing I notice is that it all as dos newlines. EPIC FAIL. The second thing that I notice is that they did not preserve case, so all the files in netfilter that are the same other than case are screwed up. Fail again. What did they do, check this into a windows based source control system? Oh, wait, they did CLEARCASE evidenced by the stgloc file. Yes my friends, the poor saps over at Samsung are actually doing kernel development via rational, and not even configured for unix clients it seems. Another consequence of this is that all permission bits are lost.
Its also very difficult to determine what work Samsung has done. Their tree appears to be based on an ancestor of:
It looks like Samsung pulled from some internal Qualcomm tree, and Qualcomm later changed all the copyright headers and pushed the code to codeaurora. "Copyright (c) 2009, Code Aurora Forum. All rights reserved." vs "Copyright (c) 2009 QUALCOMM USA, INC."
Given where some code shows up, I don't think samsung understands the directory structure or code placement for the arm arch. Also interesting is that they don't seem to get what arch/arm/mach-*/board-* files are. They have a new board-battery.c, board-headset.c, board-init.c, board-keypad.c, board-param.c, board-rfkill.c, and board-rfkill1.c. To finish the irony, they do not have a board-capela., they just modified the base mach-msm files with a bunch of #if defined(CONFIG_SAMSUNG_CAPELA).
And lets not forget code that is non-gpl, eg, drivers/i2c/chips/smb300.c
* It is not allowed to deliver the source code of the Software to any third party without permission of
* Bosch Sensortec.
scratch the lack of zipbomb, I found the Middle directory. With files in it that file actually identifies as "ASCII C program text, with CRLF, CR line terminators". What is a CRLF, CR line terminator you ask?
Yes, somehow they have taken a source tree (bluez) that originally had unix LF line terminators and managed to get CRCRLF line terminators on it. Ddouble ddosify?
Ok, lets look at the kernel source. The first thing I notice is that it all as dos newlines. EPIC FAIL. The second thing that I notice is that they did not preserve case, so all the files in netfilter that are the same other than case are screwed up. Fail again. What did they do, check this into a windows based source control system? Oh, wait, they did CLEARCASE evidenced by the stgloc file. Yes my friends, the poor saps over at Samsung are actually doing kernel development via rational, and not even configured for unix clients it seems. Another consequence of this is that all permission bits are lost.
Its also very difficult to determine what work Samsung has done. Their tree appears to be based on an ancestor of:
It looks like Samsung pulled from some internal Qualcomm tree, and Qualcomm later changed all the copyright headers and pushed the code to codeaurora. "Copyright (c) 2009, Code Aurora Forum. All rights reserved." vs "Copyright (c) 2009 QUALCOMM USA, INC."
Given where some code shows up, I don't think samsung understands the directory structure or code placement for the arm arch. Also interesting is that they don't seem to get what arch/arm/mach-*/board-* files are. They have a new board-battery.c, board-headset.c, board-init.c, board-keypad.c, board-param.c, board-rfkill.c, and board-rfkill1.c. To finish the irony, they do not have a board-capela., they just modified the base mach-msm files with a bunch of #if defined(CONFIG_SAMSUNG_CAPELA).
And lets not forget code that is non-gpl, eg, drivers/i2c/chips/smb300.c
* It is not allowed to deliver the source code of the Software to any third party without permission of
* Bosch Sensortec.
hmmmm...are you implying the kernel samsung built is actually crap?¿ Because every line I read from you comments seems like something is wrong everywhere and they've screwed it big time. The part that worries me the most is the one I bolded.
hmmmm...are you implying the kernel samsung built is actually crap?¿ Because every line I read from you comments seems like something is wrong everywhere and they've screwed it big time. The part that worries me the most is the one I bolded.
I'm not saying that the actual kernel is crap, just the source release. Its makes it very difficult for other developers to pick up where they left off.
Hmm its poorly laid out, and they have alot of bad practices about how they are developing. It looks like someone just zipped up a subtree of their develmopment directory and deleted stuff they didnt want out.
That doesnt mean its coded badly/has bugs etc. It just means they've "hacked" in their changes to make it work on the samsung. I suspect this is a zip of some early revision. Surely they cant be developing like this now.
Hmm its poorly laid out, and they have alot of bad practices about how they are developing. It looks like someone just zipped up a subtree of their develmopment directory and deleted stuff they didnt want out.
That doesnt mean its coded badly/has bugs etc. It just means they've "hacked" in their changes to make it work on the samsung. I suspect this is a zip of some early revision. Surely they cant be developing like this now.
I imagine that they will keep working like that, and merging to updates like donut will be painful for them.
It does bother me that their source releases aren't tagged to indicate which firmware they match up with. I'll email Harald Welte and Ben Dooks and ask them what they deal is.
what is interesting is Russ Dill seems to know quite alot
Can i ask what you do for a living and your involvement with android as you seem very clued up on the technologies and code
My involvement with android is only due to having an android phone. My primary experience is with ARM linux. My current job involves a lot of linux work including kernel development and maintenance for GDC4S related to a couple of Army programs. I've also done quite a bit of hobby related work. (see http://google.com/search?q="russ+dill"+linux)
It would be great to learn more on that. I think knowing the answer might actually lead me to decide whether I should keep the phone since bad coding practices can produce longer delays in updates and/or bugs later on. HTC has pretty much established themselves in Android, I might consider switching to a Magic or Hero.
Device(s): i7500@galax0-1.6.3.4
OC@710mhz
HTC Desire - never ending modding
Thanks: 104
Thanked 917 Times in 775 Posts
the likeliness is their coding practice is babba, but having said that this new compcache rom is a custom developed one and looks to be the dogs cahoones so whether or not the code is a mess, good things can still be achieved. i5 has only been out a week or so and hdblog have made a rom from its base
I imagine that they will keep working like that, and merging to updates like donut will be painful for them.
It does bother me that their source releases aren't tagged to indicate which firmware they match up with. I'll email Harald Welte and Ben Dooks and ask them what they deal is.
Unfortunately, Samsung Electronics and Samsung LSI (for which Dooks and Welte have extensively worked with) are two different companies.
Whoa... if Motorola Droid is supposed to be running 2.0 and is slated for a Nov 6th release... that would put Samsung a good 2 releases behind the current... LOL
Thank you for signing up to receive updates for the 4
An email has been dispatched to confirm your signup. Please click the link in the email.
Buy the Samsung i7500
Sign up for instant notification when the Samsung i7500 goes on sale!
When Samsung joined the Open Handset Alliance, excitement and anticipation engulfed the mobile world. With industry leading mobile phones such as the Samsung Instinct and Samsung Omnia already on the market, expectations soared. The speculation can f... Read More
Donut on Galaxy
Link to the Samsung Galaxy kernel source
AndNav2 requires Android 1.6
