yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] epicboy:
The SV version can be used on omnirom and gives you more ram than the V version, but *breaks* video playback. This can be fixed by flashing the kk_bigmem zip file, and combine that with the bigmem option in the Semaphore manager application and you will have 408MB of ram.
[Vibrant Android Development] nirogu325:
Now that the Manager works properly, I might try that option. Thanks, but...

One very important question, if I may. I know you're eventually planning to port CM12 or L-based Omni, but there'll be two missing pieces. A kernel compatible with Lollipop and a kernel developer. I'm kinda worried about the latter for our Vibrants. What's your opinion on this?
[Vibrant Android Development] epicboy:
Well, as long as the i9000 devs are developing a kernel, we're good. The vibrant uses "aries" kernel source, which is used by every og galaxy s1. I don't know if you've noticed that most kernels made for vibrant are also on i9000 and captivate. So, in conclusion, if the i9000 devs are making open source kernels, then we can port them to the vibrant.
[Vibrant Android Development] nirogu325:
Lol I barely know about that, so what you said is useful and is a relief. Thanks. :good:
[Vibrant Android Development] epicboy:
What a turn of events!

Guys, I no longer have the Samsung Vibrant :(. Last night, my vibrant just died on me and wouldn't power on. And this morning my father said he needed the Vibrant that [MENTION=4496369]benjmiester[/MENTION] donated to use at work for "emergencies." So I won't be able to test any roms I build for this device. Now I need a group of you who are able to test the roms that I build, and return back to me quickly with the results.
[Vibrant Android Development] nirogu325:
Damn, man. I would test extensively if only my mother didn't have the Vibrant as her primary phone.
[Vibrant Android Development] dzee206:
Sorry to hear that. If all goes as planned I should be getting my vibrant back soon from my wife so I'll be able to test things out once again, if not I may have to sell her my og note just to get back to supporting this community and drop support for that device...

Sent from my SGH-I717 powered by AOKP
[Vibrant Android Development] nirogu325:
[MENTION=4284290]dzee206[/MENTION] [MENTION=5562721]epicboy[/MENTION] - End of the road people. Our Vibrants won't get Lollipop. Why? Source HERE.
[Vibrant Android Development] dzee206:
Yeah I seen that. Got me disappointed for a quick minute but I'm sure some other Devs will continue working on 5.0, I hope but if not 4.4.4 will do for me. Already running 5.0.2 on my note 2 so no big deal for me. Oh yeah damn you [MENTION=3059141]nirogu325[/MENTION] for mentioning Pandora patcher now I'm back to using xposed after all these months lol, it came in handy though only after a few days of use already got like half a gig worth of songs on my SD.

Sent from my SGH-I717 powered by AOKP
[Vibrant Android Development] nirogu325:
Humberos was the last developer who was actively coding to make it possible. Pawipt is out and has been for a while now. Omni 4.4.4 so far has been the best experience. CM lags too much. It's incredible how crappy CM has gotten over the years. And they won't even fix the "can't connect to camera" issue on the GS3 builds either despite several reports over 4+ months. Oh well, it was good while it lasted! Also lol [MENTION=4284290]dzee206[/MENTION], that module is handy.
[Vibrant Android Development] rodman01:
But he finally released a lollipop test/beta version yesterday/today ;)...now you can get out of your starting box and port it :)
[Vibrant Android Development] epicboy:
We tried to port it but it's still not booting. I'm gonna try to build again with latest sources and fixes. Hoping for the best!
[Vibrant Android Development] rodman01:
I am not sure whether all commits had been already merged to github...to get a booting version I had also to cherry pick open commits. But my last build was a couple of days ago....check humbertos gerrit for open commits and pick the open and merged commits, related to samsung aries and maybe telephony too:

https://gerrit.omnirom.org/#/q/owner:"Humberto+Borba"+status:open

https://gerrit.omnirom.org/#/q/owner:"Humberto+Borba"+status:merged, especially the exynos3 commits

or is just porting his rom.zip not possible in this case? That would be easier....isn't it?
[Vibrant Android Development] epicboy:
I tried cherry picking all those commits after reading that you were able to get a booting build. All the commits that sferadev linked to. I wasn't able to get it past the kernel splash screen but I was able to boot into recovery. And in recovery it kept complaining about not being able to mount the /system and /data partitions.

Also, dzee tried to port that zip using the kernel that I built and it still didn't boot.
[Vibrant Android Development] nirogu325:
I quoted him on my previous post where he explained why he would release it. Hint: Just so we can see KitKat is better for our devices (the i9000 in his post).
[Vibrant Android Development] rodman01:
I have not only cherry picked the commits sferadev linked too, because only with that my build didn't boot neither...I picked all I said previously. It doesn't matter if you pick to much and if you get some build errors, you can revert the commits or fix the build errors.....

---------- Post added at 11:00 PM ---------- Previous post was at 10:47 PM ----------

just an idea: what deconfig are you using? the vibrant-deconfig or have you copied the galaxysmtd? Because the vibrant deconfig is much shorter then the galaxysmtd one: https://www.diffchecker.com/kr7ut4kd
[Vibrant Android Development] epicboy:
I was checking to see if there was any more aries commits but they all seemed to be merged. The defconfig must be what's the problem. I'll be off of work tomorrow so ill try to add those lines and building again. Thanks for pointing that out :) I didn't realize the huge difference
[Vibrant Android Development] :
[MENTION=5562721]epicboy[/MENTION] I have tried your lollipop build yesterday, install zip very OK but It stuck at logo. I have shot your hangout. I think we need [MENTION=3252166]sada23[/MENTION] help us although he left forum
[Vibrant Android Development] :
After flashing I see Omni logs in my sd card. I don't know what is this but I think it may have you [MENTION=5562721]epicboy[/MENTION] https://www.dropbox.com/s/zgmoy7b1ihk8frm/bml_over_mtd.log?dl=0 https://www.dropbox.com/s/akmubz5zeflce2m/mtd.log?dl=0
[Vibrant Android Development] epicboy:
thank you for taking time and testing out my build. [MENTION=4613083]rodman01[/MENTION] i have done what you said about the defconfig. yet the rom is still not working. do you know of any changes that might have been made for galaxysmtd and didnt make its way to vibrant? i believe that may be the issue since the vibrant source tree hasnt been updated since the cm10.2 days.
[Vibrant Android Development] :
I need link to vibrant kernel source. Because I one body want to help us build lollipop but he need kernel source. Thanks you
[Vibrant Android Development] epicboy:
who is this guy? i'll pm him all info necessary.
[Vibrant Android Development] nirogu325:
Beats me but we need all the help we can get. Looks like humberos over at the i9000 forum discovered and fixed the memory issue. I hope that means we can now install Gapps without severe lags.
[Vibrant Android Development] :
He is [MENTION=5074768]jeffreyvh[/MENTION]
[Vibrant Android Development] dzee206:
We gotta get it to boot first as well as the twrp issue getting fixed, after that hopefully won't be any major issues arising. I just wanna play with lollipop on the vibe just once even if the ROM does take a good fifteen minutes to flash lol.

Sent from my Half Baked Vibrant
[Vibrant Android Development] nirogu325:
[MENTION=5562721]epicboy[/MENTION] - your MediaFire ROM folder says "The owner of this folder has not added any files".
[Vibrant Android Development] :
I think he delete file to prepare for lollipop ;))
[Vibrant Android Development] epicboy:
Oh crap, my bad. I thought that i deleted the lp rom not kitkat. I'll upload an updated version.
[Vibrant Android Development] nirogu325:
Lol, alright, it's good!
[Vibrant Android Development] :
Are you working with [MENTION=5074768]jeffreyvh[/MENTION] to build lollipop for vibrant ?
[Vibrant Android Development] epicboy:
kinda
[Vibrant Android Development] :
Good luck guy ;)
[Vibrant Android Development] :
[YOUTUBE][/YOUTUBE]Wowwww Lollipop 5.0.2 for Samsung Wave (Bada OS) my old phone. Now I'm feeling so silly to sold it. Miss my Wave :crying:

[YOUTUBE]watch?v=u79DZ8osogk[/YOUTUBE]
[Vibrant Android Development] epicboy:
New

KitKAT

build uploaded, link is updated in the op.
[Vibrant Android Development] nirogu325:
Downloading! :highfive: Oh and I found this which might be useful info for other devices...with Lollipop and more RAM of course.
[Vibrant Android Development] :
What new update ? :)
[Vibrant Android Development] :
:((

I have this issue when my vibrant bootup
[Vibrant Android Development] mlkjuggalo:
Same issue here .
[Vibrant Android Development] :
Seem like i9000 have it too. I think omni source is bug
[Vibrant Android Development] selmandeli:
You can fix it by flashing Iyahman's kernel from this point. Remove battery, go to recovery an so on...
[Vibrant Android Development] epicboy:
Omg! Try what selmandeli said and tell me if your internal storage was wiped. That happened on ics and used to wipe the internal storage completely.
[Vibrant Android Development] :
It mean I must flash semaphore kernel or wipe internal to use this ROM
[Vibrant Android Development] epicboy:
flash the kernel. DONT WIPE INTERNAL!!!
[Vibrant Android Development] :
Ok thanks I will try latter
[Vibrant Android Development] selmandeli:
I have no problem with the storage.
[Vibrant Android Development] nirogu325:
It's true because I've never had that issue (been using Omni for months) as I always flash Semaphore first.
[Vibrant Android Development] :
Which version you use "s" or "sv" ?
[Vibrant Android Development] :
How to disable Wakelock in Omni Rom ?

Sent from my SGH-T959
[Vibrant Android Development] selmandeli:
Use "v" version.
[Vibrant Android Development] :
Thanks. And do you know how to disable Wakelocks ?
[Vibrant Android Development] mcselasie:
Red Flashes

After flashing update, I am getting occasional Red flashes around the screen edges. How do I fix this?:confused:

---------- Post added at 11:51 AM ---------- Previous post was at 11:44 AM ----------

I don't think you can disable app lock generally. U will have to disable it on a per app basis. Settings/app permissions/device
[Vibrant Android Development] :
You add this code into system/build.prop:

persist.sys.strictmode.disable=1
[Vibrant Android Development] :
[MENTION=5562721]epicboy[/MENTION] Why I see Sound Recorder in all apps but in the launcher it disappear
[Vibrant Android Development] selmandeli:
I have problems with the baseband after installing SU. Tried several time with no success.
[Vibrant Android Development] :
My baseband change to Captivate baseband but it OK no issue. You should back to stock and install ROM. Lastest Omni work like charm
[Vibrant Android Development] nirogu325:
I use "v" because "sv" breaks video and 720p camcorder for me despite flashing the bigmem zip and activating BIGMEM on Semaphore Manager. So yeah, I'll just stick to "v". About wakelocks? Check your apps and your battery stats to see what exactly is causing them in your unit. No wakelocks here.
[Vibrant Android Development] :
Ok thanks :)

Sent from my SGH-T959
[Vibrant Android Development] nirogu325:
Epicboy, I've just flashed your latest build and am having a bold red border flash all around the screen from time to time. I don't see anything weird toggled on Developers Options, clean flash and all. I'm puzzled. :confused:

Edit: I am reading it's related to Strict Mode being enabled...but it's unchecked here. The option is displayed as "Strict Mode enabled". I've toggled it on/off to get rid of the red border but nope. It's still there. This...is...becoming annoying.

Final edit: I solved the issue by entering these entries in my build.prop:

"persist.sys.strictmode.visual=0"

"persist.sys.strictmode.disable=1"
[Vibrant Android Development] :
persist.sys.strictmode.disable=1

add this code into system/build.prop and reboot. ROM work very fast one issue is battery drain so fast overnight lost 10% with Spirit ROM lost 1%/2hours
[Vibrant Android Development] nirogu325:
I was editing my post with two build.prop entries when you posted, lol. I've just flashed iyahman's latest Semaphore build. Are you using that specific kernel?
[Vibrant Android Development] :
With Spirit I use stock kernel of epicboy and Omni I use iyahman's kernel 7/2/2015 not lastest but new.

New semaphore kernel Does it improve battery life (only thing I need) ?
[Vibrant Android Development] nirogu325:
What does Battery say? What's consuming it the most in your case?
[Vibrant Android Development] :
Most consuming is screen. Battery say normal but when screen-on device awake all the time and deepsleep sometime device awake. With Spirit when screen-on device sometime awake not all the time when I play game or something heavy device just awake and screen-off device never awake. My opinon Spirit is friendly battery Omni is fast
[Vibrant Android Development] nirogu325:
Been using a ported version of Omni since December without battery issues. Now moving to epicboy's version. No wakelocks at all. I only installed the Pico PA Gapps along with the essential apps. Nothing else. Right now Screen is the highest in Battery here cuz I'm setting up the ROM. To me, it looks like your battery culprit could be either of these:

- A misbehaving app

- Auto-Sync misbehaving by itself or on some app

- GPS or something else turned on

- Some app trying to get root access repeatedly

- Media scanner going wild by some corrupt file, your device needing an internal and or external SDcard wipe

Something is definitely causing your wakelocks and it may be an app or several apps you currently have.
[Vibrant Android Development] :
Dose your battery drain fast? What percent drain overnight with new Semaphore kernel? Sorry for my bad English

---------- Post added at 01:46 PM ---------- Previous post was at 01:39 PM ----------

I turn off auto-sync like Gmail, Dropbox. Always turn off GPS only wifi turn on when I sleep turn off everything except mobile signal. I don;t have extenal SDcard. Superuser I choose auto allow

---------- Post added at 01:48 PM ---------- Previous post was at 01:46 PM ----------

Aaa with wakelock it said android system drain battery. But battery said no
[Vibrant Android Development] nirogu325:
No. Battery drains normally here. Could be your battery going bad or dirty battery contacts? Battery drainage usually depends on the device's usage and running scripts and apps. Careful on auto-allowing root, that's a free pass for malware apps if they ever get to your phone. Since you have Auto-Sync off, all points to some app, your internal memory needing a good wipe...or the battery itself.
[Vibrant Android Development] :
You use lastest Semaphore kernel 21/2 Does it improve battery life and performance? My screen-on is 2hours or more
[Vibrant Android Development] nirogu325:
All iyahman includes is the newest Linaro Toolchain as of his post. That impacts general performance/responsiveness. As quoted from here:

You are always welcome to try the default version of Semaphore.

---------- Post added at 03:10 AM ---------- Previous post was at 03:01 AM ----------

This is the changelog about the newest toolchain included in that latest iyahman Semaphore kernel.
[Vibrant Android Development] :
Thanks. I have tried kernel on Spirit. It is fast and friendly battery :D
[Vibrant Android Development] :
[MENTION=3059141]nirogu325[/MENTION] Do you have file Bigmem.zip of iyahman? Seem like he delete all file on google drive and mega
[Vibrant Android Development] nirogu325:
No, I don't have that file because it causes this.
[Vibrant Android Development] dzee206:
Here ya go, http://www.mediafire.com/?w67y1sc8ahkix8t. Uploaded the one's I've been using by Kasper_h from the i9000 forums.

Sent from my Half Baked Vibrant
[Vibrant Android Development] :
Thanks but when I open Camera and change to video recoder camera force close
[Vibrant Android Development] nirogu325:
I thought I quoted you previously with a post telling the consequences...it is actually 3 posts above this one...
[Vibrant Android Development] :
Oh I see. Do you know how to fix it?

Sent from my SGH-T959
[Vibrant Android Development] nirogu325:
No fix exists. This said by developers years ago.
[Vibrant Android Development] :
Ok. If after I flash bigmem, Can I play video on youtube or in SD card ( 720p or 480p) ?
[Vibrant Android Development] epicboy:
You would also need to enable big mem patch in semaphore manager. It worked for me :)
[Vibrant Android Development] :
Yep it work for me only issue is 720p video recording

Sent from my SGH-T959
[Vibrant Android Development] RudeBwoy:
did anyone test the sv semaphore kernel with this rom?
[Vibrant Android Development] :
No I only test "v" version but seem like 720p video recording will broken with "sv" version

"v" + "bigmem" = "sv" like that

Sent from my SGH-T959
[Vibrant Android Development] epicboy:
I used to use sv. Sv with bigmem zip and bigmem switch in semaphore manager. I don't remember having issues with camera using that setup.
[Vibrant Android Development] :
Really I will try now

Sent from my SGH-T959

---------- Post added at 12:21 AM ---------- Previous post was at 12:14 AM ----------

And [MENTION=5562721]epicboy[/MENTION] have you read my PM ?

Sent from my SGH-T959

---------- Post added at 12:40 AM ---------- Previous post was at 12:21 AM ----------

I am trying sv with spirit rom and it work camera 720p video recording and video player 720p are work but when i switch bigmem and reboot video recording broke only 720p video player work. It enough for me now :D

Sent from my SGH-T959
[Vibrant Android Development] dzee206:
Its what I'm running now, except I disabled big mem libs in semaphore manager and now camera is working flawlessly again. Just a heads up semaphore still works on older roms. Like a week ago I went back to C-rom 5.8 (4.4.2) and nothing seemed to be broken which was surprising to me lol, honestly thought I would of had all kinds of issues but luckily that wasn't the case.
[Vibrant Android Development] nirogu325:
Gonna try that method. Btw did you flash the bigmem libs or not?
[Vibrant Android Development] dzee206:
Yes I did but that was only cause I assumed for some reason I was on the "v" version... Facepalm

EDIT: [MENTION=3059141]nirogu325[/MENTION] I hope this works and you can actually use the sv version especially since its been an on going issue for you.

Sent from my Half Baked Vibrant
[Vibrant Android Development] nirogu325:
Thanks. I surely hope it works. Doing a nandroid before flashing the libs and the kernel. Will report back.
[Vibrant Android Development] nirogu325:
This attached picture might answer your question. If Android System is causing the wakelocks...then it is the Google Apps you are flashing. I suggest flashing the ROM first, settle your settings, then go to Recovery and flash the Google Apps. Ever since I do this, I'm no longer having battery drainage due to GApps. I personally suggest these (choose the 2nd option with the most downloads) which are the Pico Google Apps from this thread.
[Vibrant Android Development] epicboy:
Rendimiento?
[Vibrant Android Development] nirogu325:
That's spanish for "performance". I'm not currently the main user of the device.

Edit: So far the SV version works. Video and HD Recorder working fine for the first time...as long as I don't touch the Bigmem option inside Semaphore Manager as [MENTION=4284290]dzee206[/MENTION] said.
[Vibrant Android Development] dzee206:
Well damn its about time you joined in on the fun haha, glad that's all sorted now. Now you have a bunch of other ROMs to choose from that you weren't able to use previously.
[Vibrant Android Development] nirogu325:
Like which? Lol I'm not moving to a CM(lag)-based ROM ever again on this device.
[Vibrant Android Development] dzee206:
OK if you put it like that the pickings are slim (no pun intended), not many slim based ROMs to choose from for the vibe any more.

Sent from my Half Baked Vibrant
[Vibrant Android Development] nirogu325:
It's ok. Omni has fit the bill way better than every other ROM on the Vibrant. I'm only losing 1.9% per hour with very decent performance.
[Vibrant Android Development] :
Thanks for your help :D

Sent from my SGH-T959
[Vibrant Android Development] RudeBwoy:
agreed CM based roms are a no no, this Omni + greenify, tasker and Xposed is the best thing since samsung made the vibrant
[Vibrant Android Development] :
I lost 1% per 2 hours with Spirit :D
[Vibrant Android Development] selmandeli:
This ROM is good but I had problems with the baseband and mobile network after flashing Iyhman's kernel.

---------- Post added at 06:42 PM ---------- Previous post was at 06:40 PM ----------

I agree about the Spirit ROM, but it gets laggy after few days.
[Vibrant Android Development] nirogu325:
At the cost of performance, as [MENTION=1927548]selmandeli[/MENTION] said above. I'd rather pay the extra 0.99% per hour for a more consistent experience. That's the price you pay in CM-based ROMs. It is sad CM is no longer what it used to be.
[Vibrant Android Development] dzee206:
Cm just hasn't been the same since they went corporate. Haven't ran a cm build since sada's last release or was it epicboy's lol I done forgot.

Sent from my Half Baked Vibrant
[Vibrant Android Development] :
If it get laggy you go to privacy guard > advand > reset allow/deny counter and go to performance > kernel tweaker > reset > refresh. Device smooth again It work for me :D

Sent from my SGH-T959
[Vibrant Android Development] RudeBwoy:
but you missing the point, Spirit is an awesome ROM, but you don't have to worry about the lag at all on the Omni
[Vibrant Android Development] :
Agree with you Spirit is an awesome ROM, I have used the ROM several months it run like charm and have so many features good battery and good performance. Hope epicboy can build Spirit v2.0 from soucre for our vibrant
[Vibrant Android Development] nirogu325:
I've read the CM lag comes from Theme Manager running in the background even when not in use and that it is a buggy mess CM created with that thing. Omni does not use Theme Manager. I think SlimROMs recently steered away from it in favor of RRO Layers. In fact I've noticed an impact in performance in my Galaxy S3 when using CM. For example, things such as entering a lockscreen pin number lag on CM, yet it doesn't on Omni.
[Vibrant Android Development] :
But I really don't understand why Omni drain battery faster than CM-base ROM it size ≈ 150Mb and if I disable CM Theme so it don't laggy anymore?
[Vibrant Android Development] nirogu325:
You can't just delete the apk and be done with it. You'd have to build the ROM without it from the ground up. Omni just drains 0.9% faster in normal circumstances as you saw in the screenshot. It's not that much.
[Vibrant Android Development] :
Yep I just delete it :D My current device is vibrant so I need more battery than performance so I choose Spirit if I have new device I will choose Omni :)

Sent from my SGH-T959
[Vibrant Android Development] :
Hey everybody look Semaphore Recovery have Rainbox mode

Sent from my SGH-T959
[Vibrant Android Development] :
Deleted post
[Vibrant Android Development] :
Luckily Humbro is building lollipop for vibrant

Sent from my SGH-T959
[Vibrant Android Development] rodman01:
Its already finished and up and ready to test :).

http://xdaforums.com/showpost.php?p=59106020&postcount=1345
[Vibrant Android Development] epicboy:
Hopefully this boots up, then these vibrant users will finally get what they want :)
[Vibrant Android Development] :
Is this lollipop ? :)

Sent from my SGH-T959
[Vibrant Android Development] epicboy:
Yes I believe so
[Vibrant Android Development] RudeBwoy:
seriously???? has anyone tested it?
[Vibrant Android Development] :
Yes test here I will upload screenshot in few mins ;)