• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root (Port) Behold II Factory 1.6

Lets just say (and I'm assuming from previous inferences) that this was most likely a update until Google dropped the 2.0/2.1 bomb on them and they decided it was better to wait. When the BH2 came out 1.6 really hadn't been out that long, so Sammy was most likely working on this to be an update and abandoned it to pool resources for the 2.x update.

Not saying that is the truth but that's where the evidence leads me to believe.

Well I hope that's the case vs them just dropping support for the phone do to lack luster sales.
 
I think Ohgami has it right. Releasing firmware is costly for TMO because of issues with delivery/support/bricked devices etc. So it does not surprise me that they want to limit the number of releases. But I would expect the 2.1 update to be the final for this device.


Also to the guy having issues with this build, did you delete any apk's within /system/app ? I know there was a thread that discussed removing some and in actuality some will cause major problems when removed.
 
Lets just say (and I'm assuming from previous inferences) that this was most likely a update until Google dropped the 2.0/2.1 bomb on them and they decided it was better to wait. When the BH2 came out 1.6 really hadn't been out that long, so Sammy was most likely working on this to be an update and abandoned it to pool resources for the 2.x update.

Not saying that is the truth but that's where the evidence leads me to believe.

Actually, 2.0 was already out when the BH2 was released. Samsung really just dropped the ball on it.

1.5 SDK was released April 30th, 2009
1.6 SDK was released September 15th, 2009
2.0 SDK was released October 26th, 2009

Samsung Behold II was released on November 18th, 2009

I'm going to assume Samsung didn't start development until April 30th, so that means it took their dev team roughly 7 months to have a release-ready version of their Touchwiz software starting from scratch. It has now been almost 8 full months since 1.6 was released, and since 1.6 isn't vastly different from 1.5, they wouldn't be starting from scratch, so theoretically, it shouldn't take that much time to implement the changes to the Twiz package. There's no excuse for Samsung's negligence in getting a newer version out to their customers. If it wasn't for people like BH_MAN, I would have sold it and gone to a different phone by now. Thanks again BH_MAN!
 
Actually, 2.0 was already out when the BH2 was released. Samsung really just dropped the ball on it.

1.5 SDK was released April 30th, 2009
1.6 SDK was released September 15th, 2009
2.0 SDK was released October 26th, 2009

Samsung Behold II was released on November 18th, 2009

I'm going to assume Samsung didn't start development until April 30th, so that means it took their dev team roughly 7 months to have a release-ready version of their Touchwiz software starting from scratch. It has now been almost 8 full months since 1.6 was released, and since 1.6 isn't vastly different from 1.5, they wouldn't be starting from scratch, so theoretically, it shouldn't take that much time to implement the changes to the Twiz package. There's no excuse for Samsung's negligence in getting a newer version out to their customers. If it wasn't for people like BH_MAN, I would have sold it and gone to a different phone by now. Thanks again BH_MAN!

same here, I would have bought the galaxy instead because of its modding capabilities.
 
Actually the 2.0 source was never released to anyone except Motorola. Source is the code to build a ROM, while the SDK is the development kit used build apps for use on that particular version of the OS.

The 2.1 source was released to the public several days after the N1 was released in January. So Samsung is less than 5 months into development. I know everyone here has certain expectations based on BH_MAN releasing updates so quickly, but thats just not how it works in the real world. There is no way Samsung is going to release 10 versions of an update, it is just way too risky/costly (think customer support hours as a cost). This is probably why the 1.6 {it was official} update was never released. They also have an extensive QA test period, not just a few guys using the phone for a few hours. BH_MAN doesn't have a boss that will fire him if something goes wrong. Don't read this as a knock on his process, I'm just trying to explain the difference between a hacker and a real world software development cycle. FYI, I work in the financial software industry, and a typical upgrade for a client takes 18 months.

Also remember that TMO uses its own testing process and release calendar. I wouldn't expect a release of 2.1 until after the MT3G Slide is released in June.
 
Actually the 2.0 source was never released to anyone except Motorola. Source is the code to build a ROM, while the SDK is the development kit used build apps for use on that particular version of the OS.

Please note that in my original post I did specify that the release dates were for the SDK's.

The source code for Android has been available to the public since October 21st, 2008, and is updated in tandem with Google's private development. The source for 2.0 was made available on November 16th, 2009 (just a couple of weeks after the SDK). I understand the software development cycle as I'm a programmer, but Samsung really has no excuse. I can't fault TMO for it since they're not the ones developing Touchwiz.
 
Please note that in my original post I did specify that the release dates were for the SDK's.

The source code for Android has been available to the public since October 21st, 2008, and is updated in tandem with Google's private development. The source for 2.0 was made available on November 16th, 2009 (just a couple of weeks after the SDK). I understand the software development cycle as I'm a programmer, but Samsung really has no excuse. I can't fault TMO for it since they're not the ones developing Touchwiz.

Well as a programmer you obviously know that rushed code = buggy code.

Can you name one US phone that has upgraded from 1.x to 2.x? No, so its obviously not a Samsung issue, it includes Motorola and HTC (as well as Archos). The only phones that have 2.x+ have shipped with that level of the OS. I forgot to also mention that there is very little incentive for these companies to update old phones, although Samsung did generate some extra revenue from the update by including extra demo software.
 
Well as a programmer you obviously know that rushed code = buggy code.

Can you name one US phone that has upgraded from 1.x to 2.x? No, so its obviously not a Samsung issue, it includes Motorola and HTC (as well as Archos). The only phones that have 2.x+ have shipped with that level of the OS. I forgot to also mention that there is very little incentive for these companies to update old phones, although Samsung did generate some extra revenue from the update by including extra demo software.

That, I believe...why make an update for a phone that you have already gotten money for, when you can sell another phone (different model) with the update!:mad:
 
I've been pretty much lurking since my wife and I both got Behold 2's recently. I installed the factory 1.6 on mine a few days ago and my wife's last night. Great stuff. Thank you. Since you're accepting bug reports, here goes:

Google Goggles crashes after taking picture.
Barcode Scanner (by ZXing Team) causes the flash to strobe when running (might be an app issue, might be a build issue).
LCD Brightness under Display Settings crashes.

Also, I read somewhere (forgot where) that the ADB drivers do not take on 64-bit OS's after some searching for why I can't get ADB to work on my box (thank god for VMWare).

And can I just uninstall some of the bloatware with adb pulls? Or are there better ways?

1.6+ would make TeleNav kind of pointless since you can install Google Maps w/ Navi. If they get any sort of revenue from that, TMO will think twice about officially releasing anything 1.6+ on this phone (in addition to all the other reasons already provided).
 
Barcode Scanner (by ZXing Team) causes the flash to strobe when running (might be an app issue, might be a build issue

This is kind of an app issue. I know this was a problem back when I was still on the original factory 1.5 ROM. According to the release notes for the Barcode Scanner update that just came out a few days ago this is supposedly fixed, but it's still blinking the flash off and on for me (I'm using Warheads now) so it's possible that whatever method they used to fix the issue was unfixed or ineffective with 1.6. Or maybe they didn't fix it at all (I can't confirm since I'm no longer running Factory 1.5).
 
I'm trying to use ODIN to flash this image. I get an invaid image type message. I'm trying to download BH_MAN_Stock_fix.zip. Can I use this file?
 
no one running factory 1. 6 can copy the framework-res. apk, and post it here for me ?
I would really appreciate it if someone can.... :) :)
 
Love this. Swype is awesome. My only problem is screen orientation not working with google talk, messaging or web browser. Any suggestions? Settings show it is on
 
I did the whole process over again last night with same results. No screen rotation when using messaging or browser. It worked perfectly on 1.5 and I hate to go back to that. any suggestions? I did everything right so I dont know what would cause this. Settings show it on and it goes into landscape when I use youtube or play a game. Ive googled and looked through these fourms but found nothing. Please help anyone?
 
This is normal. I believe this was covered in one of the earlier posts.

Yea it was I didn't see it till after I posted. I'm installing it now. How long does it generally take my phone just says downloading and download start in ODIN. I got it to work fine with the update. First time trying a rom.
 
After trying several ROMS using the ODIN Method I attempted to go back to R11 from DOTS and now all I get is a bootloop. Can anyone tell me what happened and how I can correct this?
 
Okay Guys, It's Time For true TouchWiz 1.6.. This is Full Factory with Bloatware still installed...

A2SD Options & Install
Un-zip Playlogo & Playlogo_real to any location ( Desktop I alway do )
adb push ( a2sd_BH2 Folder Location! ) to /system/bin
a2sd_BH2.zip


BH_MAN_Stock_fix Download Here > BH_MAN_Stock_fix.zip
Mirror By
tritran18518
Mirrored Download: MEGAUPLOAD

Hello-

I've been reviewing this forum and tried following some of the links for installation instructions. Maybe I'm old, maybe I'm dense but I can't seem to get a clear answer on how to install this. If I understand correctly, the "BH_MAN_Stock_fix.zip" will upgrade my BH2 to Android 1.6, with a couple of modifications. Camera, vibration, etc fixed.

I have the ZIP file and access to either Linux or Windows XP desktops to perform the installation. I've also downloaded the SDK (Linux and Windows versions) and will follow the install instructions for the SDK. I basically need the instructions for installing this ROM to my phone.

"ODIN" comes up frequently -- not sure if that is needed since I have a Linux machine available.

I'm pretty sure I just need to use an "adb command" -- just need some help with the syntax.

If I run into major problems, can I go back to the original version of BH2?

Sorry for such a verbose post -- just want to be sure I get this correct so that I don't brick my phone. Thanks.
 
Okay. So I now figured out that these ROMs are *made* for ODIN. Took several hours, but I was able to finally get 1.6 on my BH2. I thought I bricked my phone, but I rebooted my PC and tried this ROM one more time. It seems to hang for awhile on the "system" download (progress bar stops moving) but after about five minutes it finished.

Absolutely LOVE the 1.6! I can't believe Samsung put 1.5 on there to start with -- this is so much better. Still getting used to the Swype keyboard. Thank you!! BH_MAN for this ROM.

I'm running out of memory on my phone; I take it that is what the a2sd is for?
 
I'm trying to turn on Location Services (Settings -> Phone Settings -> Use wireless networks). Whenever I tap "On" a window pops us ("Location Consent") and I click "Agree". The Window goes away and then it switches back to "Off".

Has anyone else had a problem with that? If this is not the place to report this, please let me know. Thanks.
 
Back
Top Bottom