yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] guijarrelson:
+1

In the last nightly, I have a bootup freeze. The 21072013 nigtly has the waring file_context message too.

Flashing back to 21072013, it boot well.
[Galaxy S I9000 Android Development] gverma1:
Thanks Pawitp. I knew about this. What I meant was that I should have the freedom to remove/disable apps that I don't want, which is the case with CM, so all is fine with the current CM payload. FYI, system apps can be disabled by Link2sd. Thanks
[Galaxy S I9000 Android Development] cecenac:
Guys what is your pick: Slim bean 7.0 or latest stable CM 10.1 ?

I am flashing for a friend. He wants a smooth and stable rom that is good for gaming. Thanx ahead !
[Galaxy S I9000 Android Development] Ommadawn101:
What will be your advice as for hardware problem? How can that be checked?
[Galaxy S I9000 Android Development] dark_knight35:
Seems so, flasing a custom kernel worked for me.
[Galaxy S I9000 Android Development] cecenac:
In case you missed it, I need advice so i can flash and return him the phone. Thanx again:

"Guys what is your pick: Slim bean 7.0 or latest stable CM 10.1 ?

I am flashing for a friend. He wants a smooth and stable rom that is good for gaming. Thanx ahead !"
[Galaxy S I9000 Android Development] pawitp:
It will be fixed in the next nightly.

Try a full wipe, an older working version or a Samsung ROM and see if the problem persists or not.

You'll already get biased result by asking in this thread (and it's also offtopic). Please use the Q&A forum.
[Galaxy S I9000 Android Development] joebacsi72:
Latest NIGHTLY 2013.07.22 with GearKernel work perfektly.

Tapatalk 2-vel küldve az én GT-I9000-ről JB_4.2.2_NIGHTLY + GearKernel_1.0.3s
[Galaxy S I9000 Android Development] 7kartoon:
pawitp: I said that my previous post would be the last under this thread but allow me to explain better something. I knew well before you mentioned it that CM team follows a protocol. I did not wish to learn the details behind it but obviously I wanted to doubt them. Whatever are the reasons you follow it, in my sense there are flaws.

Maybe not for other devices, like Nexus 4 or I9300, but clearly for low end ones like our I9000 something is wrong.

Someone said I want to have the last word. It has nothing to do about this. Some people hit thank you for one reason I believe. They believe as I do that CM ROM can be better. My recommendations were posted for one and only reason. They make my CM experience a lot better. And if there was no room for CM to improve this thread would not exist at all.

So, if you want to convince someone that CM is at its best for the GT-I9000 the way it is, I am sorry, clearly that person is not me.

And for those who jump to conclusions this has nothing to do with me not respecting pawtip and the CM team. It is because I appreciate the job done here that I post.

[MENTION=4450902]dk147in[/MENTION] : If you are the guy your words tell, follow pawitp 's above words. He clearly knows better.

P.S. let me tell you (dk147in ) how awesome the LG Nitro HD, the HUAWEI P6 and the XIAOMI MI2S are. To the moon and back ;) Cheers.
[Galaxy S I9000 Android Development] pawitp:
Your words aren't that much better and I don't like your "I know it all" attitude. I didn't mention it before because I feel that personal attacks isn't constructive to a discussion, but what you did was also an attack on dk147in.

Basically: what you think is a better ROM is not what everybody think is a better ROM. We're open to suggestions, but you should be open to our reasons as well.

We strive to fix things the proper way. Apps not being used should not take RAM. You insist that live wallpapers and some other system apps take RAM without being used. The "proper" way to fix it is to fix the fact that it's taking RAM without being used, not removing it. Because I cannot reproduce it, the way you can make CyanogenMod better is to provide bug reports, logcat and reproduction instruction, not to keep on suggesting that they should be removed.

And you know what's great about open source? You can fork and create your own distribution. AOKP didn't agree with CyanogenMod's policy on limiting customization and making things more stable and user-friendly. They want thousands of customization options like the CM6 days. So they've created their own distribution and it worked well for everybody.
[Galaxy S I9000 Android Development] ts1506:
I would give you a small tip. Instead of arguing with everyone , why dont you make a small zip , whose updater-script just deletes the apk's you want. Then flash it everytime after flashing a ROM , and those apps will be gone. Simple and effective , makes CM remain as it is , and makes it enjoyable for you too.
[Galaxy S I9000 Android Development] DeusEx80:
.... or freeze these apps with Titanium Backup or similar.

After installing new CM nightlies, these apps remain frozen.
[Galaxy S I9000 Android Development] Bejda:
"Btw" there's system/addon.d/****.sh scripts on which we could add some rm commands for system apps or stuffs we don't want to be conserved or reinstalled after each cm (or others rom 's) update as shown on the 4th post of this thread:

http://xdaforums.com/showthread.php?t=1617356

But I and all peoples I know who used this noticed that apparently it didn't worked anymore and that,apparently also,since the blacklist check appeared.

Strange thing is that I asked about it on the thread mentioned above and nobody confirmed..it's very odd cause on some rom like Slim that completely removed blacklist check process the rm command still works..could it be something specific to I9000? (blacklist process that differs depending on device? ..I wouldn't think so but..)

If we look at the addon.d/***.sh scripts of the optional part of goo.im gapps (the part with GoogleGallery.apk/photosphere) we can see another way to remove/not install some apps (Gallery2.apk here) but it doesn't seems as handy as was adding rm command.

Maybe I'm wrong it still works and the error is on my(our) side though so if anybody would know more about it or would want to test this further he'd be welcome :)
[Galaxy S I9000 Android Development] AusMatt:
You don't seem to be reading peoples responses to your posts.

People really do need cell broadcasts and the MS Exchange integration to work by default.

You're asking for a custom 'lite' CM and you're ignoring everyone's helpful suggestions of how you can deal with your perceived problems.

It's time for you to stop wasting everyone's time.

You really do have an attitude problem.
[Galaxy S I9000 Android Development] pawitp:
The blacklist simply skip scripts with the following md5sum

https://github.com/CyanogenMod/android_vendor_cm/blob/cm-10.1/prebuilt/common/bin/blacklist
[Galaxy S I9000 Android Development] Bejda:
Thank you.

That's what I understood very superficially when i looked at backuptool.sh file and the blacklist commit but i never found understandable (at my level) infos when i tried to dig a little further into it.

Anyway your answer acted as a key and as often with things put aside since a long time when i searched a little again today things appeared a little clearer to me...at least i feel like posting maybe stupid but more detailed questions lol.

So as md5 are made of 32 characters there's 4 scripts declared in the blacklist file?

If i simply produce md5 for "rm" (should be such "simple/shorts commands/scripts I guess?) and if that md5 is not blacklisted it means my rm story can't be related to blacklist? (i already came to that conclusion when I saw others cm users invalidated my theory but well, just to know more how things are..)

I tried some online databases based md5 revert converter,some of them found rm command when I input the rm md5 (maybe cause I used them to produce rm md5 just before lol) but I didn't find the blacklist ones correspondences. Is there a way to know out of curiosity what are those "known to cause issues" scripts?

Many thanks for...being here :)
[Galaxy S I9000 Android Development] pawitp:
It checks the md5 of the script, not the command. Use the "md5sum" utility to find out the md5sum of the file. It is very unlikely that the script would be blacklisted, since the blacklist just covers old gapps and such that breaks when used with 4.2.
[Galaxy S I9000 Android Development] guijarrelson:
New nightly released some minutes ago, anybody can confirm if the issue with selinux and the boot process works?

pawitp could you give me the change which is made in the source to fix it? :)

Thanks in advance
[Galaxy S I9000 Android Development] pawitp:
Last few commits on https://github.com/CyanogenMod/android_system_core/commits/9df8c473782968493bd4b71426e6e1bffadeaa79

I'm not a fan of explaining the technical details though. I may sometimes give pointers, but other than that, interested parties should be able to figure it out themselves from the source code, as in this forum, I'm a developer, not a teacher.

(Because well, if everyone asks me for details on everything that is fixed, it'll be double or triple the work of actually fixing it.)
[Galaxy S I9000 Android Development] guijarrelson:
Thanks pawitp, only I need the link of the github that references the change :)

I can confirm that the latest 23072013 nightly, boots up! :D
[Galaxy S I9000 Android Development] Jaazish:
Few issues I'm having on CM 10.1 nightly 7.11.13:

1. The phone 'forgets' its ringtone, meaning that it changes and looking at the sound setting it is shows as unknown ringtone. Choosing the ringtone again will help for some time, but it occurs daily; I haven't got to determine what exactly causes that.

Wasn't like that on a June nightly (don't remember which)

2. I'm having problems with the stability of USB connection to the computer, meaning that it gets disconnected after some short time, files won't transfer correctly, etc.

I carried that from the June nightly, so it's not a new 'feature', but a very annoying one.

It occurs both for the internal and external memory.
[Galaxy S I9000 Android Development] dk147in:
+1

Tried not worked....then reverted to previous nightly.
[Galaxy S I9000 Android Development] albertobom:
Todays nightly boots ok
[Galaxy S I9000 Android Development] gverma1:
23 July 2013 nightly works just fine.
[Galaxy S I9000 Android Development] slybunda:
which cpu governor do you guys use with this rom? what gives good blend of battery life and performance?
[Galaxy S I9000 Android Development] didi0815:
When I use my countdown timer and leave the clock app and the timer ends with the alarm tone, I cannot stop the alarm without going back to the clock (in the normal way using the icon of the app) where I have to select the timer icon again to find the stop button in form of a trashcan.

Is this a bug, a feature, a wrong setting or a stupid user? :o
[Galaxy S I9000 Android Development] albertobom:
I use the default (interactive / row), works well for me.
[Galaxy S I9000 Android Development] szaf:
What do you mean wipe system?Do a factory reset or format system?
[Galaxy S I9000 Android Development] slybunda:
how much battery life do you get on average? the screen on time using interactive gov?
[Galaxy S I9000 Android Development] albertobom:
One day. But most of the time I'm connected to Wi-Fi internet, seeing videos on YouTube, listening music, using tapatalk and so on.
[Galaxy S I9000 Android Development] slybunda:
i need to give this interactive governor a try i think mine is still set to ondemand.

does conservative give much more battery life gains?
[Galaxy S I9000 Android Development] geckoas:
1. This happens (also to me) when the storage is connected in "Mass storage Mode". It doesn't happen with "MTP" or "PTP" mode.

2. No idea

sent from my galaxy I9000 running CM10.1 with tapatalk 2
[Galaxy S I9000 Android Development] hornet_II:
Nobody imposed you to use CM.

If you don't like it, don't use it.

If you can make the "ideal" ROM, according to your standards, go ahead.

It is as simple as that.

Personally, I am grateful to all the developers of CM and it does piss me off to see so much ungrateful insolence that you openly show in your posts.

So please, stop complaining and at least try to be constructive.

---------- Post added at 11:36 PM ---------- Previous post was at 11:33 PM ----------

Nobody imposed you to use CM.

If you don't like it, don't use it.

If you can make the "ideal" ROM, according to your standards, go ahead.

It is as simple as that.

Personally, I am grateful to all the developers of CM and it does piss me off to see so much ungrateful insolence that you openly show in your posts.

So please, stop complaining and at least try to be constructive.
[Galaxy S I9000 Android Development] jgaviota:
[MENTION=3117667]pawtip[/MENTION]

First of all thanks for your great work.

I read on rootzwiki that the CM rom for the Galaxy Tab has a switch where you can format a SD with 3 partitions and use it instead of the internal memory when it goes kaput. (activate_data_on_sdcard file on a fat32, followed by two ext4)

I recently had that problem with a I9000, cannot mount data or system on CWM. Does CM for Galaxy S have that capability?

Thanks!
[Galaxy S I9000 Android Development] pawitp:
No. Though I've never heard about any Galaxy S with a dead internal memory either, you might want to try going back to stock and reformatting everything first. It does uses LVM though, so you can technically create an LVM partition on your external SD card with the correct name and the code will use it. (But no instruction will be provided and is fully unsupported)
[Galaxy S I9000 Android Development] jgaviota:
Already tried going back to stock with odin and repartition, didn't work :(

I hadn't heard of a dead i9000 either, but I guess there's a first time for everything

P.S. It's a I9000T I just checked.

So I'll go back to Froyo and start there.

Could anyone help me with how to create a LVM partition with the correct name?

I know that this will totally unsupported :D

Thanks
[Galaxy S I9000 Android Development] pawitp:
While I'm not going to help you with LVM (since it has never been done before and so I don't have any instruction unless I try it on a real device), I'm going to ask a bit more about the phone.

Can you boot into recovery and get the content of "cat /proc/partitions" via adb shell?

What happens when you try to format and mount the partition in recovery? Try getting the log instantly after doing it (adb pull /tmp/recovery.log). What are the partitions that are failing? Does /sdcard work?
[Galaxy S I9000 Android Development] jgaviota:
I'll run all these commands tomorrow morning, I left the device in the office.

Thanks
[Galaxy S I9000 Android Development] Jaazish:
Thanks, I'll try MTP or PTP - I have hope that it might kill these 2 birds at once :)
[Galaxy S I9000 Android Development] fmc000:
Show the carrier on the status bar

Hello,

I know that this thread is not meant to be a "feature request" one but I think that this can be useful for many. I use this mod: http://xdaforums.com/showthread.php?t=2085367 to have not only the clock centered in the status bar but also to have the carrier name shown at the top left.

This is very important to me because I need to know which carrier I'm connected to when the phone is in roaming.

I would like to know if this mod or something similar could be included in CM as there are often incompatibilities with the new nightly versions.
[Galaxy S I9000 Android Development] pawitp:
The thread is not for feature request because they can't be addressed here, people related to other parts of CyanogenMod don't read this thread. Go to https://jira.cyanogenmod.org/ and file it there.
[Galaxy S I9000 Android Development] fmc000:
Done: https://jira.cyanogenmod.org/browse/CYAN-1789
[Galaxy S I9000 Android Development] Ommadawn101:
I am not sure whether this a bug or not

I did a full wipe (from recovery wipe data, wipe cache, wipe dalvik and format system)

Flashed nightly of 23/07

Flashed Gapps

My settings (number of screens, shortcuts, ringtones, wallpaper etc) were gone, as expected.

But, my profiles, including profile names, and wifi and Bluetooth triggers were all

intact

Is this expected?
[Galaxy S I9000 Android Development] gverma1:
After all that cleaning, these should have gone too.
[Galaxy S I9000 Android Development] slybunda:
nop, need to wipe data/data
[Galaxy S I9000 Android Development] nameh:
Sorry to bother again. Does anyone have a solution or explanation to my problem?

Thank you
[Galaxy S I9000 Android Development] DerRomtester:
yeah format system and data
[Galaxy S I9000 Android Development] nekuy:
Did you try to removing and reinstalling your Google account?

BTW; installing cm 10.1.2 is better for security reason.
[Galaxy S I9000 Android Development] DerRomtester:
Yeah android 4.3 is coming with libgles 3.0 :D
[Galaxy S I9000 Android Development] ts1506:
There is a lot of activity going on in android.googlesource.com right now. :)

I think they are going to push 4.3 code to AOSP soon.
[Galaxy S I9000 Android Development] wazza1991:
4.3

so 4.3 will run fine on our phone i guess...no major changes :D
[Galaxy S I9000 Android Development] Bejda:
https://groups.google.com/forum/m/#!topic/android-building/sDovKMKTAiQ
[Galaxy S I9000 Android Development] herc2k:
what is better on 4.3 ?
[Galaxy S I9000 Android Development] ts1506:
[OT] 4.3 code online now . Yay.. [/OT]
[Galaxy S I9000 Android Development] yavu:
I hope that 4.3 don't need more ram then 4.2.2. Than it will run better on i9000 ;)
[Galaxy S I9000 Android Development] jgaviota:
Ok, results:

I went back to stock with odin and 512 repartition and dbdata.rfs could not finish flashing.

Reflashed in odin a Gingerbread stock rom without dbdata.rfs.

Flashed CWM with odin

Tried to wipe from CWM and it reported an error with /dev/block/mmcblk0p2

also there was a problem with /dev/block/stl10

Then I partitioned a 16GB card so that the first partition is fat32 the second is ext4.

copied CM10.1 onto the sd

Somehow the sdcard got erased (maybe stock rom did it or CWM)

copied CM10.1 onto the sd again

flashed CM10.1 from CWM (ext sdcard behaved as internal sd)

Booted into CM10.1

CM10.1 reports no space on the internal SD

CM10.1 reports external sd with 14GB more or less

I can no longer go into recovery without the external sdcard inserted

From recovery adb shell:

cat /proc/partitions

major minor #blocks name

31 0 7680 mtdblock0

31 1 7680 mtdblock1

31 2 432128 mtdblock2

31 3 17920 mtdblock3

31 4 12800 mtdblock4

31 5 16384 mtdblock5

31 6 11264 mtdblock6

179 0 15558144 mmcblk0

179 1 13592032 mmcblk0p1

179 2 1966080 mmcblk0p2

attached is the recovery.log after trying to wipe/factory rest and trying to format /data
[Galaxy S I9000 Android Development] pawitp:
Well, the first SD card simply disappeared and the external SD is treated as the internal as far as the recovery is concerned, so your external may have already been reformatted with LVM (well, the fact that the system is bootable must be due to something). But the Android subsystem is smarter and still knows that your external SD is external. You'll simply need some unsupported way to "swap" it with the internal card (don't ask me though).
[Galaxy S I9000 Android Development] supergeorg:
... and CyanogenMod is working on 10.2

Looking forward :D

Gesendet von meinem GT-I9000 mit Tapatalk 4 Beta
[Galaxy S I9000 Android Development] jgaviota:
A quick swap on the vold.fstab

Thanks
[Galaxy S I9000 Android Development] gverma1:
Hey jgaviota. What you are doing could be useful to many (or some) users whose internal SD cards may have crashed. Would be beneficial to them if you could list down the steps you took to get your external card working as 'internal'. Thanks

---------- Post added at 10:36 AM ---------- Previous post was at 10:33 AM ----------

Great to hear!!! Is it clear yet whether i9000 get 4.3 or not?
[Galaxy S I9000 Android Development] pawitp:
Only for devices where the OEM provide updated OpenGL drivers.

Probably yes, if it's as minor as everyone think it is.
[Galaxy S I9000 Android Development] ts1506:
About OpenGL ES 3.0 , does the SGS's GPU support 3.0 ? I was under the impression that SGX540 supports only ES 2.0 (not sure).
[Galaxy S I9000 Android Development] freakymod2120:
Two questions:

When 4.3 comes for our device can we use new features for example gles 3.0, Bluetooth 4.0??? Does our device support this new features because of its Hardware???

Another question for 10.1.2:

What are ca-certificates for??? Under security there are a lot of this login certificates???first time i saw them after update to 10.1.2...

The Option "cleaning login data" is not available... It is there but i can't use it...

Thxs
[Galaxy S I9000 Android Development] ts1506:
No, Bluetooth 4.0 LE wont work. Our devices only support Bluetooth 3.0.

And most probably , SGX 540 supports upto ES 2.0 , but I am not sure about this one.
[Galaxy S I9000 Android Development] 99x:
CA (certification authority) certificates define a trust relationship between the client and a certificate issuer. If you don't know what they are you probably don't need them :)
[Galaxy S I9000 Android Development] s3icc0:
But still ... it will be shame our device will not get the 4.3 (with the improved power and ram management) as it is 320 000+ installation of cyanogenmod the leading CM device still :) (thanks to pawitp) - and sorry for 4.3 spam in 4.2.2 thread
[Galaxy S I9000 Android Development] 99x:
Galaxy nexus has the same GPU, will this be of any use to us?
[Galaxy S I9000 Android Development] Kingo64:
It will be a lot of use. If only Google ported 4.3 to the Nexus S for us to harvest from.
[Galaxy S I9000 Android Development] pawitp:
You've just quoted my answer. OpenGL ES 3.0 is only available for supporting hardware and updated GPU driver is required. Our device doesn't have both.

No. Galaxy Nexus 4.3 only ships with OpenGL ES 2.0, presumably due to lack of hardware support.
[Galaxy S I9000 Android Development] groksteady:
you do need them; remove them all and you'll likely get annoying warnings that every connection you're trying to make is untrusted.

That said, I do remove CNNIC and Turktrust each new flash. I don't trust CNNIC, and earlier this year Turktrust was the ultimate CA in a group that issued fake certificates in Google's name. The risk is being a phishing victim -- attacker tricks you into clicking on a site that looks legit and it's not, and then you send your passwords, do your banking, whatever. The other risk is a man-in-the-middle, where the attacker places himself between you and, say, your credit card company, and easily grabs all that encrypted content in transit, decrypted, no problem.
[Galaxy S I9000 Android Development] yavu:
Will we still have advantages of Android 4.3? Better ram management or system performance?
[Galaxy S I9000 Android Development] gverma1:
So, possibly our i9000 may get 4.3, but not the complete flavour - correct? If yes, then what features/advantages might be dropped? Tks

---------- Post added at 02:58 PM ---------- Previous post was at 02:46 PM ----------

The latest nightly has removed 'Fix Permissions' option from recovery as stated in the changelog. Any particular reason for doing so, since this feature is used quite regularly. Thanks
[Galaxy S I9000 Android Development] 99x:
Yea, I understand that it only supports 2.0, but I meant that ES 3.0 support is not a requirement for android 4.3 since the galaxy nexus has 4.3
[Galaxy S I9000 Android Development] Bejda:
Suspicious guys on previous page,you just have to do this if you want access to developers options and performances settings... really ;)
[Galaxy S I9000 Android Development] narsiliouz:
I don't mean to be funny, it's truth. If You want performance options, You have to do that, and it's on..

Am I funny now :D ?
[Galaxy S I9000 Android Development] or150:
To fix the clock, clear its data from settings->apps. To fix ES file explorer, search for a fix in the last posts, there is a zip that would downgrade Superuser and fix this problem.

About Gmail, try to wipe Gapps' data, there was a zip for this in cm9's thread, if clearing Gmail's data and re-adding your Google account won't work. It might also return your lost contacts.