yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] pahlevy:
[MENTION=5364192]skepticmisfit[/MENTION] yes, im on Unjust's CM11 build... and [MENTION=5089052]jkok[/MENTION] will this works even im still on Unjust's CM11 build...? :o

thanks to both of you guys... :D
[Fascinate Android Development] jkok:
it could, it did for me, and if it fails flash a different 4.4.* kernel in that thread for kernels for the fassy and it may work ;)
[Fascinate Android Development] dublea:
The GAPPS link is broken with a file not found error.
[Fascinate Android Development] skepticmisfit:
i think there's official gapps for 4.4 now, check goo.im
[Fascinate Android Development] pahlevy:
The low_ram setting was work on some kitkat kernels i tried but it seems too many force closes that i cant permanently solve... :(

So back to unjust build for now... :o
[Fascinate Android Development] Unjustified Dev:
Here she is cm-11 beta build with didhiys kernel I see performance increases you tell me.

http://www.androidfilehost.com/?fid=23501681358542421
[Fascinate Android Development] pastapie:
I'm coming from Baked 8. What recovery do I need to flash cm 11?
[Fascinate Android Development] Unjustified Dev:
Install this zip first http://www.androidfilehost.com/?fid=23212708291679682 the rom will no longer boot but you will have the correct recovery that will allow installation
[Fascinate Android Development] pastapie:
cm 11

Ok i flashed zip recovery wiped and flashed cm11 rom and im geting "android has stopped" error with along no data or wifi. Im going to reflash but if this does not work should i odin back to stock?

Never mind i got it! The trick is to flash rom then run it. Go back into recovery and flash gapps. Have you tried Art with this?
[Fascinate Android Development] Unjustified Dev:
Interesting did you do a full wipe system , data , and dalvik? I would suggest flashing it again after wiping since now your on a newer recovery. Don't mind the words about swipe. our touchscreen doesn't support it :(
[Fascinate Android Development] pastapie:
Figured it out!

I just did a re-wipe everything rebooted recovery then just flashed the rom, boot then play with settings till the rom gets a little settled then went back into recovery flashed gapps then wiped caches. All is good i will report anything funky. By the way, supper killer job dude! :good:
[Fascinate Android Development] skepticmisfit:
ART is probably still buggy. I think I saw someone using a recent build of PA and they had success with it though. I'd say if you want to try it, make a nandroid before doing so
[Fascinate Android Development] hhp_211:
Likey, likey!!!

Have had some random reboots here and there nothing to bad.

Trying to stay with cm stuff as long as i can, for testing purposes.

I know i don't care for superuser...

Stk keyboard not taking swype input.

But overall so far. NICE!!

very responsive and fast,,, but haven't loaded up the gapps stuff yet...

Thanks again friend.

We miss you around here!

.
[Fascinate Android Development] pastapie:
Running ART, didn't really notice anything better as in battery or performance. This ROM is kicking!! :D
[Fascinate Android Development] WillyFourSixty:
Great job Unjust. So far, so good. Matter of fact I've been using your 12/06 android 4.4 build as a daily driver for the last 6mths. It was miles more stable than anything else. I've found any ROM that uses devil kernel to be completely unreliable on our old fassy. Thanks again!
[Fascinate Android Development] skepticmisfit:
i know this is a YMMV thing but i'm running cm10.1 right now with devil kernel and it's running just fine. i can't really get it stable above 1.2GHz but that's overclocking and it can cause a whole different league of issues on any device.
[Fascinate Android Development] WillyFourSixty:
No skeptic, you are absolutely correct and I should have been more specific. I used and loved devil on cm9, 10, and 10.1

I even got it to run reliably for months while oc'ing the hell out of it. I was running 1428-1456mhz while on blackbean8 ROM. Poor phone was smoking....lol.

Devil has been great for me in the past, just not on KK, and I've tried all KK ROMs out there. Only one that was reliable was Unjust's 12/06 CM11 build. With stock kernel of course.

So far Unjust's new one seems solid and definitely snappier. I very much appreciate him and others buying me a little more time before I break down and buy a new device.
[Fascinate Android Development] Ryuinferno:
*deleted*
[Fascinate Android Development] hhp_211:
Deleted
[Fascinate Android Development] Ryuinferno:
Shoot...I think I posted this on the wrong thread...it was supposed to be http://xdaforums.com/showthread.php?p=53216051

Sorry, derped...lol
[Fascinate Android Development] bmeek:
Thanks! This looks really interesting.

I've got an old fascinate that I use with WiFi. It's running cm10.1 - the last official nightly from about a year ago.

Does this build of cm11 use the same partition layout? If not, is it likely to correctly repartition when I flash it, or is it recommended that I Odin back to stock first?
[Fascinate Android Development] Unjustified Dev:
It will get corrected on flash but in order to install it you must follow installation instruction 2-3 pages back
[Fascinate Android Development] skepticmisfit:
Idk if I should really ask this but how is performance and stability in comparison to cm10.1
[Fascinate Android Development] bmeek:
Awesome. An old phone with a brand-new OS...

Thanks - interesting how TWRP is used to setup the partitions and install the ROM, while the ROM installs an updated cwm recovery.

So far, so good. I use this old fascinate mostly as a Daydream clock sitting in a desk dock on the entertainment console... It's WiFi only and occasionally gets used to control a ChromeCast unit, DirecTV, Harmony remote, etc.

The suggestion/need to install the ROM, boot, then reboot to install gapps, initially prevented the Google Play restoration of all my apps. Since I'm lazy about that, and I had initially flashed an already-downloaded-but-old version of 4.4.2 gapps, I was able to reboot into cwm, wipe data, format system, flash the ROM, flash gapps (the pa gapps "mini modular" package built yesterday), and reboot. The initial boot process started all my apps automatically installing for me, so I switched to ART and let the phone reboot ("upgrading" 99 apps to ART took a while). It's now continuing the app restore process while running ART!

Everything looks great! :good:
[Fascinate Android Development] WillyFourSixty:
Mine doesn't random reboot. I've only had it do it once when I was running it hard via constant YouTube. So far it has been very consistent for me. MMS works fine. I like it a lot. Thanks again Unjust.
[Fascinate Android Development] hhp_211:
Really, it was really starting to frustrate me.

That's good to know,,,

maybe this phone is just different enough with the tolerances hardware-wise from the one that i used to use over the last 4 years... That one went to my wife and now to my kids for them to use.

Guess i need to see if i can swap it out one day real soon...

But i think I've finally gotten a stable platform!

After a lot of adjustments the biggest change to effect the overall result was setting

build prop:

dalvik.vm.heapgrowthlimit = 60

up from the standard 48

Along with not overclocking...

I 1st tried [MENTION=1830871]1320[/MENTION] then [MENTION=1348102]1200[/MENTION], but this phone doesn't like this kernels version,,, neither does it like the smartass V2...

Currently doing 1000, interactive, noop

Will go back and test 'row' setting tonight probably.

Last night i achieved 4± hours runtime fairly hard web/G+ usage and not a single reboot

That's 2.5 hours screentime.

Not too shabby for our little single core, old phone, tiny 1500 battery with who knows how much age on it, it's had at least 3 years by me alone.

It definitely does standby/sleep very good to.

Haven't noticed the video hang/reboot yet either. But I'll keep pushing to see what happens...

but for now much happier!

Yes! Thank you [MENTION=4911249]Unjustified Dev[/MENTION]

.
[Fascinate Android Development] WillyFourSixty:
Good info hhp.

Right now I'm running smartassv2/row/ and max [MENTION=1348102]1200[/MENTION], min [MENTION=5657303]200[/MENTION].

My phone stays plugged up in the truck I drive for a living so battery life isn't as important to me as some. And I've found these phones most responsive and more reliable when the min value is higher. I also bump a few of the upper voltages up by roughly 25mv. It has really been great, and I don't seem to have the WiFi/data switching issues I had with most 4.4+ ROMs. I too tried the 1320oc, and there was improvement...however I would go to wake phone and it would be in that dead black screen. Kept pulling battery to reboot. I reverted back to the values I outlined above and my problems went away.

All in all, I'm amazed we have a nearly 5yr old device running as well as it does. Thanks especially to the great guys at xda.
[Fascinate Android Development] skepticmisfit:
ok so for some reason my phone did not want to flash the TWRP kernel. i actually was able to get around that by flashing cm11 in stock cm10.1 recovery (cwm 6.0.2.8) and then rebooting recovery and flashing cm11 in cwm 6.0.4.9 and gapps. looks like it's booting up!

edit: so i had to wipe data. turns out you have to flash the rom first, then reboot and check it out, then reboot back into recovery and flash the gapps package. at least from CWM. other than that though this is really fast and i'm liking it so far. amazed that you got torch to work with 416 MB of RAM

---------- Post added at 03:43 PM ---------- Previous post was at 02:46 PM ----------

omg unjust this rom is amazing. stupid fast so far, even better than official cm10.1. it took long enough, but you did it. you made the first usable kitkat ROM for this phone. and you should be proud of yourself.
[Fascinate Android Development] hhp_211:
thanks,

yeah I started setting my min [MENTION=5657303]200[/MENTION] also to hopefully improve stability, and when I was testing the DU ROMs I increased those min volts from

.950 to .975 and 1.000 for 200Mhz seeing as how it was -150mV under stock samsung setting

on that rom I also think I did a general bump in voltage +.25 to .50 across the board trying to see if it effected stability,,, i may go back and try that on this Rom now that I have things stable enough.

based on info found in this thread about the stock voltages and all...

1400 MHz - - 1.450V / -50mV
1300 MHz - - 1.400V / -50mV
1200 MHz - - 1.350V / -50mV
1000 MHz - - 1.250V / -50mV - If you have stability issues, try to let this one by default.
800 MHz - - 1.200V / -75mV
400 MHz - - 1.050V / -100mV
200 MHz - - 0.950V / -150mV
100 MHz - - 0.950V / -200mV

but also know what was also said about::

More volts is not always equal to more stability. Try to add more UV (less volts) if the frequency you're trying to achieve is unstable.

I was not really around for the heyday activity the fascinate received nor did I even understand as much as I do currently,,, after reading this stuff literally hundreds if not thousands of times it starts making sends more and more and I 'm not afraid to try tweaking any of settings to see how it makes the phone react

and just in posting this I noticed that the CM-11 settings for this version are as follows::

1320 MHz - - [COLOR="Red"]1.350V[/COLOR] / -[COLOR="Red"]100mV[/COLOR]
1200 MHz - - [COLOR="Red"]1.275V[/COLOR] / [COLOR="Red"]-125mV[/COLOR]
1100 MHz - - 1.275V / -??mV
1000 MHz - - [COLOR="Red"]1.275V[/COLOR] / [COLOR="Red"]-25mV -[/COLOR]
800 MHz - - 1.200V / -75mV
400 MHz - - 1.050V / -100mV
200 MHz - - 0.950V / -150mV
100 MHz - - 0.950V / -200mV -

and anytime I set smartassV2 my CPU just jumps all over the place and looking at the time in state it stays mostly in the 1000 ghz which would be fine if plugged in all the time, but obviously not so good for off charger setting,,, higher voltage settings (less under voltage) do not help this any in a very quick and minimal test...

:: wonder if anyone else sees this on smartassV2 ???

and I can not remember nor find any screenshots or saved info on voltage levels for other Roms that I have run, just never felt the need to mess around with them that much til lately.

Gonna try ::

1200 MHz - - 1.325V / -75mV

1100 MHz - - 1.300V / -??mV

1000 MHz - - 1.300V / -0mV

800 MHz - - 1.225V / -50mV

400 MHz - - 1.050V / -100mV

200 MHz - - 1.000V / -100mV

I do wonder if less under voltage will help the stability to be able to run up to 1200 MHz right now,,, well off to test and report back later...

.
[Fascinate Android Development] skepticmisfit:
i'm having issues installing certain apps for some reason. idk if titanium backup screwed things up while restoring or what, but the following games do not install on this ROM: Super Hexagon, SpeedX 3D, Deflecticon, and Tank Hero: Laser Wars. those are free on google play except for super hexagon
[Fascinate Android Development] hhp_211:
I have seen issues trying to re-install apps with/without titanium backup on this version, not experienced that before either... but I did pull the files and put them on a new microsd card too, which is what I thought those probs might be...

I may have to brake down and re-clean flash to see if it clears up my headaches...

I did install the new superSU v1.99r4(ZIP) from chainfire too.

http://download.chainfire.eu/supersu

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

Well.. to answer myself,,, NO... I can not run either 1200 or 1100 overclock both freeze and reboot phone,,, 1000 works though
[Fascinate Android Development] WillyFourSixty:
Wow hhp...

Don't feel bad. I've rooted and more or less "maintained" 5 of these phones. All identical. My mothers, cousins, friends, etc. And what is so shocking is they all behaved differently. My mothers never did run as well as mine no matter what I tried. And they were technically identical, even down to the apps used. Mine always performed better. It's weird.

And to top it off I remember reading some of your other posts as well as others concerning DU, PA, and other ROMs and for the life of me, mine absolutely would NOT run them well. It really hates Devil lately, which is surprising because it used to run like a scalded dog in earlier incarnations.

---------- Post added at 06:33 PM ---------- Previous post was at 06:31 PM ----------

Also,

Here's a shocker....I'm running the stock Samsung SD card that I was told would not work properly running these newer ROMs. Lol
[Fascinate Android Development] skepticmisfit:
hey i use that too. only 16gb card i have at the moment, don't really feel the need to buy another one. also i guess i could try supersu with the app installation issue but could somebody try installing those apps to confirm or deny my problem
[Fascinate Android Development] hhp_211:
Installed and tried Deflection, and Tank Hero with no issues

I did notice my /datadata was getting near full.

without either app I'm at 88% full, with only 57mb free

and if you don't remember this is our really fast partition that's desirable but it has to have a certain amount of space, etc etc. So JT recommended to push asps of onto the sd card that weren't critical for speed... Or something along those lines...

.
[Fascinate Android Development] skepticmisfit:
So I tried this and the situation was not alleviated. I'm probably just going to reflash the rom because I flashed it really weirdly and I think that might've caused some crap to happen.

When i say flashed it weirdly, I skipped the TWRP kernel because either I didnt flash it properly or it just doesn't work on my phone. It actually bricked my phone and I had to Odin back to EH03, then go back to cm10.1, then flash cm11 from the cm10.1 recovery, then reboot into the cm11 recovery (thank God that worked) and flash the ROM yet again. I guess somewhere along the line some area of the storage got full or something. Pretty sure reflashing may fix this.

---------- Post added at 01:34 AM ---------- Previous post was at 12:39 AM ----------

Aaaand that didn't work. Still can't install those games, but I can install any other app I want, plus I have 400+mb free in /datadata. I think I'm just going to give up and throw those games on my tablet
[Fascinate Android Development] hhp_211:
Hummmmmmnnnn...

So what happens? Will play store let you try to install/download?

Have you tried:

settings/account/remove account?

Reboot and add your account again

then settings/apps/all then click clear data/force stop form Google Services.

Now try to install apps again from playstore.

edit:

you could always try the market app from http://www.1mobile.com/

I've used that before on a off brand tablet to get apps with

or if you'd like I can upload the apk from SpeedX 3D, Deflecticon, and Tank Hero then you should be able to install them

.
[Fascinate Android Development] skepticmisfit:
I have discovered the issue! it's my SD card. Samsung 16GB class 2 has finally decided not to cooperate with a version of Android. the way those games work is they move a lot of the data to the SD upon install, and for some reason KitKat does not like my 16GB card (can't move any app to the sd card at all). it also doesn't like an 8GB card that i tested, which was a class 4.

guess i have to go buy a new ****in sd card lol
[Fascinate Android Development] hhp_211:
luckily 16 gb class 10 uhs-1 run about 8 bucks all over the place...

in an odd, but relevant, note,,, I actually downloaded/installed/played those games on my phone with my SD card OUT of the phone...

theory-busted???
[Fascinate Android Development] skepticmisfit:
oh wow. the apps installed when i took the card out of the phone. super hexagon was actually missing A LOT of assets (when i installed it i had no text so the menus were all blank, no sound, and the game was practically unplayable. seems as though that game needs the SD card, it puts most of its assets on the card) i kinda want that game to work because i actually bought it.. with real money lol

but other than that, deflecticon worked fine,speedx worked fine, and tank hero worked fine. thanks hhp! didn't even think to pull out my sd card before.. and said games continued to work after putting the SD card back in.. i'm gonna upgrade to a 32gb card soon anyway.

EDIT: after rebooting with the old class 2 16gb sd card in, super hexagon actually copied the data to the card successfully. not only that, but the game is playable! and it runs at a really high framerate as far as i can see, but that may be due to the insane overclock i have (1.32 GHz)
[Fascinate Android Development] hhp_211:
SWEET!!!!! So glad that worked out.

I've never attempted the sd out method before,,

but i was experiencing a different issue with an app and i figured i had nothing else to lose by trying it...
[Fascinate Android Development] Legitsu:
flashed it on mine but the phone won't come out of sleep if you let it sleep for more then a min
[Fascinate Android Development] skepticmisfit:
i had that issue when overclocking. try stock CPU settings

in case you don't know those or it won't reset, stock settings are

interactive, min 100, max 1000, row
[Fascinate Android Development] Legitsu:
odd I had 1200 set on PA and didn't have a issue must be something flaky in the kernel

a work around would be simply to reset the pstates to default before entering sleep and then restore them on wake passed ant tutu at 1320 this sucks

edit: I changed the govener to interactive and set the min state to 400 seems to have fixxed it

what I think is going is that the kernel is reducing the voltage to much for sleep because live OC messes with the FSB this changes the freq from 100mhz to 120 and their isn't enough voltage to keep things online [MENTION=1885052]unjust[/MENTION] bump the voltage for 100Mhz .025v and disable power collapse/deep sleep it doesn't work on this phone both PA and DU had issues with it
[Fascinate Android Development] hhp_211:
this ^^^^^^ works

""bump the voltage for 100Mhz .025v"" does not work, for me,,, I already tried 200 @ 1000 mV if you read my previous posts,,, and this

had my min @ 200 and any max over 1000 is causing various issues and getting the SOD.

to my knowledge this kernel does not have "live OC"

not to mention that DT updated that to not do any live oc on 100, 200 and maybe 400 too

but then again this kernel is based on someones else work, so??

***:o***

maybe though I am totally reading that post /scale wrong,,, :o

I guess it's giving you the stock voltages and saying you can go max undervolt to those values ie:( 950mV -150mV @ 200 Mhz) (meaning down to 800mV)

i've always read it the other way around, but when I write it out the numbers do not make sense... :o

***

---------------------------------------------------------------------------

currently testing

max 1320 - @ 1350 mV

min 200 - @ 1050 mV

interactive, noop

and no SOD for me yet :fingers-crossed:

update: still causes hang-ups/reboot on videos

----------------------------------------------------------------------------

currently testing

max 1200 - @ 1275 mV

min 400 - @ 1050 mV

update: still causes hang-ups/reboot on videos

and no SOD for me

-------------------------------------------------------------------------------

currently testing

max 1100 - @ 1275 mV

min 400 - @ 1050 mV

update: no issues with hang-ups/reboot on videos

but I do have a weird wake lock with something causing the cpu to hang at max setting

and no SOD for me

----------------------------------------------------------------------------------

currently testing

max 1000 - @ 1275 mV

min 200 - @ 1050 mV *** works 6/15

min 200 - @ 1025 mV *** works 6/15

[/STRIKE] min 200 - @ 1000 mV [/STRIKE] fails ***

and no SOD for me 6/15 ***

---------------------------------------------------------------------------------

@unjustified dev

do you think you could try removing the 1100 setting whenever/if you are messing with fascinate stuff again

if you go back and look at DT's work you can see things like

03.04.2012:

-added new frequency: 1080 mhz (1100 does not like live_oc)

- fixed SmartassV2 for live_oc

10.04.2012:

- removed 1080 mhz freq for now

.
[Fascinate Android Development] Legitsu:
its been off for most of the day with 400mhz min/1320 max no issues
[Fascinate Android Development] skepticmisfit:
anyone getting insane pulling down the notification bar lag? running stock settings.. to scared/lazy to try changing voltages and OC'ing
[Fascinate Android Development] Legitsu:
not here
[Fascinate Android Development] skepticmisfit:
it happens like occasionally and randomly at that.. has nothing to do with background tasks running, it may have to do with used RAM.
[Fascinate Android Development] scelera:
Found this nice little gem over in the Avatar thread that explains one of the big features behind KitKat and what makes it so amazing.

http://xdaforums.com/showthread.php?p=47482053&postcount=238
[Fascinate Android Development] bones420la:
Unfortunately I can't try this due to sd card and recovery issues. But thanks for keeping this phone alive.
[Fascinate Android Development] Unjustified Dev:
Your issue is your on an old recovery when flashing it I know but I don't think you would understand my instructions [MENTION=983303]hhp_211[/MENTION] could you make a flashable zip to install the new boot.img so the rom could be flashed
[Fascinate Android Development] hutchjim:
hi

when will there be a update? anybody know ?
[Fascinate Android Development] LEVATATOR™:
Always ... Nice Job Unjust !
[Fascinate Android Development] Unjustified Dev:
Whenever [MENTION=4559222]frapeti[/MENTION] can fix the sdcard issue

Our issue is the media provider in 4.4 can't get the id of sdcard because it has no access in the new code. This issue is only relevant with devices that only have external sdcards as it's main storage. Other devices have internal and external storage

For now blame google
[Fascinate Android Development] hhp_211:
Not sure if i understand the request.

I have a cm11 kernel test zip that i tried to flash on my du 4.3.1 but it only hangs at the Samsung logo.

I'll retry some more combinations later, I'm out from home right now

I did get some new 4.3 kernels posted up though, in my thread.

.