yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] need4steer:
+1 to that.

And I'm sure that [MENTION=3892276]Jammed_Death[/MENTION] and [MENTION=3881206]ivan_dinchev[/MENTION] will join too.

Though there's another solution if it's a nuisance for [MENTION=3117667]pawitp[/MENTION] - we can flash cm-11-20140303-NIGHTLY, but we need to find where this file is hosted, because apparently it's removed from the official download site.

It's probably because of the new cm-11-20140308-SNAPSHOT-M4, but it's ridiculous that it's removed because apparently there more than a few here with this issue.

I wished we could have notice them somehow that cm-11-20140303-NIGHTLY is vital for us until issues 60816 and 60817 will be fixed.
[Galaxy S I9000 Android Development] forziere:
nobody could help me?'
[Galaxy S I9000 Android Development] pawitp:
I've triggered an "sms-test" experimental build which should include the patches.

But I should take this chance to remind everyone that, nightlies are automated builds based off the current code base. Older nightlies will be removed to free space on the server without any discrimination what so ever (and no exception will be made since the process is entirely automated). Nightlies will break, and may not be fixed right away. If you're not prepared to handle such things, do not use nightlies. The M-builds are there for a reason.
[Galaxy S I9000 Android Development] ivan_dinchev:
Sure [MENTION=5157668]need4steer[/MENTION] I'm in.

[MENTION=3117667]pawitp[/MENTION] with all my respect to you, please include in next patches solution for "unable to disconnect call"
[Galaxy S I9000 Android Development] Trainer_H:
does the sms and call bug exist in the last nightly?
[Galaxy S I9000 Android Development] need4steer:
Yep, but thanks to [MENTION=3117667]pawitp[/MENTION] we have a fix that you can flash.

Its download link already available in the official download site.

For your, and others, convenience - here is a download link.
[Galaxy S I9000 Android Development] Jammed_Death:
sorry but my galaxy s has the antenna destroyed i think...lose always signal with any modem or operator...already check evertyng else and don't know what to do (i think i will just lose money buying another antenna)
[Galaxy S I9000 Android Development] Liquidator:
Quick semi-offtopic post - I'm migrating to a new device and I wanted to thank you, [MENTION=3117667]pawitp[/MENTION], and all those countless other contributors and nice people on the i9000 forums for their work on making the Galaxy S such a long-lived device to play around with! :)

You rock, keep up the good work!
[Galaxy S I9000 Android Development] fran_xda:
I'm on M4, working great after one day testing it.
[Galaxy S I9000 Android Development] Trainer_H:
is it possible to add gesture lock screen? i use it before at a custom rom and i like it.
[Galaxy S I9000 Android Development] pawitp:
This is not a petition and please don't treat it as such. I hate people ordering me around.

That's the patch that's supposed to fixed what may be causing the problem. If it doesn't fix it, file a new bug report with logs.
[Galaxy S I9000 Android Development] tomasso32:
M4, all smooth. Happy phone. T.
[Galaxy S I9000 Android Development] need4steer:
Please, don't make it what it's not.

We, the users who have these issue with disconnecting calls and sending SMS / MMS, all agreed together that we will would like it if you'll issue a patch until your fixes will be merged in the future builds.

While now I'll speak for myself, regardless the probable fact that others will agree, I truly appreciate your tremendous work and effort to the community, and I believe I'll keep thank and appreciate your tremendous contribution.

The last thing I'll do is organize a petition against one of the greatest contributors to our device.

So, once again, it was not a petition - it was merely a common agreement, social validation if you'd like, that we all will appreciate a lot a fix for this issue - and you did it for us.

So thanks a lot, and please forgive me if it was looking like we're greedy and thoughtless.
[Galaxy S I9000 Android Development] karbon222:
hi,

who use latest nightly ?

stratosk need test new compilation of his kernel for us.. and our sgs :)

it's working ?

clean compilation cyanogenmod m4 working gret on my girls phone.. thx pawit
[Galaxy S I9000 Android Development] omreJ:
man..this thread is the most confrontational :D
[Galaxy S I9000 Android Development] pawitp:
What you call it doesn't really matter, but the fact remains that I do not like it and I ask you not to do it.

I have no control over when patches get merged and cannot really rush it.

You were looking for an old nightly which was working for you. The thing is that the M4 build would have been exactly the "stable" build you were looking for which you should use while waiting for nightlies to stabilize again after a big merge.
[Galaxy S I9000 Android Development] Kocai:
How do I downgrade to cm-10-1-2?

After flashing cm-10.1.2 I was stuck at the boot animation for 6 minutes or so last night. I had to restore my backup since it was very late.

I flashed M4 snapshot this afternoon; unfortunately the green flash still appears.
[Galaxy S I9000 Android Development] pawitp:
Make sure you wipe data after downgrading.

If it still doesn't work, it is best to go back to the stock ROM with Odin before installing cm-10.1.2. After you are at cm-10.1.2 you can go to cm-10.2 and finally cm-11 in order (in order to test all versions).
[Galaxy S I9000 Android Development] Kocai:
I just did a clean flash of cm-10.1.2 and the green flash appears so most likely it's hardware failure I guess. It was just a bad coincidence that it appeared when I first flashed cm-11. Sorry for all the trouble.
[Galaxy S I9000 Android Development] fran_xda:
random soft reboots

Hi, I flashed Snapshot-M4 2 days ago, and everything is working better than in previous versions, except for some eventual soft-reboots (1 or 2 per day) that I'm having. Everything is stock, no performance tweaking, app killers (greenify),... The reboots happens during operation, not sleeping.

I'm attaching tombstones.

Thanks
[Galaxy S I9000 Android Development] pawitp:
The logs show that your phone is out of memory. Try checking Settings -> Applications -> Running and see if you're running too many services or not.
[Galaxy S I9000 Android Development] fran_xda:
The apps are the same I ran in M3 and there were no reboots in that version. Apps switch much faster in M4 though, prefer to M3 in general.

Ps: I just had a reboot attaching this image with tapatalk

Ps2: there is only one process missing in the running processes list, keyboard about 8mb
[Galaxy S I9000 Android Development] pawitp:
You'd need to get a logcat of the reboot. The tombstone may not provide enough information. And please follow the bug report format.
[Galaxy S I9000 Android Development] tomasso32:
Titanium backup crashing. [Maybe it's superuser]. I know other people have reported this on nightlies, but I'm using M4, which has otherwise been fine. Tom.
[Galaxy S I9000 Android Development] ..::WD40::..:
Patch is finally merged, I hope that tomorrow nightly will be ok
[Galaxy S I9000 Android Development] King18:
I flash the newest stable nightly...

I got sometimes the message Sim Card Entry..restart. And then it works...but some hours later i become the message again...
[Galaxy S I9000 Android Development] King18:
Cannot download from PlayStore!
[Galaxy S I9000 Android Development] need4steer:
Can you restore this behavior?

You're not giving enough information.

Is there an error? If there is one, is there an error code?

Please follow the standard bug report so it'll be more easy to us to understand and to help.
[Galaxy S I9000 Android Development] King18:
The Sim Card works again... It tooks some times to got the code. If I want to download an APP there stands only : downloading....

I will check the error code tomorrow.

Thanks
[Galaxy S I9000 Android Development] fran_xda:
Sorry next time I'll report better. I have researched about grabbing logcat in reboots and looks like adb has to be used, right? But doesn't adb need a PC attached to the phone? So how could do it if I cannot reproduce the reboot?
[Galaxy S I9000 Android Development] King18:
Okay it works. I can download again, but some apps not like MXPlayer
[Galaxy S I9000 Android Development] pawitp:
Unfortunately, you'd need to connect it to a PC, leave logcat running piped to a file and try to reproduce the reboot.
[Galaxy S I9000 Android Development] karbon222:
hello,

@ pawit or anyone else who knows what I can dump to get rid of files that make up the data and cause the problem described here: https://jira.cyanogenmod.org/plugins/servlet/mobile#issue/CYAN-2949

I did a full wipe and installed a clean nightly and this error is not there, so I decided to restore from backup only the files data and the error came back. so that makes it a corrupted file, which is in the folder data .. I removed the folder com.android.dialer but in addition also reset the settings it does not work, I cleaned the cache from the phone dialer, nothing helps.

I have some things on the phone and do not have time to configure it all from the beginning .. I installed CM11 after a full wipe but it was maybe 3 week after they began to appear official nightly, until now only performs an upgrade to the next nightly.

Is there anything else I can delete that may be responsible for it?
[Galaxy S I9000 Android Development] rhaaa:
backdoor in our devices ?

Hi all and pawitp,

have you heard of this backdoor in our devices:

http://redmine.replicant.us/projects/replicant/wiki/SamsungGalaxyBackdoor

https://www.fsf.org/blogs/community/replicant-developers-find-and-close-samsung-galaxy-backdoor

Apparently we are all vulnerable to this :(

Being a free software advocate, I candidly thought that binary blobs to drive some parts of the hardware were a lesser evil, that no reputable phone builder would take advantage of this to mess with other unrelated parts of the phones, and certainly not place backdoors... apparently I was all wrong, and Samsung did it. Please note that there is no reason to think that they are the only ones to do it, but they were busted...

Now I guess it's impossible right now to remove these backdoors, but is there a possibility to at least get a warning when these capacities are used ? The post on the replicant wiki says some things along those lines at the end, do you think it is possible and will be implemented ? Note that this is not limited to our device, plenty of others are affected too.

Thanks for your work on our now prehistoric device :)

--

Rémi
[Galaxy S I9000 Android Development] pawitp:
Only sure fire way to get what you want: submit a patch ;)

I, personally, am not too interested about it. They're just hooks to allow the code running on the baseband controller to access the files it may need to. Examples of legitimate uses include reading settings regarding radio settings or dumping debugging logs (note: they're just hypothetical examples since I have no idea about the inner working of the RIL). It's just that we don't know what code is running on the baseband and thus it is considered a potential backdoor.
[Galaxy S I9000 Android Development] mongoose:
Still have "unable to disconnect call" bug with cm-11-20140313-NIGHTLY-galaxysmtd :(
[Galaxy S I9000 Android Development] pawitp:
File a bug report in the format shown in the first post. Include a radio logcat (logcat -b radio) taken when you couldn't disconnect the call.
[Galaxy S I9000 Android Development] Galaid:
I'm still having issue with sending SMS on latest nightlies (up to 11/03) so I'm wondering if those patches are integrated now?

thanks!
[Galaxy S I9000 Android Development] pawitp:
They should be.

File a bug report in the format shown in the first post. Include a logcat and radio logcat (logcat -b radio) taken when you're trying to send the SMS.
[Galaxy S I9000 Android Development] Makifylmz:
Question

Pawitp, I want to ask you some questions. Your kernel know ro.ril.disable.power.collapse and pm.sleep_mode codes ? When I add this commands in build.prop, battery life up to 22 h (then 18h). I hope it's not placebo :o Do you recommend this commands? Now I'm in 06 nightly it's very stable and not having any issues. Thank for your hard work
[Galaxy S I9000 Android Development] pawitp:
100% placébo. Nothing in the system read those 2 props.
[Galaxy S I9000 Android Development] Makifylmz:
Arghh :D Thanks again pawitp
[Galaxy S I9000 Android Development] need4steer:
It's sad to read this.

I flashed it about a hour ago.

If I'll have any issues I'll also post a radio logcat.

According to the changelog the fix was merged in today's nightly (cm-11-20140313-NIGHTLY).

Was it merged before?
[Galaxy S I9000 Android Development] pawitp:
Oops, forgot to read the date.
[Galaxy S I9000 Android Development] Galaid:
hmm, flashed 13/03 to no avail, flashed nightly from December after wipe and still can't send sms. Wiped and omnirom, still can't send sms. Never happened before. Can't find any cwm zip with stock firmware :argh:
[Galaxy S I9000 Android Development] need4steer:
If I were you I'd have cleanly flash the latest nightly (factory reset + format /system and /sdcard), and then trying to see if it's happening again.

If it'll happen - a better practice will be taking both full logcat and a radio logcat (adb logcat and adb logcat -b radio), as [MENTION=3117667]pawitp[/MENTION] suggested, in order to investigate this issue further.

BTW, I had a similar issue with nightlies from cm-11-20140304-NIGHTLY until the latest one - cm-11-20140313-NIGHTLY, in which this issue fixes were implemented. (issues 60816 and 60817, as you quoted before)

Although others still have this issue, for me it's working for a few hours now with no issues.

In the moment I'll have issues I'll logcat just as mentioned above.

BTW, if you don't want to investigate and see if it's okay with the latest nightly, take one of the M-Series builds (M4 or M3), since nightlies before 20140304 are not available anymore.

Edit: Whatever version you'll decide to flash, the best way (and sometimes the required way) is to perform clean install (factory reset + format /system and /sdcard).
[Galaxy S I9000 Android Development] supergeorg:
Security flaw

I'm just curious if the described security issue is present in this rom, this means to what extend [MENTION=3117667]pawitp[/MENTION] has rewritten the modem code for 4.0+.

Others say it's Bullsh''t, so no worry it's not exploitable. Just curious.
[Galaxy S I9000 Android Development] legend_wok:
you may want to read pawitp's replay he gave just one page back....
[Galaxy S I9000 Android Development] PxGold:
One you are on a current nightly you can't load a previous M3 or M4 without doing a clean install, their were too many changes that prevent the installation of a previous M build.

http://www.cyanogenmod.org/blog/cm-11-m4-post-release-items
[Galaxy S I9000 Android Development] hertzschi:
http://www.xda-developers.com/android/samsung-backdoor-may-not-be-as-wide-open-as-initially-thought/
[Galaxy S I9000 Android Development] rhaaa:
TL-DR: go to the last paragraph :)

the author seems a bit fast to abandon charges... saying that we can forget about it all untill there is a proof that this is somehow exploited in the wild is (security speaking) nonsense. Security updates are most of the times about *potential* exploits, even if the discovered flaw alone is not enough to do anything harmfull. You don't wait for a clear documented and used vector of attack to close the doors...

Don't forget to read the comments by E:V:A and xsenman under the article, they are a bit more thorough.

This is not to say that pawitp (or anyone else in the CM community) *should* do anything about it, they are already doing a tremendeous job for which I'm more than thankfull. Besides, CM is probably more secure than most android variations out there. But if there is a way to create some sort of layer in the CM infrastructure that could alert the user when a binary blob does something fishy, why not speak about it. The binary blob problem is not specific to samsung either, every single android phone out there has them. And in those post-Snowden times, it's simply not possible to assume that all of them are behaving nicely.

I'm technically way out of my league there, so bear with me for the sloppy vocabulary and the possibly (probably ?) completely screwed up proposition :)

The other side of the equation is Samsung. They have been busted ? <bamby_eyes="on">Ooooooh, I'm sooooo sorryyyyy<bamby_eyes="off">, but too bad for them. There is frankly no reason to exonerate them, even if no clear vector of attack has been demonstrated to be used in the wild.

This instead should be used as a lever to make them release as much code as possible about their hardware. Or make them change the way they choose their hardware in the future so they can release all (or most) in the open.

Maybe I'm wrong, but I don't think there is anything magic in those binary blobs. There is no technical reason for not releasing the code besides prior «industry practice».

So I think the message from the FSF and replicant is right: use this flaw to put as much public presure as possible on Samsung to release the code. This probably won't work the first time, and certainly not for the current devices. But I can guarantee that they will seriously think about it for future devices if hundreds or thouthands of tweets and facebook posts land on their public pages.

Happy hacking,

--

Rémi

PS: done on https://www.facebook.com/SamsungMobile :)
[Galaxy S I9000 Android Development] Galaid:
sms

Regarding sms sending issue, I'm back on gingerbread JW7 stock firmware and SMS still not working!!?

It can't be my provider because a lot of people start complaining at the same time. I'm gonna go back to cm11 and report logcat..
[Galaxy S I9000 Android Development] pawitp:
Check your SMS message center number. Your problem and all other people's problem are probably separate.
[Galaxy S I9000 Android Development] Galaid:
I tried to change sms center via #*#*info#*#* on cm11 and omnirom but it always staid od 00 instead of what I entered. Could you please check what does it return when you press refresh?
[Galaxy S I9000 Android Development] rodman01:
Do you have an other phone, perhaps an older nokia or something like that, where you can insert your sim card and then update there the message center number? Then reinsert the sim card back in your S1 again....do not know whether it works in this case, but I had a similar and to solve my problem it worked.
[Galaxy S I9000 Android Development] need4steer:
Can't play videos after flashing cm-11-20140315-NIGHTLY

I Can't play videos after flashing cm-11-20140315-NIGHTLY.

When I try to play one, I'm just getting a blank screen within the video player. If I slide from the top and downward, or from the bottom and upward - I see the pause indicator - which means the video is "playing", but the time indicator isn't advancing from 00:00, and the video isn't playing at all.

If I'm rebooting then when I'm trying to play I'm receiving the "Can't play this video." message. However, if I'll try again after some period I'll get the same behavior I described above - a blank screen.

The video is okay.

BTW, I can't play other videos which I played before.

Now, for the dry details:

Phone model: Samsung Galaxy S GT-I9000 (galaxysmtd)

Radio (baseband): I9000XXJVT

CM version: 11-20140315-NIGHTLY

I didn't perform wipe yet.

I don't have titanium backup.

I'm not using a task killer, a non-stock kernel, performance settings, ART Runtime and other modifications

Here is my View attachment logcat.txt
[Galaxy S I9000 Android Development] pawitp:
http://review.cyanogenmod.org/#/c/61175/
[Galaxy S I9000 Android Development] geckoas:
Can't disconnect call from mobile with 20140315-NIGHTLY

For me too with the cm-11-20140315-NIGHTLY-galaxysmtd.

Kernel: Semaphore 3.4.3s

I started a call and couldn't disconnect it from the mobile during the ringing phase and also after connection was established.

Does anyone else have this issue?

Restored cm-11-20140221-NIGHTLY-galaxysmtd, because i need a working phone, and everything is fine.
[Galaxy S I9000 Android Development] petopp:
new update 20140315

new bugs: does not work H/W dekoder play videos (Mx player) only S/W dekoder work :(

does not work Google play

new feature 371 MB RAM before 368 MB
[Galaxy S I9000 Android Development] tetakpatak:
You can not report here bugs when on custom kernel.
[Galaxy S I9000 Android Development] petopp:
i flash new 20140316 + Gapp

Google play now works

videos dont work again H/W dekoder + youtube videos dont work (youtube app)
[Galaxy S I9000 Android Development] qwertyujhgfdsa:
Will fix on nightly 0317

http://review.cyanogenmod.org/#/c/61175/
[Galaxy S I9000 Android Development] need4steer:
It was fixed in today's nightly (cm-11-20140316-NIGHTLY) thanks to [MENTION=3117667]pawitp[/MENTION].

Edit: Sorry, you're right!

It's not merged in today's nightly, and the error still occurs.

I always noticed the differences between cmxlog and bbqdroid change logs, but now I see that the ifdef "stagefright: Enable GraphicBuffer usage to decoder before querying formats" issue is merged and listed in both of them, but not in the one that is in the internal update mechanism (when we click on the file in the settings --> about phone --> cyanogenmod updates).

I guess it'll best to stick to the internal change log... :)
[Galaxy S I9000 Android Development] aironmail:
Not only youtube vídeos are broken in 20140316, as the camera app does not work either and previosly recorded vídeos (without streaming).
[Galaxy S I9000 Android Development] nexzor:
not only in S1, also on nexus 5. some one is working on a fix. i hop this will help on s1 too
[Galaxy S I9000 Android Development] King18:
During the call, if I will turn the speakers on it dont work.

Please fix it. I use the newest stable nightlie...
[Galaxy S I9000 Android Development] petopp:
i go back 20140311

because video problems last build:(
[Galaxy S I9000 Android Development] joebacsi72:
NIGHTLY 2014.03.17 works fine! Call, sms, video OK! (with other kernel too)

THX! :)

GT-I9000 CM11_NIGHTLY_KK4.4.2 latest
[Galaxy S I9000 Android Development] petopp:
youtube,videos ok thx fix
[Galaxy S I9000 Android Development] tommy1945:
Problem with cm-11-20140308-SNAPSHOT-M4

Dear Pawitp,

I flushed your rom cm-11-20140306-NIGHTLY, which is excellent. I tried to install the Stability update (cm-11-20140308-SNAPSHOT-M4) directly OTA, but the phone got into a permanent loop announcement that unable to update. It was impossible to use the phone, so I took out and put back the battery, and re-flashed the original rom. Than tried to flash the update by downloading the ZIP file - through the recovery. The same happened. So - re-flashed the 06 again.

Anyway, thank you for your wonderful Rom. I am just curious why it's like that. :confused:
[Galaxy S I9000 Android Development] gverma1:
Check if you have downloaded the M4 zip file properly. Redownload if required.
[Galaxy S I9000 Android Development] nexzor:
simple read the newsticker at http://www.cyanogenmod.org/blog/cm-11-m4-post-release-items

so dont cross updatestream without doing a full wipe.

only chance is to restore a backup or do full wipe
[Galaxy S I9000 Android Development] monjovega:
Camera not working on latest update

"Camera has stopped".....
[Galaxy S I9000 Android Development] tetakpatak:
Too bad.... no photo, thus.