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

Root ( Port ) Galaxy 1.6 on the Behold 2 Final

Oh I see. Well, I'm not looking to OVERclock it. Just set it to it's maximum normal clocking. Underclocking is good for battery yes, which is why I'm going to save that overclock app to underclock it if I need to save battery. Otherwise, I'm going to leave it at 528.
 
paul89 said:
I know the difference between RAM and ROM, RAM is for loading up the systems apps and the system itself, while ROM is READ-ONLY-MEMORY, this is where the systems files are storied, ROM can only be read and not written to while the phone is in use. Download the app system monitor from the market, it once again confirms that this phone has only 220mb of RAM :( I also downloaded (free memory app too, and it also shows 220 MB Ram :(

Now I could be completely wrong because every app I have used says memory and it only says memory, it doesn't say whether its RAM or ROM

BH_MAN can you confirm whether its talking about RAM or ROM? NVM the app Free Memory's icon says RAM on it!
Click to expand...

It's likely because the system permenatly allocates a chunk of ram for the OS only. You can tell because 220 is not divisible by 16. All ram is divisible by 16. Blame binary for this weirdness. 320 is divisible by 16 though. With the crazy stuff Samsung has done with this phone be it the multiple partitions or the 40mb device management file I wouldn't be surprised if they didn't do this as well. Playstation 3 does this as well.
 
raiden89 said:
Wow. Worked like a charm. I just downloaded it, opened the widget, set the clock and removed the widget. Will it stay that way or do I have to open the widget and set the clock with every boot? I'd rather have as least widgets as possible.
Click to expand...

Try going into the option menu of the widget and setting it in there to work on boot. I don't think it will work without the widget but I might be wrong. The thing is the widget tells the phone to downclock when it's not being used and to overclock when it's active so you don't get to screwed on battery consumption.

Spiz did you turn on usb debugging?
 
spiz said:
Cool thanks. It says I need root when using Overclock Widget. Just installing this ROM means that I'm rooted right?

Edit: Something's wrong when I attempt to use Overclock Widget. It's going into SU Request and just hanging up. Is there something I need to do to ensure I'm rooted other than installing this rom?
Click to expand...

yes the rom automatically has root, but you need to allow apps individually to have root access, root doesn't function that well with the 1.6 builds, so reboot phone and try again, or if you haven't yet enabled root, then go to the terminal emulator app that came with the phone and type su (enter) this will enable root on your phone!
 
psychoace said:
Try going into the option menu of the widget and setting it in there to work on boot. I don't think it will work without the widget but I might be wrong. The thing is the widget tells the phone to downclock when it's not being used and to overclock when it's active so you don't get to screwed on battery consumption.

Spiz did you turn on usb debugging?
Click to expand...

Yeah USB debugging is on. I'm gonna try to work on paul's tip above this post.
 
paul89 said:
yes the rom automatically has root, but you need to allow apps individually to have root access, root doesn't function that well with the 1.6 builds, so reboot phone and try again, or if you haven't yet enabled root, then go to the terminal emulator app that came with the phone and type su (enter) this will enable root on your phone!
Click to expand...

Ok I did that and then selected "Always Allow." Was that correct? Now it just says:

# export PATH=/data/local/bin:$PATH
#su#

Look good?

EDIT: It's clearly working now since Overclock Widget now works.

So anyone that's using the widget... it says 528 on the widget. Does that mean its already set to 528? Or do I need to click the widget and manually adjust something?
 
spiz said:
Ok I did that and then selected "Always Allow." Was that correct? Now it just says:

# export PATH=/data/local/bin:$PATH
#su#

Look good?

EDIT: It's clearly working now since Overclock Widget now works.

So anyone that's using the widget... it says 528 on the widget. Does that mean its already set to 528? Or do I need to click the widget and manually adjust something?
Click to expand...

yes always choose "always allow", click on the widget to easily adjust the settings, when its first started it should show a screen to choose you phone, choose the one that says automatically detect speeds
 
paul89 said:
yes always choose "always allow", click on the widget to easily adjust the settings, when its first started it should show a screen to choose you phone, choose the one that says automatically detect speeds
Click to expand...

Should I set the Min and the Max to 528?
 
spiz said:
Should I set the Min and the Max to 528?
Click to expand...

I set it Max 528 and min 480, also look into the profiles tab, you can set those for like charging, slepp, ect. also make sure you have the check mark next to set on boot checked, and one last thing, remember to exclude fom being killed by your task killer, assuming you are using one! Goodnight lol, its 3:22 a.m. here!
 
paul89 said:
I set it Max 528 and min 480, also look into the profiles tab, you can set those for like charging, slepp, ect. also make sure you have the check mark next to set on boot checked, and one last thing, remember to exclude fom being killed by your task killer, assuming you are using one! Goodnight lol, its 3:22 a.m. here!
Click to expand...

Heh thanks for the tips man. I think I'm set now... and yeah, I'm off to bed too. These stupid phones are addicting to mess with. Later!
 
spiz said:
Hey BH_MAN... using your R6 now and everything's great except Swype doesn't work again. It was working fine in R4... is anything different that's causing it to not work and is there a fix I can do?
Click to expand...

are you using the version from the beta test? that didnt work for me either, but it doesnt matter cause i guess there's a set amount of times you can download it... oops =x but yeah i use the version you can just download from the first like you get after googling "Swype for HVGA Devices - *updated*"
that version worked fine for me. im still on r4
 
in Terminal type ( Case sensitive )

su
cd /system/lib
rm -r libSwypeCore.so
exit
exit
Click to expand...
Then Reboot...
I'm using my own swype & keep leaving the lib in there, Sorry about that... That will fix it from FC's

P.s.

I was able to Flash a Recovery to the Phone Last night... It didn't Boot! But I now know it's Possible to do it :D
 
WurrzMiKey said:
are you using the version from the beta test? that didnt work for me either, but it doesnt matter cause i guess there's a set amount of times you can download it... oops =x but yeah i use the version you can just download from the first like you get after googling "Swype for HVGA Devices - *updated*"
that version worked fine for me. im still on r4
Click to expand...


Worked on R4 and R5 but with R6 it doesn't :confused: The official Beta is closed. so I am not sure where to find another version of Swype that may be newer and still work.

edit: Using this version Swype-SwypeReference-HVGA-trial-release.1.16.12.5228.219.apk
 
BH_MAN said:
in Terminal type ( Case sensitive )

Then Reboot...
I'm using my own swype & keep leaving the lib in there, Sorry about that... That will fix it from FC's

su
cd /system/lib
rm -r libSwypeCore.so
exit
exit
Click to expand...

P.s.

I was able to Flash a Recovery to the Phone Last night... It didn't Boot! But I now know it's Possible to do it :D
Click to expand...


Regarding Swype FC issue's Guys!
 
mmandros said:
Worked on R4 and R5 but with R6 it doesn't :confused: The official Beta is closed. so I am not sure where to find another version of Swype that may be newer and still work.

edit: Using this version Swype-SwypeReference-HVGA-trial-release.1.16.12.5228.219.apk
Click to expand...


I'm using SlideIT keyboard. It is the same thing just like Swype. Swype also didn't work on my phone.
 
paul89 said:
4 dollars :eek:
But believe me its worth it, look into the free version first and get a feel for it, its a little confusing at first but the features it has is amazing, it not only backs up your apps from the market, but backs up literally everything except the rom itself lol, give it a try! ;)
Click to expand...

Only thing it doesn't back up is your call logs and text messages, so I use My Backup pro for that.
 
BH_Man... I just extracted the factoryrfs.rfs file from the Spica Android 2.1 firmware and now have a system dump of that. ** I should mention that extracting RFS files is a pain in the butt ** I know that once they got their system upgraded to Android 2.1 they received the same Camera that was stock on the Behold2. If you want I can upload the system dump if you want to look at installing the camera or what not.

So far I tried the most primitive way of getting it installed (I knew it wasn't going to work) through Astro. However I might continue to play as the worse outcome (from previously trying with the old BH2 camera apk is a bootloop).

Here is a link to the Spica Android 2.1 System Dump: 4shared.com - online file sharing and storage - download System_DUMP_SPICA_ANDROID21.zip

Edit:
Code: 
\tools>adb install SamsungCamera.
apk
1156 KB/s (5109505 bytes in 4.313s)
        pkg: /data/local/tmp/SamsungCamera.apk
Failure [INSTALL_FAILED_OLDER_SDK]
Humm the SamsungCamera.apk from the Spica might not work either.

Edit2: Tried to install it via my Android 2.1 AVD (Android Virtual Device) and the apk actually installs... when I try to load it FC though.
**Good sign for when we get a 2.1 Port I assume**

Edit3: Tried modifying the build.prop to change SDK=7 in order to loose the older SDK error. Now I get another error via adb install...
Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE]
 
Bh_man could you check the new firmware again? Because I'm leaking battry like no tomorrow. Unplug it this mornimg when I went to work. its almist lunch time and I'm down yo 75% wiyhout even touching it. Only to press power to seevthe clock. No wifi, bt, 3g, gps. Running gde and weather app.
 
So... with R6, I have nothing installed on my phone. Have about 8 native apps, No Market, No youtube, no google apps whatsoever, and I cant get into sync settings, along with other stuff. Tried reinstalling twice, and tried a factory reset after install, and nothing seems to work on this rom. anyone else have this problem??
 
aznknightz17 said:
Bh_man could you check the new firmware again? Because I'm leaking battry like no tomorrow. Unplug it this mornimg when I went to work. its almist lunch time and I'm down yo 75% wiyhout even touching it. Only to press power to seevthe clock. No wifi, bt, 3g, gps. Running gde and weather app.
Click to expand...

Um? Mine is Fine & Yes it the New Build...

@ Everyone
Guys... Please Keep this Thread Clean! It's getting way over posted with Help & Off topic stuff...
 
Mastermind278 said:
BH_Man... I just extracted the factoryrfs.rfs file from the Spica Android 2.1 firmware and now have a system dump of that. ** I should mention that extracting RFS files is a pain in the butt ** I know that once they got their system upgraded to Android 2.1 they received the same Camera that was stock on the Behold2. If you want I can upload the system dump if you want to look at installing the camera or what not.

So far I tried the most primitive way of getting it installed (I knew it wasn't going to work) through Astro. However I might continue to play as the worse outcome (from previously trying with the old BH2 camera apk is a bootloop).

Here is a link to the Spica Android 2.1 System Dump: 4shared.com - online file sharing and storage - download System_DUMP_SPICA_ANDROID21.zip

Edit:
Code: 
\tools>adb install SamsungCamera.
apk
1156 KB/s (5109505 bytes in 4.313s)
        pkg: /data/local/tmp/SamsungCamera.apk
Failure [INSTALL_FAILED_OLDER_SDK]
Humm the SamsungCamera.apk from the Spica might not work either.

Edit2: Tried to install it via my Android 2.1 AVD (Android Virtual Device) and the apk actually installs... when I try to load it FC though.
**Good sign for when we get a 2.1 Port I assume**
Click to expand...

Try installin the apps with Root Explorer,its like Astro but let u set permissions,sometimes u need to set permision to "write" and "execute" for them to install or try puttin them in /system/app folder and not instaling them bet rebooting the phone instead,sometimes this is only method that works for some dump apps.
 
BH_MAN said:
in Terminal type ( Case sensitive )

Then Reboot...
I'm using my own swype & keep leaving the lib in there, Sorry about that... That will fix it from FC's

P.s.

I was able to Flash a Recovery to the Phone Last night... It didn't Boot! But I now know it's Possible to do it :D
Click to expand...

Cool thanks for the tip. Worked perfect!

And to those who asked, yes I am using the downloaded version of Swype, not the official Beta release from Swype.

Thanks again BH_MAN! I'm pretty much useless without Swype on these tap-n-pray phones. :)



Edit: BH_MAN: You mentioned that you're using your own Swype. Is that something you can include in your future roms to avoid this? I assume it's already "included" but is there a way we can just use yours? Assuming you don't mind. :)
 
You must log in or register to reply here.
Back
Top Bottom