yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] tetakpatak:
Bootloader

Visually, the only difference I could obviously see with my Froyo bootloader was the fact that after flashing a Semaphore kernel I was not able to see in CM10.2 and CM11 Semaphore logo (attached) right after rebooting my device. The proper order of appearance is: splash screen (Samsung, or your modified one) then few seconds of attached Semaphore logo with just one short interruption, then the CyanogenMod boot animation. With Froyo bootloader I just saw the splash screen and afterwards imediatelly the CM boot animation.

In performance, just as I wrote before: CM11 was quite laggy. Since I've flashed GB JVU bootloader: the same CM11 nightly worked fast, smooth, just amazing! If you're not sure about your phone, just flash GB bootloader now afterwards- it takes only 5sec (check link in my last post here). This may not have any logical explaination, but how can anyone explain Ommadawn's nummerous lags, while for all else the same builds work just fine? I've flashed also on my P5110 Tab a JB bootloader (as I had ICS one on it before) and it also improved its performance.

I hope pawitp won't get mad on me mentioning the custom kernel, for I'm not really going off the topic.
[Galaxy S I9000 Android Development] Ommadawn101:
Let me reply your technical question with another technical question.

Could I still have Froyo bootloader if I have flashed at least 10 times Stock GB (3 parts+pit512), using Odin?

I believe you know the answer to that.

And to those who think I am being provcative, rude, and black campaigning:

I have been using CM since the early days of cm10, and I loved every minute of it.

The past few weeks have been unbearable
[Galaxy S I9000 Android Development] tetakpatak:
I am not sure about that, if you've never checked the option "Phone Bootloader Update" and set Bootloader as fifth file in Odin and if your phone was delivered:

it is possible you still have a Froyo bootloader.

Or was it with Eclair when you got it? Was it new then? Maybe Eclair is on it still.

Can anybody of skills answer this question? Developers?

I am highly interested in getting an explaination.

(PS, I don't find you're rude, mate :) )
[Galaxy S I9000 Android Development] pawitp:
The bootloader gets updated regardless of the settings as long as the package includes a bootloader.
[Galaxy S I9000 Android Development] tetakpatak:
Thx a lot for this info!

Is there any way to recognize if the package includes the bootloader?
[Galaxy S I9000 Android Development] ts1506:
Search for EZBase GB bootlosder for i9000. Put it in Bootloader field in Odin and flash.

I use it, it works perfectly
[Galaxy S I9000 Android Development] saszseb:
GB bootloader has nothing to do with speed of CM10.2.
[Galaxy S I9000 Android Development] tetakpatak:
Thanks :)

I know about it, as soon as you wrote me here in the thread about the bootloader last week, I've checked it and found the thread of [MENTION=340238]nitr8[/MENTION]. He isn't active since longer than one year.... hope he is well. His download links in the OP post are dead and I've posted (last so far) a link where his files still could be downloaded. I think it is a JVT kernel & bootloader (uncoded zip) yes, his file includes also the kernel.

I've extracted only the kernel from JVU firmware and uploaded it to the OP post of my sticky help thread for the i9000. So whoever isn't sure, can download it there and flash. It is up to date :)

[MENTION=3797004]rmsinaga[/MENTION] mate, I remembered how you could check it: App Android System Info!

---------- Post added at 07:47 PM ---------- Previous post was at 07:43 PM ----------

I had no problem there, but with the CM11.
[Galaxy S I9000 Android Development] zri:
touch focus and panorama working again :victory:

---------- Post added at 03:35 PM ---------- Previous post was at 03:30 PM ----------

i agree, two wrongs don't make a right..
[Galaxy S I9000 Android Development] fishears:
Camera still FC on picture size change though...

sent from somewhere..
[Galaxy S I9000 Android Development] AndroidBR:
Are there any missing features on CM 11 when compared to CM 10.1 or 10.2? For example: screen brightness control by sliding the status bar, or battery icon with the percentage on status bar (not the circle one). I'm only asking because I've flashed Dec 15th nightly on my Galaxy S i9000 and those features are missing... I'd appreciate if someone could tell me if these features are present again. Thanks!
[Galaxy S I9000 Android Development] mejok:
1. someone can explain me what is ART in cm11?

2. what is the known bugs in this ROM?

thanks alot for all developers
[Galaxy S I9000 Android Development] fishears:
Hey, Christmas was a couple of days ago - no more gifts! Read the thread and use Google ;)
[Galaxy S I9000 Android Development] solar666:
First of all you should read the OP (first comment by pawitp) it explains your 2 question.

For ART you can read the articel of following link:

http://source.android.com/devices/tech/dalvik/art.html

And for the 2nd question there is already in the OP statement stated as "Known Issues".
[Galaxy S I9000 Android Development] mejok:
what is recommend to download, the ART gapps or without ART gapps?

thanks
[Galaxy S I9000 Android Development] minghi1:
Only for knowledge and curiosity, what is the presumable cause of delay in incoming call? In a phone should be a priority bug. I don't see code submitted to http://review.cyanogenmod.org. A device with 510,208 installations of cyanogenmod deserves more attention. Thanks for the hard work on these old but extraordinary phone. :cowboy:
[Galaxy S I9000 Android Development] gverma1:
I agree that delayed caller image on incoming call should be a very high priority bug. Surprisingly it has not been solved even after so many days. I have a friend with nexus 4 with stock kitkat and that phone doesn't have this bug at all. Somebody on slimkat thread was also saying they don't have this bug.

I say this as a firm follower of cyanogenmod and with due deference to Pawitp. But high time this bug was removed.
[Galaxy S I9000 Android Development] elitevet:
Well, now that you know what ART is, you probably also know that it is not currently supported by CM and you probably won't be using it in a foreseeable future with this ROM, thus you should, probably, download the non-ART GApps package.
[Galaxy S I9000 Android Development] ciano865:
I have CM11 on nexus 4 and there is no delay at all. Just for feedback.

Tapatalked with Nexus⁴
[Galaxy S I9000 Android Development] pawitp:
It might have the highest number of users, but there's only one developer (who also maintain other devices). It may deserve more attention, but will any of the developers lurking in the thread step up and give it the attention it deserves?

I believe it is, at least partially, a hardware performance issue.
[Galaxy S I9000 Android Development] pawitp:
I've checked again and the call delays I'm seeing are at 2-second at max (which is how long the device takes to initialize the GUI and is, IMO, within acceptable limit). As you may know, it is very hard to fix a problem I cannot reproduce myself.

For those with worse delays, I suggest a full wipe and check if the problem still exists or not. Then gradually install the applications you use to check for potential causes of the issue.

(If you say you don't want to wipe, I'm not forcing you. But remember that if you want me to put effort into this, you need to put effort into it as well. The more information you report, the more I might know what might be causing the issue.)
[Galaxy S I9000 Android Development] saszseb:
Me too. http://pastebin.com/ER9fbtZV
[Galaxy S I9000 Android Development] gerald7:
so I was trying to go from 10.1 > 11... and I downloaded the latest nightly and installed without a hitch... but once the phone booted, I got two errors

" Unfortunately, the process com.google.process.location has stopped. " and " Unfortunately, Android Keyboard (AOSP) has stopped". I couldnt do anything without a keyboard. any ideas?
[Galaxy S I9000 Android Development] tazd:
did u flash the new gapps linked in the first post ? if not do :)
[Galaxy S I9000 Android Development] tetakpatak:
In-call display delay is not a bug.

I can't belive this oversized discussion here, is 2s so bad? I tought at first 20s was meant, zero not typed. Now I see some people really mean this seriuosly.

I made no wipe, flashed dirty over CM10.2 and have delay of not longer than 2s.

Look at CPU and RAM of N4 and compare it to the i9000.

It is only thanks to pawitp that we can use the i9000 and enjoy >4 Android versions. Think of what will be if he for any reason quits this and use his time rather with his friends or family?

I use several much newer devices than the i9000 and none of them has so well working CM11 like the i9000 has- that is only thanks to pawitp's very great skills- and tireless work on this.

Please show bit more respect to dev's hard work that you are allowed to benefit for free and don't oversize some little things like this one.
[Galaxy S I9000 Android Development] pawitp:
The fix was only recently merged. Should be fixed in today's (1228) nightly.
[Galaxy S I9000 Android Development] kbal:
Anybody using Skype with this?

Video calls are buggy as hell (for me), most of the times it crashes.
[Galaxy S I9000 Android Development] saszseb:
Yes. It works.

Tapatalk-kal küldve az én SM-N9005-el
[Galaxy S I9000 Android Development] bunbury:
I agree 100% with you
[Galaxy S I9000 Android Development] mobilequest:
I'm really surprised that no one already mentioned this. I flashed the newest cm 11 nightly and installed about 80 apps on my phone and soon got the "insufficient storage available" error message in the play store although there is plenty of space left. I tried everything and eventually found out that after wiping the dalvik cache the problem is gone. Not only that, after wiping the dalvik cache the phone is also faster and smoother but eventually I have to wipe it again.

This only happens with cyanogenmod 11 :confused: I'm surprised that I'm the only one who mentions this. Anyone had the same experience and what can you do about it??
[Galaxy S I9000 Android Development] twinky444:
Webview

[MENTION=3117667]pawitp[/MENTION], recently I saw this commit: https://github.com/TheWhisp/android...mmit/8600760b0fbdca7c3c9e0f2aa77a84c51215856d

If I understand correctly, could this force the device to stop using the new chromium vebview? I mean if this could fix that slow/laggy AOSP browser issues & make incognito mode work again?
[Galaxy S I9000 Android Development] jv.batista:
that is something that I never thought-out doing. maybe I will try it out when my phone becomes to slow...

ps: if that dalvik cache is the dalvik run-time cache it actually makes sense for the phone being faster. There's any way to do that on the fly, without having to reboot the phone?
[Galaxy S I9000 Android Development] nekuy:
Hi,

In-call display delay is considered as a bug, at least for KitKat. KitKat aimed to run on low-mem and/or lower-end device. Mobile phone's primary concern should be flawlessly communication. But delayed display is a problem for our phones.

This is not disrespect to CM team and Pawitp. Thanks a lot to CM Team and especially to Pawitp for using GT-i9000 with latest Android version.
[Galaxy S I9000 Android Development] theo2:
I flashed 2013-12-27. i cant delete items (apps) on the screen.
[Galaxy S I9000 Android Development] minghi1:
I agree with your considerations. However, find solutions to problems is a source of pride for a developer. Could be due to a delay in the sql engine that retrieves the contact picture? In this case, the delay should be proportional to the numbers in the phonebook. For the moment, better to stay with the excellent cm10. KitKat aimed to run on low-mem devices but Google code this time is not a real step forward. Happy New Year to all.
[Galaxy S I9000 Android Development] elitevet:
EDIT, No Tapatalk, I was quoting this from just above:

If everybody stays on 10.2 this will never get fixed and the maintainer of the device has just explained why a couple of posts above.
[Galaxy S I9000 Android Development] RammsteinNicCage:
Yeah... my post is from over three years ago and I don't have this phone anymore... thanks for the help though?
[Galaxy S I9000 Android Development] elitevet:
:laugh:

:laugh::laugh: Teh XDA mobile app is having hallucinations, I was replying to minghi1's post from TODAY 09:15 PM.
[Galaxy S I9000 Android Development] elitevet:
[MENTION=3117667]pawitp[/MENTION]

Latest nightly, all stock. GEL Launcher. about 140 apps installed. No wipes since 10.1 -> 10.2

Phone is connected to PC via USB, logcat is taken via ADB.

Logcat starts.

Phone is Idle and probably sleeping after I pressed the power button, I dial in...

The Phone is ringing, after the delay of about 4 seconds I have the UI loaded to a point where I can answer it.

Answer Call. Disconnect Call

Logcat stops.

I find the following lines in the logcat:

W/IInputConnectionWrapper( 4927): showStatusIcon on inactive InputConnection

I/InCall ( 4927): InCallActivity - onResume()...

I/InCall ( 4927): ProximitySensor - ProximitySensor{keybrd=0, dpad=0, offhook=0, hor=0, ui=1, aud=EARPIECE}

I/InCall ( 4927): ProximitySensor - turning off proximity sensor: already released

I/WindowManager( 515): No lock screen! windowToken=android.os.BinderProxy@420e06f8

I/ActivityManager( 4927): Timeline: Activity_idle id: android.os.BinderProxy@420775b8 time:3098575

I/ActivityManager( 4927): Timeline: Activity_idle id: android.os.BinderProxy@420775b8 time:3098588

[COLOR="Red"]D/PowerManagerService-JNI( 515): Excessive delay in autosuspend_disable() while turning screen on: 4533ms[/COLOR]

D/PowerManagerService-JNI( 515): Excessive delay in setInteractive(true) while turning screen on: 22ms

[COLOR="red"]I/ActivityManager( 515): Process com.google.android.apps.plus (pid 5113) has died.[/COLOR]

D/SurfaceFlinger( 144): Screen acquired, type=0 flinger=0x40913450

D/SurfaceControl( 515): Excessive delay in unblankDisplay() while turning screen on: 212ms

D/LightsService( 515): Excessive delay setting light: 520ms

I/ActivityManager( 515): Resuming delayed broadcast

E/AudioSink( 147): received unknown event type: 1 inside CallbackWrapper !

I/ContactLoader( 5041): Registering content observer for content://com.android.contacts/contacts/lookup/XXXXXXXXedited-outXXXXXXXXXXXX

[COLOR="red"]I/ActivityManager( 515): Process com.android.settings (pid 5165) has died.[/COLOR]

I/InCall ( 4927): CallCommandClient - answerCall: 3

D/PhoneUtils( 929): answerCall(INCOMING)...

A bigger snip of logcat attached ... If you want the full one, please let me know.

Hope this helps
[Galaxy S I9000 Android Development] pawitp:
Search for "/datadata" and read about it.

The code's probably not in CM and it's a bad idea for various reasons. Mainly, app compatibility. When developers use WebView on KitKat, they expect to be able to use all the new features of Chromium Webview. Breaking this assumption can contribute to Android fragmentation in a very bad way.

Please don't put word into other people's mouth. If you want to fix the bug and be proud about this, go ahead. However, I don't like being told, "fix this bug and you'll be proud".

Is the delay always 4 seconds or does it vary? The symptom of many things exceeding the time limit suggests than something is eating CPU/disk in the background.

Please capture a timestamped logcat (adb logcat -v time) and dmesg (though I don't think it'll reveal much).

Also try disabling these apps (one by one): LockClock (cLock), Hangouts
[Galaxy S I9000 Android Development] gerald7:
hehehe I did flash gapps.. but I grabbed the old one.. its working now, thanks a lot ! :good:
[Galaxy S I9000 Android Development] kbal:
Skype video call logcat

Attached log cat when receiving Skype video call.

4 calls:

1- nothing happened,

2,3- video call working OK

4- video call crashed on answer.

If somebody could look at it.
[Galaxy S I9000 Android Development] pawitp:
The process got killed, but I don't see any force close/crash log. Maybe it got killed because there's not enough RAM.
[Galaxy S I9000 Android Development] Petrovski80:
Thanks for this ROM pawitp. I have to use the old SGS from my wife for a couple of weeks since my Nexus 5 is sent back to my retailer for a warranty claim. I have to say I'm amazed how good and smooth CM11 runs on this old phone. Coming from Gingerbread stock, it's almost like having a new phone. And when using Greenify to hibernate every user app that wants to run in the background except Whatsapp, things work out well even with a lot of apps installed.
[Galaxy S I9000 Android Development] kbal:
I suspected it could be something like this. It's crashing even with bigmem semaphore & fresh install.

Thank you.
[Galaxy S I9000 Android Development] crofalcon:
Would you mind telling me where I might download it, I tried googling it but to no avail.

Sorry if the answer is something obvious.

Thanks in advance
[Galaxy S I9000 Android Development] ts1506:
http://bit.ly/KdzOyO

First link , was that too hard ?
[Galaxy S I9000 Android Development] freakymod2120:
Hi,

will the feature to input the telephone-number under Setting ==> Device ==> Status come back in CM11 at some time or will this point in menu get delete?

When I`m in the dialer app und want to get the number field (via hitting the middle button) first after flashing or rebooting the device, no number-field is shown ...it is shown only with the second time i hit the button ...is it normal???

Do some others have the same behaviour? Hope i descriped it generally understandable...:o

Or is it because of the known issue "Incoming calls sometimes take a long time to display" ?

But this issue i have never had ...

Thanks !!!:good:
[Galaxy S I9000 Android Development] pawitp:
Will be available when http://review.cyanogenmod.org/56538 is merged
[Galaxy S I9000 Android Development] nekuy:
http://bit.ly/Jn6x3U Finding a link sometimes doesn't mean finding the file :)
[Galaxy S I9000 Android Development] crofalcon:
Thanks :)
[Galaxy S I9000 Android Development] freakymod2120:
Hey perfect you`re great...

Does this include my "problem/feeling" within the dialer-app and the number field???

---------- Post added at 07:26 PM ---------- Previous post was at 07:24 PM ----------

Does someone know what the app "PacProcessor" is for???
[Galaxy S I9000 Android Development] tetakpatak:
I have attached here in the OP an extracted GB bootloader (JVU) it is up to date:

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

The link ts1506 posted you contains not only a bootloader but also a GB kernel, so if you reboot right after flashing it with Odin, you will have a bootloop or even brick!

That bootloader is OK, but flash right after that while still in DL mode (uncheck auto-reboot) Semaphore 3.4.0 kernel as tar file, or reboot directly to recovery mode and flash zip of Semaphore, or Mackay kernel for 4.4. ROMs, or pawitp's CM11 stock kernel (if he ever provided the download link for it).
[Galaxy S I9000 Android Development] ts1506:
I never flash bootloader except when downgrading to GB, so dunno about that.
[Galaxy S I9000 Android Development] tetakpatak:
Yep, normally it isn't even necessary- as each stock GB ROM contains a bootloader as well.

I've needed the extracted bootloader only for the reason that I've upgraded directly from Froyo to CM10.1 and didn't ever have GB bootloader pre-installed before.
[Galaxy S I9000 Android Development] pawitp:
No. I cannot reproduce the issue.

To process proxy automatic configuration scripts.
[Galaxy S I9000 Android Development] tetakpatak:
Truly great CM11, pawitp :)

All other, much newer devices where I've tried haven't got yet such great working CM11 builds like yours for the old good i9000 !
[Galaxy S I9000 Android Development] sas_sas:
It is wonderful respons...
[Galaxy S I9000 Android Development] freakymod2120:
Thanks ...

Okay it is only the first time after flashing or rebooting the device...afterwards it is fine, maybe it is normal because of standard-initialization ...can a logcat or an other logfile help? Or any advice where to find some infos about it ?
[Galaxy S I9000 Android Development] pawitp:
I'd just ignore it. You could try reproducing it after a fresh wipe and follow the bug report format if you're adamant about it.
[Galaxy S I9000 Android Development] ioannis_m:
Does anybody tried to upgrade CM11 to todays nightly?I am getting an abort message with the red triangle.:rolleyes:

edit:The file is only 136mb from the cyanogen official link,double checked it.Pawitp could you inform the team of the problem?
[Galaxy S I9000 Android Development] -Tex-:
Is delay on incoming/outcoming call faixed in latest nightly ?
[Galaxy S I9000 Android Development] minghi1:
Attention !! the downloaded file is incomplete. Today nightly dimension is 191.28 MB. Check the correct md5sum:c6470d2ddd9125d733ba339d0e39086f. Try another download at http://download.cyanogenmod.com/?device=galaxysmtd.

---------- Post added at 04:35 PM ---------- Previous post was at 04:28 PM ----------

Scroll back through the posts and you'll get the answer.
[Galaxy S I9000 Android Development] saszseb:
No prob using CyanDelta.

Tapatalk-kal küldve az én SM-N9005-el
[Galaxy S I9000 Android Development] twinky444:
No problem, flashed 4 hours ago... Working fine, size is also the same. Unstable internet?
[Galaxy S I9000 Android Development] krueger80:
Dualshock 4 via Bluetooth

Does anyone succeed to pair and use the Dualshock 4 (PS4 game controller) on our Galaxy S phone? It is working on my Windows 8 laptop and apparently on BeanStalk ROM 4.3 on a Nexus 4 device (http://youtu.be/57sBQgegjMI). I also tried on my Nexus 7 2013. I can pair the game controller, but then nothing works!

When I try to pair on my Galaxy S, I see the "Wireless Controller" and if I tap on it it ends up with error "Couldn't pair with Wireless Controller" (because Bluetooth discovery is over on the Gamepad).

---------- Post added at 03:45 PM ---------- Previous post was at 03:15 PM ----------

What is your--

Phone model: GT-I9000m

Radio (baseband): I9000XXJVU

CM version: 11-20131224-NIGHTLY-galaxysmtd

CM Download url: from CM updater

Gapps version: gapps-kk-20131208

Did you--

wipe: no

restore with titanium backup: no

reboot after having the issue: yes

Are you using--

a task killer: no

a non-stock kernel: no

CMSettings/Performance settings (other than stock):

ART Runtime:

other modifications:

Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:

When I try to pair the Dualshock 4 controller on my Galaxy S, I see the "Wireless Controller" and if I tap on it it ends up with error "Couldn't pair with Wireless Controller" (because Bluetooth discovery is over on the Gamepad)
[Galaxy S I9000 Android Development] pawitp:
Sorry, can't help you here. The last console I had was the PS1 :P

If you find out how it's fixed on other devices though, please inform me and I'll port it over.
[Galaxy S I9000 Android Development] gerald7:
I left my phone on the desk whole day, as you can see from the screen capture, suddenly the battery decided to take an epic nose dive. Maybe I need to get a new replacement battery. Heh.
[Galaxy S I9000 Android Development] saszseb:
3G enabled? Use 2G if you don't need mobile data!
[Galaxy S I9000 Android Development] nameh:
Hi,

I am not surprised by that drop, I am more surprised by those cca 8 hours where you had a total decrease of cca 3 %. How do you do that? If I leave the phone sleeping I get a drop of approx. 2-3 % an hour (3g disabled).
[Galaxy S I9000 Android Development] gerald7:
it does not have a sim card, just a spare phone now... after S2, and S3

I didnt do anything. Just left the phone as it was. but I didnt use it also, just wondering why suddenly it decided to nose dive to 2 %
[Galaxy S I9000 Android Development] Amrod_Ringeril:
Hi everyone!!

Has anyone experienced an increase of battery use (I have currently android OS in 21%) with the latest nightly?

PS: Happy 2014!!!