Hey.. Can someone get me the system dump on the new stock 2.3.6?
I want to make a Heimdall One-Click from it
Code:
dd if=/dev/block/bml8 of=/sdcard/kernel bs=4096
dd if=/dev/block/stl9 of=/sdcard/system bs=4096
AdamOutler said:
Hey.. Can someone get me the system dump on the new stock 2.3.6?
I want to make a Heimdall One-Click from it
Code:
dd if=/dev/block/bml8 of=/sdcard/kernel bs=4096
dd if=/dev/block/stl9 of=/sdcard/system bs=4096
Click to expand...
Click to collapse
Thanks for doing this, Adam.
System dump of the official UCKL2 anyone?
+1 cause Odin don't work for **** for me
Big Dogg Infuse I997 ZeusB5 ICS!
adam it appears that the last leak from prezkret i997uckl2 was the official. the issue is that we cant root it without using a custom kernel. for that reason if there are some minor diffs we will need to use the leaked kernel regardless. all attemps to root other than a non secure kernel fail. without root we cant dump the partitions. so id suggest just using the odin package that prezkret posted 6+ weeks ago to create the oneclick. thanks for your efforts regardless. the mac users need some love and att nor samsung will give it to them...
Dani897 said:
adam it appears that the last leak from prezkret i997uckl2 was the official. the issue is that we cant root it without using a custom kernel. for that reason if there are some minor diffs we will need to use the leaked kernel regardless. all attemps to root other than a non secure kernel fail. without root we cant dump the partitions. so id suggest just using the odin package that prezkret posted 6+ weeks ago to create the oneclick. thanks for your efforts regardless. the mac users need some love and att nor samsung will give it to them...
Click to expand...
Click to collapse
Rooting is not my concern. My concern is to get a total stock reversion package. Custom kernels can be flashed later as a upgrade. Thanks for the tip on prezkret. Ill convert an Odin package or flash a zip and pull my own partitions via UART.
Expect something next week sometime.
AdamOutler said:
Rooting is not my concern. My concern is to get a total stock reversion package. Custom kernels can be flashed later as a upgrade. Thanks for the tip on prezkret. Ill convert an Odin package or flash a zip and pull my own partitions via UART.
Expect something next week sometime.
Click to expand...
Click to collapse
I understand, I was just expressing the difficulty in actually dumping it....
forum.xda-developers.com/showthread.php?t=1475414&page=41
might look here too, maybe check it for difs. could be more logging in the leak, who knows...
Here's the odin-flashable tar if you need it.
ha, all files are identical from the leak to the decrypted kies package, last modified on the same minute and exactly the same size. for anyone that believes there may be a difference in the att realease and the leak i think this is pretty undisputable that they are infact identical.
Dani897 said:
ha, all files are identical from the leak to the decrypted kies package, last modified on the same minute and exactly the same size. for anyone that believes there may be a difference in the att realease and the leak i think this is pretty undisputable that they are infact identical.
Click to expand...
Click to collapse
If you use the App CPU Spy, You would see down below where it says Linux version that the kernel is dated Dec 13th 2011. It's FINAL!
Dani897 said:
ha, all files are identical from the leak to the decrypted kies package, last modified on the same minute and exactly the same size. for anyone that believes there may be a difference in the att realease and the leak i think this is pretty undisputable that they are infact identical.
Click to expand...
Click to collapse
Which makes me wonder what they were doing for 2 months.
Sent from my Nokia 5190 using t9
jvanlew said:
Which makes me wonder what they were doing for 2 months.
Sent from my Nokia 5190 using t9
Click to expand...
Click to collapse
Loading up bloatware on it.
Sent from my SAMSUNG-SGH-I997 using xda premium
Makes you wonder about placebo effects.
We had this leak since Nov. If it has the same file size and time and date, it kinda makes you wonder about all the statements about how much faster and snappier and better battery etc...
It's possible that just a factory reset will make your phone speedier.
Thanks, jvanlew.
jvanlew said:
Which makes me wonder what they were doing for 2 months.
Sent from my Nokia 5190 using t9
Click to expand...
Click to collapse
Arguing over who could provide the worst delivery method possible.
Sent from my SAMSUNG-SGH-I997 using xda premium
jvanlew said:
Which makes me wonder what they were doing for 2 months.
Sent from my Nokia 5190 using t9
Click to expand...
Click to collapse
The time for the Official was set right. After the final and last leak it takes a month for it to be finalized and released Officially, Although It did feel longer.
kl2 was mid December, check prezkrets post for an exact date. I 6weeks for testing isn't bad. what pisses me off is the 4 months they used to develope the firmware only started in sepember, what were they doing till then? the phone was advertised to be released with by samsung in January with gb and HDMI not one or the other, the i9000 already had gb. what was going on that they held us back all those months? the ki3 leak was a mess, data issues, galaxy s animation was still presant and so forth. far from finninshed, they made significant progress in 3 months, removed carrier IQ then decided to give us a screwed up launcher without wallpaper scrolling. were they sitting on their asses till September hoping nobody would notice their $200 flagship phone was discontinued after 3 months and was a year behind on firmware compared to similar models from the same company?
jvanlew said:
Which makes me wonder what they were doing for 2 months.
Sent from my Nokia 5190 using t9
Click to expand...
Click to collapse
Ensuring that it was indeed broken crap - we can't have AT&T releasing a good firmware that will keep a customer owning the phone, right?
AT&T claims that it's quality testing that delays this stuff, but the clear boneheaded mistakes that make it through QA and the fact that some devices (like I9100->I777 and I9000->Captivate) can run firmwares from their international brethren with little change means that AT&T is delaying these updates to mangle them.
Over in I777-land, the I9100 firmware releases are clearly of far higher quality than the I777 ones despite the fact that AT&T is supposedly doing all of this extra testing no international carrier does.
Entropy512 said:
Ensuring that it was indeed broken crap - we can't have AT&T releasing a good firmware that will keep a customer owning the phone, right?
AT&T claims that it's quality testing that delays this stuff, but the clear boneheaded mistakes that make it through QA and the fact that some devices (like I9100->I777 and I9000->Captivate) can run firmwares from their international brethren with little change means that AT&T is delaying these updates to mangle them.
Over in I777-land, the I9100 firmware releases are clearly of far higher quality than the I777 ones despite the fact that AT&T is supposedly doing all of this extra testing no international carrier does.
Click to expand...
Click to collapse
Interesting theory. What do you think they do to mangle them? Take the Infuse update for example, are you talking about things as simple as the non-scrolling wallpaper in our leak/official or more low-level things to slow it down some?
i somewhat disagree with entropy and mostly agree. i found call quality on the infuse and captivate to be better than their galaxy s bretheren from other carriers.
that's all i disagree on. the captivate had hsupa removed, no option to disable data, the samsung implimentation made it dificult to force edge. there was no voice dialer. no bluetooth voice dialing. no sideloading apps. the sources were incomplete for 2.1 so unhelpful compilied his kernels from vibrant sources. i couldn't get flash to work on stock even though 2.1 did have a flash plugin on the captivate, wifi tethering was disabled depending on the firmware, usb tethering was hidden depending on the firmware (apparently there is a way to do it but it's not a straitforward option, tetering is not something i often do and i have only used wifi so my knowledge it on the cappy is limited) the libs and kenrel and possibly other rom ellements were designed to only work correctly with the captivate modem that disabled hsupa, if you used another modem it broke bluetooth audio in calls. the captiuvate was intentionally crippled! there isnt even a question about that.
the infuse firmware is a little better but the timeline is obsurd!
if stock android wasnt so ugly and the contacts and mms app were more feature rich id be aosp all the way but the nexus phones are a bit lackluster, the backlights on the nexus s being hardwired to the screen is bs, what about notifications? one thing that made the nexus 1 great was that awesome backlit trackball. the interface sucks but the native features of the os work flawlessly on aosp. i wish manufaturers and carriers didnt deny the end user the native features like tethering however you please with no headaches in order to brand the phone with a unique ui and hold back the update schedule. the current state of android phones is really depressing.
---------- Post added at 08:05 PM ---------- Previous post was at 08:01 PM ----------
oldbbman said:
Loading up bloatware on it.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
the leak was pre loaded with bloatware, it was the year before that they were busy half-a$$ing the os and bloating it with useless apps
Related
Samsung posted this updated installation guide on their website this morning. IMHO if it's going to happen in December it's going to be this week. http://www.samsung.com/us/support/owners/product/SGH-I897
http://downloadcenter.samsung.com/c...2349485/ATT_I897_Captivate_Kiesmini_Guide.pdf
I think they just added the instructions for recovery mode. Seeing as how "Some of" the Canadian Vibrants are reporting corrupt storage issues after trying to upgrade via kies mini.
With all of the gingerbread action in the past week, I don't know why anyone would even bat an eye at an official froyo release. If you aren't running a 2.2 rom based on the leaked versions yet, you are severely limiting the speed and "snappiness" of your device. In short, while you guys wait for Sammy to roll out their "official" 2.2 update, we'll be running GB.
SlappyMcGee said:
I think they just added the instructions for recovery mode. Seeing as how "Some of" the Canadian Vibrants are reporting corrupt storage issues after trying to upgrade via kies mini.
Click to expand...
Click to collapse
Good point, but isn't that the U.S. site?
jatkins09 said:
With all of the gingerbread action in the past week, I don't know why anyone would even bat an eye at an official froyo release. If you aren't running a 2.2 rom based on the leaked versions yet, you are severely limiting the speed and "snappiness" of your device. In short, while you guys wait for Sammy to roll out their "official" 2.2 update, we'll be running GB.
Click to expand...
Click to collapse
There are plenty of reasons as discussed in these forums. For me I heavily use my phone for business and cannot afford any "hiccups".
jatkins09 said:
With all of the gingerbread action in the past week, I don't know why anyone would even bat an eye at an official froyo release. If you aren't running a 2.2 rom based on the leaked versions yet, you are severely limiting the speed and "snappiness" of your device. In short, while you guys wait for Sammy to roll out their "official" 2.2 update, we'll be running GB.
Click to expand...
Click to collapse
JH7 w/ Voodoo is faster than any ROM based on a leaked Froyo build (from my experiences). I haven't tried the i9000 based ROMs however.
jz3 said:
There are plenty of reasons as discussed in these forums. For me I heavily use my phone for business and cannot afford any "hiccups".
Click to expand...
Click to collapse
I too use my phone for work. And I also cannot have any "hiccups". I can be without it long enough to flash a ROM and then re-setup the stuff I need. That process takes less than 30 minutes nowadays.
If you stick to a true Cappy ROM (not an i9000-based one), then you won't experience hiccups...at least I don't. Battery life is a slight issue, but really, when are completely without the means to charge up some?
I've flashed maybe half a dozen times since I can't afford a bricked phone. I'm picky about flashing. But I'm also very picky about having a phone that is quite impressive hardware-wise, but almost completely crippled by the lackluster software. While Froyo isn't the most awesome thing ever, it is a major improvement over Eclair.
guthriemd said:
I too use my phone for work. And I also cannot have any "hiccups". I can be without it long enough to flash a ROM and then re-setup the stuff I need. That process takes less than 30 minutes nowadays.
If you stick to a true Cappy ROM (not an i9000-based one), then you won't experience hiccups...at least I don't. Battery life is a slight issue, but really, when are completely without the means to charge up some?
I've flashed maybe half a dozen times since I can't afford a bricked phone. I'm picky about flashing. But I'm also very picky about having a phone that is quite impressive hardware-wise, but almost completely crippled by the lackluster software. While Froyo isn't the most awesome thing ever, it is a major improvement over Eclair.
Click to expand...
Click to collapse
I used to flash quite often.. But it got to be a hassle restoring game saves... Contacts (then re-linking then to my Facebook contacts)... yada yada... It takes up more tme than one would think.
And like its been said. A stable release from Samsung means a stable release for the devs.
Though Im not gonna think twice about flashing 2.3... Can't wait for a working version.
Sent from my SAMSUNG-SGH-I897 using XDA App
jz3 said:
Good point, but isn't that the U.S. site?
There are plenty of reasons as discussed in these forums. For me I heavily use my phone for business and cannot afford any "hiccups".
Click to expand...
Click to collapse
thats understandable but i would say in my experience there are less hiccups with most custom 2.2 roms than there are with either stock 2.1 rom.
Not to mention on the business front Exchange is much more stable and functional for me on the 2.2 roms vs. 2.1 stock.
Axura, Assonance, Chronos all very stable.
I thought the hold up was the carriers on the update. But I think Samsung has been really slow in the release of 2.2. Samsung not AT&T has been the problem all along. Don't you think one of the carriers would have tried to be the first to have their device on 2.2 to sale through the holidays.
more speculation here, but I suspect there has been some back and forth between samsung and att. Like att put it through their testing procees. (we know it is pretty extensive) and asked for a change or two. 'caus I'm pretty convinced that samsung just checks that the phone powers up and gets signal with no care as to the quality of signals it is receiving... I am certainly intrigued to see what they come out with after "working" on it for so long.
gmanunited said:
I thought the hold up was the carriers on the update. But I think Samsung has been really slow in the release of 2.2. Samsung not AT&T has been the problem all along. Don't you think one of the carriers would have tried to be the first to have their device on 2.2 to sale through the holidays.
Click to expand...
Click to collapse
The carriers don't care that much... OS version as a selling point matters ZERO to most users unless it brings some major feature. Most feature improvements are minor and don't affect most users - they are not hackers or flashers. For every one person visiting phone Forums, there are 10 others that own the phone and just use it.
2.2 has been out for Galaxy S and Armani - so it is really done for the hardware - we haven't seen any Froyo leaks in a while either - the hold up is the carriers - Samsung was probably late getting it to them, and now they have to give it their blessing.
The Vibrant Froyo was released recently but pulled as it corrupted internal storage. So T-Mo was first, and i guess AT&T will be second.
I also think this updated doc is relevant to the Froyo release - we didn't see this doc with the previous Kies Mini update and there was no Emergency recovery option - they are definitely getting ready to push something new.
gmanunited said:
I thought the hold up was the carriers on the update. But I think Samsung has been really slow in the release of 2.2. Samsung not AT&T has been the problem all along. Don't you think one of the carriers would have tried to be the first to have their device on 2.2 to sale through the holidays.
Click to expand...
Click to collapse
No...certainly not AT&T...they always push the I-phone harder than their Android phones...Can't say for any others selling Galaxy phones though..
Seriously...I use my phone for my work and business as well,and there are quite a few stable 2.2 roms out to use.Hiccups...are always possible...but most times..it's because of a bad install that causes more headaches than anything else..or something left over on the system too. No way in hell would I wait on either Samsung or AT&T for another bloat filled update.Not to mention...all of the bricked phones that happened with Kies last time around...Your much safer getting your upgrade longing filled here..than any OTA update....at least if you get it from here you will get help fixing it...Good luck doing that with AT&T or Samsung...you'll be out a phone for a few days or weeks..
Mac
alphadog00 said:
The carriers don't care that much... OS version as a selling point matters ZERO to most users unless it brings some major feature. Most feature improvements are minor and don't affect most users - they are not hackers or flashers. For every one person visiting phone Forums, there are 10 others that own the phone and just use it.
2.2 has been out for Galaxy S and Armani - so it is really done for the hardware - we haven't seen any Froyo leaks in a while either - the hold up is the carriers - Samsung was probably late getting it to them, and now they have to give it their blessing.
The Vibrant Froyo was released recently but pulled as it corrupted internal storage. So T-Mo was first, and i guess AT&T will be second.
I also think this updated doc is relevant to the Froyo release - we didn't see this doc with the previous Kies Mini update and there was no Emergency recovery option - they are definitely getting ready to push something new.
Click to expand...
Click to collapse
Froyo was not released then pulled for the T-Mobile Vibrant. It was released and pulled for the Bell (Canada) Vibrant.
Thought that Sprint's Epic has Froyo released? Or is that just another leak too? Forgot to ask my brother last night (he has the Epic)
None of the US carriers has Froyo update for Galaxy S yet. That tells me it is Samsung that is dragging the feet.
foxbat121 said:
None of the US carriers has Froyo update for Galaxy S yet. That tells me it is Samsung that is dragging the feet.
Click to expand...
Click to collapse
Even if samsung pushed the update to the carriers 2 weeks ago they still have to test it.
Sent from my MB520 using XDA App
alphadog00 said:
Even if samsung pushed the update to the carriers 2 weeks ago they still have to test it.
Sent from my MB520 using XDA App
Click to expand...
Click to collapse
Samsung knows exactly how long carriers need to validate and test the firmware. If they intent to release the Froyo on schedule, they should have pushed the update earlier. After all, carriers test updates from all manufacturers like Motorola and HTC, not just Samsung. If Motorola and HTC can release Froyo, and subsequent patches, in time for their phones, there is no reason Samsung can't if it is capable of.
This just tells you how somethings never change when it comes to firmware update from Samsung.
Then why does AT&T have the Samsung Galaxy Tab available with Android 2.2?
C.C.W. said:
Then why does AT&T have the Samsung Galaxy Tab available with Android 2.2?
Click to expand...
Click to collapse
Because the tab was released with 2.2. It never had to get updated.
Sent from my SAMSUNG-SGH-I897 using XDA App
C.C.W. said:
Then why does AT&T have the Samsung Galaxy Tab available with Android 2.2?
Click to expand...
Click to collapse
I think you may have answered your own question. It's likely that Samsung put their development resources in the Galaxy Tab and let the phones wait. They already have our money.
So uhh, i dont know if anyone has seen this.. but here you go
http://androidcommunity.com/galaxy-s-android-2-3-gingerbread-update-imminent-20110225/
It looks like a legit release for 2.3 for Galaxy S. If thats the case, how hard would it be to port it from that to the captivate?
and a march release
Oh and btw... dont flame me if its wrong or anything.. im just a guy posting something he found... which may help out the community -.-
supaphreek said:
So uhh, i dont know if anyone has seen this.. but here you go
http://androidcommunity.com/galaxy-s-android-2-3-gingerbread-update-imminent-20110225/
It looks like a legit release for 2.3 for Galaxy S. If thats the case, how hard would it be to port it from that to the captivate?
and a march release
Oh and btw... dont flame me if its wrong or anything.. im just a guy posting something he found... which may help out the community -.-
Click to expand...
Click to collapse
I think this has been posted a couple of times (can't remember, but I know I've seen it around the web a couple of times). Either way, right now it's a "friend of a friend said this" type thing. Until there is some proof myself and many others will remain skeptical.
Another issue is that the Galaxy S phones are much more popular in other parts of the world. With Samsung trying to charge all the carriers upgrade fees like they did with 2.2, causing a lot of the delays, the carriers may not be interested in upgrading the phone to 2.3 even if Samsung has it ready. Especially since we're going to see the SGS 2 and multiple other newer and better phones out by then. The Captivate and other SGS phones will be low end phones by then, and the carriers probably won't want to pay Samsung for updates to an old phone.
oh man! so theres the possibility of never seeing a legit 2.3? :S i guess il have to live with CM7.
ANY custom rom will be better than the rom its based off of.
WHO CAN?
XDA CAN!!
AJerman said:
Another issue is that the Galaxy S phones are much more popular in other parts of the world. With Samsung trying to charge all the carriers upgrade fees like they did with 2.2, causing a lot of the delays, the carriers may not be interested in upgrading the phone to 2.3 even if Samsung has it ready. Especially since we're going to see the SGS 2 and multiple other newer and better phones out by then. The Captivate and other SGS phones will be low end phones by then, and the carriers probably won't want to pay Samsung for updates to an old phone.
Click to expand...
Click to collapse
This "issue" was debunked a long time ago.
Miami_Son said:
This "issue" was debunked a long time ago.
Click to expand...
Click to collapse
Was it? I hadn't heard that, but I didn't pay that much attention to the AT&T release of 2.2 since I've been running 2.2 for months.
Either way, even if it doesn't come to a money issue, it's still going to come down to the same issue. The SGS 2 will have replaced the SGS by the time Samsung would have Gingerbread ready, and I wouldn't doubt at all if this phone never saw another update. It was hard enough to get 2.2 out of Samsung when this phone was their flagship, let along getting them to push one more update when it's replacement is already ready.
Edit: Just read an article about that, you're right. I hadn't seen Samsung's reply to that rumor. I guess that just makes Samsung lazy and not lazy and greedy, haha.
Miami_Son said:
This "issue" was debunked a long time ago.
Click to expand...
Click to collapse
It was debunked by Samsung denying it, which means it wasnt really debunked.
I wouldn't expect them to be public about such things....you can have a "price to prioritize" or something which is essentially the same thing but allows you to say you aren't charging for the upgrade.
I'm not saying I know what's going on, I'm just saying I don't trust Samsung at their word.
Sent from my SAMSUNG-SGH-I897 using XDA App
AJerman said:
I guess that just makes Samsung lazy and not lazy and greedy, haha.[/i]
Click to expand...
Click to collapse
Why do you assume it was samsung that held back the update? It was more than likely ATT, being that other providers had already released the update.
Sent from my SAMSUNG-SGH-I896
fatttire said:
It was debunked by Samsung denying it, which means it wasnt really debunked.
I wouldn't expect them to be public about such things....you can have a "price to prioritize" or something which is essentially the same thing but allows you to say you aren't charging for the upgrade.
I'm not saying I know what's going on, I'm just saying I don't trust Samsung at their word.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Pretty sure there would be some sort of outcry from carriers if Samsung was lying. There would probably be more legal ramifications if Samsung lied about not charging for updates rather than some bad publicity about charging for the updates.
shust82 said:
Why do you assume it was samsung that held back the update? It was more than likely ATT, being that other providers had already released the update.
Sent from my SAMSUNG-SGH-I896
Click to expand...
Click to collapse
Samsung did its part in holding up the update by not wanting to pay the fee the service providers were charging. Same goes with all carriers that were way behind on the 2.2 update.
I'll be skipping it. I had problems with the 2.2 update and just flashed my first ROM. So much faster and the battery lasts a ton longer
Trusselo said:
ANY custom rom will be better than the rom its based off of.
Click to expand...
Click to collapse
You're stating the obvious. Why would anyone modify a ROM to make to inferior to the original? It would be nice if there were an original 2.3 to base something on.
opcow said:
You're stating the obvious. Why would anyone modify a ROM to make to inferior to the original? It would be nice if there were an original 2.3 to base something on.
Click to expand...
Click to collapse
he means custom source-built rom.
a.vandelay said:
he means custom source-built rom.
Click to expand...
Click to collapse
No what he is doing is his usual routine of taking a dump on any post where someone mentions being interested in Samsung firmware releases, because he thinks what is already out via third-parties is all anyone with a brain should want. And yet the AT&T Froyo release resulted in, in my opinion, the best ROM yet from DesignGears.
opcow said:
No what he is doing is his usual routine of taking a dump on any post where someone mentions being interested in Samsung firmware releases, because he thinks what is already out via third-parties is all anyone with a brain should want. And yet the AT&T Froyo release resulted in, in my opinion, the best ROM yet from DesignGears.
Click to expand...
Click to collapse
you obviously haven't tried any 2.2.1 i9000 roms then... Because they blow the doors off any official froyo rom from samsuck. I tried cog 4 and torch and it lagged beyond belief, no offense to dg, but its samsucks fault.
davwman said:
you obviously haven't tried any 2.2.1 i9000 roms then... Because they blow the doors off any official froyo rom from samsuck. I tried cog 4 and torch and it lagged beyond belief, no offense to dg, but its samsucks fault.
Click to expand...
Click to collapse
I was running the official Rogers 2.2. and it was better than the official 2.1 that I played around with for a few days first to compare. However, putting Firefly 2.3 (and Andromeda 1.2 before that) I can certainly confirm that the custom rom route is definitely the way to go. MUCH faster (lagfix probably has huge impact on this) far more functional (rooted) better battery consumption (custom kernels) and IMO far better support. I can tell you I fully expect that XDA and the like would provide far superior peer based support than you'd get from your provider. Of course chances are if you weren't putting custom stuff on your phone you'd be far less likely to need it, but the collective knowledge here for general support of devices is far more impressive than some tech support drone that you'd speak to if you called in to you provider.
shust82 said:
Why do you assume it was samsung that held back the update? It was more than likely ATT, being that other providers had already released the update.
Sent from my SAMSUNG-SGH-I896
Click to expand...
Click to collapse
Let's be honest, this phone could have come with 2.2 on it already when it shipped. Samsung took quite a while to get 2.2 ready even for the I9000s. There are always going to be carriers delays after it's ready, but Samsung took their time as well.
AJerman said:
Let's be honest, this phone could have come with 2.2 on it already when it shipped. Samsung took quite a while to get 2.2 ready even for the I9000s. There are always going to be carriers delays after it's ready, but Samsung took their time as well.
Click to expand...
Click to collapse
Froyo was announced less than 2 months before this phone shipped. The source wasn't available until less than a month before. I see no problem with shipping with 2.1 under these circumstances.
davwman said:
you obviously haven't tried any 2.2.1 i9000 roms then... Because they blow the doors off any official froyo rom from samsuck. I tried cog 4 and torch and it lagged beyond belief, no offense to dg, but its samsucks fault.
Click to expand...
Click to collapse
I've used 2.2.1 ROMs and they are great. If I recall Serendipity is one and it was my favorite prior to Andromeda (which is 2.2 i9010 based and very fast). Cog 4.1 is the first of DGs ROM I've used for more than a day in months; I haven't been a huge fan. As soon as i9000 kernels became mostly trouble free I moved on. I'm not saying the others were bad and I'm not saying 4.1 is better than brand x, I just like it better than previous DG ROMs I tried.
As for your lag problems with Cog 4.1, I don't doubt you, I just don't have it, but I'm using the Paragon kernel which may account for our different experiences.
The leak was out a while ago right?
So how long would it take them to release the official gingerbread OTA or via kies???
Another month? or most likely more?
Probably not for a while. I'm guessing somewhere around Janurary or Feburary.
I think KH1 or one of the others was an update through Kies but Samsung removed it.
Hopefully they'll release an official release before they release Hercules.
For now ICINB or Valhalla are 2 good Gingerbread ROMs. Even the stock KH2 is good. I'm currently on Valhalla.
pwner5889 said:
Probably not for a while. I'm guessing somewhere around Janurary or Feburary.
Click to expand...
Click to collapse
lol if they released it around jan or feb it would be a waste as ics will be released this winter
Personally u just gave up on Tmobile GB official release. They really only care about money. Soft ware support for their devices is all the way in the bottom of their priority list unless it bring in direct cash income.
Are you blaming Tmobile? Definitely is samsungs responsibility to provide the update not t mo
Sent from my SGH-T959V using xda premium
Yes t mo may do otas but they have to be given the update from the devs which I believe Samsung is holding out or not prioritizing it cause they want more moola
Sent from my SGH-T959V using xda premium
Why would tmobile want this gb leaks to their customers?They are holding up because these samsung gb are kinda pathetic to release to the masses..bluetooth issues,low wifi signal when your only like inches away etcc..if they release gb like this you"ll have many customers calling tmobile about issues left and right.unless samsung figures out a really good gb release of THEIR OWN device its not coming out!..dev s make gb good on this phone
Ohh and lets not forget sg2 is around the corner,samsung might just screw us over or the people who are waiting on GB! Tmobile in general are idiots but on this ill agree with them releasing this would just bring them more trouble than good!
My bet is that if Hercules gets released before gb update then there will be no update. That will be Samsung and t mobiles flagship device. Their focus will be on that and ice cream for the newest phones.
Sent from my SGH-T959V using xda premium
Yeah good point
BTW, Ice cream sandwich is designed to receive OTAs directly from google, instead of from the phone makers. So, ice cream sandwich will only work, if they remove the updater function or dump touchwiz. And I highly doubt that they will dump touchwiz, so that means Galaxy s will die with all their devices being stuck on GB(or leaks), and they are not doing any more nexus line phones. HTC or LG will be making nexus 3. Also, you said that they would focus on releasing ICS to the newer devices, I doubt that. GB was already long out when our phone was released on Froyo. And "50+%" chance that GB will never officially come to our phones. So what makes you think that they will update to ICS. They will probably give out buggy leaks and die there.
Phone release on eclair or froyo from Sammy, will stay on Froyo.
Phone release on GB from Sammy, will stay on GB.
That is my point. Not to make anyone's hopes down. We will have a lot more fun with this phone, I guarantee that CM7 will "eventually" work and we will many more roms to come.
PS. I never liked Sammy. This was just the best phone when I bought it
im going to disagree that the sgs4g in your mind wont be getting ics as google plans to release it to all devices to unify and defragment the android os.. remember samsung makes the hardware and some of the applicatons that go in the phone they how ever do not make the os. t mobile att verizon orange vodaphone will submit to google the stuff they want in there rom (the bloatware we remove ) Once approved that there features do not break the os (this is why they do test for the most part.) the carriers get there updates and wala so do u once they are pushed out as ota or keis
You have a great point. But touchwiz is created by samsung. Standardly, otas are pushed out as recovery edify flash able files with a META-INF, and a /system and etc folders. Samsung releases their kies otas that flash a bunch of rfs files. Samsung maintains their rfs file system and zImage kernel form. Android uses boot.imgs. So in order to use ICS, there will probably need to be an irreversible boot loader flash that will make the phone use boot.imgs instead of zImages. Possibly revert method would be flash old bls with CWM or stock androidbl
I find it disheartening that people are now guessing january or february for a gb release, when in july everyone was saying august or september.
I knew before purchasing this phone that Samsung sucks at updating firmware, but it truly seemed to have the best features at the time, and to be honest, (six months later) I'm glad I didn't wait for the S2. When does the Hercules come out btw?
Also, how long would it take a noob to load a custom rom/bootloader, and would it be possible with a mac?
Sent from my SGH-T959V using XDA App
Sure, you just need heimdall Mac edition, that is what I use.
Sent from my SGH-T959V using XDA App
ToiletSalesman said:
I find it disheartening that people are now guessing january or february for a gb release, when in july everyone was saying august or september.
I knew before purchasing this phone that Samsung sucks at updating firmware, but it truly seemed to have the best features at the time, and to be honest, (six months later) I'm glad I didn't wait for the S2. When does the Hercules come out btw?
Also, how long would it take a noob to load a custom rom/bootloader, and would it be possible with a mac?
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Disheartening indeed. The longer they take to release it the longer we all have to wait for kernel sources to be release and they have up to 3 months I believe after the OTA release to release kernel source code. Until then we have no custom kernels for GB that support cool things like Voodoo for sound and BLN. Those two things not being available for GB though the former is thanks to RaverX3X, are the sole reasons why I still stick to froyo.
Compxpert said:
Disheartening indeed. The longer they take to release it the longer we all have to wait for kernel sources to be release and they have up to 3 months I believe after the OTA release to release kernel source code. Until then we have no custom kernels for GB that support cool things like Voodoo for sound and BLN. Those two things not being available for GB though the former is thanks to RaverX3X, are the sole reasons why I still stick to froyo.
Click to expand...
Click to collapse
Um theres voodoo sound for gb too..just get the paid lastest version!
daxecutioner24 said:
Um theres voodoo sound for gb too..just get the paid lastest version!
Click to expand...
Click to collapse
he means i modified the sound in the rom enough that its not really needed
Ugh will they ever come out with new stock firmware?
Sent from my SGH-T959V using XDA App
Are there any ICS Kernels for Rogers devices?
Im looking for one that hopefully has:
Boot Animations
OC/UV
BLN
Will older kernels made for GB still work in the ICS leak?
Since the ICS leak was an AT&T build, I do not believe there are any kernels for Rogers specifically. As for the GB kernels working, I'm not sure; nor would I risk the chance of bricking by flashing one.
I'm sure someone will be around soon enough who knows more than I.
OFWGKTADGAF said:
Are there any ICS Kernels for Rogers devices?
Im looking for one that hopefully has:
Boot Animations
OC/UV
BLN
Will older kernels made for GB still work in the ICS leak?
Click to expand...
Click to collapse
No kernel for Rogers and no kernel that has OC/UV and BLN yet also.
GB kernel will make you bootloop so don't bother with them. ICS kernel for ICS ROM...
Sent from my SAMSUNG-SGH-I727 using Tapatalk
kr3w1337 said:
No kernel for Rogers and no kernel that has OC/UV and BLN yet also.
GB kernel will make you bootloop so don't bother with them. ICS kernel for ICS ROM...
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Click to expand...
Click to collapse
I think i may have already flashed an unsecure kernel... i dont remember if i did or not.
Can anyone upload the stock kernel for me?
outside of a couple of insecure kernels, nothing else out there. i don't believe the source code for the kernels has dropped either. Once that happens I am sure there will be some out there with what you are looking for.
called Rogers today to inquire about the ics update that the sales person told me was coming soon 2 months ago and they told me they don't know when and if it's going to happen once samsung gives them the update they will put it out and that each rogers store is franchised, independently owned and operated so basically washed their hands of it and that I would need to deal with the store manager directly for any compensation or apology looks like canadians are going to wait a long time before we get official ICS next time def gonna go with a nexus and **** this bull****
Rogers updates, not
My 15 year experience as a Rogers customer has shown that it has never updated the kernel or firmware on the phones that I've purchased while every other non-canadian providers did (very frustrating).
Rogers only updates its bloatware. What you buy is what you live with unless you mod. If you want new firmware, Rogers wants you to buy a new phone.
As far as I know, the only exception to this "policy" is if you have an iPhone but then that's a different kettle of fish because you are dealing with Apple not Rogers. But I can't really confirm this as I've never been an Apple user. I don't care for Apple's Orwellian business model.
Ciao!
phil9000 said:
My 15 year experience as a Rogers customer has shown that it has never updated the kernel or firmware on the phones that I've purchased while every other non-canadian providers did (very frustrating).
Rogers only updates its bloatware. What you buy is what you live with unless you mod. If you want new firmware, Rogers wants you to buy a new phone.
As far as I know, the only exception to this "policy" is if you have an iPhone but then that's a different kettle of fish because you are dealing with Apple not Rogers. But I can't really confirm this as I've never been an Apple user. I don't care for Apple's Orwellian business model.
Ciao!
Click to expand...
Click to collapse
I agree with you Phil. I have had 3 Android handsets, and if I didn't root and flash, I would still be on ver 2.3.3.
It is a blessing that there are (collectively) these amazing individuals that can make sense of the software, to give us the plethora of features we get to enjoy.
Maybe it is just me, but I tried and tried my hand at modding... Let's just say, I would rather be envious of the Dev's than screw up my laptop again.
Thanks to all the Dev's that put in the time it takes to make these amazing mods.
maybe....
http://au.ibtimes.com/articles/5034...veals-android-4-kitkat-os-11.htm#.UicpuH-I68A
here's a quote from the article:
Android 4.4 KitKat Features
Google hasn't revealed any features yet of the upcoming Android 4.4 KitKat but instead, the company said: "our goal with Android KitKat to make an amazing Android experience available for everybody."
With this statement from Google, it is expected that KitKat will become accessible to Android-running devices with lower RAM such as 512MB and older Android version such as 2.3 Gingerbread. This optimisation has been rumoured to be included in Android 5.0 Key Lime Pie.
Click to expand...
Click to collapse
What...
http://signatures.mobile-overload.com/wp-content/uploads/2013/07/sig-cm-5.png
I would not hold my breath.
Sent from my SCH-I545 using XDA Premium HD app
lol no. Unless if it was created by an awesome person here, but there's no point in that. This phone is long dead, earlier this week I finally moved on, and oh my gosh, its been great having a Nexus 4 over this phone that was out-dated before it was even released back in Spring 2011.
Nope
You'll probably never see a KitKat version on the Charge. The main reason is the same that you never saw ICS or JB on the Charge. The code for the radios was never released. I've tried JB on the Charge, it runs well; however the camera and data don't work. Also, while I still use the Charge as my primary phone, there's not many of us left.
ICS and all versions of JB work fine on this phone already... we are just missing the radios.
I doubt anyone cares about this phone anymore anyways...
10amla said:
You'll probably never see a KitKat version on the Charge. The main reason is the same that you never saw ICS or JB on the Charge. The code for the radios was never released. I've tried JB on the Charge, it runs well; however the camera and data don't work. Also, while I still use the Charge as my primary phone, there's not many of us left.
Click to expand...
Click to collapse
I'm inclined to agree, though it would be awesome to be proven wrong!
JihadSquad said:
ICS and all versions of JB work fine on this phone already... we are just missing the radios.
I doubt anyone cares about this phone anymore anyways...
Click to expand...
Click to collapse
Yeah not many folks left that's for sure... still a few that care though
dwitherell said:
I'm inclined to agree, though it would be awesome to be proven wrong!
Yeah not many folks left that's for sure... still a few that care though
Click to expand...
Click to collapse
I agree with both assessments. Thanks for all the work you've done on Tweaked, Dwith. My wife and I love it on our charges.
P.S. One problem I had with Tweaked Lite, when I installed it, it didn't install file manager(I think that's what it's called on stock) and when I went to select a sound(not ringtone) for a ringtone it would show and error. I went to tweaktools and installed the file manager and it works fine. Not sure why it wouldn't work with my other file management programs.
10amla said:
I agree with both assessments. Thanks for all the work you've done on Tweaked, Dwith. My wife and I love it on our charges.
P.S. One problem I had with Tweaked Lite, when I installed it, it didn't install file manager(I think that's what it's called on stock) and when I went to select a sound(not ringtone) for a ringtone it would show and error. I went to tweaktools and installed the file manager and it works fine. Not sure why it wouldn't work with my other file management programs.
Click to expand...
Click to collapse
Yeah I am not a fan of MyFiles, and for better or worse the call to that for ringtone selecting is hardcoded... at least tweaktools brings it back quick enough - forgot about that tbh, sorry for the troubles!
dwitherell said:
Yeah I am not a fan of MyFiles, and for better or worse the call to that for ringtone selecting is hardcoded... at least tweaktools brings it back quick enough - forgot about that tbh, sorry for the troubles!
Click to expand...
Click to collapse
I agree with your take on MyFiles, one of the first thing I did was replace it with something else(currently FX File Manager). I wasn't a big deal, I had planed on copying my few ringtones to system anyway.
while I agree that the we are more likely to see Republicans and Democrats agree on something, would still be interesting to see if this holds true. I really would not be surprised though, if older devices do get upgraded to the latest OS - that could mean larger revenues for Google. more folks would be able to use their apps, services, etc. without having to get a new device.
however, after then, they could see how slow their device is, and then they decide to upgrade. but still, worth keeping an eye on.
Google and Verizon both agreeing to do this? Hell will freeze over first.
Sent from my SCH-I510 using xda app-developers app
From my understanding of several stories posted from Android sites since KitKat was announced, It sounds like either Google is going to update phones to KitKat silently like they have been doing everything else without the help of Samsung or Verizon or perhaps we just get these features without ever actually upgrading to KitKat
Hangouts is supposed to be replacing the stock Messaging app-If Google can do that then why would they need anything from Samsung/Verizon??
http://www.androidpolice.com/2013/1...msmms-integration-video-sharing-capabilities/
http://mobilesyrup.com/2013/10/08/h...uts-will-almost-certainly-integrate-with-sms/
4.4 "Google Experience" Launcher Launcher could be released from the Play Store (which would replace touchwiz??)
http://www.androidpolice.com/2013/1...re-some-things-we-are-expecting-to-see-in-it/
The truth of the matter is this. The Motorola Droid 1, a phone I bought as a media/mp3 player for 50 bucks and fixed up, is working better than a phone I paid 300 new and had nightlies and better support. I loved my charge, the battery sucked. And the phone I use now is the Verizon note 2 and sprint note 3 as a business phone since I now work for the sprint corporation. Do I miss my charge? Yes. Do I wish it had some cyanogenmod support being a phone 1 1/2 years newer than the droid 1? yes. As soon as I can learn how to make a rom for the charge, I plan to make an ics or jb nightly that will support a wifi only support on this relic. It was my first 4g phone. I have it in my desk and feel sad since it helped me achieve so much.
asacado said:
The truth of the matter is this. The Motorola Droid 1, a phone I bought as a media/mp3 player for 50 bucks and fixed up, is working better than a phone I paid 300 new and had nightlies and better support. I loved my charge, the battery sucked. And the phone I use now is the Verizon note 2 and sprint note 3 as a business phone since I now work for the sprint corporation. Do I miss my charge? Yes. Do I wish it had some cyanogenmod support being a phone 1 1/2 years newer than the droid 1? yes. As soon as I can learn how to make a rom for the charge, I plan to make an ics or jb nightly that will support a wifi only support on this relic. It was my first 4g phone. I have it in my desk and feel sad since it helped me achieve so much.
Click to expand...
Click to collapse
That's exactly what I was thinking - even if the radios weren't released, having the phone to use over wifi would be good enough for me. I guess that's the question - would it be possible to work up a kitkat ROM that was just purely wifi?
zereoue said:
That's exactly what I was thinking - even if the radios weren't released, having the phone to use over wifi would be good enough for me. I guess that's the question - would it be possible to work up a kitkat ROM that was just purely wifi?
Click to expand...
Click to collapse
I've seen an ics rom that was floating around, but support for this phone was always limited. It came and went faster than any other phone I saw. Hell, the bionic I owned had support and nightlies all the way up to the day I got the note 2. I digress. I am looking into it as soon as I can get a linux kitchen set up.
asacado said:
I've seen an ics rom that was floating around, but support for this phone was always limited. It came and went faster than any other phone I saw. Hell, the bionic I owned had support and nightlies all the way up to the day I got the note 2. I digress. I am looking into it as soon as I can get a linux kitchen set up.
Click to expand...
Click to collapse
I am learning how to build for android. Starting with the fascinate since there is a lot of support so I can gain familiarity and then I'm going to do a build for the charge. I intend to only use it as a media device. I can't promise or guarantee anything but, I will try my best to deliver a bootable kitkat rom. This is all pretty difficult. We shall see what happens.
pyroman512 said:
I am learning how to build for android. Starting with the fascinate since there is a lot of support so I can gain familiarity and then I'm going to do a build for the charge. I intend to only use it as a media device. I can't promise or guarantee anything but, I will try my best to deliver a bootable kitkat rom. This is all pretty difficult. We shall see what happens.
Click to expand...
Click to collapse
I have a Fascinate as well, but haven't installed any of the KK offerings for it yet. I did notice that when updating the Fascinate to KK you have to flash a 4.1 or 4.2 rom first, to get the file system setup, right? Then flash the 4.4 rom. Would the steps be the same for the Charge?
zereoue said:
I have a Fascinate as well, but haven't installed any of the KK offerings for it yet. I did notice that when updating the Fascinate to KK you have to flash a 4.1 or 4.2 rom first, to get the file system setup, right? Then flash the 4.4 rom. Would the steps be the same for the Charge?
Click to expand...
Click to collapse
AFAIK you shouldn't have to flash any rom first.. I could be wrong. I don't keep up with all the fascinate development. I did flash a 4.4 rom in the past from cm10.1.
I have a build enviroment set up and I am running into problems building cm11 for the fascinate. I think by the errors that I need to increase the system partition. Because the build always fails at making the system.img. The build guides make it seem like you should run into no errors at all.
I'll start building for the charge soon. I'm too much of a noob to actually develop for it right now, but I think I can atleast boot it once I figure out how to build it.
pyroman512 said:
AFAIK you shouldn't have to flash any rom first.. I could be wrong. I don't keep up with all the fascinate development. I did flash a 4.4 rom in the past from cm10.1.
I have a build enviroment set up and I am running into problems building cm11 for the fascinate. I think by the errors that I need to increase the system partition. Because the build always fails at making the system.img. The build guides make it seem like you should run into no errors at all.
I'll start building for the charge soon. I'm too much of a noob to actually develop for it right now, but I think I can atleast boot it once I figure out how to build it.
Click to expand...
Click to collapse
not sure if I mentioned this earlier, but it could be the fact that the charge is based on RFS system (GB 2.3). I believe android went EXT4 with ICS and higher. there are some kernels that can convert the Charge to EXT4 - so not sure if that would help ya.