[Official] Samsung posts Gingerbread source code for the I9000

Toggle sidebar Toggle sidebar
I bet someone has a crappy build ready by tomorrow. I'm more excited about the improvements they might be able to make to CM7 with this.
 
The hints are dropping quite strongly in the ROM threads. sometimes by the LACK of posting on the part of the chefs... I think they all got their hands on it already and are building 2.3 versions. Good for everyone there.

I hope the CM guys can do something with it too, but I think it is not going to offer them much unless the drivers are open.
 
I hate to admit it, but I'll be/am (even more) glued to the boards for the next week(ish). lol
 
konazxiii said:
I hate to admit it, but I'll be/am (even more) glued to the boards for the next week(ish). lol
Click to expand...

Let's see how quickly we can crash XDA ;).

Whenever we get a kernel released, I'll try to package together a build to hold everyone over until the devs get their stuff built (keyword being try lol).
 
  • Like
Reactions: konazxiii
Yeah, my days of iffy functionality are over. It will be nice for the devs to have it however, to start polishing their new ROMs.
 
Beta 2 out. Everything seems to be fixed other than reorientation. Home button fix requires a flash of another file, I think it's a ROM issue.
 
Now that there is a working Recovery, this is much more attractive. I will probably flash today :).
 
loraque said:
Now that there is a working Recovery, this is much more attractive. I will probably flash today :).
Click to expand...

Let us know how it works. If I have time later I'll work on packaging everything together with the button fix.

Sent from my SGH-I897 using Tapatalk
 
Up and running. The process is not as easy as normal. This is the first time I have had 4/5 of the ODIN lines filled up with files, and the post install process has several steps (reoriented kernel, modem, home button fix, etc). I can't recommend it for anyone but an experienced flasher, and please note that you do flash a new bootloader, so there is the potential of a brick if the USB cord pops out at the wrong time. We all know how that COULD happen on our phone.

The ROM I loaded was Juwe's i9000 [ROM][20/4/11] Juwe's Smart Edition *v4.1 XWJVB Based on official 2.3.3* | Domination - xda-developers . White on black base theme is not my favorite, but it does feel fast. Just ran the restore operation and will test out things at lunch.

EDIT- It is noticeably faster, and there is no lagfix installed. Yet. May not be able to call EXT4 conversion, when we can do it on ours, a "lag" fix anymore.
 
Last edited:
loraque said:
Up and running. The process is not as easy as normal. This is the first time I have had 4/5 of the ODIN lines filled up with files, and the post install process has several steps (reoriented kernel, modem, home button fix, etc). I can't recommend it for anyone but an experienced flasher, and please note that you do flash a new bootloader, so there is the potential of a brick if the USB cord pops out at the wrong time. We all know how that COULD happen on our phone.

The ROM I loaded was Juwe's i9000 [ROM][20/4/11] Juwe's Smart Edition *v4.1 XWJVB Based on official 2.3.3* | Domination - xda-developers . White on black base theme is not my favorite, but it does feel fast. Just ran the restore operation and will test out things at lunch.
Click to expand...

Thanks. I read on the thread that someones tried it without the bootloader and it worked fine, so that might be avoidable.

EDIT- It is noticeably faster, and there is no lagfix installed. Yet. May not be able to call EXT4 conversion, when we can do it on ours, a "lag" fix anymore.
Click to expand...

We can call it a benchmark fix, since that's all it'll be good for :p
 
I did install the Talon 0.1.3 kernel that has EXT4 support, and installed the EXT4 app the i9000 guys use to convert the filesystem. Did the conversion, and MAYBE things smoothed out a little in the screen transition, but the difference is far less noticeable than it was on 2.2.

Seeing the same battery drain from Google Maps/Latitude that I did with CM7. Something about it is keeping Maps open and consuming 16-20% battery. Easy to work-around, but a little annoying.
 
Use care with Chainfire's EXT4 conversion app.

I've found that the OSs internal master clear (Settings> Privacy) does not play well with CWM3 & ext4. I'm talking about a wacked out recovery failure that includes pushing itself back to 3e recovery (after multiple red and yellow error messages) with no button presses working in the 3e menu.

Master clear through CWM3 seems not to fully format, or at least not the internal SD.

I found I'd have to revert to back to RFS then master clear from both places to get it good and clean, safely.

That was before going back to xcals kernel. lol
 
Last edited:
One thing I have found for those 2.3.3 users here. I finally identified my battery drain (most of it at least) in 2.3.3. In CM and every Samsung 2.3.3 ROM I had abnormal battery drain, turns out it was the geolocation option in Beautiful Widgets that was causing it. I had previously figured out it was something with GPS as when I would turn it off, the problem went away.

I mistakenly blamed Google Latitude, but have now confirmed that the drain is gone by turning off geolocation. If you use beautiful Widgets in GB, make sure you try turning geolocation off and seeing if it helps.
 
  • Like
Reactions: konazxiii
Thanks for the tip- I just turned mine off. I've been using Fancy Widget more lately anyway. We'll see how it goes.

Like you, I've noticed the GB ROMs/kernels do eat more battery than JS7/8.
 
You must log in or register to reply here.

Latest posts

Trending Posts

Members online

Total: 3,546 (members: 7, guests: 3,539)

Forum statistics

Threads
963,661
Messages
6,993,805
Members
3,165,099
Latest member
Luis Gonzalez

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom