yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] nepal12:
Mirror : https://app.box.com/s/eorqcszggo6yfcqxoj4emfog1yda3erw

---------- Post added at 10:48 PM ---------- Previous post was at 10:47 PM ----------

I'm always getting error 491 while downloading apps. I tried everything . I'm using the gapps from devloz

---------- Post added at 10:50 PM ---------- Previous post was at 10:48 PM ----------

yup
[Galaxy S I9000 Android Development] devloz:
So Phone FC is because this build requires full wipe.
[Galaxy S I9000 Android Development] MICHAELMAGED:
[MENTION=3031478]humberos[/MENTION] thank you alot for this rom, i wonder if the memory leak issue supposed to be fixed in this version because it is still there and is it possible to add the 0.25 scale animation back because they made the phone much smoother
[Galaxy S I9000 Android Development] nepal12:
how about my error? any solution ?
[Galaxy S I9000 Android Development] humberos:
Thanks [MENTION=5248028]devloz[/MENTION] but...

We need to test SELinux and it requires a FULL wipe.

If we can't test it then it can't get official status, unfortunately.
[Galaxy S I9000 Android Development] MICHAELMAGED:
you can try these gapps http://xdaforums.com/android/software/gapps-google-apps-minimal-edition-t2943330
[Galaxy S I9000 Android Development] devloz:
Ouch,, i thought it was SELinux bug :/ Okay, will test after wipe :)

BTW: It's now installing much faster :D
[Galaxy S I9000 Android Development] He_Knows_It_All:
if your getting errors, just factory reset and try again, thats a fix i found that works
[Galaxy S I9000 Android Development] humberos:
I don' t know if it isn't deprecated yet.

Sounds like CAF is not using it anymore.

But I will check it.
[Galaxy S I9000 Android Development] humberos:
Only the first installation is more tragic due to ART conversion process.

Yes now it is much better than 20140313.
[Galaxy S I9000 Android Development] He_Knows_It_All:
Evidence

I can't log it as i don't know how to but i can provide screenshots and videos. it's really bugging me as it's impossible to access the google services (Play store etc..).
[Galaxy S I9000 Android Development] Audiracecar90:
Sorry devloz i'm not able to get what you are asking?
[Galaxy S I9000 Android Development] ThunderOver:
It is true that the availability of ram is lower, but the device is much more fluid than in the previous version.
[Galaxy S I9000 Android Development] devloz:
I mean, you can place this kind of code between CODE tags. Example:

Running flash_image...
+ /sbin/flash_image boot /tmp/boot.img
mtd: successfully wrote block at 0
mtd: not writing bad block at 0x00040000 (ret 1 errno 22)
mtd: successfully wrote block at 80000
mtd: successfully wrote block at c0000
mtd: successfully wrote block at 100000
mtd: successfully wrote block at 140000
mtd: successfully wrote block at 180000
mtd: successfully wrote block at 1c0000
mtd: successfully wrote block at 200000

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

Yeah but I think it's thanks to improved animations (however in some places it's still cracking - recents sometimes do). What's true, unlike usual memory leak reports, "System" is eating ~200MB from the very beginning to the very end (it's not going down and up). Maybe one of features like "animation cache", "JIT" (I saw merged commits about JIT and it was supposed to eat several MB's per app) or so are added? I'm still with memory leak - scenario:

- Android 5.0 -> memory leak.

- OmniROM -> memory leak fixes (i had ~200MB free).

And then:

- Android 5.1 -> memory leak.

- OmniROM -> reverted some fixes that were supposed to be ok in Android 5.1.

- OmniROM -> merged upstream to Android 5.1. Memory leak persists :( (~100MB free).

- [FUTURE] -> OmniROM -> again memory leak fixes.

Yes, i have to admit, it's working nice.

EDIT: Whoops, look attachment - definitely memory leak!

PS: MTP isn't freezing anymore ;)
[Galaxy S I9000 Android Development] Audiracecar90:
Ok devloz u have any idea about seeing log files? why its struck in vibrant screen?
[Galaxy S I9000 Android Development] devloz:
Yours:

mtd: successfully wrote block at 0
mtd: not writing bad block at 0x00040000 (ret 1 errno 22)
mtd: successfully wrote block at 80000
mtd: successfully wrote block at c0000
mtd: successfully wrote block at 100000
mtd: successfully wrote block at 140000
mtd: successfully wrote block at 180000
mtd: successfully wrote block at 1c0000
mtd: successfully wrote block at 200000
mtd: successfully wrote block at 240000
mtd: successfully wrote block at 280000
mtd: successfully wrote block at 2c0000
mtd: successfully wrote block at 300000
mtd: successfully wrote block at 340000
mtd: successfully wrote block at 380000
mtd: successfully wrote block at 3c0000
mtd: successfully wrote block at 400000
mtd: successfully wrote block at 440000
mtd: successfully wrote block at 480000
mtd: successfully wrote block at 4c0000
mtd: successfully wrote block at 500000
mtd: successfully wrote block at 540000
mtd: successfully wrote block at 580000
mtd: successfully wrote block at 5c0000
mtd: successfully wrote block at 600000
mtd: successfully wrote block at 640000
mtd: successfully wrote block at 680000
mtd: successfully wrote block at 6c0000

Mine:

mtd: successfully wrote block at 0
mtd: successfully wrote block at 40000
mtd: successfully wrote block at 80000
mtd: successfully wrote block at c0000
mtd: successfully wrote block at 100000
mtd: successfully wrote block at 140000
mtd: successfully wrote block at 180000
mtd: successfully wrote block at 1c0000
mtd: successfully wrote block at 200000
mtd: successfully wrote block at 240000
mtd: successfully wrote block at 280000
mtd: successfully wrote block at 2c0000
mtd: successfully wrote block at 300000
mtd: successfully wrote block at 340000
mtd: successfully wrote block at 380000
mtd: successfully wrote block at 3c0000
mtd: successfully wrote block at 400000
mtd: successfully wrote block at 440000
mtd: successfully wrote block at 480000
mtd: successfully wrote block at 4c0000
mtd: successfully wrote block at 500000
mtd: successfully wrote block at 540000
mtd: successfully wrote block at 580000
mtd: successfully wrote block at 5c0000
mtd: successfully wrote block at 600000
mtd: successfully wrote block at 640000
mtd: successfully wrote block at 680000

Your phone failed to flash block "40000", however it flashed extra block at "6c000" so it handled it. Kernel is likely to be flashed correctly.

Next:

Yours:

+ /tmp/busybox umount -l /system
umount: can't forcibly umount /system: Invalid argument
+ /tmp/busybox umount -l /data
umount: can't forcibly umount /data: Invalid argument

Mine:

+ /tmp/busybox umount -l /system
+ /tmp/busybox umount -l /data

Why it failed? Maybe try to revert to stock and from there to KK -> LP? [I had problem flashing Omni 5.x on TWRP - binary bug].
[Galaxy S I9000 Android Development] humberos:
Sorry dude!

I've just made a built for vibrant... as I told before I can't debug it since I don't have|know the hardware.
[Galaxy S I9000 Android Development] devloz:
Statusbar space happened only once (at morning - after unlocking and locking again it fixed itself).

Bluetooth disappearing didn't happened again (it's a plus).

That's what i mean, "System" - 200MB while in 5.0.2 it was 100MB :/

PS: This photo with bugged "free" isn't from I9000. I just wanted to show it exists on 5.1 too (it's really extreme situation).
[Galaxy S I9000 Android Development] He_Knows_It_All:
Home Button.

Why isn't home button bring up recents?
[Galaxy S I9000 Android Development] devloz:
Buttons -> manual -> home longpress -> recents :) [Yes, it's kind of bug].

PS: Today's GApps [20150314] for KK | LP | LPMR1: MEGA.
[Galaxy S I9000 Android Development] phil_greg2001:
Have you try this gapps in 240 dpi?

http://xdaforums.com/showpost.php?p=56820635&postcount=1

:confused:
[Galaxy S I9000 Android Development] devloz:
They're 5.0 i think ;)
[Galaxy S I9000 Android Development] Audiracecar90:
okay anyway Thanks humberos

---------- Post added at 09:37 PM ---------- Previous post was at 09:34 PM ----------

okay devloz i already tried revert back to stock->GB->JB->KK->LP again same problem occurs and same log error do u know any solution for it?
[Galaxy S I9000 Android Development] devloz:
I'm sorry, no idea (however it happened to me a few times - without this bad block of course) :(
[Galaxy S I9000 Android Development] phil_greg2001:
http://xdaforums.com/showpost.php?p=59359111&postcount=286
[Galaxy S I9000 Android Development] humberos:
Sorry, I can't help you without logs.
[Galaxy S I9000 Android Development] Audiracecar90:
okay Thankyou devloz lets wait for some other builts
[Galaxy S I9000 Android Development] humberos:
Remember it's an alpha version then please don't expect all features incorporated in at moment.

Let's improve it by using tiny and safe steps.

But I think that all main phone functions is working for a daily driver use.

Anyway thanks to your feedback.
[Galaxy S I9000 Android Development] devloz:
But I like to have 5.1 GApps on Android 5.1. The thing is, i like to get them all from Nexus, update from Play Store, organize them according to layout from old goo.im's and then use them ;)

PS: Can someone try to take old (Omni 4.4.4) update-binary and place it in 5.x Omni? Through ADB i noticed it's copying these files really slow.
[Galaxy S I9000 Android Development] He_Knows_It_All:
What needs to be tested to make this official? i've flashed this rom and i want to help
[Galaxy S I9000 Android Development] humberos:
Requisites for devices before they can become nightlies:

Active maintainer

SElinux in enforcing mode

Fully functional recovery build

reference: http://docs.omnirom.org/Lollipop_Device_Status

then, I really want your feedbacks!

Thanks in advance!
[Galaxy S I9000 Android Development] He_Knows_It_All:
Devloz should be a maintainer. Excellent Gapps provider..
[Galaxy S I9000 Android Development] humberos:
Android 5.1.0_r3

Android 5.1.0_r3

https://gerrit.omnirom.org/#/c/12832/

Let's move on!
[Galaxy S I9000 Android Development] He_Knows_It_All:
This lollipop build is basically fully functional with minor bugs.. When in lockscreen, menu button unlocks screen ..
[Galaxy S I9000 Android Development] hollandais:
I had also an fc after flashing this rom. Back to recoveey, full wipe and flash again. Reboot and everything seems ok.

Envoyé de mon GT-P5110 en utilisant Tapatalk
[Galaxy S I9000 Android Development] neteagle86:
Some behavior for me, back to Recovery, Reset to defaults, install ROM and then GApps and All Ok! Thanks for your Work [MENTION=3031478]humberos[/MENTION]
[Galaxy S I9000 Android Development] neteagle86:
I reset and loaded last build and same first impression, more smooth and fast! Thanks [MENTION=3031478]humberos[/MENTION], If I can test something that can be usesul for you, please write or contact me.
[Galaxy S I9000 Android Development] humberos:
yeah!

It is a known issue since that menu key always did it at least for physical qwerty keyboards.

I mean, this behaviour is happening for all devices that have a dedicated menu button (excluding soft keyboard as well).
[Galaxy S I9000 Android Development] :
[MENTION=3031478]humberos[/MENTION] please help epicboy to build 5.1 for vibrant. He build done but phone doesn't bootup
[Galaxy S I9000 Android Development] humberos:
As I posted before, just make sure if he is using this:

https://gerrit.omnirom.org/#/c/12840/
[Galaxy S I9000 Android Development] :
Can you build 5.1 for vibrant because he just built 5.1 30mins ago and it still not bootup stuck at second samsung logo
[Galaxy S I9000 Android Development] humberos:
Sorry,... it's 1h40 AM here

I am really tired.
[Galaxy S I9000 Android Development] :
Oh sorry Im in GMT+7
[Galaxy S I9000 Android Development] k3loo:
[MENTION=3031478]humberos[/MENTION] - everything works fine (including installation which works like charm now). However microphone mute during call still not working.

Thanks you for your hard work.
[Galaxy S I9000 Android Development] szigeza:
Hi! The calendar app doesn't connect to the gmail calendar!

Is there any solution?
[Galaxy S I9000 Android Development] hollandais:
This is a problem with google sync. In the past I downloaded google agenda and that solved the problem. I don't know if that's still ok.

Envoyé de mon GT-P5110 en utilisant Tapatalk
[Galaxy S I9000 Android Development] beinto:
thank you

[MENTION=3031478]humberos[/MENTION] thank you so much for this rom.....

---------- Post added at 01:22 PM ---------- Previous post was at 01:16 PM ----------

I installed the google calendar and it syncronized both apps
[Galaxy S I9000 Android Development] Ridxrock:
Omni Lollipop 5.1 :)

I have not yet installed that one but could anyone try and install the facebook app from playstore and tell me if it works :)

the last builds couldn't and that i really hate :x

So anyone please try it and tell me if it install correctly without any need of side installing :)

Do tell me before ill do it myself it could save me the pain of backing up everything for nothing because i shifted back to omni 4.4.4 caused these minor problem thanks :)

On the last build while using the camera app its color is kinda dark compare to the camera on kitkat omni i do not know if others noticed that im just pointing it out,hope it changed on this build :)

[MENTION=3031478]humberos[/MENTION] Thank you for the new build you're really an :angel: :laugh: Keep it up

If you need any feedback or help let me know im kinda of a tester "Haha Good" :) :good:
[Galaxy S I9000 Android Development] :
Install FB lite
[Galaxy S I9000 Android Development] Ridxrock:
No I do not need FB lite i want the rom to be installing the fb app from playstore without using fb lite or anything else.

I just do not understand why other roms can install fb correctly from playstore whereas the lollipop can't it just does not feel right man :/

please find a solution to it dev :)

Thank you :)
[Galaxy S I9000 Android Development] devloz:
Lollipop is newer OS, it's have bigger "weight". If you want this slowing-down-even-fast-phones app, then go for lighter ROM (i.e. 4.0 or 4.4[this one is faster than LP but slower than ICS]). It doesn't feel right? It does :D No solution (unless there will be suprising speed improvement, but i think we are at almost max possible for I9000 on LP).
[Galaxy S I9000 Android Development] Ridxrock:
Okay,Hope we can solve it out without slowing LP.

Yes i understand,but why doesn't it install,installing in memory isn't speed its using space,so like other apps it should install right?

then when it did it would eventually slow down the device. You cant tell me im wrong because even if LP has bigger weight other app still install such as skype from playstore,it only slow down when you are in it.

:confused: :confused: :confused:
[Galaxy S I9000 Android Development] devloz:
Open Facebook app and check how many classes*.dex is inside. It's not about size of app, it's about amount of code in here. Our phone need a few fixes to installation process (next Android rev). Facebook app memory management sucks.
[Galaxy S I9000 Android Development] neteagle86:
I reset Device yesterday and load last ROM's build and last GApps from Devloz.

I configure the phone and load n.3 Apps that work with calendar, I does not see any abnormal state in Calendar with Last GApps.
[Galaxy S I9000 Android Development] jawad872:
Couldn't move app to sd, not enough storage space

i flashed lollipop 5.1 using twrp. Everything works smoothly but when i try to move apps to sd card via the move to sd option in the application manager,or Titanium Backup i get the following message "Couldn't move app to sd, not enough storage space" though i have 5 GB of space in sd card. Please help.
[Galaxy S I9000 Android Development] movitum:
hello and first thanks for the rom it runs much better than i thought it would!

but i have to ask if anyone else is having my problem: the phone restarts from time to time without me touching it. i see the leds light up and it starts rebooting. does anyone know how i can troubleshoot this? it happens on 100% default settings without even installing anything extra.

thanks for any help :)
[Galaxy S I9000 Android Development] zeelyke:
Hi There!

First [MENTION=3031478]humberos[/MENTION] Thanks for the great ROM!

Everything works fine (facebook,youtube,messenger etc..) but sometimes the phone just reboot itself.. how can i fix it?
[Galaxy S I9000 Android Development] devloz:
In 20150326 i've noticed random reboots (mostly soft ones - just android restarted, not kernel). No avc: denied in logs and nothing noticeable in logcat. Laboring it through network (live logcat). Thanks for ROM! :)
[Galaxy S I9000 Android Development] artyfarty:
me too, i have random soft reboots
[Galaxy S I9000 Android Development] ThunderOver:
[MENTION=3031478]humberos[/MENTION]

with the latest rom 03/25/2015 I had about 3 automatic reboots

I have attached the logicat
[Galaxy S I9000 Android Development] devloz:
BTW: OmniROM @ 5.1 [20150325] - MEGA.

[MENTION=5520219]ThunderOver[/MENTION]

A lot of those:

E/AndroidRuntime( 5300): java.lang.OutOfMemoryError: Failed to allocate a 1024012 byte allocation with 154800 free bytes and 151KB until OOM

E/OMXNodeInstance(19222): getExtensionIndex(f:SEC.MPEG4.Decoder, OMX.google.android.index.storeMetaDataInBuffers) ERROR: BadParameter(0x80001005)
E/OMXNodeInstance(19222): getExtensionIndex(f:SEC.MPEG4.Decoder, OMX.google.android.index.prepareForAdaptivePlayback) ERROR: BadParameter(0x80001005)
W/ACodec (19222): do not know color format 0x7f000001 = 2130706433
E/OMXNodeInstance(19222): getExtensionIndex(10:SEC.H263.Decoder, OMX.google.android.index.storeMetaDataInBuffers) ERROR: BadParameter(0x80001005)
E/OMXNodeInstance(19222): getExtensionIndex(10:SEC.H263.Decoder, OMX.google.android.index.prepareForAdaptivePlayback) ERROR: BadParameter(0x80001005)
W/ACodec (19222): do not know color format 0x7f000001 = 2130706433
E/OMXNodeInstance(19222): getExtensionIndex(11:SEC.AVC.Decoder, OMX.google.android.index.storeMetaDataInBuffers) ERROR: BadParameter(0x80001005)
E/OMXNodeInstance(19222): getExtensionIndex(11:SEC.AVC.Decoder, OMX.google.android.index.prepareForAdaptivePlayback) ERROR: BadParameter(0x80001005)

W/OMXNodeInstance(19222): [15:google.mpeg4.decoder] component does not support metadata mode; using fallback
W/OMXNodeInstance(19222): [16:google.h263.decoder] component does not support metadata mode; using fallback
W/OMXNodeInstance(19222): [17:google.h264.decoder] component does not support metadata mode; using fallback

This one is interesting:

W/MediaScanner(19985): Error opening directory '/storage/sdcard0/.android_secure/', skipping: Permission denied.

Amount of those errors is amazing :) But why my lc didn't catched these? [maybe because of old kernel?].

PS:

W/AudioTrack(19455): AUDIO_OUTPUT_FLAG_FAST denied by client
[Galaxy S I9000 Android Development] ioannis_m:
I am also having reboots so it is something from the rom. Hope it get fixed soon! Great work [MENTION=3031478]humberos[/MENTION]
[Galaxy S I9000 Android Development] humberos:
E/AndroidRuntime( 5300): java.lang.OutOfMemoryError: Failed to allocate a 1024012 byte allocation with 154800 free bytes and 151KB until OOM

LMK parameters ?

E/OMXNodeInstance(19222): getExtensionIndex(f:SEC.MPEG4.Decoder, OMX.google.android.index.storeMetaDataInBuffers) ERROR: BadParameter(0x80001005)
E/OMXNodeInstance(19222): getExtensionIndex(f:SEC.MPEG4.Decoder, OMX.google.android.index.prepareForAdaptivePlayback) ERROR: BadParameter(0x80001005)
W/ACodec (19222): do not know color format 0x7f000001 = 2130706433
E/OMXNodeInstance(19222): getExtensionIndex(10:SEC.H263.Decoder, OMX.google.android.index.storeMetaDataInBuffers) ERROR: BadParameter(0x80001005)
E/OMXNodeInstance(19222): getExtensionIndex(10:SEC.H263.Decoder, OMX.google.android.index.prepareForAdaptivePlayback) ERROR: BadParameter(0x80001005)
W/ACodec (19222): do not know color format 0x7f000001 = 2130706433
E/OMXNodeInstance(19222): getExtensionIndex(11:SEC.AVC.Decoder, OMX.google.android.index.storeMetaDataInBuffers) ERROR: BadParameter(0x80001005)
E/OMXNodeInstance(19222): getExtensionIndex(11:SEC.AVC.Decoder, OMX.google.android.index.prepareForAdaptivePlayback) ERROR: BadParameter(0x80001005)

W/OMXNodeInstance(19222): [15:google.mpeg4.decoder] component does not support metadata mode; using fallback
W/OMXNodeInstance(19222): [16:google.h263.decoder] component does not support metadata mode; using fallback
W/OMXNodeInstance(19222): [17:google.h264.decoder] component does not support metadata mode; using fallback

Oh, this is happening for all exynos3 and exynos4 devices...

We are working on!

W/MediaScanner(19985): Error opening directory '/storage/sdcard0/.android_secure/', skipping: Permission denied.

hummm!

I will check it.

W/AudioTrack(19455): AUDIO_OUTPUT_FLAG_FAST denied by client

Yeah I saw this audio spam.

weird, we aren't using this flag on audio config.

anyway, I will check it.

The kernel is ok! (except for zpool feature.... I think it is causing random reboots).

The challenge is about ROM side port process.

Thanks!
[Galaxy S I9000 Android Development] ThunderOver:
LMK parameters attached

I set the parameters of "mild" because on the previous Romwere fine
[Galaxy S I9000 Android Development] humberos:
Ok!

I will bring back the values from previous rom to the next.

I think it is necessary.
[Galaxy S I9000 Android Development] margadias:
Finally separated thread for Lolipop!
[Galaxy S I9000 Android Development] hollandais:
Can you give us the link?

Thanks

Envoyé de mon GT-P5110 en utilisant Tapatalk
[Galaxy S I9000 Android Development] :
The official Facebook apps is total pants.

I've never been able to run it without problems on any phone I've had, but the Facebook lite app is way way way better, especially on lollipop 5.1.

My advise is to steer clear of the official Facebook app and use something "lighter" and yes I've tried it on my SGS on lollipop and it took 19 (!) Minutes to log in then crashed, total waste of time.

On a different matter, I've had several random reboots on the new 0325 build, no errors or lag before had, just sudden reboots.

Anyone had this?? :-/
[Galaxy S I9000 Android Development] margadias:
Link for what? I meant, that it's good, because before it was like 4.4 and 5.0 in the same (4.4 OmniROM) thread. So it's good, that they have been divided into two threads.
[Galaxy S I9000 Android Development] dzee206:
For those of y'all wanting to install FB but can't, use this unofficial version. Its ram friendly and I've been using it since it got released. It has issues when you hit the menu button or volume buttons the app will exit out on its own but besides that's it has been my go to app when I hop on FB. http://xdaforums.com/showthread.php?p=52161520
[Galaxy S I9000 Android Development] exerramun:
Good work. After one day of use I think this rom has lower performance than the previous 5.1. [MENTION=3031478]humberos[/MENTION] pleased to test your work. Regards.
[Galaxy S I9000 Android Development] :
Im getting a parsing error :(
[Galaxy S I9000 Android Development] dzee206:
Here ya go, same app different link. Hopefully it works for you...

http://www.mediafire.com/?tvmw5koq5qd7sd0
[Galaxy S I9000 Android Development] :
Thanks,

Got it working but I've ran into problems.

Clean install of 0325 this morning and didn't really start testing until late this evening but very quickly the phone reboots suddenly without warning and has very bad lag now too.

I get many blank screens.

I tried taking screenshots of this error but my phone has noe been saying for 20 minutes "saving screen shot" :(
[Galaxy S I9000 Android Development] dzee206:
I would roll back to previous release or an older version that didn't have any random reboots or just restore your nand and wait for next release for the random reboots to addressed. Sorry that's all I can suggest...
[Galaxy S I9000 Android Development] :
Dear [MENTION=3031478]humberos[/MENTION], epicboy used your config to build ROM but it still not bootup:( Any iead, please? :)
[Galaxy S I9000 Android Development] humberos:
[MENTION=5562721]epicboy[/MENTION]

Try again by removing this flag:

BOARD_USES_LEGACY_MMAP

aries-common/BoardConfigCommon.mk

https://gerrit.omnirom.org/#/c/12890/