Samsung Galaxy S I9000

Forums › Android › Samsung Galaxy S I9000

1 | ... | 301 | 302 | 303 | 304 | 305 | 306 | 307 | 308 | 309 | 310 | 311 | ... | 427

162 posts

Master Geek

#440446 16-Feb-2011 20:26

Neets:
defragger:

Type "adb devices" when there is no $ or #. Because you are executing the "adb.exe" file here, and giving it a parameter.

So in bold is what you are typing and pressing enter.

C:\Program Files\Android\android-sdk-windows\platform-tools>adb devices
[returns device]

C:\Program Files\Android\android-sdk-windows\platform-tools>adb shell

$su

#[now you can carry on with the dmesg thing]

Yep, doing all that:

That is very strange, never had any issues running dmesg. Hardcore may have made a mistake when compiling the kernel. Are you both using 13A?

wazz

162 posts

Master Geek

#440448 16-Feb-2011 20:27

Anyway I'll flash 13A after dinner and see if it gives me any issues.

Neets

1376 posts

Uber Geek

Trusted

#440449 16-Feb-2011 20:28

wazz:
Neets:
defragger:

Type "adb devices" when there is no $ or #. Because you are executing the "adb.exe" file here, and giving it a parameter.

So in bold is what you are typing and pressing enter.

C:\Program Files\Android\android-sdk-windows\platform-tools>adb devices
[returns device]

C:\Program Files\Android\android-sdk-windows\platform-tools>adb shell

$su

#[now you can carry on with the dmesg thing]

Yep, doing all that:

That is very strange, never had any issues running dmesg. Hardcore may have made a mistake when compiling the kernel. Are you both using 13A?

Affirmative. Lets go blame him

Clearly tonight is not the night for me to fix my skin thing on my phone

Samsung Galaxy S5 SM-G900I

wazz

162 posts

Master Geek

#440460 16-Feb-2011 20:58

Neets:
Affirmative. Lets go blame him

Clearly tonight is not the night for me to fix my skin thing on my phone

And yep it is his kernel, will have to let him know.

Shrapnel

260 posts

Ultimate Geek

#440462 16-Feb-2011 21:23

Neets:
wazz:
Neets:
defragger:

Type "adb devices" when there is no $ or #. Because you are executing the "adb.exe" file here, and giving it a parameter.

So in bold is what you are typing and pressing enter.

C:\Program Files\Android\android-sdk-windows\platform-tools>adb devices
[returns device]

C:\Program Files\Android\android-sdk-windows\platform-tools>adb shell

$su

#[now you can carry on with the dmesg thing]

Yep, doing all that:

That is very strange, never had any issues running dmesg. Hardcore may have made a mistake when compiling the kernel. Are you both using 13A?

Affirmative. Lets go blame him

Clearly tonight is not the night for me to fix my skin thing on my phone

Not that I know anything about dmesg :P but I came across this on xda the (reply is by Hardcore himself):

Hi hardcore!

I'm using Doc's XWJS5 rom with your k13a kernel. And what I'm trying to achieve is to get dmesg output in adb.

I enabled Android logger in CWM, in Tweaks section. I can launch logcat and read output. dmesg isn't working.

I tried to run dmesg through busybox in adb, but still nothing happened. Even su didn't help.

Sorry to say, dmesg is disabled in the newer kernel versions, and it can't be re-enabled from CWM (only logcat can be re-enabled). Do you really need dmesg - it's probably only useful to the kernel devs.

So there's your definite answer, no dmesg on K13A

Galaxy S I9000T 8GB Kingston 8GB Class 4 Micro SD MIUI 2.3.5 V1.9.9 JL2 Modem

wazz

162 posts

Master Geek

#440469 16-Feb-2011 21:33

Shrapnel:
Not that I know anything about dmesg :P but I came across this on xda the (reply is by Hardcore himself):

Hi hardcore!

I'm using Doc's XWJS5 rom with your k13a kernel. And what I'm trying to achieve is to get dmesg output in adb.

I enabled Android logger in CWM, in Tweaks section. I can launch logcat and read output. dmesg isn't working.

I tried to run dmesg through busybox in adb, but still nothing happened. Even su didn't help.

Sorry to say, dmesg is disabled in the newer kernel versions, and it can't be re-enabled from CWM (only logcat can be re-enabled). Do you really need dmesg - it's probably only useful to the kernel devs.

So there's your definite answer, no dmesg on K13A

Hmm yeah bugger, wouldn't hurt to flash the older firmware if you're unsure anyway. Here's the link
http://forum.xda-developers.com/showpost.php?p=10056736&postcount=6706

Neets

1376 posts

Uber Geek

Trusted

#440472 16-Feb-2011 21:42

Well, that was quite the experience. Thanks wazz and defragger for your help. I'm glad it wasn't all my fault for being female and all ;-)

Sorry to have taken up plenty of real estate in the thread.

Now, if R2D2 has been watching, I hope he's got his sorted - which assume he's not on Hardcore's k13a.

Samsung Galaxy S5 SM-G900I

Sharesies

Trade NZ and US shares and funds with Sharesies (affiliate link).

defragger

268 posts

Ultimate Geek

#440481 16-Feb-2011 22:00

Neets: Well, that was quite the experience. Thanks wazz and defragger for your help. I'm glad it wasn't all my fault for being female and all ;-)

Sorry to have taken up plenty of real estate in the thread.

Now, if R2D2 has been watching, I hope he's got his sorted - which assume he's not on Hardcore's k13a.

Yeah I'm not on 13A, and it didn't work for me.

Wiping my battery stats tonight and recalibrating my battery. Hopefully gives me better battery life.

wazz

162 posts

Master Geek

#440483 16-Feb-2011 22:03

The JPY wifi driver really is shocking, left my wifi on the other night and it drained 70% overnight.

ArtooDetoo

1044 posts

Uber Geek

Trusted

#440509 16-Feb-2011 22:40

wazz: The JPY wifi driver really is shocking, left my wifi on the other night and it drained 70% overnight.

It's worth following lokhor's link and replacing the JPY wifi drivers with the JPA ones referenced. I haven't done a close measure of the comparative performance of the two wifi driver executions, but I can say that as of this moment, my SGS has been up for 21 hours and the battery monitor says there's 53% remaining charge, indicating 40+ hours on a full charge. I understand that it's not the world record or anything, but today's performance is so superior to yesterday's that it mght as well be 2 different phones we're talking about here.

So give it a whirl if you're on JPY and having battery duration issues. You have nothing to lose except a reason to whinge here about Sammy and their flawed but eminently desirable kit.

Cheers,
R2D2

Galaxy S has gone to its new owner. HTC Sensation has gone to its new
owner. Galaxy S3 has gone to its new owner. Now using Galaxy Note 3. Skipping Note 4 I think...

ArtooDetoo

1044 posts

Uber Geek

Trusted

#440512 16-Feb-2011 22:45

Neets: Well, that was quite the experience. Thanks wazz and defragger for your help. I'm glad it wasn't all my fault for being female and all ;-)

Sorry to have taken up plenty of real estate in the thread.

Now, if R2D2 has been watching, I hope he's got his sorted - which assume he's not on Hardcore's k13a.

Haven't done a SpeedMod or comparable kernel transplant as yet and I didn't really follow the train of thought behind the grep-fest. So I'll read the posts again when I'm fresh and semi-intelligent next - possibly tomorrow?

Thanks all for attempting to get the issues resolved. And especially Neets for being my Den-Mother.

Cheers,
R2D2

Galaxy S has gone to its new owner. HTC Sensation has gone to its new
owner. Galaxy S3 has gone to its new owner. Now using Galaxy Note 3. Skipping Note 4 I think...

wazz

162 posts

Master Geek

#440513 16-Feb-2011 22:46

ArtooDetoo:
wazz: The JPY wifi driver really is shocking, left my wifi on the other night and it drained 70% overnight.

It's worth following lokhor's link and replacing the JPY wifi drivers with the JPA ones referenced. I haven't done a close measure of the comparative performance of the two wifi driver executons, but I can say that as of this moment, my SGS has been up for 21 hours and the battery monitor says there's 53% remaining charge, indicating 40+ hours on a full charge. I understand that it's not the world record or anything, but today's performance is so superior to yesterday's that it mght as well be 2 different phones we're talking about here.

So give it a whirl if you're on JPY and having battery duration issues. You have nothing to lose except a reason to whinge here about Sammy and their flawed but eminently desirable kit.

Cheers,
R2D2

I replaced them a couple days ago and yeah it does make a massive difference. Suprised Samsung haven't fixed it yet, oh wait no im not.

wazz

162 posts

Master Geek

#440514 16-Feb-2011 22:48

ArtooDetoo:
Neets: Well, that was quite the experience. Thanks wazz and defragger for your help. I'm glad it wasn't all my fault for being female and all ;-)

Sorry to have taken up plenty of real estate in the thread.

Now, if R2D2 has been watching, I hope he's got his sorted - which assume he's not on Hardcore's k13a.

Haven't done a SpeedMod or comparable kernel transplant as yet and I didn't really follow the train of thought behind the grep-fest. So I'll read the posts again when I'm fresh and semi-intelligent next - possibly tomorrow?

Thanks all for attempting to get the issues resolved. And especially Neets for being my Den-Mother.

Cheers,
R2D2

Those posts were just a way to check which wifi firmware you're using, turns out hardcore has disabled dmesg anyway.

ArtooDetoo

1044 posts

Uber Geek

Trusted

#440515 16-Feb-2011 22:51

wazz:

Those posts were just a way to check which wifi firmware you're using, turns out hardcore has disabled dmesg anyway.

Aha...

Thanks for the clarification.

Cheers,
R2D2

Galaxy S has gone to its new owner. HTC Sensation has gone to its new
owner. Galaxy S3 has gone to its new owner. Now using Galaxy Note 3. Skipping Note 4 I think...

ArtooDetoo

1044 posts

Uber Geek

Trusted

#440539 17-Feb-2011 07:20

Battery update...

Hi all.

Overnight drop was 11%, with data on but wifi off. So looking good so far.

Doubt that 40 hours will be possible but 30 is a given and 36 is certainly within reach. Woohoo...

Cheers,
R2D2

Galaxy S has gone to its new owner. HTC Sensation has gone to its new
owner. Galaxy S3 has gone to its new owner. Now using Galaxy Note 3. Skipping Note 4 I think...

1 | ... | 301 | 302 | 303 | 304 | 305 | 306 | 307 | 308 | 309 | 310 | 311 | ... | 427