yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] pdb23103:
Thank you for your reply. I changed to BFQ, but the phone still crackles. I had already used the mms patch, and the email problem was not fixed by that. Question: would you recommend going to OTB 1.2 vs 1.3, or even to EC10 Source Built ComaVolt TouchWiz, the latter which I was using before on SC with excellent battery life and no problems? Other than these headaches, this ROM screams. I hope that I can iron out these nuisances.
[Fascinate Android Development] breaker911:
Yes... Still trying to find a solution.
[Fascinate Android Development] beray5:
I believe JT1134 and imnuts kernels used the same SIO default scheduler, you could verify with imnuts or JT1134. You should try CFQ first as with nemesis2all kernel the BFQ scheduler may only be partially implemented and not full complete.

"Question: would you recommend going to OTB 1.2 vs 1.3, or even to EC10 Source Built ComaVolt TouchWiz, the latter which I was using before on SC with excellent battery life and no problems?"

If you'd used imnuts_100 before without problem, the best match OTB kernel is 1.2 as its proven to use less droop compensation. If not then OTB 1.3 is better as it used more droop compensation the same as default Samsung OEM, don't know for sure what is what on OTB 1.4.
[Fascinate Android Development] djblu:
I'm so frustrated at the moment it's all I can do not to swear on here... I followed all the instructions as listed above, went back to clean install of the stock, got the ed01 radio, install cwr 3, and the comm rom... everything went great...EXCEPT - NOW I HAVE NO DATA AT ALL... NOT EVEN MY MARKET WILL CONNECT...

WILL SOMEONE PLEASE JUST HELP ME GET THIS DAMN THING WORKING?!?

sorry for the caps, but thank you for letting me vent... I feel a little better now...

and why does the market say TSM market... what the hell is that about?

I would say screw it but I refuse to return to stock... I HATE BING!

Seriously, this shouldnt be that difficult...
[Fascinate Android Development] kwinders:
The TSM Market is the new themed version that was released the other day, it's black instead of white, I like it.

As far as you connection issue, I had something similar my first go around. I too used the cwr3, I re did odin from scratch, this time using the latest cwr2.5. Also make sure after flashing the comm rom fire the 1st time, clear data after it is flashed before you let it boot, that made a difference for me.

There is also a link to a good tutorial in the OP.

Hope some if this helps, the finished result is worth it.

Ultimate KangBang 1.3 Fascinate on XDA Premium

Much <3 to all the AWESOME developers
[Fascinate Android Development] Daswolven:
Had the data issue for a few. I Odin'd to stock and let the updates roll through before I Odin'd CWM and then flashed the Rom. No issues since.
[Fascinate Android Development] m771401:
I must be lucky in a sense.

I've had no major issues with this ROM other than the TSM parts as mentioned already.

However battery has sucked big donkey balls since coming from SC292. Anywhere between 10-15% discharge/hr.

I've tried all the suggestions in the thread short of starting completely from stock.

I just have a feeling that if I were to invest time doing so it won't work.

I'm coming from a Moto Droid so I'm still learning the device. Just want to say thanks to all those involved. Documentation has been golden.
[Fascinate Android Development] mrmidnight:
Thanks bro, I don't have all day to check the forum, and I appreciate you answering for me.
[Fascinate Android Development] ezas:
Yes, still a problem after working pretty well for awhile. It's hit or miss for me. Earlier today It would not even find satellites using GPS status to monitor what was happening. Just tried it now and it started finding satellites. If it finds satellites I will eventually get a lock. Sometimes quick other times it takes a minute or so.

A reboot always makes it work right away. I can't find any rhyme or reason to this and have pretty much just accepted it as just one of those things.
[Fascinate Android Development] MattRussNC:
Not sure if there is a better way but going back to stock fixed out for me. Before I had about the same discharge as you, great on sc crap on comrom. Tried reflashing a few times under coherent circumstances with little change. However after going back to stock and back up to comrom battery has been amazing. Been to stock and back so many times now I dont even mother with nand backups.
[Fascinate Android Development] matthe4292:
Does anyone know when or if the record audio attachment option will be resolved?
[Fascinate Android Development] nitsuj17:
i edited the market to say TSM as this is a TeamsSbrissenMod rom...you dont like..dont use it :rolleyes:

and really flashing stuff isnt that difficult for the vast majority of people..

if you odin back to stock then go from there, things usually work out
[Fascinate Android Development] nitsuj17:
honestly people.....if you have problems and want help you really have to

1) post your exact setup (version of com rom, kernel, voltage settings, any other mods you did flash)

2) did you wipe data/cache/davlik cache before flashing the rom

3) what rom/setup did you flash com rom over

4) what is your *specific* problem...not "omgz ma ****z be borked yo"...that helps no one and frankly is annoying to see...

5) ive said this 500 times already, but hey whats once more? POST AN ADB LOGCAT OF YOUR YOUR BOOTLOOP/FORCE CLOSE PROBLEMS/ETC...it aint hard

cd your adb folder

then

adb logcat > logcat.txt

-this creates a text file in your adb folder in the sdk (tools or platform-tools, w/e) post it in a pastebin and link the pastebin here or post it from dropbox or something

for the less sdk literate folks (and really im tempted to say if you dont have adb, dont flash stuff...but umm...i wont)

you can use terminal emulator on your phone to logcat (obviously not when booting to diagnose bootloops, but can help with force closes)

logcat > /sdcard/logfile.txt

-this creates a file on your sdcard...copy it to your computer and pastebin/dropbox it

going forward this is the only way TSM/com rom team will help you with issues....its too hard/annoying to help people with random problems with no background or information to start from

dont like it? theres always a way too similar other rom with all of com rom mods in it...go flash that

/end rise in blood pressure
[Fascinate Android Development] nitsuj17:
using the tw mms *should* fix that...or i suppose i could post aosp audio recorder later today..w/e works
[Fascinate Android Development] Headcase8911:
Now nitsuj, remember, none of this will matter in 10,000 years.....breathe.

Sent using mental telepathy
[Fascinate Android Development] nitsuj17:
haha of course not :)

just trying to get a handle on this thread...which is all over the place
[Fascinate Android Development] sunder74:
Amen...and again people WIPE, WIPE AND WIPE AGAIN. Glad you're doing this it will hopefully help development.
[Fascinate Android Development] the_passenger:
99% of the time people don't finish reading the first post but they started to flash and get problem. Then people tend to complain and point finger. My rules of thumb when flashing a new ROM: If an app does not work, reinstall the app. If many apps don’t work, wipe wipe wipe, reinstall all apps. If it does not boot, make sure the download file is good and flash again. To be honest, the entire process would probably take less than an hour.

To me, if u can help them, great. If u can't, that is ok. No need to feel mad since there is no point of doing so. We can't make everybody happy.

My $0.02.
[Fascinate Android Development] garywojdan81:
^^++1 Ditto. Just checked my d/l file name for comm.rom 1.3 & its listed as "test" in the file name from the first mirror put in the post. That + the explicit/implicit rules of this community kinda say it all.
[Fascinate Android Development] sunder74:
The thing I don't get is I never have any of these crazy issues. I wipe every flash every time regardless and I manually restore my set up every time.

The comrom though by release number seems like small incremental changes but there's new kernels, significant framework changes etc.
[Fascinate Android Development] Daswolven:
Endless problem. No one should flash anything without at least reading the first and last three pages of the thread. That alone would eliminate 90% of the "something is broken" posts.
[Fascinate Android Development] dablitzkrieg:
This is excellent. Im on 1.3. OC to 1300. No fc. Only issue I'm having is no ability to use music controls at miui screen. Anyone else having this issue?
[Fascinate Android Development] ssewk2x:
One thing I noticed just now is that, at least as of 1.2, the google dns servers don't appear to be configured quite right in /etc/resolv.conf. Specifically, the second one is listed as 8.8.8.4, and it should be 8.8.4.4.

I haven't upgraded, so I don't know it it's the same in 1.3, nor do I know if it really matters, but I figured I should let the devs and others know so you all can check.

Edit: fixed an unfortunate typo
[Fascinate Android Development] seanatsb:
Video Camera Force Close. Please Help. All info included

Hi all. I have read this whole thread over the past week. I see a couple other people have had a similar problem as I do. I, though, am including as much info as possible, including logcats so that the developers might be able to figure out what the problem is.

My issue is that the video camera will randomly stop recording, giving an error msg and then exits out of the whole camera app when recording in highest resolution.

I am on Community Rom 1.3. Here's exactly what I did coming from Com rom 1.2.

1. Odin'd to DL09

2. Over air update to Ea28.

3. Over air update to ED01. (at this completely stock point, video camera worked fine)

4. Odin'd cwm-recovery-ALL-3-30-FIX.

5. Powered on into recovery.

6. Wiped data, cache, and dalvik, all three times.

7. Flashed superuser file from link in OP

8. Rebooted directly back into recovery

9. Flashed community Rom 1.3

10. Rebooted.

11. Set up google, downloaded TiBu, restored Term Em.

12. Tested video camera. ( I got a couple errors and closes, then the recorder appeared to work normal for a couple five minute videos and one 10min video.)

13. Then flashed White Chrome v2.0. (recovery, wipe cache and Dalvik 3x each, but no data wipe)

14. Tested video camera. Error/close after as little as 8 sec, and never more than a minute.)

15. Recovery. Wipe Data, Cache, and Dalvik 3x each. Reflash Com Rom1.3

16. Tested video. Error/Close again happens a couple times.

17. Set up google, downloaded TiBu, restored Term Em.

18. Generate logcats hosted on pastbin. Had to make 2 files since it was so long. Here are the links: part A http://pastebin.com/2dzg4S4k and part B http://pastebin.com/181ibtKC

19. After i generated logcats, i was able to get video camera to work without errors for three videos ranging from 5 min to 10 min.

I will reflash White Chrome and test and post logcats if more errors.

►EDIT: This time around, I wiped Data in addition to Cache and Dalvik before flashing White Chrome Theme. I got a couple of Video failed right after flashing, but now the video appears to be working. I've made three 10 min videos without a failure.

Still not sure why I get the initial failures after flashing the Rom/Theme, but happy for now that video is working.
[Fascinate Android Development] nitsuj17:
thanks for the detail and log....video camera issues if i recall existed in earlier OTB kernels...did this happen at all on com rom 1.0 or 1.2 (different kernels)?
[Fascinate Android Development] Groundhound:
After a full day on 1.3 this issue has resolved itself, no idea why but I'll take it. Everything is now working well with this rom AFAIK.
[Fascinate Android Development] HTCuser916:
Don't wipe too hard

Remember that you don't need to wipe wipe wipe. Wiping more than once will not improve the situation. If you are using the correct version of CWM and you receive a message that the data/cache/dalvik wipe was complete then it was complete. Wiping again will not make it more complete.

Remember - Don't wipe more than once, you might make your phone irritated and bleed. :D
[Fascinate Android Development] nitsuj17:
yeah one of each is fine...just wipe wipe wipe is more of us just screaming to get users attentions
[Fascinate Android Development] HTCuser916:
ADB logcat question

Does anyone know of a script or widget that will automatically generate a logcat? It would be so cool if there was an automated easy way to generate a logcat.

Do you have to generate the logcat after connecting to ADB via the computer?

Thanks
[Fascinate Android Development] times_infinity:
yeah. it's called aLogcat in the market. Might wanna use google next time.
[Fascinate Android Development] seanatsb:
Yes, it was occurring with com Rom 1.2 while running a white chrome theme. I didn't test on 1.2 only. Unfortunately, I didn't make logcats at those times.

oh, and I used the kernels that came packaged with the ROM and I did nothing to change kernels, voltage, etc. I've only flashed ROM package and themes.
[Fascinate Android Development] seanatsb:
However, unlike your bunghole, excessive wiping won't hurt your phone
[Fascinate Android Development] agsded:
Well, I'd think it would shorten the lifespan of the phone's internal storage, though....
[Fascinate Android Development] euklid:
Does this work with eb01 radio?? Whats best radio to use with 1.3???
[Fascinate Android Development] seanatsb:
Don't know enough about the internal memory to know if this is the case or not...However, I do know that if by some miracle I killed my internal memory by wiping the phone before my two year contract was up, verizon would be replacing my phone for free.
[Fascinate Android Development] rctreadaway:
Since 1.2 and 1.3 I've found that my gps will not lock on what so ever. It was great on the original release however. Is this a kernal issue? Anything I can do?

Besides this flaw I love this rom. Almost stock like in terms of force closes etc.. Thanks guys!
[Fascinate Android Development] nitsuj17:
this will work with any radio...personally i prefer ec01...though some took the ota to get ed01
[Fascinate Android Development] dablitzkrieg:
Yes, I have also had this issue, but apparently you and me are the only ones. This is quite unfortunate.
[Fascinate Android Development] mod143:
anybody have an issue with the gallery using the sensors almost 100%? i got bored and went into spare parts and noticed that under 'sensor usage' that the gallery was almost 100%. i dont check it that often but i know it hasnt always been like that. my battery life seems consistent to previous roms so i dunno if its actually draining or not.
[Fascinate Android Development] beray5:
Here you go, you can try the original OTB kernel from the first release to verify kernel issue. And you can flash back to the latest OTB 1.4 from here -> http://xdaforums.com/showpost.php?p=13565199&postcount=697
[Fascinate Android Development] euklid:
How can I get ed01 radio if I don't have verizon to get ota update?
[Fascinate Android Development] beray5:
http://xdaforums.com/showthread.php?t=1044474
[Fascinate Android Development] kwinders:
Search the forum, adyn has it posted to flash or odin

Ultimate KangBang 1.3 Fascinate on XDA Premium

Much <3 to all the AWESOME developers
[Fascinate Android Development] nitsuj17:
no you have to take the ota to get the ed01 radio
[Fascinate Android Development] beray5:
adrynalyne did included all OTA updates required to get FULL ED01 stock here -> http://xdaforums.com/showthread.php?t=1044474
[Fascinate Android Development] matthe4292:
Thanks for the reply. I switched the mms app and that fixed it perfect!
[Fascinate Android Development] rctreadaway:
I tried the old kernal you attached and no difference. I was getting 8-9 satellites in gps aids at one time now I can't even get one. The gps has to be the biggest flaw in this phones. Almost makes me want my droid 1 back :(
[Fascinate Android Development] beray5:
Did you ever try CFQ or BFQ in voltage control app drop down menu?
[Fascinate Android Development] rctreadaway:
Let me try that. Appreciate the prompt replies! Thanks
[Fascinate Android Development] mkarps:
With all the status bar mods included in TSM now(clock options, text color, etc)....is it possible to include option to use a white statusbar like on AOSP?
[Fascinate Android Development] rctreadaway:
Ok still nothing. Rebooted and tried gps aids, google nav. No gps
[Fascinate Android Development] beray5:
Did you verify that you could connect to your time servers? no time fix = no GPS.
[Fascinate Android Development] nitsuj17:
at the present time no...although who knows what sbrissen is capable of :)
[Fascinate Android Development] rctreadaway:
Yes my phone is always showing the correct time if that's what you mean?
[Fascinate Android Development] beray5:
Use root explorer and look at the file /etc/gps.conf, it will list the ntp server your GPS is using.

This is what on mine -> NTP_SERVER=us.pool.ntp.org

I use the below command in terminal emulator to check my connection to the NTP server

ping -c 8 us.pool.ntp.org
[Fascinate Android Development] rctreadaway:
That's the one. Then it has three other ones listed below it
[Fascinate Android Development] rctreadaway:
Ok I just tried it again and now it sees 12 locked in 9 so it's hit out miss I guess... This thing has me just ready to toss it out the window as far as the gps goes. While watching it it would intermittently go out then come back. Appreciate your help
[Fascinate Android Development] comeoriginal:
I haven't updated to 1.3 yet, but today randomly my 3g stopped working. Anyone ever come across this at all? Toggling the mobile network on and off doesn't do anything. Tried *228 both options just to see, but to no avail. I'm going to update to 1.3 shortly, but I was just curious if this is a known issue or if it's just something random (I haven't found anything in this thread about it though). Also, I'm in an area that always gets good signal and solid 3g connection, so it seems weird to me.

thanks
[Fascinate Android Development] xjestersdeadx:
Yes, there's a couple posts about it. If it happens consistently it you can replace the phone on your account with another phone (using the Verizon website), then put your current phone BACK on the account, and it should solve the issue. This worked for me. If you don't have another phone to swap you can call tech support and ask them to use one of their dummy serial numbers.
[Fascinate Android Development] dablitzkrieg:
Still was wondering if there was a reason why the music option does not work at miui screen
[Fascinate Android Development] comeoriginal:
Alright cool, I'll try that. Sorry if this was already answered before, I just couldn't find it I guess.

thanks
[Fascinate Android Development] Wolfkmann:
So, I am running 1.3 (and loving it, thanks devs), and then I flashed the rotating dialer from,the first page, and now I lost the puzzle answer ability. I checked, under settings - TSM - misc settings - answer options - puzzle answer is still selected.
[Fascinate Android Development] ssewk2x:
Rotating diaper? Sounds ****ty.

Ba-bump, shhhhhh!
[Fascinate Android Development] HTCuser916:
Thank you for the reply. I did search for one on Google and on XDA and on AC.

Does everyone prefer aLogcat over Catlog? Or is there another one that is preferred?

Also, does anyone have a mirror to the chat log that Adrynalyne made regarding using ADB?

Thanks for all the help.
[Fascinate Android Development] OhioYJ:
nemesis2all OTB-Reloaded Kernel included the tethering dummy module, does this mean the kernel in this rom includes it as well?
[Fascinate Android Development] speedingcheetah:
Battery Life

I realize its too early to report on battery life...but....should a bstats wipe be done after flashing this...

Also, wondering if those coming from SuperClean 2.9.2 with EC01 radio and EC10 voodoo kernel...if there is a big difference in this new rom or not..since it doesn't have the ED01 radio...

I just got my phone the way I want it and there is always something new to flash that requires a data wipe..so I am looking to be convinced that this is worth the trouble..
[Fascinate Android Development] hd0120:
Awesome ROM. Thanks a lot, adrynalyne.
[Fascinate Android Development] stereoblind:
Everything about this ROM is perfect. No issues at all coming from the debloated EC01 with all the necessary wipes. Thanks guys. :)
[Fascinate Android Development] Phasze:
Another side note, whenever I slide the TSM option on the 4 button lock screen it restarts the phone.
[Fascinate Android Development] bobloblaw1:
As has been stated several times already, you must set an action to the tsm button prior to using it.
[Fascinate Android Development] Phasze:
Yeah was just going through the already 16 pages and found that lol.
[Fascinate Android Development] ssewk2x:
Nemesis2all and/or the rest of the devs: does the kernel in this have the patch I gave nemesis2all a couple days ago?
[Fascinate Android Development] DirgeExtinction:
Is this what you're looking for? http://xdaforums.com/showthread.php?t=1046377
[Fascinate Android Development] GoogleAndroid:
Awesome. Best ROM ever. I have the v4 test build from the IRC, but I'll definitely be wiping(since I'm having issues) and flashing this.
[Fascinate Android Development] speedingcheetah:
That is a pure stock rom ODIN..not the community rom..and it does not have ed01 radio(modem)...
[Fascinate Android Development] nemesis2all:
No it does not. I sent you a pm. If you get a chance I would like to work with you more on the patch so I can finalize current state of otb. Feel free to respond in pm or let me know when you have a chance to jump on irc.
[Fascinate Android Development] sbrissen:
Kernel is included, rom will use your current modem.

Yes this has accurate battery

this is rooted but it doesn't flash cwr. :-)
[Fascinate Android Development] phatmhat:
i had the same .core fc too. no dialer. and i did a data, cache and dalvik wipe. guess ill try from scratch again. get ec01 radio and then up from there.
[Fascinate Android Development] tapout27:
Can we please get a patch for the stock Android keyboard? Please and thank you!
[Fascinate Android Development] loganpimpman42o:
kinda new to this fascinate flashing, seems different then the cappy, my wife got the fascinate and i wanted to flash this rom now do i use clockworkmodd or is there a different way i'm supposed to flash
[Fascinate Android Development] speedingcheetah:
Ok..thanks..

So..do a data/cache wipe etc..

Flash this rom...

will have no cwr after flash this...

then will have to ODIN cwr after...right?

Just want to make sure I do things in right order..
[Fascinate Android Development] oak25:
i have the same question CWM or odin?

sorry IDK much about this phone.. i am a MT4G user... this is for the lady
[Fascinate Android Development] ssewk2x:
Responded via pm. Thanks :)
[Fascinate Android Development] Grimis:
So I try to import contacts from the sd card via contacts menu and it just runs forever searching. I did the export before flashing the new rom. Stumped.
[Fascinate Android Development] garywojdan81:
I have noticed the same thing since updating to 1.3, but a reboot generally fixes it. For me, it seems like the scheduler plays a part. Happens more with bfq than any of the others. I'm currently back on cfq & no problems yet.
[Fascinate Android Development] dablitzkrieg:
K, this will the the forth attempt to get someones attention. HAS SOMEONE HAD AN ISSUE WITH THE MIUI SCREEN NOT ALLOWING YOU TO USE THE MUSIC PLAYER FUNCTION? :mad:
[Fascinate Android Development] chopper the dog:
No. Are you double tapping the lock icon on the lock screen to display the music controls on the miui lock?

good day. using xda premium.
[Fascinate Android Development] garywojdan81:
Sorry, but no. The miui screen even shows the controls with the themed miui music app I've been playing with from the games & themes thread here on xda. I did have to check "always show music controls" in the TSM lockscreen settings menu.