yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] bmeek:
Good stuff - but I need a dock audio redirect...

I'm really impressed with this ROM - I've been using the ART runtime option and it seems to do pretty well for my purposes with just one exception: I need to redirect audio to a car dock...

I've got a couple of old fascinates that no longer have mobile service, and I'm using one for home theater remote control functions around the house and GPS + streaming music while in the car (the data is supplied by my d2vzw / Galaxy S3 via CM11's WiFi tether). So, I'm going back to GeeWiz Media (Android v4.3) for the audio features.

Question: does the (apparently new) partition layout of this ROM allow one to flash back and forth between these new CM11 builds and the last CM10.2 nightly from back in July? I assume not, since I tried restoring a CM10.2 nandroid backup over this, and although clockworkmod reported success upon completion, the result wouldn't boot and had to be remedied through ODIN.

Thanks again!
[Fascinate Android Development] Unjustified Dev:
Is it just me or is adb broke on all this stuff and usb storage as well. I can't get no commands to my device except in download mode using heimdall to flash boot.img

edit: fixed it jt made a typo and I guess op is using jt source

https://github.com/CyanogenMod/andr...42bd#diff-3b27725fa91399ccbb4e4e7a2f8ccff8R45

I can upload a boot.img to flash it's devil so... let me know if you want adb working it's twrp too
[Fascinate Android Development] SupraLance:
Unjust, since this is just a drop and possible not support by TimesInfinity (Although we appreciate that tremendously...), i would love to see your CM11 thread resurected with a new Devil/TWRP version with updates. I'm still having soft reboot issues and then Android.process.media forcecloses with this once I install Devil over it, and I would love to see the themes.provider issue resolved at some point.
[Fascinate Android Development] Unjustified Dev:
Ok , I need to rebase my new source since I started from cm clean since jt cleaned up device tree
[Fascinate Android Development] neozen21:
Thanks for all the great work on bringing CM11 to the old Fascinate guys!

I just installed the 1/9 version, however, so far I can't get ADB to work.

My Windows 8.1 computer just can't see the Fascinate. (USB storage works though).

ADB was working fine with the last CM10.2.

I'm using the Fascinate as my development test phone, so without ADB, I'll have to go back to CM10.2

Any ideas?

Appreciate all the great work you've done!
[Fascinate Android Development] hhp_211:
read up at post #45....
[Fascinate Android Development] neozen21:
Thanks! I'll try Unjustified Dev's 1/21 version.
[Fascinate Android Development] times_infinity:
adb is working fine for me guys. I don't know what you guys are doing to break it. o.o
[Fascinate Android Development] times_infinity:
New Build 2/20/14

New build guys.

It's been over a month so I honestly don't know what the changelog would be like.

Good news though. No need to reverse or delete the lowram prop anymore.

They added a highendgfx override toggle to the performance menu in Settings.

I've used this build for a day or so now. Runs great.

Enjoy!
[Fascinate Android Development] ktweb:
problem running rom

I am not sure if this is a problem with my phone running ROM or the phone. I purchased my phone on eBay, it was already running this ROM and rooted. I am having issues with the phone screen not lighting up and coming on when I try to wake the phone. It doesn't happen all the time, but frequently enough to be annoying. The soft keys just come on for a few seconds and go off. I have to pull the battery and restart. I didn't know if anyone else has had this happen and is there anyway to speed up the system and make the phone more responsive. Otherwise I am really enjoying the ROM. Being on Page Plus I am stuck on older phones, but this makes it nicer. Thanks
[Fascinate Android Development] jkok:
thats in almost all 4.4.* roms atm, its a problem with the display not comming up all the way, i managed to fix it on my personal-build, but its a pain in the butt to do in the rom's source... when i got mine fixed i had to edit over 20 files...not to mention over 10000 lines of code overall XD.

but [MENTION=3103747]times_infinity[/MENTION], its a hard thing to fix like voicemail, data, Sometimes MMS, so untill someone does the patch in CM11's source code the bug will sadly stay there with or without the low_mem build.prop entry =( it wont happen as much with the entry, so by default keeping it could be good =)
[Fascinate Android Development] times_infinity:
I have never had that issue. This is straight CM. The only thing I added was the FascinateRIL sub class so data would work.

I've actually been using my Fascinate as a SIP phone with my google voice account.

So everything is working fine for me. The only thing I can't test directly is MMS and Data. But I haven't heard from anyone that neither of those are working.

If you're running a custom kernel or anything like that, especially if you're "rolling your own" builds, I would advice you to go to the kernel dev's thread and post about your problems there, or if you're running the build I compiled.
[Fascinate Android Development] jkok:
well on your version of CM11, Unjustified Devs CM11, Paranoid Android, basicly all roms over 4.2.2 (minus gee-wiz) have had no native voicemail implemented/working, only apps to display it from google play, as for the display thing, it has been a problem for some people over 4.3 as its not popping up on the screen as fast as people are used to due to lag in ram for displaying it/loading all stuff to display, it was mostly needing some tweaks for memory preformance, as the touchlights go on sometimes before the code is fully done TO DISPLAY, u know what im saying? some of the tweaks automatically get applied with the low_mem build.prop value is set, but its a temporary solution tbh, alot of ram is used since 4.2 was released given taken why they made 4.4 with the low_mem build.prop entry, but some processes that are universal on android are usually disabled on a per-device quota from "Bloated-Stock developers" (e.g. samsung's touchwiz, HTC's versions, LG-Modded) etc, some things if u look at their codes (often closed-source, but decompileable enough to compare), some flags are taken off of stock aosp and replaced, not only with new images, but newer universal codes thats configurable on an "on device basis", much like is someone sets a public String in java so it can be changed but other codes stay the same just reads that string where needed, some coding ive always thought was easier making it more universal like that, but aosp codes as u most likely see, u have to edit lines after lines to get just one part changed u know? its just something i picked up handy when making peoples apps/source code smaller using public (or private) Values that can be changed to reflect different things, same can be used in bash tbh with the "export (export name here)=(value here)" command in "~/.bashrc" and making a ref with "$(export name)" to use in the direct terminal and/or scripts. ive messed with a few building scripts for some people using such methods, and its come in handy with memory size, source code size, and sometimes ram usage, but thats all my viewpoints. everyones different, as i like hard-coded strings due to decompilers, some like XML String Values, its all our experiences and what we all see fits in our own patterns =)

sorry for all the talking/typing/words but i tried to explain it as much as i could, but in a way more then one type of developer could understand u know? =)
[Fascinate Android Development] tekweezle:
I loaded the 2-21 rom over my pa beta 6 to test. I dirty flashed, only wiping out cache, dalvik and system. Happy to report that it flashed successfully.

Seems to have similar issues. Hardware gps doesn't work. Can't move apps to SD card.

Other than that, seems okay.
[Fascinate Android Development] tekweezle:
Success with the GPS.

I downloaded GPS Toolbox from the playstore and some combination of resetting the GPS, downloading the AGPS data and toggling the location services tile in Quickpanel(it was enabled in settings so I don;t know why it would be turned off) got my phone to start recognizing satellites. I will have to see if this a longterm fix that will survive a reboot.

Edited to say that GPS stopped working after I switched batteries and I haven;t been able to get it activated again. definitely seems like a software issue. so back to sqhare one except at least I know the hardware is working somewhat.

so at this point, GPS not successful.
[Fascinate Android Development] donaldj83:
kinda odd question but...

interested in building this rom from scratch maybe some one is able to shed some light on this ive downloaded the cm sources now im trying to add https://github.com/TeamRegular/andr...mmit/6678964eac6a9443adc85ef34dad0c2e76f30d58 in post #2 thats where im running into problems i was wondering if you could shed some light on your local_manifest.xml for this rom or are you just taking that ril from that and stuffing it into place?
[Fascinate Android Development] jkok:
goto the device/samsung/fascinatemtd directory in your shell/bash in root or user baed on how you created the files when u did repo init+sync

then do these commands:

mkdir ril

cd ril

touch FascinateRIL.java

gedit FascinateRIL.java

(copy+paste the contents of the file from the commit here, then remove all the "+" at the beginings of the line, and fix the neatness if any misaligning came across for neater source code) then save and do in terminal

cd ..

gedit BoardConfig.mk

(add the needed line, then remove the "+" if needed) then save and do in terminal

gedit device.mk

(change the line, or add the line if non-existant in the PRODUCT_PROPERTY_OVERRIDES section, if in the middle of the area dont forget the " \ " symbol, its not needed if at the end of that override area)

save+close all gedits, then compile =) its the manuall way if u dont want the hasstle of adding git remotes, having it do it, then forcing to make a commit if u dont want to =)

edit: heres my local_manifest if u want to use it =) if u want for the "CyanogenMod/android_device_samsung_fascinatemtd" you can change to "TeamRegular/android_device_samsung_fascinatemtd" to get that patch automatically =) but heres my current code sinc e i just add the patch manually with the above steps =)

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_fascinatemtd" path="device/samsung/fascinatemtd" remote="github" />
<project name="CyanogenMod/android_device_samsung_aries-common" path="device/samsung/aries-common" remote="github" />
<project name="CyanogenMod/android_kernel_samsung_aries" path="kernel/samsung/aries" remote="github" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" />
<project name="Pinky-Inky-and-Clyde/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-11.0" />
</manifest>
[Fascinate Android Development] donaldj83:
your awesome

dude your awesome

one more dumb question after i manually edit this if i do a repo sync all of those changes will be over written with the server version right so ill have to go back and re change those files again right?
[Fascinate Android Development] jkok:
its a repo "sync" as in whatever they change, gets changed onto yours, some may get erased, some may stay, its really up to what is synced, the best way to prevent it is say u wanted just that data patch, keep the TeamRegular string i mentioned in your (dir you repo init'd)/.repo/local_manifests/roomservice.xml and it will stay there between syncs, as it is IN THE CODE ALREADY =) but other stuff you do to other files may differ unless you commit, but if u are doing a personal build, you can always do the long process of making a github account, fork the repositories for the things you dont want overwritten (e.g. vendor/****/**** in android_vendor_****_**** or pripietary_vendor_****_****, kernel/***/**** in android_kernel_****_****, device/****/**** in android_device_****_****, apps in android_apps_******, and simalier methods like that, if you search some git or repo tutorials theres other methods to keep things, remove things, and whats called a "cherry-pick", but remember dont commit to others repositories without their approval, aknolagement you did so, or at least make sure its working code if you do commit ;) but the gitcherry-pick command usually forces you to make a commit before you can re-sync, so using your own repositories and updating them when needing could be the best when begining to learn java, or android sequences =) it took me through tiral and error since 2009 to get as far as i am with java, now i hvae to learn C, C++, and more XML+HTML with roms =S but its all trial+eror, and once you get the hang of it you can make a bash script (***.sh) to make it easier, like how pac-man roms use build-pac.sh for faster building =)
[Fascinate Android Development] donaldj83:
well i created my first build.... unfortunately it wont boot just sitting on the galaxys cyanogen(mod) screen i do know my recovery went from twrp to cw so thats cool that works

heres what i did

mkdir ~/cm11

cd ~/cm11

repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0

repo sync

(took for ever)

. build/envsetup.sh

breakfast fascinatemtd

repo sync

cd ~/cm11/vendor/cm

get-prebuilts

croot

did those edits manually

brunch fascinatemtd

it spit out a zip i flashed it in twrp cleared caches and factory reset it sat at this screen went into cwr and reflashed with same results sadly i cant get into adb so see a log or whats going on and the image doesn't flicker as if its boot looping...any suggestions?

edit:

i just went in to cw to recover my backup and i figured id format every thing again. the format look a little bit of time which makes me think that the it wasn't empty i'm going to give it another shot maybe i'm getting jumpy and not giving it enough time
[Fascinate Android Development] jkok:
did you do the "extract-files" step? the sources itself cannot give you all files, as some are not open-sourced, so they need to be extracted, if you can odin or restore a backup to get booted up, do your usuall flash prcedure to any of the two cm11's on this forum, then do the extract-files step, dont do it for a different ind of rom, e.g. cm10.2, aokp, PA, Pac-man, etc, it has to be the same kind of rom u are building, as redundant as it sounds one already needs to be made, or the same android version without too many edits =S, but if anything keep on trying, make sure the edits are same syntax needed, and all prcedures are done, cause that roomservice.xml i used will be good for cm11.0 based roms, as thats what i thought u were building =S but all-in-all its all trial and error like i have said =)
[Fascinate Android Development] donaldj83:
extract step you say.........? hmmm..... yea i could see that helping......lmao!

yea thats what im after was a cm11
[Fascinate Android Development] jkok:
the step consists of connecting your fascinate, if you have working adb connection+usb debugging enabled goto your device/samsung/fascinatemtd directory in terminal and do

. extract-files.sh

it will take the needed files for your device that are not open source taken u are on a 4.4.* rom atm =)
[Fascinate Android Development] donaldj83:
Yea I know I did the first time but botched something up so I started from scratch then forgot to do it again,
[Fascinate Android Development] donaldj83:
My last test I was able to boot but had no cell / data or anything. I ran out of time though I'll play again this weekend
[Fascinate Android Development] jkok:
make sure apns-conf.xml is in /System/etc/ folder on the device+zip, make sure you did the RIL data patch correctly, as one messup can compile, but leave NO data at all lol, if anything instead of cyangenmod's android_device_samsung_fascinatemtd, use this one

https://github.com/TeamRegular/android_device_samsung_fascinatemtd

if you need it for local_manifests/roomservice.xml use this line and REMOVE cyanogenmod's

basicly change

<project name="CyanogenMod/android_device_samsung_fascinatemtd" path="device/samsung/fascinatemtd" remote="github" revision="cm-11.0" />

to

<project name="TeamRegular/android_device_samsung_fascinatemtd" path="device/samsung/fascinatemtd" remote="github" revision="cm-11.0" />

delete the device/samsung/fascinatemtd diectory from the build source by going to where you repo init'd and do

sudo rm -rfv device/samsung/facinatemtd

you only need to do -rf but the added v is so u see whats erased/u know its working :P

the data patch is already implemented so nothing new will need to be done there =) then it should work, unless you did something else we dont know yet :P

then of course repo sync :P
[Fascinate Android Development] donaldj83:
lol i followed your directions but now im getting errors lol

target thumb C: libminui <= bootable/recovery/minui/../../../device/samsung/fascinatemtd/recovery/graphics.c
bootable/recovery/minui/../../../device/samsung/fascinatemtd/recovery/graphics.c:165:5: error: conflicting types for 'gr_text'
In file included from bootable/recovery/minui/../../../device/samsung/fascinatemtd/recovery/graphics.c:34:0:
bootable/recovery/minui/minui.h:36:5: note: previous declaration of 'gr_text' was here
bootable/recovery/minui/../../../device/samsung/fascinatemtd/recovery/graphics.c: In function 'gr_text':
bootable/recovery/minui/../../../device/samsung/fascinatemtd/recovery/graphics.c:167:5: warning: implicit declaration of function 'gr_text_impl' [-Wimplicit-function-declaration]
make: *** [/home/don/cm11/out/target/product/fascinatemtd/obj/STATIC_LIBRARIES/libminui_intermediates/../../../device/samsung/fascinatemtd/recovery/graphics.o] Error 1
make: *** Waiting for unfinished jobs....

i removed the recovery folder with graphics.c attempting to recompile again

.......... prior to hitting submit on this post that failed lol i think im just goina start from scratch again
[Fascinate Android Development] skepticmisfit:
how is the 2/20 build? stable? thinking of moving to something more recent than ICS.. undecided between this and cm10.1 or hellybean
[Fascinate Android Development] kb8no:
Same question. Anybody have any comments about 2/20 build? Particularly data drops and lagginess.
[Fascinate Android Development] electric bill:
I've been running it for a few days. seems fine. I did have a random reboot when I took it off the charger this morning.
[Fascinate Android Development] skepticmisfit:
no other random reboots though?
[Fascinate Android Development] electric bill:
not since yesterday.

I did find one issue. I was trying to replace the hosts file in /system/etc and was having problems. turns out, /system was full. right now, tibu shows system ROM size is 590MiB with 4.00KiB free. internal flash is 1.12GiB with 360MiB free and SD card is 29.7GiB with 7.21GiB free.

Would one of you guys running this rom look and see what size your system partition is and how full it is?

Thanks
[Fascinate Android Development] skepticmisfit:
you probably should have wiped data before going to this ROM, i'm about to flash it right now so i'll tell you how much space i have

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

one thing i would like to note is that, while flashing cm11, newest zip, it came with CWM 6.0.4.7, not the mentioned 6.0.6.4. just thought i'd tell ya. following the guide seems to have installed everything just fine, not sure why the installation is such a pain and requires so many reboots (maybe it might be due to the fact that fassy roms include their own recoveries.. hmmph). oh also this new version of CWM is actually kinda slow.. that sounds stupid but it's true.

yay just got to the CM boot animation! this is a good sign
[Fascinate Android Development] kb8no:
I got 94MB left on system. No idea what you are filling it up with. This ROM seems stable and good for me. No crash yet. No data drops yet. Any idea how to make this work with OTG adaptor?
[Fascinate Android Development] skepticmisfit:
i think the last thing that worked with an OTG adapter was the Glitch kernel for MTD Gingerbread and ICS ROMs (CM7, CM9, AOKP). correct me if i'm wrong but i don't really think these phones ever had good OTG support.
[Fascinate Android Development] kb8no:
Not that I know anything, but seems to me that hardware can support OTG and that kitkat should support it. So if it doesn't work then maybe it is a kernel limitation?
[Fascinate Android Development] Unjustified Dev:
No , but not yet. Only derteufel kernel had otg support and a few others. I tested otg when I used it using sztupy I think app. He's the one who ported it to Aries from s2 a while back. Cyanogenmod kernel which this uses doesn't support it.
[Fascinate Android Development] kb8no:
So definitely a kernel problem. It would take a kernel dev who cares to modify the kernel and a ROM dev who cares to bake the kernel into the ROM to make otg work. I've developed an interest in otg. Not that I know anything but I wonder if a patch could be made from derteufel kernel.
[Fascinate Android Development] jkok:
ive been experimenting with the bland cm11 kernel, i had to fix the darn static in the headphones after a certain frequency was used... after i get the headphone buttons to work ill see if i can try OTG cable support i acually have a powered female Micro-USB=> female USB=>Male Micro-USB cable handy since i reprogrammed my buds Chromecast lol, but if its anything like to make a jack for a powered-download-mode jig i can test some things, and maybee make a OTG zip just to make a test file in the sdcard =S it worth a shot lol
[Fascinate Android Development] kb8no:
Unfortunately, data drops on this and every kitkat ROM I've tried. Usually couple times a day. You can tell no data when data tile in quick settings is orange. Toggle it on and off and data restarts. Need data so back to 4.2.2 until someone figures it out. Looking for suggestions on favorite 4.2.2.
[Fascinate Android Development] skepticmisfit:
helly bean was pretty good. i actually use cm7 now lol but for 4.2 HB was the best
[Fascinate Android Development] hhp_211:
strange then,,, did you happen to try this version

http://goo.im/devs/notta/roms/fascinatemtd/pa_fascinatemtd-4.1-BETA2-RIL-20140312.zip

I used it for over a week [ til new 3/18 version was out,lol ] and I did not notice a single drop out of service...

.

4.2.2 ROMs

my favorite 4.2.2 was Slim Rom that bdogg did [ Slim-fascinatemtd-4.2.2.build.7.1-UNOFFICIAL-20130708 ]

correct links below

http://www.mediafire.com/download/e...-4.2.2.build.7.1-UNOFFICIAL-20130708-1801.zip

with these gapps

http://www.slimroms.net/index.php/d...load/916-addons/5416-slim-gapps-4-2-2-build-8

may have to use an updated SuperSU on it,,,

I was reading back thru rom pages, but its too hard to remember it all

there was also Domination which was excellent

http://xdaforums.com/showthread.php?t=2273375&page=32

Domination_20130618.zip

Domination_20130623.zip

Domination_20130627.zip

again can't remember all particulars but linked up to the post from 6/18 to start your re-reading, plus I linked up the 6/23 & 6/27 builds that are not available anymore

I'd throw up some dirty Unicorns stuff too but It looks like you did not like the 4.2.2 version very well, lol

.
[Fascinate Android Development] electric bill:
Yeah, I'm seeing the same thing. I might spend some time investigating but I'm not sure if I can fix it.
[Fascinate Android Development] kb8no:
Every 4.4 I have tried has the same data drop problem so whatever is the issue it is common to all the ROMs . Otherwise this is an adequate ROM so if you could fix it then a lot of folks would benefit.
[Fascinate Android Development] electric bill:
I'll see if I can set up a build environment. I haven't made a build for quite a while.

I did run top in a terminal window the last time it happened. A process named

netd or something like that was using around 25% of the cpu. seemed odd.