yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] rschenck:
What is your basis for assuming the battery drain is due to the modem?

Bugs in JVO? What bugs?
[Galaxy S I9000 Android Development] Laum:
Yeah I know that latitude is a battery drain, but I'm pretty sure it drains too much battery ONLY when the modem is bugging and the phone cant receive data properly (ofc it's sort of a problem with latitude/maps too). With Samsung roms the data network was working great and I had rarely problems. The phone has great signal here in Helsinki, Finland all the time, but somehow when I'm moving and the phone has to switch between cell towers, the data connection just freezes. I can see the upload arrow flashing, but no data is arriving. Usually it corrects itself after waiting a minute or two, but a few times I have had to reboot the phone. If I try to use flight mode, the power button menu switch just stays grey and theres no way to turn the modem back on.

I try to get some logs next time it happens.
[Galaxy S I9000 Android Development] a_ballads:
If you haven't been able to fix it yet, it may be your SMSC (messaging center number). It happened to me after flashing the previous nightly.
[Galaxy S I9000 Android Development] Laum:
Well ofc it can be a CM7 problem, but I was just guessing that maybe JVO modem and my (virtual) operator Saunalahti here in Finland just can't co-operate very good.

Well enough of guessing (I guess :p) and I just try other modems and we'll see if the same data problem persists.
[Galaxy S I9000 Android Development] edgardurao:
Radio dumps

Hello, noticed a great number of files in my sd card, related to radio.

Is this to be used by something or to help in anything?

Ex: radio_dump_20110510154807.bin - 37mb
[Galaxy S I9000 Android Development] FadeFx:
These files are related to radio crashes, if you don't want to file a bug or do some debugging by yourself you can safely remove them.

----------------------------------------

tapatalked
[Galaxy S I9000 Android Development] josteink:
I'm pretty sure you can delete them. We've still had no explanation of why they're there and what they're good for ;)
[Galaxy S I9000 Android Development] FadeFx:
if cyanogenmod is not responsible for those dumps, the modem firmware most likely does them automaticaly on crash for debugging use. for sure they are memory dumps when the modem crashes and requests pin entry.
[Galaxy S I9000 Android Development] Laum:
I found two of those from yesterday created when I was going home from work. The phone didn't definitely ask for a pin code and I didn't even notice a possible reboot.

In total there were 5 dumps created in 5 previous days.
[Galaxy S I9000 Android Development] rschenck:
Are these in a folder on the Ext SD or just dropped into the root Ext SD directory?

EDIT NVM< found them in the main SD card. My bad. I have 7 in there, all are 37MB except for one, which is just 7 MB.

I have never had my phone ask for a PIN as I do not have a PIN set...however I have gotten a number of "Connection Reset by Peer" while using WiFi...could that be what triggered these?
[Galaxy S I9000 Android Development] Joans:
I'm using the stock voltages. Been having them for ages, whichever kernel I use.
[Galaxy S I9000 Android Development] lohho:
Could specify when the reboot happened(on high cpu usage, or on idle,- which programm) and if it was a soft reboot(only "gui restart") or hard reboot (complete reboot).
[Galaxy S I9000 Android Development] Joans:
It's always idle, sometimes it just does a quick reboot, I see the boot animation, then I'm back at the lockscreen, it only takes 5, maybe 10 seconds (not sure if that's what you mean by a soft reboot)?

The problem is sometimes it bootloops until I pull the battery or long press the power button, if it does that while it's in my pocket and I don't notice, then there goes all my battery life.

Edit - I've been keeping an eye on this issue
[Galaxy S I9000 Android Development] toddmworth:
Good call, and thanks. I'm not OC or UV'd, widgetlocker is not installed, but I do have the transparent sliders morph, and volume rocker music controls and a few other tweaks going on I think... I'll experiment and report back if I find something interesting

Heh... LNoD. LOL :D
[Galaxy S I9000 Android Development] atinm:
I thought I should second this - pawitp is the de-facto I9000 maintainer for CM7 now since the rest of us seem to be more concentrated on I9100. He is doing all the heavy lifting now - and he is much respected within the team, of which he is now a serious contributing member. Kang builds from him should be understood to be coming from me or codeworkx too. Bugs are all his though ;-)
[Galaxy S I9000 Android Development] olus:
yeaah.. its great.. pawitp is our last samurai ;)

@samsung

dont give him a sgs2!
[Galaxy S I9000 Android Development] mobidzid:
Well said. As much as I admire rschenck's work here I disagree with him on that. Kang build from pawitp IS THE official nightly for me now when buildbot is down. We need this other way of delivery of fixes as the situation is not ordinary.

Please note I do not encourage any one else to post their rouge builds here. I personally will not dare to install them.

@pawitp: great work! At last a CM7 stock with led-notif and some fixes for really important things, like Android Bug and SoDs. I'm running it since yesterday and have only positive experience so far. Perhaps the only minor thing is a bit slow reaction to pushing home/power when waking the phone up, like there is half-a-second lag.

EDIT: one more thing - video recorded using front facing camera is screwed. Means probably can't be used for video-conferencing.
[Galaxy S I9000 Android Development] rschenck:
Thanks for the clarification Atinm, that is just what I was hoping for...and thanks for your previous work.

So everybody hail new king in town?

In the tradition of the Bastard Nightly, I suppose this is Pawprint 105 then?

Oh, and fwiw, I am STILL opposed to double standards, "giving respect" and right-by-commit hierarchies. I also feel (as Paw apparently does too as he apologized for being bad with people) this whole thing was handled totally backassward, but I am glad we have things officially sorted.

Oh, and I would expect that Pawitp's builds will be the ONLY Kangs posted in main thread, as they are now official. All friends again? Thank you and carry on.
[Galaxy S I9000 Android Development] atinm:
I should add that pawitp works closely with us - he is on irc with us all day, so nothing is going in that we don't really know about. And we appreciate the help!
[Galaxy S I9000 Android Development] rschenck:
Well, he is NOW. Before he was just SAYING he was official. How many Devs have you known to do THAT in forums and then go tits over teacups when the grownups return?

Law and order, every time..that's me.
[Galaxy S I9000 Android Development] atinm:
I saw that he was going to post a kang build, but didn't have time to post here to make sure it was "respected" as a CM7 team build - we invited him into the developer channel after one too many good review requests on github and gerrit. I am most probably not going to be coming back to aries, I lost my Captivate to my wife so until the S2 comes to AT&T and she takes that (soon we hope), my only phone is the S2. And thanks for looking out for the channel - it was my mistake, you were doing what I had set the tone for: namely, NO UNOFFICIAL KANG BUILDS.
[Galaxy S I9000 Android Development] pawitp:
Samsung didn't support video recording with FFC in the stock camera app so there's a bug in Samsung's libcamera.so which prevents it from working. As for video conferencing, that will work.
[Galaxy S I9000 Android Development] krarvind:
Check my signature on tips of how to extract stock kernel, the last item on my signature. I have done it before but I don't have a copy of it now.
[Galaxy S I9000 Android Development] DerTeufel1980:
are you using neo kernel, as your sig is telling? if so, this is the reason for the screwed ffc.

edit: ok, did not see the second page ;)
[Galaxy S I9000 Android Development] hassaan123:
Hello plz help me with few q.

1. The cm7 flash package at first post, does that have its own kernel included or we need to flash the kernel separate?

2. Which kernel is most stable to use with cm7?

I am new to galaxy S , i hope you wont mind my noob questions

Regards.
[Galaxy S I9000 Android Development] Zatta:
Please don't thank rschenk for this. It is not his responsibly to protect the thread from whatever although he thinks about this differently.

Stay in your shoes, please (Dutchism). Pawits position is clear now and it was already to everyone who was paying enough attention.

taptalked u see
[Galaxy S I9000 Android Development] rschenck:
I love you too, Zatta.
[Galaxy S I9000 Android Development] Zatta:
Kiss:)

taptalked u see
[Galaxy S I9000 Android Development] Lakerdas:
1&2: The package contains the stock cm7 kernel which is, in my opinion, the most stable.

Sent from my GT-I9000
[Galaxy S I9000 Android Development] katsooba:
after a few hrs of regular usage, my battery was at about 45% and BAM! SOD!

on the new kang.

it never happened to me on 80~103

just thought to let you guys know.
[Galaxy S I9000 Android Development] DROCSID:
Guys

Formatting / wiping:

system

data

datadata

sd

will be enough to undo the systemui / framework things I changed

when reflashing new / fresh nightly? Or?

Thanks
[Galaxy S I9000 Android Development] bLaZeR666_uk:
104 is my first CM7 on this phone. I installed from stock ensuring all cache's were flushed and I wiped SD and cleared battery stats.

Had 2 issues with random key pressing and phone dialed out on it's own. Battery life is superb and phone has always resumed from sleep.
[Galaxy S I9000 Android Development] FadeFx:
Depends on what changes you did, but if u just changed files in /system you will be back to stock by just applying the nightly...

----------------------------------------

tapatalked
[Galaxy S I9000 Android Development] siky_dude:
"and merged kernel changes but not yet added to the prebuilt kernel:

- LED Notification returns"

i think this is the culprit.

zach had, and i think still has them (sod) since he merged this fix in neo 17 :)
[Galaxy S I9000 Android Development] DROCSID:
I changed to a centered clock + some other mods.
[Galaxy S I9000 Android Development] backhead92:
format system and then flashing nighlty would to it.

As far as i know centered clock only affects systemUI (/system/app) and framework-res.apk (/system/framework)
[Galaxy S I9000 Android Development] katsooba:
as silky said. i thing led notif' is causing sod.

had no sod since ever! and new kang brought up with led notif' = sod.
[Galaxy S I9000 Android Development] DROCSID:
Yeah, well I know that these 2 files were affected by my changes.

But the strange thing is that I wiped my whole phone and my bar

is still f##ked after reflashing it. And no I did not make any changes

in the nightly hehe. Now trying to do it again. But it IS strange though.
[Galaxy S I9000 Android Development] backhead92:
You did format system before flashing the nightly?

Bacause I sometimes had something stayed, but after formatting /system and then flashing nighlty it always disappeared
[Galaxy S I9000 Android Development] pawitp:
In a SoD, see if the phone still responds via adb and gather "adb shell dmesg" and "adb logcat".
[Galaxy S I9000 Android Development] DROCSID:
Can you please use the QUOTE button to quote eachother?

Yep, from CWM I formatted a sec ago:

cache duh

data

datadata

system

boot

And now it's still like that, or it's a problem with the theme which

I can't imagine. It did work before. Now trying #103. Maybe that

will be better. Thanks for the feedback
[Galaxy S I9000 Android Development] insanedreamz:
Oh, well that's what I said- no new nightly in 2 and a half week.

Good to know, just let us

know if get a fix for hd video recording! And probably WiFi, which stops working as soon as my phone is locked.
[Galaxy S I9000 Android Development] iakovl:
I got i9000 with jv6 baseband, jv8 2.3.3 rom and 3e.

How do i act in order to flash cm7?
[Galaxy S I9000 Android Development] Bork84:
Dont tell me you searched and did not find...

there are like 3 guides to do it, and the first post here has a guide on how to do it...

ill give you a hint... first root your phone.

http://xdaforums.com/showthread.php?p=14246743#post14246743
[Galaxy S I9000 Android Development] iakovl:
The problem isnt to root. Its to use cf root so i can have cwm recovery. Jv8 is a local rom, dont know what cf to use with it.
[Galaxy S I9000 Android Development] zacharias.maladroit:
FYI

@pawitp:

sure will report

thanks !

the last I got was yesterday: the soft touchkey buttons were lit on & the screen wouldn't turn on (stayed off) :confused:

[and that's with the recent SOD & touchkey fixes included]
[Galaxy S I9000 Android Development] bLaZeR666_uk:
Anyone know why when I plug in headphones I get the icon at the top but the sound continues to play out of phone speaker
[Galaxy S I9000 Android Development] Bork84:
use this kernel

http://xdaforums.com/showthread.php?t=1044519&highlight=speedmod

it will work on your JV8.
[Galaxy S I9000 Android Development] pawitp:
Also try https://github.com/pawitp/android_k...mmit/c09d64ded56f99d9f8f328f1182232e6df9c1a5d
[Galaxy S I9000 Android Development] k9nadav:
Help anyone.. market does not enable installation of big applications

sorry for repeating this but somehow between all of threads here, nobody noticed this...
[Galaxy S I9000 Android Development] melorib:
Any news... :confused:
[Galaxy S I9000 Android Development] rschenck:
The repo is still down but codeworkx and atinm have made pawitp an official maintainer and authorized him to release official Kangs until buildbot is back.

His first release, dubbed by me Pawprint 105, can be found a few pages back posted by himself, complete with custom changelog.
[Galaxy S I9000 Android Development] zacharias.maladroit:
Thanks a lot !

already included in kernel repo & will test it asap in a new kernel :)

(oh well - all thanks still used up :confused: )
[Galaxy S I9000 Android Development] rschenck:
Sorry to miss the question, however to be honest I don't know for certain. I don't believe it has to do with where you store it, but with the amount you are downloading.

You could try downgrading to the older version of the market. That has worked for me in the past when large apps balk on me.

However I know other people have complained of download size limits so I am not sure of this is a bug, or behavior according to spec at this point
[Galaxy S I9000 Android Development] darklordkk:
SetCPU values making Phone Hang

Well,, not exactly HANG,, but it's sort of putting it in Sleep from which phone doesn't wake up at all. Have to remove battery and reboot phone thereafter.

I've set a Screen Off profile to reduce the clock speed to 400Mhz max and 100Mhz min. All the other profiles of "Battery <" and "Charging" work fine, but this profile seems to really conflict with the phone's working. Is anything wrong with the setting per se??

My usual Cyanogenmod setting is ONDEMAND governor with 100Mhz min to 1GHz max speed setting. My UV settings are 25mv UV for all speeds. In the CPU state readings,, the phone spends maximum time at 100Mhz and second most time at full 1ghz.

On RC1 released on 26th August. If anyone can give me alternative UV values and/or clock speed values that don't make the phone go to permanent sleep, i'd be most grateful.:)

Edit - A reply as a Private message would be most convenient..
[Galaxy S I9000 Android Development] katsooba:
pawit we love you!

hope this succeeds!

http://review.cyanogenmod.com/#change,7975
[Galaxy S I9000 Android Development] flip360:
that would be wonderful! thanks pawit:)
[Galaxy S I9000 Android Development] btje:
agps

I have been switching between miui and cyanogen. As the base is the same i can't explain the following difference.

On miui when using navigon navigation is says "turning on agps for 60 seconds" this should help getting a fast fix. On cyanogen i don't see this message?

Any idea?
[Galaxy S I9000 Android Development] :
cyanogenmod settings forces close on the latest nightly. report com.android.settings has stopped working
[Galaxy S I9000 Android Development] rschenck:
Which latest nightly? Buildbot 104 or Pawprint 105?
[Galaxy S I9000 Android Development] jose.celestino:
Pawprint 105 isn't technicaly a nightly.
[Galaxy S I9000 Android Development] :
Sorry, I should have made clear that it was on Pawprint 105. I tried a clean install, clearing the data via Titanium Backup, and a fix permissions. Nothing worked. Is anyone else experiencing this? I'm running a first generation UK Samsung Galaxy S.

Thanks
[Galaxy S I9000 Android Development] Daneshm90:
Please post a log. Thnx
[Galaxy S I9000 Android Development] :
What's the easiest way for me to do that? Ok, found app on market called alogcat (free).

Here is the relevant sections

V/alogcat ( 3048): save instance
V/alogcat ( 3048): paused
V/alogcat ( 3048): resumed
I/CheckinService( 493): Preparing to send checkin request
I/EventLogService( 493): Accumulating logs since 1316369753873
D/ResourceType( 493): calling getConfigurations
D/ResourceType( 493): called getConfigurations size=225
D/dalvikvm( 3048): GC_CONCURRENT freed 417K, 53% free 2860K/6023K, external 711K/1042K, paused 1ms+2ms
I/CheckinTask( 493): Sending checkin request (5548 bytes)
D/dalvikvm( 493): GC_CONCURRENT freed 399K, 48% free 3518K/6727K, external 82K/512K, paused 3ms+4ms
D/ResourceType( 493): calling getConfigurations
D/ResourceType( 493): called getConfigurations size=225
I/CheckinTask( 493): Checkin success: https://android.clients.google.com/checkin (1 requests sent)
I/CheckinService( 493): From server: Intent { act=android.server.checkin.FOTA_CANCEL }
V/alogcat ( 3048): save instance
V/alogcat ( 3048): paused
D/Launcher( 2687): -- loadPreferences()
D/alogcat ( 3048): stopping ...
D/alogcat ( 3048): stopped
D/dalvikvm( 117): GC_EXPLICIT freed 11K, 54% free 2494K/5379K, external 0K/0K, paused 152ms
D/dalvikvm( 117): GC_EXPLICIT freed <1K, 54% free 2494K/5379K, external 0K/0K, paused 150ms
D/dalvikvm( 117): GC_EXPLICIT freed <1K, 54% free 2494K/5379K, external 0K/0K, paused 127ms
D/szipinf ( 3089): Initializing inflate state
D/dalvikvm( 3089): GC_EXTERNAL_ALLOC freed 77K, 52% free 2606K/5379K, external 0K/0K, paused 27ms
D/dalvikvm( 3089): GC_EXTERNAL_ALLOC freed 19K, 51% free 2638K/5379K, external 513K/519K, paused 21ms
I/ActivityManager( 196): Displayed com.android.settings/.Settings: +1s52ms (total +7s406ms)
D/AndroidRuntime( 3089): Shutting down VM
W/dalvikvm( 3089): threadid=1: thread exiting with uncaught exception (group=0x40015560)
D/Launcher( 2687): -- loadPreferences()
I/Process ( 3089): Sending signal. PID: 3089 SIG: 9
D/dalvikvm( 196): GC_EXTERNAL_ALLOC freed 722K, 43% free 6879K/11975K, external 3096K/3116K, paused 119ms
D/dalvikvm( 196): GC_EXTERNAL_ALLOC freed 54K, 43% free 6843K/11975K, external 3820K/3845K, paused 117ms
D/alogcat ( 3048): stopping ...
D/alogcat ( 3048): canceling periodic saves
V/alogcat ( 3048): started
V/alogcat ( 3048): resumed
D/alogcat ( 3048): starting ...
D/dalvikvm( 3048): GC_CONCURRENT freed 516K, 54% free 2823K/6023K, external 711K/1042K, paused 4ms+5ms
[Galaxy S I9000 Android Development] rschenck:
Atinm says it is official, so as far as I am concerned it is no different then the dark and bastard nightlies from the bad old days. We just need to make clear which build a bug report refers to is all.
[Galaxy S I9000 Android Development] Daneshm90:
First get this from market

Now reproduce the fore close.

Then run the app and save the log, and attach it to your post or put it on pastebin.

Or use adb logcat to get the log.

Please post the full log.
[Galaxy S I9000 Android Development] rschenck:
The easiest way is pastebin links, please ....saves the headache for those of us who are allergic to code.
[Galaxy S I9000 Android Development] dhiru1602:
Can anyone please post the Kernel only from the latest Kang build?
[Galaxy S I9000 Android Development] :
Thanks guys, here's the log of a settings force close on PawPrint 105

V/alogcat ( 3048): save instance
V/alogcat ( 3048): paused
V/alogcat ( 3048): resumed
I/CheckinService( 493): Preparing to send checkin request
I/EventLogService( 493): Accumulating logs since 1316369753873
D/ResourceType( 493): calling getConfigurations
D/ResourceType( 493): called getConfigurations size=225
D/dalvikvm( 3048): GC_CONCURRENT freed 417K, 53% free 2860K/6023K, external 711K/1042K, paused 1ms+2ms
I/CheckinTask( 493): Sending checkin request (5548 bytes)
D/dalvikvm( 493): GC_CONCURRENT freed 399K, 48% free 3518K/6727K, external 82K/512K, paused 3ms+4ms
D/ResourceType( 493): calling getConfigurations
D/ResourceType( 493): called getConfigurations size=225
I/CheckinTask( 493): Checkin success: https://android.clients.google.com/checkin (1 requests sent)
I/CheckinService( 493): From server: Intent { act=android.server.checkin.FOTA_CANCEL }
V/alogcat ( 3048): save instance
V/alogcat ( 3048): paused
D/Launcher( 2687): -- loadPreferences()
D/alogcat ( 3048): stopping ...
D/alogcat ( 3048): stopped
D/dalvikvm( 117): GC_EXPLICIT freed 11K, 54% free 2494K/5379K, external 0K/0K, paused 152ms
D/dalvikvm( 117): GC_EXPLICIT freed <1K, 54% free 2494K/5379K, external 0K/0K, paused 150ms
D/dalvikvm( 117): GC_EXPLICIT freed <1K, 54% free 2494K/5379K, external 0K/0K, paused 127ms
D/szipinf ( 3089): Initializing inflate state
D/dalvikvm( 3089): GC_EXTERNAL_ALLOC freed 77K, 52% free 2606K/5379K, external 0K/0K, paused 27ms
D/dalvikvm( 3089): GC_EXTERNAL_ALLOC freed 19K, 51% free 2638K/5379K, external 513K/519K, paused 21ms
I/ActivityManager( 196): Displayed com.android.settings/.Settings: +1s52ms (total +7s406ms)
D/AndroidRuntime( 3089): Shutting down VM
W/dalvikvm( 3089): threadid=1: thread exiting with uncaught exception (group=0x40015560)
D/Launcher( 2687): -- loadPreferences()
I/Process ( 3089): Sending signal. PID: 3089 SIG: 9
D/dalvikvm( 196): GC_EXTERNAL_ALLOC freed 722K, 43% free 6879K/11975K, external 3096K/3116K, paused 119ms
D/dalvikvm( 196): GC_EXTERNAL_ALLOC freed 54K, 43% free 6843K/11975K, external 3820K/3845K, paused 117ms
D/alogcat ( 3048): stopping ...
D/alogcat ( 3048): canceling periodic saves
V/alogcat ( 3048): started
V/alogcat ( 3048): resumed
D/alogcat ( 3048): starting ...
D/dalvikvm( 3048): GC_CONCURRENT freed 516K, 54% free 2823K/6023K, external 711K/1042K, paused 4ms+5ms
[Galaxy S I9000 Android Development] Daneshm90:
Like i said, can i get a full log ? Plz ? Thnx
[Galaxy S I9000 Android Development] :
Sorry, here it is

http://pastebin.com/winF6JV7
[Galaxy S I9000 Android Development] Daneshm90:
I think you waited too long to take the log. Try again.

Take the log right after you get the force close.

Fyi look for the presence of something like this in the log:

Start proc com.cyanogenmod.cmparts for activity com.cyanogenmod.cmparts
[Galaxy S I9000 Android Development] gjroeleveld:
Because it's a MIUIUIUU customization??

An interesting one...

Switching agps off could avoid data usage, but still help for a faster fix..
[Galaxy S I9000 Android Development] :
Booted phone, initiated FC, saved log. No sign of any 'start proc'

http://pastebin.com/Dm5ggsvA
[Galaxy S I9000 Android Development] melorib:
You made me read till page 1691, bad boy... :p

Thanks Pawtip,
[Galaxy S I9000 Android Development] btje:
But does this mean agps is not on in cm7. Or constant?
[Galaxy S I9000 Android Development] pfannenwender:
had problem connecting to my wifi with the kang build from yesterday.

took pretty long to connect.

flashed 104 again.

just asking if others experienced something similar
[Galaxy S I9000 Android Development] iakovl:
what is the recommended kernel for the 104? stick to the stock that comes with it or is there something else good?

i want max bat life, not performance
[Galaxy S I9000 Android Development] aaron.bufc:
I've yet to try another kernal. The stock one has given me resonanly good battery life, I switched from Juwe's rom to 104.
[Galaxy S I9000 Android Development] siky_dude:
try neo xx beta 6, i get fantastic battery :)

remember , its still a beta, so no whining