yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] baciany:
I think yes. I have newest nightky and i had one call. Phone was ringing but thebsreen shows uo later :P

I have smal bug: when i try to go any contact in contacts list i have fc. Tried wipe and still the same. Alsi sync had priblems. It cannot sync conntacts because of some problem message. After one hour of clicking refresh sync it works. But still caant open any contanc
[Galaxy S I9000 Android Development] devloz:
Hello!

The same problem bro. Important to fix [MENTION=3117667]pawitp[/MENTION] ;)

Best regards.
[Galaxy S I9000 Android Development] legend_wok:
important to provide information in proper format (post 1) and logcat.
[Galaxy S I9000 Android Development] nexzor:
It's not an i9000 bug.

Temporarry fix is to add the countrycode, like +49 for germany. After adding this there won't be any FC.
[Galaxy S I9000 Android Development] jeroendj2:
all browsers crash :(
[Galaxy S I9000 Android Development] vpnair:
On latest nightly (11th June), and I do not have this problem. I can open all contacts from both Dialer and People app. I don't have country code in contact. All my contacts (~50) are sync'd with my gmail, and it happens perfectly. Everything stock except for Banks Minimal Gapps from 2-6 and the deletion of a few unnecessary system apks (Email, exchange, everything to do with live wallpapers, all CM apps, etc). Using Dalvik.
[Galaxy S I9000 Android Development] knuckles1978:
No such problem here. I'm running 4.4.3 and I'm using stock browser. Haven't tried any others because I like the stock browser.
[Galaxy S I9000 Android Development] devloz:
Okay, installing Contacts.apk from previous nightly is good as temporary fix. Contact details and sync are working properly ;)
[Galaxy S I9000 Android Development] Paulroberts:
did you turn google now on? it's in settings next to wallpaper and widgets on homescreen if you have the google launcher.
[Galaxy S I9000 Android Development] ciao99:
i'm using trebuchet and nova. Why should i use GL to have trebuchet panel?
[Galaxy S I9000 Android Development] vobbi:
Not yet merged :crying:
[Galaxy S I9000 Android Development] udkSD:
Trebuchet is crashing and when i click some contact it FC.
[Galaxy S I9000 Android Development] vobbi:
it is fixed in the latest nightly 20140613
[Galaxy S I9000 Android Development] mythenmetz:
Hey, can someone help me out: I want install on a friend's phone M7, but I get a status 7 error. When I want to update recovery I get status 0 error. Can someone tell me which recovery I need and how to update (best would be with a flashable zip). Currently cwm 6036 is used.

Thanks in advance!
[Galaxy S I9000 Android Development] tetakpatak:
You need Cyanogenmod 10.2 as first, its stock kernel featurws CWM 6.0.4.5 that is KitKat compatible.

tetakpatalked from Nexus 7 flo
[Galaxy S I9000 Android Development] devloz:
Flash Semaphore 3.4.3 or Neo Kernel Kk, and after reboot to recovery flash CM11.
[Galaxy S I9000 Android Development] King18:
The mobile conmection isn't so good. The Symbol isnt showing full.
[Galaxy S I9000 Android Development] sanguinesaintly:
Recovery lost - help !

I'm running CM11 latest nightly on Galaxy S i9000. System boots fine and USB Mass storage works fine, but recovery seems to be broken. I cannot get into recovery or connect via download. Is there an easy way to flash a new kernel and or recovery from inside a working system ?

EDIT

Got it - ADB saved the day
[Galaxy S I9000 Android Development] knuckles1978:
Have you tried rebooting into recovery from adb command line?

---------- Post added at 04:40 PM ---------- Previous post was at 04:34 PM ----------

Also, there's an app called flashify that can install zips. I've never tried it, I'd rather do it manually. It may help you though if you're stuck.
[Galaxy S I9000 Android Development] sanguinesaintly:
Flashify wouldn't cut it, but ADB got me back. Thanks !
[Galaxy S I9000 Android Development] pawitp:
What did you mean by broken?
[Galaxy S I9000 Android Development] sanguinesaintly:
It was strange. No problem with normal booting. But booting into recovery or download mode just sat on the kernel logo. Was working fine yesterday until I flashed latest nightly. Maybe my trusty i9000 is getting tired. All is well now though.
[Galaxy S I9000 Android Development] ktulu84:
sorry for posting here, i'm from i9001 forum. i've noticed a bug in trebuchet (but it seems to be also in GEL, so maybe is AOSP bug) and i want to know if it is the same for you or it is a device issue. try it with a light wallpaper, itnlooks like the first attached image (notice the shadows on the top and the bottom of the screen), then try this:

-open an app from app drawer and press back button until you come back to home screen (not pressing home button), shadows will disappear like the second attached image

-open an app from home screen and press back button, shadows will come back

[MENTION=3117667]pawitp[/MENTION] sorry if i bother you, but if this is not a specific device issue, where can i submit this?

EDIT: this bug is only on trebuchet and GEL (and maybe Launcher3 in the early CM version it was there before trebuchet return), third party launcher seems not to be affected
[Galaxy S I9000 Android Development] knuckles1978:
If it happens again try removing your battery, holding the buttons for recovery or download mode, then put the battery back in while holding the buttons.
[Galaxy S I9000 Android Development] pawitp:
Cannot reproduce
[Galaxy S I9000 Android Development] ktulu84:
i just noticed how badly i have wrote my post... edited it and changed wrong parts :D btw thank you
[Galaxy S I9000 Android Development] pawitp:
Okay, I've checked again and the bug is there. General bugs are to be reported on jira.cyanogenmod.org, but bug reports from unofficial devices/builds are not accepted.
[Galaxy S I9000 Android Development] ktulu84:
thanks for the info. so what can I do for it?

Inviato dal mio GT-I9001 utilizzando Tapatalk
[Galaxy S I9000 Android Development] :
+1

Same with me on i9000 with NightlyBuilt 2014/06/15

Another method to reproduce:

Lock your phone from homescreen by pressing power button.

Unlock to homescreen.

Voila: Shadow returns.

Me did not notice so far because of wallpaper / background set to nothing.

If there is no way to file a report, just spread the word and someone will take notice. Hopefully..

Best regards,

Frank
[Galaxy S I9000 Android Development] Half Man Half Biscuit:
First time i flashed CynagonMod!

I did a clean fullwipe install,it is really snappy and fast no question!

Flashed latest nightly.

But many things wont work or FC,messaging Fc all the time,every sms client!

Bluetooth isn´t working!

Data+mobile usage can´t disable!

When i reboot phone,there is no PIN to enter!

Rest is pretty nice,anyone else can reproduce some same issues?
[Galaxy S I9000 Android Development] ioannis_m:
Seems to me like you lost the imei number that's why no pin on reboot.

Yoy must flash again an official via odin in order to get it back.

For the FC's check the Gapps if they are the appropriate for the rom.:)
[Galaxy S I9000 Android Development] pawitp:
Flash the latest M build and then use that to report the bug.
[Galaxy S I9000 Android Development] :
Thanks for the quick answer.

Did a clean install of M7 and the bug is there as well.

I am not so experienced so please give me an advice / link where to file my report.

Regards,

Frank
[Galaxy S I9000 Android Development] nexzor:
you have to create an account on jira https://jira.cyanogenmod.org/secure/Dashboard.jspa

before you create a bug search the board if it was already reportet. in this case you can vote for the bug
[Galaxy S I9000 Android Development] :
Very nice, thank you.

This topic has already been addressed and the issue was filed under CYAN-4003.

Voting for it seems to be the way to go.

Thanks again,

Frank

2014-06-17:

jira account created, voted for it and commented on this topic there.
[Galaxy S I9000 Android Development] Angristan:
Good news

https://jira.cyanogenmod.org/plugins/servlet/mobile#issue/CYAN-3170

Issue is re-opened
[Galaxy S I9000 Android Development] Half Man Half Biscuit:
Can you please provide me the link for the M7 download?

Tut mir leid,kann es irgendwie nicht finden,finde nur die nightlies leider :(
[Galaxy S I9000 Android Development] rupeshn:
https://download.cyanogenmod.org/get/jenkins/71639/cm-11-20140609-SNAPSHOT-M7-galaxysmtd.zip
[Galaxy S I9000 Android Development] Half Man Half Biscuit:
Thnx so much buddy :highfive:
[Galaxy S I9000 Android Development] idCyber:
System settings -> display & lights -> advanced settings force close every time. I am on 17/06/2014 nightly, on vacation with a tent , no PC. Can someone grab and post a logcat if you experience the same as me?
[Galaxy S I9000 Android Development] vobbi:
we have to wait, `till it is merged i think:rolleyes:
[Galaxy S I9000 Android Development] magician369:
Hi I installed the ROM but I noticed some battery drain.is it just me?
[Galaxy S I9000 Android Development] Art.:
Guys, is it safe to flash 20140606 gapps on M7? Few days ago there was some kind of alert here, but now it's gone...
[Galaxy S I9000 Android Development] tomasso32:
I flashed gapps-kk-20140606-signed.zip on June 10. Onto M7. The odd thing is that this gapps was 150 MB, compared to 83 MB for the previous gapps-kk-20140105-signed.zip.

Seems to work, but I haven't done exhaustive testing...

Tom.
[Galaxy S I9000 Android Development] Saber:
The reason why the gapps package is bigger is because it includes more google products than the previous version. Also, note that the updated versions of the apps tend to be bigger than the older versions. In terms of stability on the M7 snapshot, the 20140606 gapps is very stable. Note to pawitp: I am finding that the stock internet browser is unstable as it has crashes a few times already.
[Galaxy S I9000 Android Development] bilbonotry:
bug report format, logcat

Envoyé de mon One X en utilisant Tapatalk
[Galaxy S I9000 Android Development] legend_wok:
i am also seeing huge battery drain after a fresh install. i am going to try to find out with which nightly this drain problem started...

edit: where can i find older nightlies? the oldest that is available to me is from 06/11. the cm download site only goes back to the 13th...
[Galaxy S I9000 Android Development] Saber:
You need to make a bug report in proper bug report format, logcat.
[Galaxy S I9000 Android Development] legend_wok:
i think i am very well aware of that. but i need to get more information before making a proper bug report.
[Galaxy S I9000 Android Development] :
Hi, just my observations:

Battery drain was not unusual until 2014-06-15 (i am on that rom since 2014-06-04, updating regularly).

At 2014-06-17 there was huge drain and that rom broke my imei after a sudden reboot maybe due to battery low.

Recharged, went back to 2014-06-15. imei is o.k. And waited till 2014-06-18.

Battery drain seems to be o.k. again by now.

Today installed 2014-06-19 and everything is fine so far.

Short phone calls, just writing a few SMS each day and use WLAN for 2 hrs. a day, GPS and data on less than 1 hr..

Battery life then is max. 2 days with nights in flight mode.
[Galaxy S I9000 Android Development] Saber:
According to the cyanogenmod changelogs (gerrit), there have been issues where the theme engine is not fully compatible on the latest android 4.4.3 and there are various bugs in the overall ui. The 2014-06-19 nightly seemed to have many fixes regarding to these problems but I find it difficult to help identify the problem for you guys. I suggest staying on this nightly I have just mentioned or staying on an older/newer nightly other than the ones that are known to be unstable.
[Galaxy S I9000 Android Development] magician369:
Yes exactly I installed a fresh nightly on 2014-6-15
[Galaxy S I9000 Android Development] knuckles1978:
2014-06-20 is android 4.4.4!

Hopefully this will fix any issues people were having. I heard there were quite a few with 4.4.3 but I never had any myself. In fact 4.4.3 is by far the fastest and smoothest release I've ever seen on i9000. :good:

Edit: I installed 4.4.4 through settings>about phone>cyanogen updates. On first boot I was getting android.process.acore FC. Just reboot into recovery and wipe cache and dalvik and you should be good to go.
[Galaxy S I9000 Android Development] idCyber:
Question : Has ART been optimised over the last months? I mean does it work nice and tidy now with Samsung Galaxy S GT-I9000 ?
[Galaxy S I9000 Android Development] Saber:
[YOUTUBE][/YOUTUBE]

I still wouldn't recommend using art yet until the next major release of android as there are many websites saying that art will be made default in future releases. To stay safe, stick with dalvik for now. I think it will be revealed in the google conference later this month.
[Galaxy S I9000 Android Development] sanguinesaintly:
Every time I've used ART including the last 4.4.3 nightly, I've had freezes and running out of storage messages. Android.phone stopped mostly and just looped, so had to reflash. I would wait until Google (or a good dev) can confirm that it's ready for prime time on the i9000. If it's baked into the ROM then maybe, but I won't hold my breath.
[Galaxy S I9000 Android Development] idCyber:
Sticking with Dalvik for now :D
[Galaxy S I9000 Android Development] fran_xda:
Well I have been using it for 2 weeks now (4.4.3) and only had issues with one app, everything else is working good, better than Dalvik in my opinion.
[Galaxy S I9000 Android Development] Angristan:
When I active ART, all my apps on the SD Card are erased... ^^
[Galaxy S I9000 Android Development] knuckles1978:
Is everyone's in-call dialer screwed up, or is it just mine? And before making a call it takes two attempts to get the dialer number pad to appear.

Also, does anyone else have the problem of the screen going black when making a call, and not wanting to come back on? I have a fix for this one if required.

---------- Post added at 07:37 PM ---------- Previous post was at 07:33 PM ----------

I've tried art a couple of times, and found it to be slower and full of problems. To be fair though it's still under development and nobody has suggested it should be used as daily driver. Best sticking to dalvik for now I'd say.
[Galaxy S I9000 Android Development] :
Hi!

Dialer is o.k. for my. Just one tap on the "receiver" icon brings up the dialer. Can make calls and screen stays on.

Have to say that i cleared cache and Dalvik cache twice after the OTA update because several apps fc'd.

After that everything is fine so far. Knock on wood.
[Galaxy S I9000 Android Development] sanguinesaintly:
The dialer takes a couple of goes before it appears here too.
[Galaxy S I9000 Android Development] didhiy:
Try to check the gapps you used, afaik some gapps coming with google dialer that cause similar problem in lg g2 aosp rom
[Galaxy S I9000 Android Development] sanguinesaintly:
I'm using the latest 2014/06/06 gapps. Strange.
[Galaxy S I9000 Android Development] steevo_bass:
No problem with dialer, but I have this problem too!

I have to press home button to see the screen again!
[Galaxy S I9000 Android Development] :
Checked this again.

No probs with dialer.

Screen goes black when in a call and cellphone held near the ear. Expected behaviour, i know that from a stock S3 mini. It's for privacy reason.

Screen goes on again when looking on the display. No home button needed.

I am on nightly 2014-06-21. Getting better every day. Even 4.4.4 did not break anything for me.

Knock on wood.

Always doing these OTA updates without backup. :rolleyes:

Best reagrds,

Frank
[Galaxy S I9000 Android Development] knuckles1978:
My screen goes black when I bring the phone to my face, but doesn't come back on when a take it away from my face.

Sometimes the home button brings it back on, other times I need to wait for about ten seconds. It was a pain in the ass.

Found a fix by disabling the proximity sensor, which means the screen obviously just stays on in-call now, but that's not a problem. I'd much rather have that than the way it was before. There's been no problem with accidentally hanging calls up with my face either - you'd need to be pressing the phone right against your face for that to happen. It's not happened once to me.

If anyone wants the file and instructions to disable the proximity sensor only, then say and I'll put it up.
[Galaxy S I9000 Android Development] karbon222:
do you know guys about WI-FI AP?, i have problem to enable it, not working :( - nightly 21.06..
[Galaxy S I9000 Android Development] tomasso32:
4.4.4 seems to be using battery pretty fast.

I was wrong about this.
[Galaxy S I9000 Android Development] sanguinesaintly:
---------- Post added at 08:08 AM ---------- Previous post was at 08:02 AM ----------

solved by changing Animator Duration Scale to anything other than 0. I don't like the delay so set to 0.01 sec and keypad pops up first time now.
[Galaxy S I9000 Android Development] The_Wolf91:
Flash semaphore kernel (4.3.x) .tar version with odin. Then wipe data/cache/dalvik/system and restore a nandroid backup or flash a 4.3.x ROM.

Inviato dal mio GT-I9000 utilizzando Tapatalk
[Galaxy S I9000 Android Development] Rohitdahiya:
How to change the DPI settings? Thanks in advance
[Galaxy S I9000 Android Development] pawitp:
After the installation error and while still in recovery, please get the recovery log and post it.

adb pull /tmp/recovery.log
[Galaxy S I9000 Android Development] pataykhan:
So I fresh installed 20131115 build.

Wipe Factory / Data

Wipe Cache

Wipe Dalvik Cache

And only installed this zip (20131115) and no Gapps at all.

And when the ROM boots, I have no dailer. Any idea whats going on. Anyone else with this problem?
[Galaxy S I9000 Android Development] yadavjpr:
There should be a phone app in app drawer. Open Phone app, Click on keypad icon on bottom-mid.
[Galaxy S I9000 Android Development] fmc000:
By manually editing the LCD density property in system/build.prop .
[Galaxy S I9000 Android Development] jaibar:
It looks like editing doesn't stick across rebooting? I also tried to remove some system apps (e.g. email, exchange services and some live wallpapers)- everything looks fine but after rebooting their back again.

Is there any way to override this so I can change build,prop, remove system apps etc? Has it got anything to do with SELinux being on "enforced" state?

Another question- the ROM looks more AOSP than CM? I can't figure out where is the "interface" menu.It's gone from system/settings... I can't actually change any cm features at all.. Now I read in OP that *some* cyanogenmod features are not working and please not to ask about it, but it looks like *none* are working for me, other than cm wallpapers and cm account- all the rest looks like AOSP.

Am I missing something? Is there a way to restore/bring hidden menu (e.g. like pressing many time on build number to bring developer menu)??

[MENTION=3117667]pawitp[/MENTION]- great great work and infinite thanks for bringing this build for us all! I'll keep pressing the thanks button for you at all times :)
[Galaxy S I9000 Android Development] Netmatrix:
First my kitkat is running at 200dpi across reboots maybe your Installation did not gone well.

Second, If you can imagine how dificult is to bring all the cm goodies and insert on 4.4 code, you didn't ask these, therefore I think and maybe Pawitp share my thoughts that we need a base bug free and stable enough to allocate CM code then, in my opinion you should wait some more time...

Enviado do meu GT-I9000
[Galaxy S I9000 Android Development] xandas:
skipping low ram mode

I've got better performance, by deleting from the build prop file, the line "ro.config.low_ram=true". By doing this, I also avoided random reboots.
[Galaxy S I9000 Android Development] pawitp:
"None other than a, b" does count as "some". There's also LED customization, theme support, profiles, superuser, performance settings, CM Updater, etc.

Everytime there is a major version update, we need to restart with a nearly clean slate and it will take sometime before they get reimplemented. (And I'm not the one doing it, other people in CyanoenMod will.)
[Galaxy S I9000 Android Development] pawitp:
You will get better graphics performance (since GPU acceleration is always enabled) at the expense of having less RAM for applications. I've never had any random reboots though and you should report it (see first post) if you experience them.
[Galaxy S I9000 Android Development] vla-wot:
Why not open Google Play problem??? help how open google play please!!!
[Galaxy S I9000 Android Development] octolith:
*sry, wrong post :(*
[Galaxy S I9000 Android Development] Ommadawn101:
missing menu item in settings>security

The option "enable widgets " is missing, under

Settings>security
[Galaxy S I9000 Android Development] pawitp:
Read first post, under FAQ, low RAM.
[Galaxy S I9000 Android Development] Rohitdahiya:
[MENTION=3117667]pawitp[/MENTION] Thanks for such an awesome work you are doing for our SGS.

All the stuff is working nicely. Even OK Google is perfect. Awesome experience except some problems with graphics in a no. of apps

The other issue I am facing is it takes me around 3-4 seconds to go to incoming call navigation. (Little Hang while incoming call)

I am curious to ask one question:

Texas Instruments released the binaries for Galaxy Nexus to support kitkat. Aren't these binaries able to give advantage to our SGS?
[Galaxy S I9000 Android Development] baciany:
How you did "ok, Googlw" working?

Im Polish language and not work even if im speaking english
[Galaxy S I9000 Android Development] CeesitarJet:
Read FAQ in first post.

Inviato dal mio GT-I9000 utilizzando Tapatalk
[Galaxy S I9000 Android Development] s3icc0:
incredible pawitp

thanks again
[Galaxy S I9000 Android Development] smjrifle:
[MENTION=3117667]pawitp[/MENTION] you are one of the best developers ever :highfive:
[Galaxy S I9000 Android Development] sanguinesaintly:
GApps packages

Has anyone tried using SlimROM GApps (latest 4.4.4 beta version) on CM11 ? Just curious.
[Galaxy S I9000 Android Development] lordlambda:
Can't confirm this.
[Galaxy S I9000 Android Development] BeriCud:
I don't think so I use today last CM Nightly 4.4.4 and I think that it is the same as previous Nightly 4.4.3 or 4.4.2.
[Galaxy S I9000 Android Development] devloz:
Impossible, changes done are mainly focused on OpenSSL vulnerability (a'la Heartbleed). Security fixes, nothing more.

++ 90% of these fixes were applied to CM before Google made idea to push fix release to public, so CyanogenMod team had really small amount of work (mainly bumping version number :)).

Best regards.
[Galaxy S I9000 Android Development] tomasso32:
I was wrong. Battery drain is OK.

[I found the battery drain fast because my Garmin/Navigon maps updated via wifi after the cache/Dalvik cache clear, and that's a lot of data, with GPS turned on and screen on, at the same time].

Tom.

---------- Post added at 12:05 AM ---------- Previous post was at 12:03 AM ----------

I was wrong about battery drain on 4.4.4.
[Galaxy S I9000 Android Development] karbon222:
Problem nightly or a problem generally CM 11? Could somebody let me know on this question? I do not know whether to wait for a fix or return to 10.2

But it seems to me that it worked..

I ask again because it's important for me.
[Galaxy S I9000 Android Development] rupeshn:
I am on nightly 22.06 and WiFi AP works fine.
[Galaxy S I9000 Android Development] el_dobre:
I had the same problem with a S4 and a S3 (with CM11 M7), I resolved recalibrating the proximity sensor without disabling it... maybe you can do that with galaxy s too.
[Galaxy S I9000 Android Development] knuckles1978:
I'll give it a go thanks. How do you recalibrate the proximity sensor?
[Galaxy S I9000 Android Development] bilbonotry:
You can use rezound proximity sensor app, mainly play with the first slider and test the sensor. The app displays near if the sensor detects something, else displays far.

Envoyé de mon One X en utilisant Tapatalk