yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] xc-racer99:
Source Code and Downloads

Main Source

http://github.com/omnirom

Device Specific Source Code

http://github.com/xc-racer99/android_device_samsung_fascinatemtd for the device tree (see android-5.1 branch)

http://github.com/xc-racer99/android_device_samsung_aries-common for the common device tree (see android-5.1 branch)

http://github.com/xc-racer99/android_kernel_samsung_aries for the kernel (see android-5.1 branch)

http://github.com/xc-racer99/proprietary_vendor_samsung for the prop blobs (see android-5.1 branch)

Downloads!

All builds are found at https://drive.google.com/folderview...VVSzJxYVU3eHlWZGR1VVNZUWk1V1QzOUk&usp=sharing

Gapps

Gapps can be installed from http://xdaforums.com/showpost.php?p=59731008&postcount=2

SuperSu

SuperSu can be found at https://download.chainfire.eu/696/SuperSU/
[Fascinate Android Development] Ophidian_DarkCore:
Make sure to do the following before flashing this rom: flash this https://mega.nz/#!YBYXGTRI!7NscLqn139vvNCroS94HlQ6uNYpTFqmc1y3ktvtQIsw in odin https://drive.google.com/file/d/0B0J5C6YxKg67bW11WFJrbjYxNW8/view?usp=sharing

Gingerbread bootloader is required, you must have previously been on cm11 before using this rom, otherwise go to one of the cm11 threads and follow the 'from stock' instructions.

EDIT: recommended gapps https://basketbuild.com/devs/TKruzze/5.1.x GApps Packages/MODULAR - Pico GApps
[Fascinate Android Development] xc-racer99:
Thanks, I wasn't sure how you installed it. Will update OP.
[Fascinate Android Development] hhp_211:
OK, Only worked from the odin cwm.

I tried flashing and while I got*cwm 6.0.5.1 and/or twrp,,, It looked like it installed cm11 and/or omni,,, but nothing ever booted, always looped back to recovery.

1st impressions are wow!!

looks good and kernel has OC

and a few nice features.

Good work on all involved!

Installed beta SuperSU-2.49

Gonna test with 200/1400, interactive(tweaked), deadline-1024, KSM-off, standard LMK. for now*

Stable so far.

I'll test changing vm heapsize and LMK values

Also trying omni switch, but probably go back to asop recents as its using a lot of mem

oh and I'll check Big Mem settings too.

So far no gapps installed yet but loaded up subway surfer and candy crush,,, both had significant lag before,,, on cm 11, du, slim before,,, but are running fantastic so far on omni !

Later:

Gapps : I went very minimal install package,

Yes performance still takes a hit and I've also noticed some random reboots too.

I'd like to go back and try again without a gapps to make sure/verify, but i don't remember any reboots without gapps.

As a side note,, I wish some one could build a modified base play services that didn't have all the extra services stuff like,,, in car, fit, nfc, weareable, etc.

I always disable that stuff even on my other/main phones.

.
[Fascinate Android Development] Ophidian_DarkCore:
i juse disableservice and autostarts for that stuff.

my experience has been this rom idles for several days and no crashes. i guess oc's but a last_kmsg would be nice. then have a logcat gathering while you try to recreate the crash. or gtfo?

i was surprised to have 1400. i could never get hummingbirdover 1300 on gb, and i overvolted the piss out of it. even my other hummingbird(sammy aviator).

EDIT: "interactive(tweaked)" hispeed_freq?

edit edit: ksm is optimized in this kernel, and row is best for our flash until fiops is added. ;)
[Fascinate Android Development] Godlovskiy:
will new releases ?
[Fascinate Android Development] Ophidian_DarkCore:
I'm working out lots of bugs and improving performance. Expect a much improved build soon.

Meanwhile, I'm gonna be jamming out on one of my test builds(24 bit audio anyone?) :p I figured out gcc 4.8. all i'm gonna say for now is it's a user build, debugging all disabled in the kernel, fiops is proposed, telephony all removed, art is set to fully optimize. a bunch of awesome sauce that I'm not gonna tell about just yet ;)
[Fascinate Android Development] Godlovskiy:
***I'm working out lots of bugs and improving performance. Expect a much improved build soon.***

in buld 08/01 when I turn on OC phone don't wake
[Fascinate Android Development] xc-racer99:
OC is very phone specific. An OC that works on my phone may not work on your phone. That's one of the reasons the clock speed is normally only 1Ghz - all devices can support it. Some will definitely support higher (there were rumors of people going up to 1.8Ghz a few years back...). For me, 1.2Ghz is stable, 1.4Ghz often crashes.

If the phone isn't waking with an OC, you've pushed it too far. Try a lower OC.

The only way I can do new releases is if somebody sends me bug reports. Since I don't have a fascinate, I can't see what problems will appear. Anything I find out that is wrong on my device (essentially a Galaxy S 4G) that is common with the Fascinate will come to the Fascinate but I haven't found anything like that since I put up the last build.
[Fascinate Android Development] Godlovskiy:
it is noteworthy that in build from 30/07 this is not observed
[Fascinate Android Development] xc-racer99:
Ok, that is very noteworthy. I figured it was the same on all of them. Does it only not wake up when OC is enabled? I'll have a look through my code and see exactly what changed.

The most likely way to get around this, so to speak, would be to replace the boot.img in the new build with the one from the older build and then flash the zip. OC is mostly at the kernel level, so the boot.img should be the trick.

If someone does this and they don't see any adverse effects such as wakelocks, I'll do up a new build with the relevant change reverted.
[Fascinate Android Development] Ophidian_DarkCore:
OC didn't actually work in that build I think.

---------- Post added at 01:57 PM ---------- Previous post was at 01:55 PM ----------

On 200 to 1.4 it stays on a black screen unless you fiddle with the volume buttons before waking the screen.
[Fascinate Android Development] Cross09:
I can help you with bug reports,you just shoud tell me what I have to do
[Fascinate Android Development] xc-racer99:
Awesome! Find what doesn't work, reproduce the issue, and then take logs as per http://xdaforums.com/showthread.php?t=2185929 and then let me know. It helps if you explain in detail what exactly you do - more detail is always better than less. While this doesn't really apply here as there's not many builds, its always good to know if the bug is a regression (ie it worked in past builds but no longer works) or if it never worked in the first place.

To transmit this info you can use the bug reports tab at the top of this thread, PM, or just post in the main thread, it doesn't matter to me.
[Fascinate Android Development] Ophidian_DarkCore:
Here's something for you to do. When headphones are plugged in, no music is playing, and the screen is off, collect logs on why it won't come back on until the headphones are removed. Collect a logcat constantly throughout. Then grab a kmsg and dmesg after you remove the headphones and turn the screen back on.

Collect logs during listview scrolling.

Let me know if the play store can install apps.
[Fascinate Android Development] quickgiant:
If you got 24 bit audio working, you would be my hero. I've been using this thing as a media player for a long time and it's fantastic, but I've been having some issues with Geewiz Media and this would be a nice improvement.

THANKS!
[Fascinate Android Development] xda_bg:
I also would be thankful if you would add 24 bit audio.

Thanks
[Fascinate Android Development] Ophidian_DarkCore:
the frame size of 10 million exabytes is larger than my patience^2

http://i.imgur.com/eljXmhJ.png
[Fascinate Android Development] xc-racer99:
New Build Uploaded!

Changelog for 2015/08/13 Build

Untested!

Encryption should now work

Keymapping may be fixed

A quick status update on this project: I haven't gotten any bug reports so I don't know where to go next with it. As I don't have a Fascinate myself I can't do anything with it. I can only add the bug fixes that I believe are in common with my device. Selinux is still in permissive mode as I don't want to break anything by putting it to enforcing mode. If someone can send me a dmesg from this latest build I can rectify that on the next build, assuming that at least one person is using this ROM.

With regards to 24bit audio, that's not my territory. I'm not very sure of the audio system. For me, its low priority and I want to fix some other bugs on the Galaxy S 4G first (mainly the laggy video recording....)
[Fascinate Android Development] Ophidian_DarkCore:
and i've been tripping hardcore for the last two days ~~whats new
[Fascinate Android Development] Godlovskiy:
phone did not wake up after locking in the first two builds of all was the norm

:(

Now try to change the boot.img from the old to the new build, may be all right

I put boot.img from the assembly by 30.07 in the new build , so far everything is normal

:o

No, nothing happened , and now when I block the phone , he just shuts down

I found a problem in performance tuning need to put a minimum processor speed of 200 MHz , and only then start all operate normally. Governor ondenmand 200-1300 MHz

:good:

but with this there is a bug with boot.img TWRP
[Fascinate Android Development] xc-racer99:
So let me get this straight - things work as they should when there is a minimum processor speed of 200Mhz and you're using the first build's boot.img? Have you tried the latest build but setting the minimum processor speed at 200Mhz? If things only work with the boot.img of the earliest build then I know which change to revert. Otherwise, just set the minimum clock speed at 200Mhz;)
[Fascinate Android Development] hhp_211:
Yeah! Thanks! Thanks! Thanks!

My kids have been using this as their gaming devices and haven't mentioned any issues,,, but they also had to put up with a lot of faulty builds and/or bug issues over the last 1-2 years,,, so this is fantastic and stable and can play games with no to little lag that were totally unplayable before ( subway surfer, candy crush saga, etc )

I'll drill them a bit and what they think.

I'll update to this version over the next few days and get you a dmesg log.

I'll make note to check the 'home' key mapping

A far as I'm concerned,,, please always keep builds as selinux permissive.

24 bit audio is a low priority from my end as well,,, but I understand others have used this as an in car audio player device...

.
[Fascinate Android Development] Godlovskiy:
Yes , I tried to put on the new build rate of the standard kernel , but no results, but I doubt that it is the frequencies , the problem was in the build, from 01/08 , were treated as replacing the boot.img. in build on 01/08 unlock works on 100 MHz , but in build 13/08 only 200MHz
[Fascinate Android Development] Ophidian_DarkCore:
Somewhere a lonnnnng time ago i think it was adamoutler that said hummingbird uses no more power at 200 mhz than at 100 mhz. therefore it would be a waste to have min set to 100 to begin with. yes, ondemand is godly 200 - 1400 for this phone.

[MENTION=983303]hhp_221[/MENTION] would pageplus be viable for me as a 16 year old?
[Fascinate Android Development] hhp_211:
Well 1st it's hhp_211 not _221, lol.

Yes I was gonna post about the same 200 mhz using no more power than 100, I remember seeing all those stats and testing threads way back.

Page Plus is great for me,,, I use the 29.95 plan = 3000 minutes,, 1500 texts,,, 500 gb data.

They, just this year, added 4g data which is nice,,, I'm always on Wi-Fi though and usually barely use ½ my data...

You just have to provide your own phone.

For new the fascinate and now a moto g have fit my needs great.

And it saves a ton over a big red contract

Only downside I see is it's getting harder to come across unlocked cdma models that can have custom ROMs done, which is becoming more important to me so I'm going to explore t-mobile & att at some time.

.
[Fascinate Android Development] tekweezle:
Glad to see there is still development on the Fascinate.

I moved to the LG Ultimate 2 L41C. Better phone overall and still compatible with the ppc standard plan since it's a 3g phone.
[Fascinate Android Development] hhp_211:
Short time on latest build 2015/08/13 so far

home key appears to be fixed and working proper. :good:

here is a dmsg View attachment dmesg.txt

this was taken right after a reboot from a 'sleep of death' as a few have mentioned, (no fiddling or long pressing worker & not near charger)

"fiddle with the volume buttons before waking the screen" does sometimes work,,, as does unpluging/pluging from charger

I'll be happy to investigate more if you can point to any ideas.

Also running this time with the gapps mentioned in the 3rd post and performance, so far, seems better that earlier build with a different minimal gapps.

running beta SuperSU-2.49

with 200/1200, ondemand, deadline-1024, KSM-off, tweaked LMK (bigger values). for now (( 38, 42, 48, 64, 80, 120 ))

And now Big Mem too.

.
[Fascinate Android Development] xc-racer99:
While a dmesg is always appreciated, for something that crashes a phone, a dmesg doesn't work. The dmesg only contains logs since the crash, not before. If it crashes again, then a last_kmsg is the ticket. Its basically a dmesg for the last time the phone was on (plus some extra debugging stuff).

For what its worth, I don't see any glaring issues in the dmesg provided. There's a couple of minor selinux issues that I won't bother fixing. The only thing that might be connect is the line

<3>[ 3.028525] gpio_event_input_request_irqs: request_irq failed for input 158, irq 171

but I doubt it. Also, when the SoD happens, does a computer recognize the phone or is it totally dead?

Another thing, how is 720p recording? It is just terrible on the SGS4G but I'm not sure where the problem lies.

PS Anybody can answer these questions, it doesn't have to by hhp_211 (but it definitely can be:))
[Fascinate Android Development] hhp_211:
I sent the dmesg b/c you had requested one in an earlier thread, but thought it may also be helpful on this too.

here is a logcat View attachment logcat.txt captured with a sod and only could wake up by plugging usb power to it either from wall or pc, and yes pc recognises at time of connect.

I have tried many times, and failed, to get a sod while plugged in,,, either to wall or to my pc both debugging on or off.

also here is a last_kmsg View attachment last_kmsg.txt which had a few sod and wake up by usb plugging in.

I see 158 is the back key

171 is music ? in the Generic.kl

"720p recording" I current went for big mem, which cuts out ability to record in 720. When I get some time I'll see how it compares to my Moto G though.

.
[Fascinate Android Development] xc-racer99:
Whoops, I forgot that I had asked for a dmesg. I had already got one via PM. My bad.

I'll have a look through the logs when I get a chance and see if anything pops out at me.

Thanks very much!
[Fascinate Android Development] xc-racer99:
Ok, this may be a work-around. Thanks to [MENTION=6319859]Godlovskiy[/MENTION] for testing this. Unzip the latest zip and replace the boot.img in it with this one (renamed to boot.img obviously).

Then,

Other options may work as well but I haven't tested

(For those wondering, the only difference this kernel has with previous ones is that the RIL component of the kernel was added back in)
[Fascinate Android Development] xc-racer99:
New Build Uploaded!

Changelog for 2015/08/31

Updated Android version (5.1.1_r5 to 5.1.1_r12)(upstream Omni Change)

SoD should be fixed...

Untested by me
[Fascinate Android Development] Ophidian_DarkCore:
> http://phoronix.com/scan.php?page=news_item&px=F2FS-FS-Linux-4.3

>_<

La Shetpost
[Fascinate Android Development] aznsephyi:
Came back to my first smartphone forums and am surprised to see there's still development going. Major props developer. Puts a warm fuzzy feeling in my heart.
[Fascinate Android Development] pcwizzy37:
Going from CM10.1 is fine

Going from CM10.1 is fine, you don't have to go from cm11.
[Fascinate Android Development] Ophidian_DarkCore:
Hell I think even some cm7 roms had the mtd conversion.

so long as you get the zImage from op flashed you should be good to go.
[Fascinate Android Development] xc-racer99:
Experimental 6.0 build

Hi all, I was prompted to try to make a 6.0 build, so I did. It can be downloaded at https://www.androidfilehost.com/?fid=24438995911968309. No idea if it even boots, and there's definitely no RIL...

No, it reportedly doesn't boot. Sorry guys
[Fascinate Android Development] Cross09:
No,it doesn't boot
[Fascinate Android Development] xc-racer99:
Ok, thanks for letting me know, I'll remove it. Sorry.
[Fascinate Android Development] Legitsu:
dug my fassy out of mothballs today flashed directly from CM11-TWRP

had to fiddle with gapps to get it working (ended up using a old release of tkgapps as the latest open gapps doesn't work)
[Fascinate Android Development] Legitsu:
for those having SOD issues when overclocked you can install this app from the playstore

https://play.google.com/store/apps/details?id=eu.thedarken.wl&hl=en

open the app and set the wake-lock to partial

this will keep the cpu online and prevent it from crashing when resuming

the downside is that it will put a hurting on the screen off standby time but that may or may not matter to you

attempted to get 1600mhz working but the kernel doesn't support liveoc/bus overclocking
[Fascinate Android Development] Legitsu:
lockscreen widgets don't appear to be working

seems to be a issue with the touch priority as widgets are visible but you can't interact with them

also seeing issues with some full screen lock widgets such as black player not rendering (likely do to scaling issues due to the age and density of the screen)

edit: after some fidding about with the lockscreen settings I was able to get them to 'work' but its pretty flakely and full screen widgets don't work

good enough tho I dug the fassinate out to replace my dads ipod 3g so its pretty much gonna sit on a mount on his motorcycle pulling mp3 duty

I did get viper4android to work
[Fascinate Android Development] xc-racer99:
Ah, I remember that issue now - took me a while to figure it out. There was a mismerge in Omni somewhere. To fix it, go to Settings, Performance, Advanced, and select Force High-end Graphics. In theory, they're disabled to save a bit of RAM but I've never noticed a difference...
[Fascinate Android Development] Legitsu:
that seems to have done the trick

many thx

was there any particular reason RIL was removed other then the phone being older than dirt

id be nice to at-least be-able to use it to dial 911
[Fascinate Android Development] xc-racer99:
From what I've been told, it didn't work (even for 911). As I don't have a Fascinate myself, there's not much I can do about it.
[Fascinate Android Development] pcwizzy37:
The fascinate has a good dpi. it is very very much better than some tablets and cheap android phones I have seen.
[Fascinate Android Development] Legitsu:
The fascinate is also from 2010 the scaling specs have changed over the years

its older then dirt is all
[Fascinate Android Development] pcwizzy37:
Dirt was made at beginning of time so technically it is not older then dirt, my main computer is from 2008 (Asus X83vm) my school computer is from 2003 (Toshiba Portege 3500).
[Fascinate Android Development] Ophidian_DarkCore:
i build kernels on a pentium 4 box. dont even bring that in here. lol

edit: the only reason to use this device is for the dac tbh
[Fascinate Android Development] pcwizzy37:
Whats the RAM and CPU model and Ghz?
[Fascinate Android Development] xc-racer99:
Are you guys interested in another attempt at a Marshmallow build? I think I know what the issue was in the last one I posted...
[Fascinate Android Development] Legitsu:
why not its not like the device has any value lol
[Fascinate Android Development] pcwizzy37:
Even though I hate newer Android versions due to their difficulty, I will make a backup and try Marshmallow (and when I am done I am going back!).
[Fascinate Android Development] Legitsu:
I guess the question is

is marshmallow gonna be any lighter than LP

we are already taxing the ram limits as it is even with bigmem

its a 2010 phone about its only value is a mp3 player and it doesn't even do that particularly well
[Fascinate Android Development] pcwizzy37:
Yes it does, it is very very good with music and video, Just remember to download advanced Task manager to kill all the background apps.
[Fascinate Android Development] xc-racer99:
Alright, I've been using Marhsmallow for my variant and it seems much better than LP. IMO, its now similar (when used without gapps, haven't tested with) to CM11 (with gapps) in terms of performance. RAM-wise, there is an (experimental, but still quite stable) kernel which implements CMA. Basically this means that as opposed to bigmem which disables some of the RAM for the camera, the RAM is only used when the camera is used. So, we have roughly 440MB of RAM available.
[Fascinate Android Development] Legitsu:
does the CMA kernel implement overclocking ... id really like to see live overclocking aka bus strap overclocking support

upping the buss speed really helps with responsiveness

camera is so old its near useless anyway so conceivably you could live without it
[Fascinate Android Development] xc-racer99:
No, I haven't implemented live overclocking. While its been done on the i9000, I haven't added it to the kernel that I maintain (and I don't really have any plans to, but I haven't investigated it fully. Currently reading up on it but absolutely no promises whatsoever).
[Fascinate Android Development] Legitsu:
devil kernel for the fassinate supported it on KK

source

https://github.com/DerTeufel/samsung-kernel-aries
[Fascinate Android Development] pcwizzy37:
Out of all my devices, it is the best camera I have. My LG Lucid (vs840) does not focus very well, And my tablet, (Acer B1-730HD) just has very bad camera (very dark, blurry, choppy), period.

Sorry for going off-topic.
[Fascinate Android Development] xc-racer99:
Yep, and but its probably just easier to cherry-pick the cherry-picks from the i9000 MM kernel as some of the frequency bits were changed. I'm just not sure I want to do it as the kernel is a shared one with my main device and I'm still focused on stability. You'd be welcome to cherry-pick the commits and compile yourself:D
[Fascinate Android Development] Legitsu:
buy a recent phone lol

I have S3 S4 LG-G3

the fassinate is very very old and very very slow by modern standards

think 486 vs Pentium 4
[Fascinate Android Development] pcwizzy37:
I do have newer devices my lucid (which has poor dev support), and my tablet, which has a stupid locked bootloader.

Hey, are you offering me a newer device?
[Fascinate Android Development] xc-racer99:
Alright, can we please stop talking about what our phones/computers are, how old our phones are, if people should get new gear (some can't afford new stuff, others prefer old stuff), etc? You guys can create a thread in General if you want to do that... Thanks:)

In terms of MM, as opposed to uploading a new build, can you guys try flashing the previous build I uploaded (download link is now https://www.androidfilehost.com/?fid=24438995911968309) and then flash the attached kernel (for some reason its not working here, try the one in my reply later) over top immediately afterwards? If the error is what I think it was, this should do the trick. It saves me uploading a 200+mb file over slow internet. Apparently not, I guess a kernel flasher for my variant needs a bit of modification for the Fascinate. Oops...
[Fascinate Android Development] Legitsu:
attachment is borked