yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] DerRomtester:
I dont know what i did wrong but i get this error with cwm recovery.

E:Can't make /tmp/update_binary

Kernel is booting fine and i can acces the recovery.

Already added your commit and ramdisk and ramdisk_recovery are using .cpio

i am using non standard method of ramdisk integration..
[Galaxy S I9000 Android Development] sanguinesaintly:
Glad I'm not alone - I got the same error this morning. Installed Semaphore tar file with Odin to get going again.
[Galaxy S I9000 Android Development] DerRomtester:
This is not a problem with cm kernel only with NEO-KERNEL. CM kernel is working fine only i made some mistakes but i dont find them.
[Galaxy S I9000 Android Development] sanguinesaintly:
That's right - I'd already been using Neo Kernel with CM11 - love it !
[Galaxy S I9000 Android Development] tetakpatak:
[MENTION=4804871]DerRomtester[/MENTION] I really highly admire that you have joined the development for i9000. Alone the idea to patch the CM kernel with my beloved TWRP is great.

But I have one more very serious question: why wouldn't you get PhilZ contributor? Phil3759 has totally opened the source of PhilZ recovery just two days ago. We would just need touchscreen to be fixed. Phil has already compiled it with pawitp's old kernel (pre-M4).

I unfortunatelly really can't afford more time to dedicate to this, I've tried to get from pawitp the newest kernel sources and repo for Phil but never got an answer. Soon my kind-of off year will be finished and I will have much less time for XDA when I fully return to my obligations, although I love this forum and Android development.

I really highly appreciate to see people who bring such energy in android development, like pawitp does since years- and kind of imagine to feel also from you a big motivation to rock for the i9000 :D
[Galaxy S I9000 Android Development] DerRomtester:
The problem is i would not call me a developer. My c++ skills arent good and i dont know much about compiling a recovery. If anyone can fix this touch problem, i add philz touch recovery to my kernel. Also i am a bit busy with school so i dont have much time at improve my skills.
[Galaxy S I9000 Android Development] tetakpatak:
Everybody has started somehow, at some point ;)

Step by step, one can come quite far.
[Galaxy S I9000 Android Development] tomasso32:
OTOH, it's a good idea that testers don't do much coding - they may excuse or miss issues...

Tom.
[Galaxy S I9000 Android Development] pawitp:
PSA: Please avoid going off-topic. Discussions of other kernels, recoveries, etc. are considered off-topic and should be discussed in their respective threads.
[Galaxy S I9000 Android Development] sanguinesaintly:
Sorry
[Galaxy S I9000 Android Development] Trainer_H:
pawit, are you trying to solve the SystemUI bug?
[Galaxy S I9000 Android Development] true_lies:
I think the fix is included in the latest nightly 20140513.

I've flashed it and haven't had a systemui crash/FC after a day's use
[Galaxy S I9000 Android Development] rupeshn:
Thanks, last time when i tried nightly 20140507 (before the system ui issue was known), I reverted back to nightly 20140407 but since then lost incoming calls, notifications stopped, usb mounting not working (usb enabled in developer options) since then. Tried a factory reset, formatted /system didn't help.

Will try this nightly to see if this sorts all my issues.
[Galaxy S I9000 Android Development] geckoas:
I also had this hope, but after 10 hours of operation with Nightly 20140513 I had a sudden reboot and then again the "systemui was stopped" message again and again.

Also my custom picture wallpaper was reverted to the standard of the theme.

sent from my galaxy I9000 running CM11 with tapatalk
[Galaxy S I9000 Android Development] ioannis_m:
Same here and also an old problem appeared again....unknown sound both ringtone and notifications every reboot happens and even if i normally shut it down and boot it again.

Can anyone confirm?
[Galaxy S I9000 Android Development] pawitp:
Because it's a fix for an unrelated bug, not the bug you're experiencing.
[Galaxy S I9000 Android Development] rupeshn:
So how do we resolve this issue, I am on nightly 20140407 with practically a lot of functionality broken.

Do i need to go the odin way to reinstall or is there some other way this can be resolved.

Thanks
[Galaxy S I9000 Android Development] pawitp:
I'd appreciate if you read the last few pages before asking. You'd either have to wait until it's fixed or go back to M5.

The issue is being looked here: https://jira.cyanogenmod.org/browse/CYAN-4047
[Galaxy S I9000 Android Development] marcedli:
first try to wipe data from recovery, most of the times it's enough.
[Galaxy S I9000 Android Development] rupeshn:
Had done that earlier, will try M5 as suggested with wipe data & system
[Galaxy S I9000 Android Development] devloz:
CM nightly destroyed my phone.

Hello!

On 20140512/20140513 nightly i have issues too. I was forced to wipe everything to continue using phone. Now on 20140514 and will move to 20140515 nightly.

Bugs i've occured (before wiping):

Bug 1: Trebuchet was FC'ing and i was forced to cleand data.

Bug 2: In Settings/Applications i had "-5834583405834905830" bytes used and "1.4" GB free (LOL :eek:).

Bug 3: Every Google related application went to FC's.

Bug 4: I was forced to flash Semaphore kernel via odin to boot Android (kernel soft-bricked device).

"Have you flashed properly?" - I'm using procedure 'ROM -> GApps -> Reboot'.

"Are you using stock CM kernel?" - Yeah. Flashed Semaphore only for unbrick procedure.

Best regards.

PS: Regarding to bug #2, i can post ScreenShot.
[Galaxy S I9000 Android Development] rupeshn:
Did factory reset and formatted /system. Installed M5. Restored /data.

Still the following issues persist

1) Incoming calls get dropped with line busy tone, outgoing works fine.

2) USB mounting not working (option enabled in Settings -> Developer Options) in Linux & Windows

3) Notifications not working

4) Screen Lock also doesn't work.

I am on stock kernel.

Please advise on what needs to be done to get this sorted.

Thanks.
[Galaxy S I9000 Android Development] ioannis_m:
I also have the 2 . 3 . 4 issues.:eek:

EDIT:Also the incoming calls get dropped.What the...???
[Galaxy S I9000 Android Development] pawitp:
Restoring /data may not work properly when the backup is made from a newer version of the ROM (or when a downgrade is done without wiping). You need to wipe and DO NOT restore /data made from a newer version.

Did you restore /data or didn't wipe? Read above.
[Galaxy S I9000 Android Development] ioannis_m:
I did a full wipe + system and then i indeed restored data from M6 to M5.You where right pawitp.:good:

I'm currently flashing cm-11-20140515-EXPERIMENTAL-systemuirevert-test-galaxysmtd.zip clean install to see how the UI will go.:D
[Galaxy S I9000 Android Development] rupeshn:
Oh, so i need to wait for an update or otherwise format data and loose all existing data. :(
[Galaxy S I9000 Android Development] pawitp:
You (or anyone else experiencing the System UI crash issue) can try http://download.cyanogenmod.org/get...PERIMENTAL-systemuirevert-test-galaxysmtd.zip.
[Galaxy S I9000 Android Development] mongoose:
Have no SystemUI crash anymore with cm-11-20140515-EXPERIMENTAL-systemuirevert-test-galaxysmtd.zip build.
[Galaxy S I9000 Android Development] abobobilly:
[MENTION=3117667]pawitp[/MENTION]! That issue where screen wakes up late in an incoming call ... is that issue fixable? Just curious to know, if there is a fix underworks.
[Galaxy S I9000 Android Development] tetakpatak:
It is not an issue. The phone is just a bit too slow for KitKat.

The delay affects all KK roms and can not be fixed.

tetakpatalked from Nexus 7 flo
[Galaxy S I9000 Android Development] CatalystWon:
Where is this documented? Could you provide a link for that?
[Galaxy S I9000 Android Development] pawitp:
20140517 contains a fix for the System UI crash bug, please test.
[Galaxy S I9000 Android Development] tetakpatak:
If you have regularly checked all pawitp's posts in this thread, you would woukd not have to search for the links.

tetakpatalked from Nexus 7 flo
[Galaxy S I9000 Android Development] rupeshn:
Been using this for over 12 hrs, not seeing any issue probably too early to actually comment.

The issues mentioned earlier are still there .... installed this nightly without factory reset as I am still not comfortable in leaving out /data (restore), can't afford to loose old data.
[Galaxy S I9000 Android Development] true_lies:
Have you tried downgrading back to gingerbread and then doing a clean flash?

---------- Post added at 07:15 AM ---------- Previous post was at 07:09 AM ----------

Downloaded and flashed the latest nightly 20140517. so far all good, no systemui crashes after an hour or so usage.
[Galaxy S I9000 Android Development] idCyber:
20140517 working great as the 20140515 experimental release. No SystemUI crash when coming out of an app and pulling the status bar down so far. ty pawitp !
[Galaxy S I9000 Android Development] pawitp:
So, case closed.

You should thank Clark for the patch (http://review.cyanogenmod.org/64114).
[Galaxy S I9000 Android Development] zuphus:
About Luminosity/Proximity sensors

Hi,

few weeks ago, I reported a bug that occurs when I start a phone call (the screen becomes black and unresponsive). Few days later I recognized that the luminosity sensor does not work anymore (it reports 4 lux in the brightness adjustment screen). Then I discovered that luminosity and proximity sensors are on the same chip, so I thought that the black screen is due to the broken proximity sensor. I then replaced the broken hardware part with a new one, but both problems are still there.

Going back to stock ROM does not solve as well.

In short, I was wondering if there is an "hidden" command that can enable or disable these sensors.

I found a possible solution on this thread, where it is explained how to "re-calibrate" the sensors, but I didn't find any file such a proximity_cal file in my filesystem..

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

In addition, I tried several codes from the dial app, but most of them are not working (e.g. the *#0588# code, which should open the proximity sensor test): is this normal?

Any hint?

Ciao,

Marco
[Galaxy S I9000 Android Development] rupeshn:
Didn't try Gingerbread, but will that solve my issue if i restore my /data.
[Galaxy S I9000 Android Development] King18:
Will the Mackay Kernel work with the M6 Version????
[Galaxy S I9000 Android Development] :
That's great! Are there any plans to release M7 sooner to have this issue fixed? I'm on M6 and facing this very often and badly need this fix applied. Can I safely flash latest nightly now and then to next M series without wipe?
[Galaxy S I9000 Android Development] nexzor:
i would say you could flash this nightly and after this m7. i think the codefreez for m7 will be after this nightly, but you can´t be 100% sure. as stated on the cm-webside switching between releaschanels is not recommandet.

so better make a nandroid of your m6, flash this nightly and then m7. if aniting goes wrong you can easyly flash the nadroid an straight afterwords m7 and you should be good, becouse you didn´t switched the releaschanel in theroy.
[Galaxy S I9000 Android Development] Angristan:
I confirm that the system ui bug is solved :D
[Galaxy S I9000 Android Development] Black.Hawk:
I don't have access to internal SD card via USB ,just the memory card ...

by the way...

Is there a way to make the status bar transparent ?
[Galaxy S I9000 Android Development] iamnotkurtcobain:
Instagram too. Almost everywhere. And as you said in google now results too.

What could be the reason? On my stock kitkat on nexus 7 is all ok!

Could it be fixed on cm11?

Gesendet von meinem Nexus 7 mit Tapatalk 4
[Galaxy S I9000 Android Development] Harsha Raj:
Both questions has been asked and clarified many times in this thread! Please read thread or check OP before asking.

I would tell this last for time:

For installation aborted, you need to be on stock CWM (that is whatever comes with CM ROMs.

To enable transparent status bar you need to remove this line "ro.config.low_ram=true" from system/build.prop file and install Google experience launcher or latest beta of Nova launcher.

And it's written in the OP bug list that ROM can mount only 1 SD card.

I just don't want the Dev to get frustrated with repeated questions asked on every page. Thanks!
[Galaxy S I9000 Android Development] microMXL:
any way to remove google search bar from launcher3?
[Galaxy S I9000 Android Development] idCyber:
Guys you can use AirDroid to access the phone's sdcards (internal and external) and other stuff from the phone if you have a WiFi router at home. And you don't need anything more than a web browser on the PC and your phone with the app. I have stopped using the usb cable 4 months ago. (I know the transfer over wifi is a bit slower than the usb cable but my phone is no longer on a "leash" laying on my desk.) :)
[Galaxy S I9000 Android Development] Karo.:
just install GEL ( google launcher) apk

works on all devices

http://www.androidfilehost.com/?fid=23212708291676903
[Galaxy S I9000 Android Development] Soerdroid:
Pawitp, everything works great. This rom is smoother than slimrom 4.1.2. Thank you very much. :good:

I hope it is not too complicated to solve the chromium black screen problem. In my opinion it is a weird bug because it is even present in common apps. For example; bbc news app and other similar apps.

I have had some problems with google play store. It was not present in the app drawer and after some research I found that there was not enough space in the system folder. Phonesky.apk in priv-app folder was around 2mb but it should be 6 mb. I have manually removed Google+ app and Hangouts and after a full wipe re-flashed the rom& the new gapps. Now I have Google playstore and the Google account sync is working properly.
[Galaxy S I9000 Android Development] jasonfish1976:
Hi

I installed the latest rom with this procedure:

-Wipe factory reset/wipe cache /wipe dalvik cache

-Installed the latest version of the rom

-wipe cache /wipe dalvik cache

-Installed gapps-kk-20131113.zip

-reebot system

I have 2 problems:

1)the rom is sometimes laggy

2) i can't add home screens (only have one)-tried with both launchers that come with the rom

Is there anything i am doing wrong that cause these problems?

Thanks

Jason
[Galaxy S I9000 Android Development] twinky444:
1) It's still WIP. If you want, you can search this thread for how to get ART compiler to work and use that one. It may/may not speed things up. However, RAM management is REALLY improved in KitKat - Multitasking between browser, twitter, tapatalk, google keep and no redraws anywhere.

I think our GPU has some driver issues also with KitKat now...

2) You can add homescreens when you drag the icon from app drawer to the homescreen and deploy it to the right/left side next to the existing homescreen. A new homescreen should be visible then.
[Galaxy S I9000 Android Development] Soerdroid:
It is recommended to use 3rd party launcher (Nova launcher beta for example). Googels launcher is ram hungry and it has limited options. Which runtime (Art, Dalvik) are you using? I use dalvik and with 43 apps the old sgs is flying.
[Galaxy S I9000 Android Development] jasonfish1976:
Hi thanks for quick response:

1) i moved over to art it helps a bit but still laggy sometimes

2)ill try adding homescreens the way you suggested

Thanks a lot

---------- Post added at 10:58 PM ---------- Previous post was at 10:34 PM ----------

Ill try nova launcher beta

I tried art and dakvik

Thanks a lot

Jason
[Galaxy S I9000 Android Development] david23400:
What do you mean?? i'm already on CM 4.4 from pawitp.. i didnt flash any kernel :-s how can i be on another CM if i cant flash anything else than 4.4 roms..??
[Galaxy S I9000 Android Development] XuperLugia:
Just wanted to drop a big THANK YOU Pawitp.

With zRAM at 18% and KSM I'm getting around 200MB of free RAM plus a very responsive and snap experience while still having an "alpha" release, just amazing.
[Galaxy S I9000 Android Development] hertzschi:
I didn't read about superuser problems for some pages now.

Maybe this helps in the next days

http://review.cyanogenmod.org/#/c/53898/
[Galaxy S I9000 Android Development] tetakpatak:
You are our star, [MENTION=3117667]pawitp[/MENTION]! :o
[Galaxy S I9000 Android Development] mobilequest:
I found two more bugs:

1. The vibration intensity doesn't get saved. It resets after reboot.

2. The browser doesn't synchronize bookmarks.
[Galaxy S I9000 Android Development] Difusal:
IMEI problem

first of all, thanks for the rom!

my problem: IMEI changed. as soon as I booted, I was notified there was a problem with my IMEI.. :/ little help?
[Galaxy S I9000 Android Development] thiagoribeirorj:
I can not install the ROM with full wipe or not to upgrade from 10.2. In both'm still stuck on the error 7.
[Galaxy S I9000 Android Development] kalashenicof:
Restore EFS partition.
[Galaxy S I9000 Android Development] ZoomahZoomah:
Hi. I'm also unable to flash back to an earlier ROM

I've also tried installing official CWM and again get installation aborted.

Can anyone help?
[Galaxy S I9000 Android Development] geckoas:
Me too. Thanks to all who worked on it.

sent from my galaxy I9000 running CM11 with tapatalk
[Galaxy S I9000 Android Development] Angristan:
[MENTION=3117667]pawitp[/MENTION] Why this issue is shown as resolved ?

https://jira.cyanogenmod.org/browse/CYAN-3170
[Galaxy S I9000 Android Development] CatalystWon:
I haven't required Odin for a few years; last time I used Odin 1.85 and this device it worked for me, so I was asking for confirmation about a statement you made because misuse of Odin could have bad consequences so it matters to be certain about this. This is a simple question and I don't understand your protective response. Are you saying every time you make a statement we are supposed to check all other posts to see who said it first?
[Galaxy S I9000 Android Development] pawitp:
Because a core CM member thought it's not a bug. IMO, it's a bug, but I can't override that decision without fixing the bug myself (rule of open source: if you want something, submit a patch).

Unfortunately, it's not that easy to fix due to the recent assumptions Google made about devices with emulated SD cards (and I won't be fixing it). Those don't have "Move to SD card" any more and Google pretty much no longer maintains the feature.

Luckily, the bug is in the launcher and you can switch to a different launcher which doesn't have the bug (Google Now Launcher also has the bug, and there's no way to fix that since it's Google's closed source launcher).
[Galaxy S I9000 Android Development] :
Thanks! Switched to 17th nightly for now to have the issue fixed. Will update to M7 once released.
[Galaxy S I9000 Android Development] Angristan:
Ok Pawitp thanks anyway :)

I use now Nova Launcher and dont have the problem anymore :beer:
[Galaxy S I9000 Android Development] tetakpatak:
Ouch, sorry, I tought I was still answering the post #2766 LOL :D

(why i9000 has in-call delay with all KK roms... pawitp has said few times that our old phone is a bit slow)

Regarding Odin v1.85: it might work in many cases but it was created for the newer devices by Samsung. Despite it will work in many situations, the possibility that it will stuck/freeze during flashing process is higher than if you use compatible version. Unless it freezes in the moment of flashing the bootloader, no bigger harm will happen. Otherwise a hard brick is result.

I don't care when people use wrong charger or wrong flashing software for their own devices, I just don't like when they advice totally unexperienced users to do the same.

tetakpatalked from Nexus 7 flo
[Galaxy S I9000 Android Development] rupeshn:
Did a factory reset, formatted /system, installed 20140518 (didn't restore /data), seems to be fine, no issues from the last 15-16 hrs.

Thanks for your help Pawitp.
[Galaxy S I9000 Android Development] Turtuga:
Pawitp what you think about this

http://xdaforums.com/showthread.php...mcct=/showthread.php&__utmv=-&__utmk=38512544
[Galaxy S I9000 Android Development] pawitp:
IMHO, if something sounds too good to be true, it probably is (the "up to 6x" part).

-O3 can expose compiler or code bugs not normally experienced using less aggressive optimization levels. While it usually decreases execution time, it can also cause the binary size to grow larger (causing it to take longer to load from the eMMC and take more space in memory). So it's not something I'd mess with without careful testing and benchmark.

In any case, compiler optimization is not my area of expertise, so take what I say with a grain of salt.
[Galaxy S I9000 Android Development] DerRomtester:
pawtip if you have time can you pls send me your ramdisk.cpio and ramdisk-recovery.cpio

(need it for testing )
[Galaxy S I9000 Android Development] everb00b:
Using 18/5 nightly, anyone experinced issues with audio notes on Whatsapp?

I can't manage to play them, getting issue "cant play" and crash.
[Galaxy S I9000 Android Development] Makifylmz:
Yes, getting same issue
[Galaxy S I9000 Android Development] pawitp:
Use this script to extract it from boot.img: https://gist.github.com/pawitp/bc896a9c005900af1c7c

Edit the two top parameters, then you will get a whole_disk.cpio, which contains the actual ramdisk. Extract that with "cpio -i < whole_disk.cpio" and you will find the 2 cpio files you're looking for in the stage1 directory.

Try 20140520, if it still doesn't work, get a logcat.
[Galaxy S I9000 Android Development] DerRomtester:
Thank you very much :D
[Galaxy S I9000 Android Development] Makifylmz:
Problem solved. Thanks...
[Galaxy S I9000 Android Development] devloz:
Hello!

Pawitp, GPS sucks so much on our phone? Because my weaker phone (S5830i) renders my location fine. Our one is "mocking everywhere".

Thanks, for "eventual" response :)

Best regards.

PS: If anybody needs updated "goo.im" GApps, then: http://www.mediafire.com/?9f2j9mlocczi692.
[Galaxy S I9000 Android Development] tomasso32:
Hardware issue maybe: http://xdaforums.com/showthread.php?t=1697217

I didn't use the soldering method. But use a bit of electricians tape (2 layers) as in this: http://xdaforums.com/showthread.php?t=1043034

Good GPS lock ever since.

Tom.
[Galaxy S I9000 Android Development] abobobilly:
Can any of you guys recommend me a 3rd party kernel? Because CM Kernel is giving me nightmares. My RAM gets filled leaving a mere 50MB at my disposal. On Mackay 4.4.2 ... i always had nearly 120MB at my disposal which allowed me to multitask without having to worry about Launcher Redraws (using Google Now Launcher + Google Now itself), or a Music App closing itself in the background to free up more RAM.

Just to clear it up, i am aware of how Android manages its RAM, and stock CM kernel keeps all apps cached in the background. But i am using Greenify as well, and keeping quite a lot of memory hungry apps on halt. Heck not even using any Theme (adore the new theme engine btw :P)

I'd be glad if someone could let me know:

- If i am the only one with this problem.

- If its known Cyanogen Mod issue because its currently a "nightly" (if thats the case then how did other ROM devs managed to pull better performance?)

- A solution!?

Help will be appreciated.
[Galaxy S I9000 Android Development] ioannis_m:
Try DerRomtester's kernel....fast,stable and ram friendly.(in logical use) :good:

http://xdaforums.com/showthread.php?t=2662853
[Galaxy S I9000 Android Development] sanguinesaintly:
I've been using Neo kernel without any problems. 415 MB to start with, so plenty of free RAM (if you think it makes any difference) and available now in CWM or TWRP. Read about it here http://xdaforums.com/showthread.php?t=2662853
[Galaxy S I9000 Android Development] joedom1:
Well if you like Mackay.

Kasper_h Mackay kernel I never had a problem...

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