yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] ztotherad:
man, i feel sorry for you (regarding your sig). I had the Droid X2 and that thing was more locked down then the new Knox Bootloaders from Samsung.
[Fascinate Android Development] Sippi4x4man:
Man that phone had to go. I loved the phone but had no idea how locked down it was when I bought it. In my noobness I assumed that all android phones were unlocked as part of this "open" idea. That phone drove me crazy
[Fascinate Android Development] ztotherad:
totally understand. I bought it, but knew it was locked down, but I guess I was hoping that it'd have the same dev work as the original X; which unfortunately didn't happen. thank god for dzk though!

edit: so I definitely may stay on 4.2/4.3 for the time being, lol. I'm liking jellybean on my old fassy. it's running like a champ.
[Fascinate Android Development] ocs111:
Sippi

Is all I need to do is get to a CM10 Rom, flash the new recovery zip, reboot, factory reset, wipe and install 4.4? At what point do I install the gapps that go with 4.4, let is reboot first??

So far the furthest I have gotten is installing the 4.4 then attempting to reboot with "C" arrow going around forever.

Thanks, I haven't messed with these Showcases in awhile, I have been trying to my gs3 maxed out.
[Fascinate Android Development] Sippi4x4man:
That sounds exactly right. When I first booted with 4.4, the CM logo was on the screen for quite a while
[Fascinate Android Development] ocs111:
I sure it is something simple I missing but for some reason I cannot get it. It is my understanding you don't flash the rom and gap at the same time. Are any of the boxes supposed to be checked? I continue to get a loading failed now.
[Fascinate Android Development] hhp_211:
that is right on these 4.4 roms, let it boot before flashing a gapps.

if you are having trouble i would boot back into twrp recovery, chose advanced wipe, & wipe dalvik, system, cache, data... then reinstall cm11 and reboot... that should have you :fingers-crossed:
[Fascinate Android Development] Sippi4x4man:
This is what I did:

1. Odin to Stock

2. Flash CWM for CM7 with Odin

3. Boot into CWM and flash a 4.2 rom

4. After you flash the 4.2 rom, boot into recovery and flash the 4.4 kernel zip

5. Reboot Recovery, you should be in TWRP now

6. Flash CM11 alone and then flash the modular gapps alone. Do not flash them together

7. Reboot system

I should clarify step 6, TWRP allows you to flash multiple zip files at once, DO NOT DO THIS. Flash the rom, once it says "successfull" then flash the gapps
[Fascinate Android Development] skepticmisfit:
no. but thanks guys for all your work, i'm ditching and going back to ICS for a while. glitch kernel :D
[Fascinate Android Development] hhp_211:
Thats proper,,[just did to check again and confirm],, with 2 small exceptions that may or may not matter too much it seems

1. Odin to Stock

2. Flash CWM for CM7 with Odin

---* 3. odin flash GBBootloader.tar

4. Boot into CWM and flash a 4.2 rom

5. After you flash the 4.2 rom, boot into recovery and flash the 4.4 kernel zip

6. Reboot Recovery, you should be in TWRP now

7. Flash CM11 alone and Boot ROM

---* 8. Reboot into Recovery flash the modular gapps alone. Do not flash them together

9. Reboot system
[Fascinate Android Development] ocs111:
I see the instructions state 4.2 rom; do you know if you can advance from a 4.1 rom
[Fascinate Android Development] hhp_211:
yes should be fine, even any mtd [cm7, Android 2.3, Gingerbread] ,,, [cm9, Android 4.0, ICS],,, [cm10, Android 4.1, Jelly Bean]

the only thing with the ones older than 4.1 would not have the new partitioning setup which would just mean more work
[Fascinate Android Development] ocs111:
Thanks, it is my son's phone. I currently have it loaded back with CM10, 4.1 running on it. I appreciate all of your advice, I think I am going to let it rest for the night. I have reloaded that thing all afternoon long trying to figure it out. LOL
[Fascinate Android Development] Sippi4x4man:
What gapps package are you using?
[Fascinate Android Development] nm3210:
It seems I can't send text messages to short-code numbers. I was trying to text to Twitter (40404) and i get a bunch of "com.android.phone has stopped" messages. Anyone else? I'm on the 12/06 build.

edit: I can link the logcat once I'm done with work (6est) but it looks like a bunch of errors from the SMSDispatcher.java lines 823 and 764, CdmaSMSDispatcher line 175, and ImsSMSDispatcher line 196. There are a bunch more too, so i'm not sure where it originates from.
[Fascinate Android Development] ocs111:
I am planning to use the 4.4 gapps on the first page, I haven't even gotten that far yet though.
[Fascinate Android Development] scelera:
Thanks, but that doesn't work either. Maybe it has something to do with the fact that I ran mine through ROM Konverter so I could have MMS....
[Fascinate Android Development] hhp_211:
is that through hangouts or another text program?

Are you Verizon?
[Fascinate Android Development] nm3210:
Just through Messaging (MMS.apk) and yes on Verizon.
[Fascinate Android Development] hhp_211:
thats strange, mine works fine on 12/16 PA in both mms8 and hangouts Verizon/pageplus.

i reckon plan to post your LogKat later...
[Fascinate Android Development] nm3210:
Trying to post from my Fascinate! Logcat should be attached.
[Fascinate Android Development] Sippi4x4man:
Does MMS work for you with hangouts? I haven't been able to send mms with hangouts since the first kitkat rom came out, however, it works fine with the stock sms app
[Fascinate Android Development] scelera:
Ditto on that. MMS doesn't work on Hangouts, works with sms app though. Haven't tried other third party apps.

---------- Post added at 03:30 PM ---------- Previous post was at 03:09 PM ----------

Yup, I get the same thing. It tries to load and every once and a while I can see the page start to load and then it disappears. That's strange.
[Fascinate Android Development] hhp_211:
Yep, in PA,, no hangouts mms but works in a reg mms.apk

Uc browser not displaying right either but did previously.
[Fascinate Android Development] lightningdude:
I'm using UC Browser Mini, and it works just fine for me on CM11. Just an FYI.
[Fascinate Android Development] scelera:
Did it die.....

[MENTION=4911249]Unjustified Dev[/MENTION]... Let me know if you need a beta tester. I just upgraded to the SGS3 so my Mez is available for testing. I can't test data on it but everything else is fine.
[Fascinate Android Development] skepticmisfit:
i'm pretty sure Unjust is just leaving it up to BDogg and notta. that's kind of what happened with 4.3. he put out cm10.2 builds and then eventually other devs (bdogg, notta, jt) put their own builds up.

btw, we may never see official cyanogenmod builds. ever. unless Unjust becomes an official maintainer.

jt left CM and isn't doing 4.4 for our phone. he did code 4.3 but it never got integrated into the nightlies.
[Fascinate Android Development] Unjustified Dev:
Jt is still maintainer he updated fassy to 4.4 . I don't think he has right to add nightlies. I have no idea why he isn't listed as part of the team on github. I have been much busy with my tablet and helping others out.
[Fascinate Android Development] skepticmisfit:
dude good luck getting cm on the tab 3. i yelled at a guy for being disrespectful on that thread
[Fascinate Android Development] kb8no:
Please. Where is the tab3 cm thread?
[Fascinate Android Development] skepticmisfit:
this is for tab 3 7.0: http://xdaforums.com/showthread.php?t=2561064
[Fascinate Android Development] ztotherad:
bro, fershur good luck with the Tab 3. looks like there's already some awesome kernels out, at least for the tab 3 8.0. I actually got for Christmas the Note 8.0, definitely a bad ass tablet, just missing the AOSP kernels, but it's got official CM11/Omni, so I'm content, lol.

EDIT: where did jt, on his github update the fassy to 4.4? I can't seem to find it anywhere, lol. I may totally be missing it.
[Fascinate Android Development] Unjustified Dev:
on cyanogenmod github
[Fascinate Android Development] ztotherad:
I was looking at his github, lol. wonder if there's an updated kernel.
[Fascinate Android Development] Unjustified Dev:
Soon we can have 4.4 nightlies :) up to cm guys I made the request

https://github.com/CyanogenMod/hudson/pull/202
[Fascinate Android Development] Unjustified Dev:
Well I don't think they are merging it. I started my own build twrp and devil with zram from kit kat
[Fascinate Android Development] times_infinity:
Builds without the FascinateRIL class (epicril should be renamed SamsungExynos3CDMARIL and commonized since both the epic and fascinate need it.) have data issues. So that might be why they haven't merged the pull request yet. That and they'd probably want the pull request to be from one of the Fascinate maintainers.
[Fascinate Android Development] Unjustified Dev:
I sent pull request for them to build using jt source not mine. I use my source for other roms too. I used epic ril because bbelos said it helped him :) and we have the same ril. Also it still uses SamsungExynos3RIL it's just a subclass . I haven't merged it back since I started from scratch with jt source and I made a build and did not like it plus I got an error about boot size because aries-common plus my twrp is too much so I again started from scratch

https://github.com/TeamRegular/andr...mmit/80638a78733cf7d9bd632fb3aa486b77af958509
[Fascinate Android Development] Unjustified Dev:
Well here it is had some complications throughout the day and don't want to talk about it :p

http://goo.gl/N674dK

twrp and my devil based kernel

Apparently only issue is mms which bbelos might have fixed.
[Fascinate Android Development] SupraLance:
This is working great. Running fully TransparentCM11 theme with no themes.provider issues. Overclocked to 1368 (1200+114%live), zen, lulz, zram at 40% and all settings holding across reboot. Had a minor issue with superuser permissions when first running deviltools, but everything is working great now. Truly amazed by the capabilities of this 3+ year old phone & the devs who make it happen. Thanks Unjust etc!
[Fascinate Android Development] neozen21:
Thanks for your hard work!

However, I still can't get ADB to work.(worked fine under CM10.2). USB mass storage works fine though.

Any ideas?
[Fascinate Android Development] Unjustified Dev:
Sounds like you need to enable adb. Settings > about phone > tap your build number about 7 times. It will say you enabled developer options. Press back you will now be in the main settings go to developer options . Enable advanced reboot to get recovery in power menu . Then go down to usb debugging and enable it as well. Grant permission to your pc and it should work
[Fascinate Android Development] neozen21:
Lol. Maybe I should have mentioned all that to avoid sounding like a noob, but trust me, I already did all those. ADB Debugging is definitely already enabled.

When I plug the Fascinate in, I get the "Android debugging enabled" notification. But don't get the Grant Permission prompt.

And even without granting permission, you would still see it when you do "ADB devices".. there is just nothing showing up.

I even tried toggling the "Android debugging " settings many times, restarting the phone, restarting the phone with cable plugged, etc.

And I know it's not the cable or my computer. ADB works fine, when I use my Galaxy S3 and my Nexus 10, and the Fascinate when it was on CM10.2

I'd prefer CM11 over CM10.2 but without ADB, the phone is of no use to me, since I'm using the Fascinate as a development test phone.

Any ideas?
[Fascinate Android Development] Unjustified Dev:
Test adb in recovery.

If it doens't work. In twrp format everything except sdcard and flash over. My adb works fine now.
[Fascinate Android Development] neozen21:
Hmmm.. No ADB in recovery either, and then I formated data, system, cache, dalvik, everything except sdcard.

Still no luck. I installed Times_infinity's version 1st, then just flashed yours over (when I found his has that bug), wiping only cache and dalvik the 1st time.

This time, I wiped everything and resintalled but still no luck.. I see the Android Debugging notification, but no prompt to grant access and nothing listed under ADB devices..

Thanks for all your help.. I'll keep trying tomorrow.
[Fascinate Android Development] Unjustified Dev:
Ok you need heimdall. Command line open command prompt.

Get my boot.img from the rom zip

put it in heimdall folder

type

heimdall flash --KERNEL boot.img and adb should work. Alternatively return to stock and try again
[Fascinate Android Development] SupraLance:
Working fine for me on Linux Mint; ADB devices shows Fascinate as soon as I plug the phone in with ADB enabled (no prompt to grant access needed). Coming from TimesInfinity CM11 w/CWM, I wiped, flashed the TWRP kernel in post 1, and then the 1-21 CM11. If you didn't flash the separate kernel first, you might try that. Or it could be a Windows only issue.
[Fascinate Android Development] lightningdude:
I'm getting install errors from play store, not wanting to install to usb storage or sd card. Had it on timesinfinity's build, but not on Unjust's older build.
[Fascinate Android Development] Unjustified Dev:
In twrp wipe , data , cache , system , and dalvik. Wipe your sdcard as well and and clean install the rom and pa mini gapps 4.4
[Fascinate Android Development] neozen21:
DOOH!! Big oversight here on my part..

I finally got ADB working. Turns out, all I needed to do was to reinstall the Google USB drivers.

I didn't think I would need to reinstall them, since the Fascinate had ADB working under CM10.1. Weird, maybe the deviceID changed or something..

Well.. big thanks to you guys for helping!

By the way, I couldn't get Heimdall or Odin to work, since I couldn't install the Samsung USB drivers on my Windows 8.1 x64 machine :( (Windows says they are not for the right version of the OS)

That machine is actually a dual boot between Win8.1 and Ubuntu 13.10, but since I'm not that good with Ubuntu, I just use Windows most of the time.

Well, thanks again guys!
[Fascinate Android Development] ztotherad:
I may have the right Samsung Drivers for Windows 8.1. just make sure you've turned off driver signature for Windows.

and here are the drivers uploaded to my box: https://app.box.com/usbdrivers

got the drivers from here: http://xdaforums.com/showthread.php?t=2038555

(this is a lot easier to download from my box upload than the site above because this doesn't include inputting codes to download and no 30+ seconds wait for the link)

Have a great day!
[Fascinate Android Development] hhp_211:
thanks zac

and I have the .rar if you need to do method INSTALLATION 2: or INSTALLATION 3:

http://www.androidfilehost.com/?fid=23134718111255952

.
[Fascinate Android Development] times_infinity:
It's easier to go with koush's universal adb driver. No need to disable driver signature enforcement.
[Fascinate Android Development] Jordanqkoch:
I get android process media and download manager processes force closing constantly. Tried multiple versions, downloaded multiple versions multiple times, tried without the kernel and with it, wiped 10 times prior to flashing and still have the problem.

Any ideas?
[Fascinate Android Development] hhp_211:
This is how I tackle the situation::

Choose Settings::Apps || All || Media Storage

select it and,,, clear data

select back button twice

go up to Storage:: Unmount SD Card

wait for it to finish...

Then Reboot

It will take a while upon reboot for it to rescan your SD card

This will wipe any of your ringtone, notification sounds, etc.

when you go into Sound:: Ringtone -- if nothing comes up or only a couple show,,, then the rescan process has not completed,,, keep waiting...

I've had to wait 15-20 minutes, possibly even another reboot and wait cycle, before ringtones, etc returned...

if after this you still experience f/c of the android.process.media

Try this:::

go up to Storage:: Unmount SD Card,, wait,,, Remount SD Card

Sometimes this just becomes a temporary fix lasting only an hour or two, before having to repeat the Unmount /Re-mount,,, but hey then again KitKat for the fascinate is still in an early lifecycle... Be happy we've come this far.

.
[Fascinate Android Development] Jordanqkoch:
Wow, excellent response. I will definitely try that for the media fc. Any ideas about the download manager fc though?
[Fascinate Android Development] Jordanqkoch:
Got all my fcs fixed, noticed there's no way to add a tile in the quick settings pull down menu thing for torch. Is there a way to add that?
[Fascinate Android Development] hhp_211:
Not exactly but kind of...

AntTek Quick Settings

Look it up in the play store, it's basically a replacement qs app

It's really got a lot of abilities i wish the built in app had
[Fascinate Android Development] kb8no:
Notification Toggle is another nice quick setting app that makes up for the short comings of CM quick settings I've used a lot.
[Fascinate Android Development] CGSemperParatus:
Working Link

Does anyone have a working link to this latest build? The one posted by Unjust has been disabled on Dropbox due to it generating too much traffic.
[Fascinate Android Development] hhp_211:
give this a whirl

http://www.androidfilehost.com/?fid=23329332407568998

let me know if it doesnt install right , I may have to re-upload,,,
[Fascinate Android Development] CGSemperParatus:
Thank you.... installed perfectly. Much appreciated. Running perfectly as well.
[Fascinate Android Development] skepticmisfit:
i know this isn't related to cm11 but

anybody notice these builds: http://www.androidfilehost.com/?w=files&flid=9319

these are apparently self-compiled cm10.1 builds done by unjust? idk
[Fascinate Android Development] Unjustified Dev:
Stop stalking :Dread my post though I work on another device for a friend. That host doesn't have his device.
[Fascinate Android Development] donluz:
status?

Gapps 4.4 link doesn't work.

Does anyone know where this is 3 months later? I'm curious if it's an active project or not.
[Fascinate Android Development] skepticmisfit:
yeah there's another unofficial cm11 build that's a bit more recent done by Times_Infinity. its not active all the time but the dev pops in every now and again with something
[Fascinate Android Development] donaldj83:
virgin mobile

first post in years sence i left but...

is it at all possible to add blarfs virgin mobile mms fix to this heres the link

https://github.com/bigsupersquid/an...mmit/789b973eb8522fd7636e737015b6a99f5118a8df

either that or if you have the all of the changed sources for this i'd love to get down and dirty
[Fascinate Android Development] skepticmisfit:
uh.. Virgin Mobile? that's like the last thing I thought someone would use this phone with this ROM with.

Sent from my SCH-I500
[Fascinate Android Development] donaldj83:
hahaha yea... well..... boss upgraded, i was bored with my phone and needed a challenge anyhow i'm in the process or dling the cm sources as we speak figured... heh why not
[Fascinate Android Development] jkok:
lol ive gotten mine to read sprint, at&t, verizon (OFC :P ), t-mobile, and currently its a Straight talk XD even if its CDMA phone only, u can spoof it as a GSM phone so it will read the tower, the raido+antennana in mine is still unchanged from stock XD, that just how the codes work i guess :P
[Fascinate Android Development] donaldj83:
lol nice well hopefull after today ill have virgin mms running if im sucessfull ill upload it for ya so u can keep it in your collection with the rest lol
[Fascinate Android Development] jkok:
Nah its more just in apns-conf.XML in the /system/etc/ folder, most mms.apk (messenging) apps do work fully, but CyanogenMod, and roms using it as it's base put all apns for each carrier in one APN per carrier and their type, some like straighttalk cannot be done this way without MMS issues, so get into that file search for virgin mobiles, and get the apn values u spicificly need and separate MMS, data, and tethering if applicable, and u should be good to go :)

---------- Post added at 03:35 PM ---------- Previous post was at 03:34 PM ----------

But I'm sticking with straight talk, thanks tho :)
[Fascinate Android Development] Unjustified Dev:
Soon my friends. Have to redo some code and work with [MENTION=5089052]jkok[/MENTION]
[Fascinate Android Development] jkok:
lol ok, btw im working on fixing that darn DU44 build lol i think i fixed the bugs with that test build i sent ya too :P the test build was almost flawless on the first try lol, i forgot to add the low_mem build.prop so random reboots were there, boot animation didnt build, but ill add a default one later, and the /system/bin/sh file didnt compile fully so menus like init.d tweaks wouldnt open by

default coding lol. but ive gotten some of those issues solved and building as i type this lol. altho the voicmail patch used seems to be the reason MMS is getting killed in the roms, i think cause it spoofs it as a GSM phone its also spoofing it to need GSM apns so ill look into some GSM-branded Apns and add then to a apns-conf.xml and see if thats whats causing it lol since all of our fassys have basic CDMA carriers ill see if i can add the GSM varients of the compatible carriers to the APNS but currently i can only test as StraightTalk as stated above lol, but ill find a way ;) ive been doing java coding for ~6 years now and im only 18 atm XD and the codes in android's rom source is somewhat easier then the codes ive done or had to reverse manufacture for others "universal methods" lol
[Fascinate Android Development] Unjustified Dev:
Im going to test out the high end gfx setting allows transparency with low mem prop
[Fascinate Android Development] jkok:
idk if that was already in DU source, i saw the option to force high end gfx, but in its specific source it might need to be added, but the low_mem prop might be a struggle due to priorities of build.prop > settings app ill look into it while i find an easier way to fix voicemail without conversion of cdma to gsm spoofing as it kills MMS due to different APN REQ. and the apns-conf.xml doesnt build with the new gsm+cdma apns for some reason, but ill modify the telephony a bit more and get a solution lol ill keep you in touch with progress ;)
[Fascinate Android Development] pahlevy:
im editing build.prop with root explorer and adding ro.config.low_ram=true to the list.... after that my phone wont boot or stuck on boot animation... went to recovery on twrp and flash the same build without doing anything else to get all my app and setting back... my problem now is i cannot get data to work at all.. try switching airplane mode on and off and changing network mode between 2g 3g lte several time... still no luck.. :(

Edit: got my data work again now... weirdly enough i got this working by flashing datafix for jb... :D

Btw, continuing what im looking for at first was lowram setting on my phone... why i cant get that works... i also try setting it with terminal emulator but nothing is change even after restart several time... :(
[Fascinate Android Development] skepticmisfit:
so you're using the Unjust cm11 build? or are you using another ROM (like PA, times_infinity cm11)?

if i remember correctly, the build.prop edit doesn't work for Unjust's cm11. try PA or times_infinity's cm11 build if you really need it.
[Fascinate Android Development] jkok:
try doing it using adb on the computer, type these in (taken you have the terminal/comand prompt in the directory the edited build.prop is)

REMEMBER TO EDIT IT IN NOTEPAD++ NOT REGULAR NOTEPAD OR THINGS LIKE IT! (caps so it will be remembered cause i chant shake you repeditly like on a cartoon lol

adb root
adb remount
adb push build.prop /system/build.prop
adb shell chmod 644 /system/build.prop
adb shell chown 0.0 /system/build.prop
adb reboot

if you want to keep it on-device without editing in notepad++ (or dont want to install it) do the following (remember for echo > is for only that in file, and >> to add it in the bottom of it, what to put in there needs to be in quotations " ")

adb root
adb remount
adb shell echo "ro.config.low_ram=true" >> /system/build.prop
adb shell chmod 644 /system/build.prop
adb shell chown 0.0 /system/build.prop
adb reboot