yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] notta:
Since you posted in the fascinate thread I can only assume that you are saying you will add the fascinatemtd to your roster? Clarify and if it is the case I will gladly get a device tree up for the fascinate folks.
[Fascinate Android Development] notta:
Source!

Ok, so I put in some work today and have source up on github as well as a local_manifest. I ran through the builds for confirmation and I also will be uploading the builds from said source to goo after this! Same BETA3 just new date.

I freshly forked the repos and redid the commits, it did get a bit daunting so I might have gotten a little lazy at the end. The only thing that I believe is different is I left DocumentsUI as a standalone and I think PA OTA is still in. Whoever uses it can decide if they want that or CMFilemanager.

Since the source is up now this will most likely be my last builds unless of course there is an issue! I'll peek back every so often.

Github
[Fascinate Android Development] ayysir:
noice
[Fascinate Android Development] jkok:
acually notta ide personally love to see what commits you have made to your device trees i was always curious on what you did differently then what me and [MENTION=4911249]Unjustified Dev[/MENTION] have done (as we use the same device base, and edit when needed, mines a forked one of his tho) ive barely managed to get the UI glitching out of the DU builds(still happens, but not as much if any), but i need to update it to DU 7.1 anyways, and ide love to see what all you did differently and compare where the base we are using is leading to errors :P
[Fascinate Android Development] Legitsu:
[MENTION=3128576]notta[/MENTION] did you add a fix or work around for the devil kernel incompatablity issue or is it just luke that hp isn't getting it with the latest beta 3 I am still on pa_fascinatemtd-4.3-BETA3-20140506.zip
[Fascinate Android Development] skepticmisfit:
is it safe to say that we may never have stable kitkat for this phone.. most people who still have this phone as their daily drivers are using older versions of android.
[Fascinate Android Development] Legitsu:
I been using it as my daily for 3 weeks now no issues at all
[Fascinate Android Development] kb8no:
No data drops? That's been the problem that drove me back to 4.2.2.
[Fascinate Android Development] supdog:
MMS failures, no ring, changing ring and notification tones, and (rare) random reboots. PA has been my daily driver for months and at times I have been quite disappointed... but notta is da man, so I'll throw this down----

Any dev who can give me a stable KK gets a $50 donation.

---------- Post added at 04:51 PM ---------- Previous post was at 04:49 PM ----------

To be fair I have to mention that Verizon is part of the problem. I use a mifi daily at work and everyday I have to do a battery pull (on the mifi) because it cannot handle switches between 4g, 3g, and 1x.
[Fascinate Android Development] Legitsu:
not that I am aware of I ran data only for a few days no issues

remember the majority of the issues are carrier 3g support is basically non existent in a lot of area's
[Fascinate Android Development] kb8no:
Four days could easily miss the data drops. Also more prominent in weak signal areas. Not carrier related because 4.2.2 = no data drops. If you are not using data then it is not a DD.
[Fascinate Android Development] Legitsu:
could be a minor difference in the way the rom has the tcp windows configured I would start there instead of just blaming 4.4

3g is dead and gone doesn't surprise me that support is hit and miss if it happens more in "weak signal" area's that leads me to believe you need to tweak the TCP/ipv4 stack settings and lengthen the window/retry count

really sounds like its your carrier/location to me just because it doesn't happen on 4.2 doesn't mean its not your carriers fault
[Fascinate Android Development] puterdoc:
I have had great luck with this as a daily driver. I have lost cell service completely a couple of times over the last two to three weeks. I have had 1 reboot and a few lockups total. I have done the manual reboot just to clear a lag here and there and plane mode and back as well. But for the most part it has been solid.

I had been running DU, sorry but LUV LUV DU, but could not handle a reboot after ever call and more. First and foremost, my phone needs to work as a phone (then as a GPS, PDA, life coach, media organizer, entertainer, bar buddy, librarian, etc ha). I like PA too. This is an awesome rom. DU does have more options and is a bit more fun. But, if these two could be combined, hmmm. I understand the compromises that must be done on each to get the functions they provide or don't. PA has had nominal lag and took days to build up before I chose to reboot. Have not played too much with the overclocking yet. I have two of these phones and would test more if I could clone the other as I need one to work all the time. (cloning suggestions welcome)

Audio seems better (maybe just has more steps) and vmail notifications work on DU. Had a msg three days old and had rebooted at least once and never got a notice. Emails, Evernote, and my favorite GPS app Waze works well on this rom, which does require 3G data. I use GoSMS so that all works on both, with camera and flash light good as well. I stole dashclock from another rom for PA, which I think has been added back to DU's next version.

All in all, this has been the most stable 4.4 for our poor little phone I've tried. I am so glad you guys even attempt to make it do what you do and accomplish so much in the process. Thank you all for your contributions and efforts, and keep up the good work.
[Fascinate Android Development] skepticmisfit:
**** it I'm still going to use cm9. nobody could really fix anything after jt left and cm10.1, as good as it is, just isn't as fast as cm9.

---------- Post added at 01:40 PM ---------- Previous post was at 01:37 PM ----------

I think the reason all the other major Galaxy S variants have decent builds of cm11 is because they have dedicated developers who actually know how to optimize and update, not the guys here who basically use 4.2.2 code, have no idea how to even fix anything, and the one dude who did moved to a different phone. face it, anyone who still uses this phone as a daily driver will have to use an older version of Android. data drops and lack of maintenance just don't cut it for me. also, the lag in kitkat is worse than in 4.2.2. WAY worse.
[Fascinate Android Development] Legitsu:
its a SINGLE core phone with 320MB of ram it is what it is

the problem with running older ROMS is that anything older then 4.0 is either gonna much all the ram or its not gonna be compatible with **** most of the useful apps require at least android 4.1+
[Fascinate Android Development] skepticmisfit:
we don't even have custom kernels anymore. cm11 is one of the biggest pains in the ass to flash. this phone is dead as far as I'm concerned. and I personally probably won't upgrade to something newer for a long time due to weird issues IRL
[Fascinate Android Development] Legitsu:
ill do a kernel once I figure out why boot image is broken hp hasn't replied to my thread after I posted a video showing him that his kernel doesn't work I really don't wanna waste 3 hours getting a build environment configured but as the saying goes if you want something done right ....

some of the people here are what I call "make release" devs meaning they can compile and make minor tweaks but as for actually fixing anything yea... good luck with that i guss ill need to checkout nottas repo do a diff on the kernel and see if I can isolate the problem
[Fascinate Android Development] jkok:
im working on a new diu build but i still need to know [MENTION=3128576]notta[/MENTION]'s device, kernel, and vendor tree he used if he can provide it as the ones im using and trying to work with arent doing quite as well, so in the meantime im doing personal builds for testing as i have to fix more graphical glitches that are still present, my gps antennea in both my fascinatemtd's are broken (why i got my second cheep) but so far im more focusing on getting it faster, and possibly making it run a better kernel/vendors as the ones i find that work arent fully working to-que as du is omni-rom baded so i cant just use cyanogenmods without alot of editing so be patient a bit longer =) +im still trying to fix some kinks why screen recordings going bad i might need to look what mines missing compared to pa's
[Fascinate Android Development] hhp_211:
Not doubting toy had problems, but no one else has reported or seems to have an issue. I myself tried multiple times and different ways and it worked fine as long as i let it boot with its included kernel/recovery 1st, then install the newer twrp 2.7.x

I'm definitely not at a point to get full builds from source. Maybe i have environment build issues out other issues that i haven't been able to figure out yet.

I have ideas of ways I'd like to build our setup a ROM, but i see no point in focusing on that till i know i can build the basic ROM...

---------- Post added at 05:06 PM ---------- Previous post was at 05:02 PM ----------

http://xdaforums.com/showthread.php?p=52518891

Post #1188, has his github link in it.
[Fascinate Android Development] Legitsu:
TBH: ill probly just buy a new phone single core is single core its got limitations and no matter what magic you use in the kernel its still 4 years old
[Fascinate Android Development] jkok:
it doesnt have the device tree for fascinatemtd, aries-common, or any kernels is what i mean lol without those u cant build for the specific device, i have some, but not his that seems to be more stable then mine lol
[Fascinate Android Development] Legitsu:
thats because its just a generic CM11 kernel and not a targeted one
[Fascinate Android Development] skepticmisfit:
if we want to get technical about complaining,

this phone has 512 MB of RAM. however, the GPU shares RAM with the system and each version of Android requires different amounts of memory for the GPU and system. i believe even the Samsung firmware had varying amounts of free RAM available (i think it was at 379 on the official GB firmware, where it was originally like 383 on older versions of Android)

Samsung did not update the OG galaxy s range to ICS due to the bloat of Touchwiz and the larger size of ICS not complying with the internal storage of the Galaxy S (which was admittedly pretty low, 2GB on our variant)

when i was running CM7 i felt like my phone was one of the fastest things around. it was a truly amazing experience. i think i flashed to ICS just because i wanted to run certain apps. but if you can live without certain things (google keep, etc.) then by all means, CM7. it's fantastic.
[Fascinate Android Development] Legitsu:
I am aware you can change the cpu/gpu split by patching files (devil kernel does this) but if you need video to work properly you are pretty much stuck with stock witch gives you like 380MB also #define fast

outside of being a phone and a camera it lacks the power todo any thing useful so "speed" is a moot point

if you want snappishness just use a lighter launcher and turn off all the animations

mine doesn't feel "slow" running apps like youtube/chrome can be a touch laggy but again single core no ram crap gpu what do you expect
[Fascinate Android Development] supdog:
A single core device should be able to make/receive calls, send/receive MMS, and connect to wireless data sources without falling on it's face.

($0.02)

The donation amount just increased to $100 for a stable ROM. :fingers-crossed:
[Fascinate Android Development] Legitsu:
mine does that on PA LoL

old phone is old part android has become heavily threaded if you don't have at least 2 logical cores its gonna by doggy
[Fascinate Android Development] supdog:
At least you're correct about the LoL part...funny post, su.
[Fascinate Android Development] jkok:
for all with some lags+battery loss on my du rom here is a init.d script to help with some issues comment/uncomment the ones u need or dont need as it seemed to be an issue with lulzactive settings and the fact i set to "zen" instead of "sio"

just do this:

-(download attachment and remove .txt extention in its name first of all)

-push this attachment to /system/etc/init.d/89kittleapps

-reboot phone (you can wipe cache/dalvik if wanted, but not required)

-see the results, it lowered and/or stopped graphical glitching for me as its loading graphical/animation data a bit faster. but that may be just my part idk its all user-based experiences, i personally use listview animations and a bit more so it may be plasibo but it has shown results so far =)

**note it only works on Devil Kernel (Stock Du kernel in the zip) or at least a kernel with lulzactive(version 2) and sio**

ill get a du update+a new thread when i can so be patient =) (may also work on a odin-flashable package too so idk)
[Fascinate Android Development] skepticmisfit:
the GPU really isn't that bad. i have a nook tablet, which has the exact same GPU as this but with a TI OMAP 4430 processor (dual core, 1GHz) and on that thing i can play the majority of Android games at acceptable settings just fine.

in the case of our phone it's the CPU that's holding the GPU back. keep in mind though, the GPU in this phone (the PowerVR SGX540) is like 6 or 7 years old.
[Fascinate Android Development] jkok:
i personally see better results setting "Force gpu to draw screen" then using GPU maybee thats why some people see lag yet im crystal-clear smooth-sailing idk =S but again its still mattering on each individual device because shock(drops/damage), its total amounts of R/W's done (as it degrades over time like sdcards for instance, but not as fast as the sdcards), anything in there causing damage (dust/sediments/water on circuits or faulty resistors/soldering), and sometimes it also matters on anything on your phone (too many apps in or not in use, ram-eatting hogs, bad user-defined settings, "battery tweaks" as some arent meant for this device and just downloaded/viewed + applied, or something like overvolting (as it makes it r/w more, and with more power to it degrading it further over time if constant)

i personally use lulzactive+sio (defaulted at 1000/100, or undervolted to 800/100 if i dont want to use too much battery), minimum screen brightness, no auto rotate(enabled if i need it), and i adjust my lulzactive settings from my new default battery-friendly to "preformance mode" via that init.d script i posted (requires commenting/uncommenting required lines i put) so if i know i need preformance i change the script, apply permissions(usually not needed but i do if it changed), reboot and its faster, but more ram-usage, then revert to battery-friendly otherwise, balanced if wanting to test something;

overall it really matters on the users indiviual devices for cpu/gpu chips as some degrade over time like if you use the same sdcard for 8 years or the same battery for 5 years, its bound to wear down overtime, but still the cpu/gpu and even the HDD doesnt degrade as fast, but it still happens mattering on usages (you can make em last over 10 years, but if you use a "Battery killer" like app to drain battery, but are plugged in you can run the app 2-3 years straight and it uses soo many R/W's to the cpu/gpu that it can die 8-9 years early for instance to prove cpu/gpu degrading if your device doesnt overheat lol)

**edited mark here**

i also use ram-hungry apps, so im not acting like a hypocryte

i use:

-next launcher lite (but get-jar Gold paid all features, with high quality enabled, all features on but the 3d mode as its not a get-jar compatible payment)

-Go Sms

-Facebook app+messenger

-Some Dirty Unicorn Settings (like toast/system/listview animations, Circle bar(with multitasking)(releasing soon dw), OmniSwitch, Statusbar+lockscreenmods+lockscreen notifications, and more)

i still only have around ~70mb to 100mb Ram free at a time, with no lags, no reboots, minimal graphical glitchings, but overall stable, so thats why i have issues finding whatr people have problems with as i use 2! fascinates to test my roms (one deactivated on verizon to test, my daily-driver after it looks stable) so idk what all is causing it as i cant get logcats of errors i dont have =S
[Fascinate Android Development] wws12:
Hey guys, been having a problem with the April 10 build. Sometimes my phone will report low battery and shut off. If I try to turn it back on, it boots up fine and displays a full battery. This happens most often when I've finished charging it. Anyone else have this issue?

Is this fixed in a newer build, or it it a setting I have to change?

Thanks,

wws12
[Fascinate Android Development] puterdoc:
I had a similar thing with the battery and charging. I first thought I finally killed the jack and it wasn't charging. Then thought the batteries were going, and so continued thinking it must be me.

It seems to be better over the last few days for me. I have swapped batteries back and forth as I have a few. That was actually my original reason for rooting, charging after market batteries in the phone. So short sighted then. Anyway, could it be that some of the google apps updated and screwed something up, then fix with another update? I even considered a wipe and redo but it did improve.

Either way, you are not alone. I've had a few issues and instability that have popped up over the last week that hadn't been around until now. It is still my daily driver for now.
[Fascinate Android Development] hhp_211:
[MENTION=4731993]wws12[/MENTION] [MENTION=1903184]puterdoc[/MENTION]

Yes I've noticed it on several ROMs.

Currently running cm11.

Mine usually happens the other way...

I'll have 75% then get a random reboot and battery will come up showing 14% or less ( the red zone) and a 2nd reboot usually will fix the issue, sometimes it takes a 3rd...
[Fascinate Android Development] jkok:
make sure u have a battery with the brand of phone u have (e.g. official samsung 1500 mAh/2200mAh v.s. a generic 3500mAh Made-in-china battery) as it doesnt have the right computer chip in the battery terminal for our phones sadly making it reset and mis-calibrate what the percentage is even if it says "replacement for SCH-i500" make susre its an official Samsung battery as i dealt with this all the time thinking it was the codes, but instead its a faulty or missing chip in the battery's terminal itself

if u had a samsung battery have it discharge fully untill it shuts off, to do so do these:

turn it on (and wait for it to turn off at 0% then repeat, or just leave it on recovery with screen shut off (set to 0 on TWRP, always on for CWM) and leave it on overnight while you take a rest as this gets frustrating after a while, then try turning it onto system (pull out battery, put in, reboot into system as normal), then if it shows the "Samsung" Boot logo and shuts off you are good, pull out the battery one more time, put in, and put onto charger WITHOUT TURNING INTO SYSTEM OR RECOVERY! then it will show 100% after a while, pull out the battery AFTER you unplug it and repeat and it will show a bit or majorly lower, u will need to charger and repeat untill it shows 100% on the turn on, then you boot into system and it should be good as long as u use a SAMSUNG battery =)
[Fascinate Android Development] wws12:
Will this be updated to PA 4.4.4 Final release?

Thanks,

wws12
[Fascinate Android Development] astonmartin214:
how do I flash this since am on stock
[Fascinate Android Development] aircooledbusses:
Start with the OP

There is a thread for that.......probably starts with can't flash in the help section.

To the best of my recollection from stock

Gb bootloaders

Cm fix for all

Milestone https://www.dropbox.com/s/i20kuqtho9hn2pv/superclean__sc3_milestone2_full.zip

Then flash the ROM, maybe twice for the kernel

Super su

Gapps

Enjoy
[Fascinate Android Development] Lgrootnoob:
does anyone know if i had an armv7 libart.so from 4.4.3 that i could just replace it in the rom?

the reason being is that:

ART Changes in 4.4.3

d5e4ac0 : Properly tolerate missing declaring source files

c0f96d0 : Fix stack overflow for mutual recursion.

0c6afa4 : Fix NewLocalRef, NewGlobalRef to handle cleared weak globals.

7170092 : Search for miranda methods in virtual methods instead of interface.

3addc29 : Fix stack trace for proxy methods and added test case.

8151b8f : Fix FindFieldID to use class's classloader to find field type.
[Fascinate Android Development] mes215:
Hey guys,

I think I need some help flashing the updated version to my Fascinate. Every time I reboot into recovery using GooIM to TWR, It tells me that the update failed. Then, I reboot back onto my current build. I'm currently on Paranoid Android version 3.10-L13N. Andriod 4.2.2

Is my problem that I have to wipe the device completely? I was under the impression that devices with PA 3.0+ would not have to wipe to install. Anyone have a handy guide on how I can update to the most recent version? I was trying to install PA Fascinate 3.99-RC2.
[Fascinate Android Development] hhp_211:
Pa 3.99 is Android version 4.3 and a major upgrade from 4.2.2

Full wipe would be advised...
[Fascinate Android Development] monochrome83:
I've been running this ROM for around 6 months, so I suppose its about time to comment... ROM is running great, couple FCs for Chrome, and Google play music, so installed Firefox and Apollo, no issues there. Battery life's been excellent. KitKat has been a little taxing on the old ass system, but hoping development isn't dead on this gem.
[Fascinate Android Development] astonmartin214:
Hey does anyone still have ROM the link is down want to flash data is spotty on CM11
[Fascinate Android Development] wws12:
Hey guys,

What's the best cpu governor to use with this ROM to balance energy efficiency and performance? Currently on interactive.

Thanks,

wws12
[Fascinate Android Development] astonmartin214:
Hey can you post a link so I can download this rom
[Fascinate Android Development] hhp_211:
Just had to follow link in op to find

Your welcome

https://goo.im/devs/notta/roms/fascinatemtd/pa_fascinatemtd-4.3-BETA3-20140508.zip

.
[Fascinate Android Development] astonmartin214:
Thanks man & I did but there was no goo link to go to
[Fascinate Android Development] astonmartin214:
How do you flash this ROM meaning which recovery cause I'm on TWRP 2.6.3.0 won't flash & I can't get to CWM 6.4......
[Fascinate Android Development] Godlovskiy:
Is there any one working link to the latest version ?
[Fascinate Android Development] DjPorkchop:
Yeah I would love one as well.

My old Fassy is in great shape and I hate to let it sit. All I need mine for now days is to basically be a glorified MP3 player as well as ruin a app or 3 and to use the camera. Camera sounds stupid I know but I have a 2014 Moto X and the camera on it just blows!!

I currently have the SlimRoms SlimBean 4.2.2 on the Fassy but it is bad laggy and most apps will not work on it as it is to old and the battery drains form 100% to dead in a few hours. Even if the phone is turned off. I have to pull the battery to save it.

I found a link to files but not sure I can post them here and I am not a spammer so I will refrain. I am going to give it a try from the other site i found but man I really hate to follow any site unless it is XDA.

Any links or help would be awesome. The old fassy is not dead just yet!
[Fascinate Android Development] icemanwbs:
Have 2.00 up and running with devil 1.4.1....any reason to upgrade to new 2.12 ? Just curious
[Fascinate Android Development] vrahn:
My phone keeps telling me com.process.Google.gapps has unfortunetly stopped.
[Fascinate Android Development] LasVegasRomeo:
Did u try wiping both cache 's. Reflashing gapps then fix permitions?

Sent from my SCH-I500 using Xparent Blue Tapatalk 2
[Fascinate Android Development] notta:
Give what LasVegasRomeo said or better yet full wipe if you haven't done so. They install fine on mine. :o

That didn't make it but I can confirm this Fixed Touchwiz TaskManager will make you feel right at home... :D

I just pushed this to system, no reboot was needed!

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