Samsung Galaxy S II Owners Thread

Forums › Android › Samsung Galaxy S II Owners Thread

1 | ... | 234 | 235 | 236 | 237 | 238 | 239 | 240 | 241 | 242 | 243 | 244 | ... | 294

Mad Scientist
29769 posts

Uber Geek

Trusted

Lifetime subscriber

#606971 9-Apr-2012 09:32

just reporting - found a sweet spot

Omega 6 - with bloatware frozen to the bone w titanium
Siyah 3.0 + extweaks overclocked to 1.6, GPU to 400MHz and forced 2d rendering

no problems, super fluid

fingers crossed didn't jinx myself

not updating for a while now!~

gaberad

6 posts

Wannabe Geek

#607149 9-Apr-2012 18:59

Brendan:

It'd be simpler to just install a custom rom from xda over GB anyway, which have already dealt with that issue.

in that case, which roms would you recommend? I had heard of the ability to reset the flash counter, are there roms that do that automatically or something?

I was just about to install the latest official ICS rom (LP4), but I'll wait to see what you say.

Chis

99 posts

Master Geek

ID Verified

#607153 9-Apr-2012 19:08

ADB behaves different on Omega 8 or ICS in general, and seeking any advice on using it.

Under 2.3 I could type from a Windows command shell (actually Console, a friendly command line shell replacement):
adb shell
ls
sd /sdcard
ls

I'd get two lists of files that looked normal.

Now with Omega 8, I get the following:
adb shell
root@android:/ # ls
ls
←[1;34macct←[0m                  ←[1;32minit←[0m                  ←[1;34mres←[0m
←[1;34mcache←[0m                 ←[0;0minit.goldfish.rc←[0m      ←[1;34msbin←[0m
←[1;34mconfig←[0m                ←[1;32minit.rc←[0m               ←[1;36msdcard←[0m
←[1;34mcustomkernel←[0m          ←[1;32minit.smdk4210.rc←[0m      ←[1;34msys←[0m
←[1;36md←[0m                     ←[0;0minit.smdk4210.usb.rc←[0m ←[1;34msystem←[0m
←[1;34mdata←[0m                  ←[1;34mlib←[0m                   ←[1;34mtmp←[0m
←[0;0mdefault.prop←[0m          ←[1;32mlpm.rc←[0m                ←[0;0mueventd.goldfish.rc←[0m
←[1;34mdev←[0m                   ←[1;34mmnt←[0m                   ←[0;0mueventd.rc←[0m
←[1;34mefs←[0m                   ←[1;34mpreload←[0m               ←[0;0mueventd.smdk4210.rc←[0m
←[1;36metc←[0m                   ←[1;34mproc←[0m                  ←[1;34mvendor←[0m
←[1;32mfota.rc←[0m               ←[1;32mrecovery.rc←[0m
root@android:/ # cd /sdcard
cd /sdcard
root@android:/sdcard # ls
ls
ls: can't open '.': Value too large for defined data type
1|root@android:/sdcard #

For the root directory listing it seems some terminal type is expected. Not sure what the sdcard listing is all about.

Any help much appreciated, I've become rather used to using a shell to get around my S2.

d3Xt3r

688 posts

Ultimate Geek

Trusted

#607224 9-Apr-2012 22:46

Chis: ADB behaves different on Omega 8 or ICS in general, and seeking any advice on using it.

Under 2.3 I could type from a Windows command shell (actually Console, a friendly command line shell replacement):
adb shell
ls
sd /sdcard
ls

I'd get two lists of files that looked normal.

Now with Omega 8, I get the following:
adb shell
root@android:/ # ls
ls
←[1;34macct←[0m                  ←[1;32minit←[0m                  ←[1;34mres←[0m
←[1;34mcache←[0m                 ←[0;0minit.goldfish.rc←[0m      ←[1;34msbin←[0m
←[1;34mconfig←[0m                ←[1;32minit.rc←[0m               ←[1;36msdcard←[0m
←[1;34mcustomkernel←[0m          ←[1;32minit.smdk4210.rc←[0m      ←[1;34msys←[0m
←[1;36md←[0m                     ←[0;0minit.smdk4210.usb.rc←[0m ←[1;34msystem←[0m
←[1;34mdata←[0m                  ←[1;34mlib←[0m                   ←[1;34mtmp←[0m
←[0;0mdefault.prop←[0m          ←[1;32mlpm.rc←[0m                ←[0;0mueventd.goldfish.rc←[0m
←[1;34mdev←[0m                   ←[1;34mmnt←[0m                   ←[0;0mueventd.rc←[0m
←[1;34mefs←[0m                   ←[1;34mpreload←[0m               ←[0;0mueventd.smdk4210.rc←[0m
←[1;36metc←[0m                   ←[1;34mproc←[0m                  ←[1;34mvendor←[0m
←[1;32mfota.rc←[0m               ←[1;32mrecovery.rc←[0m
root@android:/ # cd /sdcard
cd /sdcard
root@android:/sdcard # ls
ls
ls: can't open '.': Value too large for defined data type
1|root@android:/sdcard #

For the root directory listing it seems some terminal type is expected. Not sure what the sdcard listing is all about.

Any help much appreciated, I've become rather used to using a shell to get around my S2.

1. What you're seeing there are the ANSI color codes, which is actually cool, provided you use a terminal app that supports it. Most Linux and Mac based terminals support it, not sure about windows. Perhaps you could use Cygwin as a shell inside Console?

2. Regarding your second case, it's a common user error: the sdcard is located in /mnt/sdcard , and your external would be /mnt/sdcard/external_sd. Now /sdcard should actually link to /mnt/sdcard, but for some reason it looks like your's isn't.
Is your sdcard mounted? If it is, and you're still getting the error, then you could try fixing it by issuing "ln -s /mnt/sdcard" in the root dir.

networkn

Networkn
32358 posts

Uber Geek

ID Verified

Trusted

Lifetime subscriber

#607338 10-Apr-2012 11:10

Are there no ICS Launchers which do what the GB Launchers do and display the number of missed calls and unread messages on the icon in the dock? Apex and Nova don't appear to, and it's annoying. I guess I could put SPB Shell 3D back on...

nofam

1094 posts

Uber Geek

#607355 10-Apr-2012 11:32

networkn: Are there no ICS Launchers which do what the GB Launchers do and display the number of missed calls and unread messages on the icon in the dock? Apex and Nova don't appear to, and it's annoying. I guess I could put SPB Shell 3D back on...

Post it as a suggestion on the Apex thread at XDA? The dev seems quite approachable. . . .

Chis

99 posts

Master Geek

ID Verified

#607507 10-Apr-2012 17:12

d3Xt3r:

ls: can't open '.': Value too large for defined data type
1|root@android:/sdcard #

2. Regarding your second case, it's a common user error: the sdcard is located in /mnt/sdcard , and your external would be /mnt/sdcard/external_sd. Now /sdcard should actually link to /mnt/sdcard, but for some reason it looks like your's isn't.
Is your sdcard mounted? If it is, and you're still getting the error, then you could try fixing it by issuing "ln -s /mnt/sdcard" in the root dir.

Thanks on the ANSI colour find, I suspected something like that.

On the SDCARD, I think it's the number of files that causes the problem. sdcard seems to be mounted correctly as I can ls on a subset of files, but the full list of files gives the error.

Perhaps the Omega developer left his prefered setup on the ROM by mistake. I'll put v9 on tonight and see if anything changes.

Quic Broadband

Move to New Zealand's best fibre broadband service (affiliate link). Free setup code: R587125ERQ6VE. Note that to use Quic Broadband you must be comfortable with configuring your own router.

d3Xt3r

688 posts

Ultimate Geek

Trusted

#607525 10-Apr-2012 18:04

Chis:
d3Xt3r:

ls: can't open '.': Value too large for defined data type
1|root@android:/sdcard #

2. Regarding your second case, it's a common user error: the sdcard is located in /mnt/sdcard , and your external would be /mnt/sdcard/external_sd. Now /sdcard should actually link to /mnt/sdcard, but for some reason it looks like your's isn't.
Is your sdcard mounted? If it is, and you're still getting the error, then you could try fixing it by issuing "ln -s /mnt/sdcard" in the root dir.

Thanks on the ANSI colour find, I suspected something like that.

On the SDCARD, I think it's the number of files that causes the problem. sdcard seems to be mounted correctly as I can ls on a subset of files, but the full list of files gives the error.

Perhaps the Omega developer left his prefered setup on the ROM by mistake. I'll put v9 on tonight and see if anything changes.

Well, unless you have more than 16,384 files in the root folder, I don't see that being an issue. (65,536 for 8.3 filenames).

I'm on Omega 9 right now, having no such issues though. What version of BusyBox are you using? I'm on v1.19.4-cm9. IIRC, there was a bug in one of the versions of busybox which showed this error.

d3Xt3r

688 posts

Ultimate Geek

Trusted

#607566 10-Apr-2012 20:14

gaberad:

in that case, which roms would you recommend? I had heard of the ability to reset the flash counter, are there roms that do that automatically or something?

I was just about to install the latest official ICS rom (LP4), but I'll wait to see what you say.

Omega or WanamLite. For resetting the flash counter, you need to use a USB jig or an app called "Triangle Away". Or you can avoid incrementing the counter altogether, by flashing the ROM using Mobile Odin. Of course, you'll have to root your phone first, and if you want to root it without increasing the flash counter, you'll have to use the zergrush exploit. (DarkTremor has written a script for it.)

Chis

99 posts

Master Geek

ID Verified

#607574 10-Apr-2012 20:40

d3Xt3r:
Chis:
d3Xt3r:

ls: can't open '.': Value too large for defined data type
1|root@android:/sdcard #

2. Regarding your second case, it's a common user error: the sdcard is located in /mnt/sdcard , and your external would be /mnt/sdcard/external_sd. Now /sdcard should actually link to /mnt/sdcard, but for some reason it looks like your's isn't.
Is your sdcard mounted? If it is, and you're still getting the error, then you could try fixing it by issuing "ln -s /mnt/sdcard" in the root dir.

Thanks on the ANSI colour find, I suspected something like that.

On the SDCARD, I think it's the number of files that causes the problem. sdcard seems to be mounted correctly as I can ls on a subset of files, but the full list of files gives the error.

Perhaps the Omega developer left his prefered setup on the ROM by mistake. I'll put v9 on tonight and see if anything changes.

Well, unless you have more than 16,384 files in the root folder, I don't see that being an issue. (65,536 for 8.3 filenames).

I'm on Omega 9 right now, having no such issues though. What version of BusyBox are you using? I'm on v1.19.4-cm9. IIRC, there was a bug in one of the versions of busybox which showed this error.

BusyBox v1.19.3 (2011-11-22 01:37:10 MST)
I assume that's what I got with Omega.

d3Xt3r

688 posts

Ultimate Geek

Trusted

#607580 10-Apr-2012 20:53

Chis:
BusyBox v1.19.3 (2011-11-22 01:37:10 MST)
I assume that's what I got with Omega.

Hmm, I'm not sure how I got the newer busybox.. I remember it was included with something, not sure what. Anyways, I'm uploading it here for your convenience: http://dl.dropbox.com/u/8141638/busybox

Just replace your existing binary in /system/xbin

Foo

522 posts

Ultimate Geek

#607582 10-Apr-2012 20:54

My new battery arrived today from Adriatica, just running down the old battery before I put the new one in. I'll let all know how it performs.

Chis

99 posts

Master Geek

ID Verified

#607623 10-Apr-2012 22:30

d3Xt3r:
Chis:
BusyBox v1.19.3 (2011-11-22 01:37:10 MST)
I assume that's what I got with Omega.

Hmm, I'm not sure how I got the newer busybox.. I remember it was included with something, not sure what. Anyways, I'm uploading it here for your convenience: http://dl.dropbox.com/u/8141638/busybox

Just replace your existing binary in /system/xbin

Thanks, but is there any chance what you uploaded was the 1.19.3 version?
The size is 1116332 bytes, exactly the same as my old version, and when I execute it:
/system/xbin/busybox --help
BusyBox v1.19.3 (2011-11-22 01:37:10 MST) multi-call binary.

Brendan

716 posts

Ultimate Geek

Trusted

#607643 11-Apr-2012 00:57

gaberad:
Brendan:

It'd be simpler to just install a custom rom from xda over GB anyway, which have already dealt with that issue.

in that case, which roms would you recommend? I had heard of the ability to reset the flash counter, are there roms that do that automatically or something?

I was just about to install the latest official ICS rom (LP4), but I'll wait to see what you say.

I'd reccomend the latest mega or wanam ics roms. They have already been fixed to stop the flash counter being changed.

The problem is the new bootloader that comes with the official ICS has been changed by samsung so the flash counter in it cannot be wiped with the usb jig etc. So we have to install the old bootloader to get that back if you want the yellow triangle gone or to return it under warranty.

There are official smasung releases that have also had the bootloader removed in one of the xda threads.

Kelem

188 posts

Master Geek

#607690 11-Apr-2012 09:58

Gone back to 2.3.6 using CheckROM RevoHD V6, much easier to use and is super fast, no issues, will wait tfor a while to go to ICS, if i keep my droid stuff, got a hankering to go to the darkside (IOS) for a play

1 | ... | 234 | 235 | 236 | 237 | 238 | 239 | 240 | 241 | 242 | 243 | 244 | ... | 294