yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] rigglemania:
The boot problem caused by it has been reported plenty in this thread. That's broke enough not to include it in an extremely popular ROM, if you ask me. It's also not available separately, which reinforces my point.

Glad it's working for you, but I think you took my post a bit too literally.
[Fascinate Android Development] beenz:
IMO, if you aren't willing to follow the thread, you shouldn't flash the rom (any rom). Also, you can't get mad if something isn't in the OP, but has been answered a ton of times already. Drives me nuts when something gets asked and answered 15 different times
[Fascinate Android Development] nitsuj17:
at the time of testing only 1 of my MANY testers had issues with otb 1.4, so we had little reason to believe there would problems....clearly the problems with it are more widespread than that...seems like 1/4 or 1/5 have issues flashing it

since 1.3 is the last release we've had up until now, clearly it hasnt been replaced

it will not be in the next version, and there will be more than one kernel as option as well in 2.0...the new thread will have a faq and known issue section that will be updated as things come to light

we dont knowingly include files/kernels/mods that have issues...sometimes these things slip through testing...but that being said the kernel still works for the vast majority of people...if it was the other way around a patch would probably have been necessary
[Fascinate Android Development] Headcase8911:
Nitsuj dude, I really admire your timely and comprehensive approach to the wide range of questions people throw at you, thanks
[Fascinate Android Development] rigglemania:
I'm guessing you didn't read the thread either since you apparently aren't aware that I *didn't* ask anyone about this issue, having read thread myself and found the solution. I'm not going to apologize for suggesting that pertinent information should be added to the OP instead of forcing users to wade through 200 pages of responses, however. Especially when the failure rate is apparently as high as 20-25%
[Fascinate Android Development] rigglemania:
I appreciate your response. I don't mean to suggest that there was insufficient testing or that anyone is to "blame", it just seems prudent to mention such a common issue in the OP if the version affected by said issue is to remain available. Doing so would not only cut down on the number of questions asked about said issue, but also on the amount of whining about such questions by self-appointed moderators :p
[Fascinate Android Development] nitsuj17:
yeah like i said in the new thread we will keep better track of stuff and reserve more posts and such...2.0 shouldnt be that far away
[Fascinate Android Development] chronster:
can you fix the camera picture browser app, and gallery app, so it doesn't force close when I want to look at pictures I've taken?

Seems like such a simple thing, and now here I am happy as a clam with a stock debloated/deodexed rom, but where are the themes? Oh right, going to the broken rom, and everyone acts as if I'm crazy for asking for an ED01 port.

PM me when you get that fixed, and I'll flash back over.
[Fascinate Android Development] GrainOsand:
http://xdaforums.com/showthread.php?t=1073930

Posted this in sbrissens thread to, hopefully can be added or patched to comm rom. 2.0

Gingerbread screen off animation mod to froyo...dev claims most devices and posted source code to boot...such a cool animation
[Fascinate Android Development] mlarma:
Anyone know if the correlation between the 1.4 kernel puking has anything to do with the hardware revision? A poll would be interesting... For what it's worth, I have no issues and have hardware revision 04.
[Fascinate Android Development] fwdixon:
It allows you to use the 3.5mm audio jack on the Samsung car and desk docks to put all but phone audio to an external device or speakers. For some reason, I get the keypad tones through the external, but the phone call itself is played through the onboard speaker.
[Fascinate Android Development] nitsuj17:
Yeah I have no desire to pm you to personally let you know that something has been fixed

And gallery and camera galleries don't force close for me or anyone I've asked to try it...most camera issues were fixed by changing the scheduler in voltage control

Either way I don't see a logcat that you posted of the issue...if its in here somewhere I guess I missed it...that's the main way for us to get to the bottom of issues

And if you didn't post a logcat then don't bother complaining....that's useless...we can't blindly guess as to what is causing the issue...

And themes are made generally for the most used roms....so the fact that virtually all of the themes are made for this rom implies that the themers at least are personally using this

But again....I wont be personally notifying you of anything...you can read the updates just like everyone else if you care to
[Fascinate Android Development] MattRussNC:
Thats pretty dang cool, hope they can find a way to work it in.
[Fascinate Android Development] andmer:
This requires native libraries being rebuilt, which rules out a touchwiz release, the guy himself did it on CM6.
[Fascinate Android Development] jthompson0019:
Not to rush or being a ****, but i'm planning on reflashing my phone because of lag issues i haven't been able to work out and I was hoping to be able to have a new build. Any word when we might have one?
[Fascinate Android Development] landshark68:
@jthompson0019 - You couldn't have read 2 pages back to see this post by nitsuj17?
[Fascinate Android Development] jthompson0019:
Nah when you get promoted with a job And have 2 little ones at home makes it hard to find time to read through thousands of post. Haven't had a day off in 12 days and many of those days where 12+ hours long.
[Fascinate Android Development] landshark68:
That would explain it. Sorry. Like nitsuj's post said, they are hoping to get it out on irc for testing next wed/thu, so may not be posted and available until next weekend or just after next weekend depending on the results of testing. But definitely not before then.
[Fascinate Android Development] beenz:
Sad panda
[Fascinate Android Development] MattRussNC:
Oh well who needs it then. This rom is for fast and kicken ass not being pretty :p. But should they ever pull it off, well that would be ok to :D

Cant wait for 2.0. Great work fellers.
[Fascinate Android Development] nfrederick:
Don't hate, I just came from an Incredible and this is quite a bit different.

Should I flash an AOSP or TouchWiz based kernel for this? I didn't see anything in the first couple posts stating which type of ROM this is, being community based my guess would be AOSP but I just want to make sure.

Thanks.
[Fascinate Android Development] patvet10:
Is there anyway I can disable the lock screen totally on this ROM?
[Fascinate Android Development] DirgeExtinction:
I do believe it'll be TouchWiz.

Bow chika wah wah
[Fascinate Android Development] jpricesd:
Com Rom is a TW based ROM.
[Fascinate Android Development] ssewk2x:
Touchwiz. And I'd highly recommend the otb 1.5 kernel, fwiw.
[Fascinate Android Development] reisb:
This was posted in Evil Fascination thread:

Everyone can have their own opinions and like whichever roms they please (I have tried and like both EF and CM), but this manic020 guy is just posting to piss people off.

Mods, please remove him and/or forums, please do not help him.
[Fascinate Android Development] mrmidnight:
I would love to be able to use my xm app and gps at the same time through car speaker while using the dock, is there anything for that

Sent from this EMT's Fassy runnin' ComRom!
[Fascinate Android Development] eshu68:
Cool... a slap on an arrogant face.. Thanks devs.. You rock..
[Fascinate Android Development] patvet10:
Would anyone be able to answer if there is a way to disable the lock screen. I have the no lock app which I have always used but it won't kill any of the lock screens on this ROM. Any thoughts, suggestions, pointers please. Thanks.
[Fascinate Android Development] aaronDroid80:
screen lock during bluetooth phone call

OK, please don't kill me. I'll direct this description of my experience toward the devs, since I have no way of knowing what tweaks and fixes went on under the hood of the stock apps. That said, I don't know if this is a request for an improvement from stock or a bug report for the ROM, and I apologize in advance for not having a log, but this should be something that can be easily recreated. [Comm ROM 1.2, ED01, OTB 1.3; flashed from stock ED01 OTA, full data/cache/dalvik wipes]

The other day, I made a phone call to my financial institute and was using my bluetooth headset. I had to use the keypad to enter all my account info, and while I was entering the numbers, the screen lock timed out (literally as I was pressing numbers, the screen faded out), so I had to wake the phone up & enter my unlock pattern to continue entering the numbers. This happened 3 times during the call. I tried a phone call without the bluetooth and instead used the speaker, and in this case, the screen never shut off. So my thoughts are that a couple of components are not communicating with each other properly, causing the screen lock control to not see the number input from the phone.

I was going to hold off on posting this until I could run a few more test calls, but since you are about to roll out an update for testing, I figured that I could at least let you know about it.

Thanks for all the hard work you guys do. Looking forward to what's to come.
[Fascinate Android Development] MattRussNC:
Afraid its been discussed before and the responses were that you cant now. It was stated that the ability to disable lock screen was lost after building off official froyo. Not sure of the details, I am only repeated what was said after I asked the same thing.
[Fascinate Android Development] lissa5168:
Sorry, I just saw this. I have been able to bypass the screen lock successfully on ComRom 1.3 (and all roms up to this point) with an app named myLock Utilities. https://market.android.com/details?id=i4nc4mp.myLock&feature=search_result

It will also let you lock the screen while in a phone call so that your face doesn't disconnect the call, but a) I really haven't had much trouble with that on the Fascinate like I did my OG, and b) It gets REALLY annoying to have to disable that every time you hang up or have to enter a number with the keypad. I don't use that feature.
[Fascinate Android Development] patvet10:
Thanks guys appreciate it.
[Fascinate Android Development] nitsuj17:
just to further clarify some things for 2.0:

-sgs2 lockscreen will require tw mms and tw music to properly function, so these will be built into the rom (there will be optional downloads for themed miui music, aosp music and aosp mms, that will delete the tw version, but render sgs2 lock useless)

-there will be 3 versions of the rom (i think) 1 with an otb kernel, 1 with an pbj kernel, 1 w/ no kernel (pretty sure of this, but subject to change of course)

-2.0 will be in a new thread....there will be several posts to the op 1. brief overview/credits 2. faq 3. instructions to install and instructions to bug report 4. downloads (rom and add ons)

-similar to the required bug reporting post i made somewhere in this thread that everyone ignores even though i link it in post 2, you will have to give explicit details of what is happening bug/error/fc wise including setup...and you WILL HAVE TO provide a logcat or TSM will not even respond to the issue...its required

(i will however link how to set up the sdk/how to logcat for the 500th time, no excuses to not be able to do either)

-faq will be updated from questions/issues that arise from within the thread...if you do not read through it before posting your question/issue, we will also ignore that and you will probably get flamed (fair warning)

-the last few points are just for us to be able to keep track of what is going and best serve the most amount of folks possible...com rom is pretty popular for the time being..and will continue to be developed/worked on for awhile (2.0 will not be final, we have several other things already for consideration for 2.1 and beyond)...and even if jt's cm7 becomes fully functional id think many will stay with tw based roms for various reasons, so this wont be abandoned

-and again, tsm is made up of many different members/contributors/testers/etc...i generally find myself being the spoke person for much of it, but it is *not* my rom, its not adrynalynes rom, its not sbrissens rom (although the latter two are clearly the most influential)...

-it is the "community rom"...if you feel like you have something worthwhile to contribute, or a particularly good suggestion/idea/mod or otherwise, feel free to stop into freenode irc #teamsbrissenmod and help out :)
[Fascinate Android Development] jpricesd:
Sounds great! Can't wait to try it out
[Fascinate Android Development] jkat797:
awesome thanks!:) do u have any idea for how much longer before we will see this update?
[Fascinate Android Development] DirgeExtinction:
Yes! I miss the TW music app. Will we still have the TW Video app? Can't wait for this update. :)

Bow chika wah wah
[Fascinate Android Development] nfrederick:
I flashed this rom yesterday around 10am. I set it up how I wanted to and it was running flawlessly. Later last night I picked it up to text a buddy of mine and when I went to press the power button for the screen to come on nothing happened. Even holding it for a second to try and turn it back on (thought maybe it shut down by itself) didn't do anything. I had to do a battery pull to get it to reboot. Would this be considered a rom issue or a kernel issue? I tried 2 different kernels. OTB 1.3 and OTB 1.5. Maybe another which would have been the PBJ.

Any ideas? The first time it happend I flashed a new kernel right away. Happened even faster on the new kernel. I wish I would have paid enough attention to see which version did it when and what I was using when it started but yesterday I flashed so many different roms/kernels I'm stunned my head didn't explode.

Thanks in advance for anybody willing to help me figure this out. I'm currently running the stock deodexed/debloated rom and have had zero issues. OTB 1.5 kernel.
[Fascinate Android Development] landshark68:
Just like verizon's answer on the Froyo update......soon :p

Last update I saw Nitsuj post was just a few pages back and the estimated (just estimated so probably subject to change) eta was for 2.0 to go out on irc for testing on wednesday or thursday.
[Fascinate Android Development] landshark68:
That would be the dreaded sleep of death or SOD. I am having the same problem and am going to try and catch a logcat to send to TSM. If you want to go back to Comm ROM with the OTB kernel, start out your undervolting at -25 across the board and work your way up from there to figure out how much undervolting your phone can handle.
[Fascinate Android Development] nfrederick:
So you believe this is directly related to undervolting? In that case I'll reflash Comm Rom and try agian leaving the voltage settings as default.

Thanks.
[Fascinate Android Development] garywojdan81:
Stay away from Youmail as well. Its a known cause of SOD as well.

Sent from my OTB Comm.Rominate
[Fascinate Android Development] nfrederick:
Ha, and I absolutely love YouMail.

Well, sacrifices need to be made. Goodbye YouMail.
[Fascinate Android Development] beray5:
times_infinity comavolt kernel is the gold standard for SOD from uv. If you still have SOD with it the problem isn't uv.
[Fascinate Android Development] nfrederick:
One more thing. Is there any way to get the stock skin back for the Swype keyboard?
[Fascinate Android Development] landshark68:
Amen to this. I've never had SOD with ComaVolt. I was just on ComaVolt for a week after I had my SOD problem with OTB 1.5 & 1.3, no SOD.
[Fascinate Android Development] sunder74:
I think there's one in the OP. Always check the op for add ons, mods and stock apps. :)
[Fascinate Android Development] nitsuj17:
the *goal* is to have it out to testers by thursday at the latest and then a friday/saturday xda release...but that depends on a few things we are working on, and how testing goes of course :)
[Fascinate Android Development] nfrederick:
I don't know why I didn't look there. Thanks for pointing me in the right direction.

EDIT

All I found was TSM themed swype from gunnermike53. Couldn't find anything about stock Swype theme. Could it be the Swype theme fix that is attached?

Thanks.
[Fascinate Android Development] streebs87:
I believe so. Just flash that.
[Fascinate Android Development] jpricesd:
What else could cause it? I tried a couple of different OTB kernels and got SOD even with very little UV. I tried comavolt and got SOD as well after only a few hours. I'm trying PB&J SV now just to see what happens and so far no SOD, but sometimes it takes a couple of days to get it. I'm not or never have installed Youmail either.
[Fascinate Android Development] garywojdan81:
Look up beray5 in some of these posts. He seems to have a good handle on SOD. It seems to have something to do with droop voltage settings, if I recall his explanation right.

Sent from my OTB Comm.Rominate
[Fascinate Android Development] aaronDroid80:
It's funny you mention the verizon thing... I took my wife's phone into the local vzw (authorized retailer) (I know, but it's the closest one to my house), and the guy there actually thought that 2.3 was passed out a couple weeks ago. Had to remind him that it was 2.2.

:)
[Fascinate Android Development] Wolfkmann:
Can't wait for 2.0

Meant to post this comment/suggestion earlier, but didn't get a chance. I work in a building that constantly interferes with my phone picking up a signal. So while my phone is in my pocket it is constantly searching for a network. I have 98% battery at 7:00 am, and when I take it out at lunchtime it would be down to 60%. I would spend ten minutes or so checking email and then put it away until I left work when it would be down to 30%. I downloaded from the market and app called green power and now at the end of the day it is only down to 80%. Awesome, huh. My point here is can this functionality be built into comm rom 2.0? I think it would be great if the rom could do this without needing an add-on app.
[Fascinate Android Development] MattRussNC:
Gave that app a shot and while it's a little quirky sometimes it does indeed work. Thank you for the recommendation. Been using it since you posted the link and am happy with it, at least until the ability is built into the rom.

Thanks again.
[Fascinate Android Development] eibbed0001:
I haven't made any changes to the voltage settings but still sometimes get the SOD with the ComRom kernel. I'm going to try the times_infinity one.
[Fascinate Android Development] nitsuj17:
bumping this for those who missed it :)
[Fascinate Android Development] Bubbadogg14:
Sounds like an update is rite around the corner... Definately interested in giving this release a go :)
[Fascinate Android Development] davidstre:
i love this rom but theres just one thing

setcpu makes my phone go crazy on this rom, it lockes up and then get stuck in a bootloop. does anyone know why this happens and how can i overclock my fascinate using this rom
[Fascinate Android Development] jpricesd:
Use the voltage control app that comes with it if you are using the OTB kernel
[Fascinate Android Development] Bubbadogg14:
U nd the voltage control app w the OTB kernel that comes w this rom not setcpu it doesnt work properly... You can oc w the paid version of voltage control
[Fascinate Android Development] Dread This Day:
You can overclock in the free version as well, you mean you can overVOLT in the paid version.
[Fascinate Android Development] euklid:
Anyone have the the problem thag gmail sync stays on for a while and the gmail app uses a lot of cpu so it drains the battery quickly, have to kill gmail using task manager.
[Fascinate Android Development] ssewk2x:
I've noticed that. What worked for me was to clear gmail's data from the application manager under system settings. Titanium backup might let you do it, too.

Good luck.
[Fascinate Android Development] AlexDeGruven:
If your data connection goes to crap right before, or during the sync, it will also cause the sync to hang up/run really long.
[Fascinate Android Development] nitsuj17:
for those who arent on twitter (or dont follow me :eek:)
[Fascinate Android Development] drnihili:
Sweet! I'm all on tenterhooks!
[Fascinate Android Development] stereoblind:
"Tsm Market" is just a market theme, right? Or is it actually different than the regular market?
[Fascinate Android Development] mrjake1970:
id guess the tsm market is a theme/mod kitchen similar to the old blackhole rom and the choices you had when loading it...
[Fascinate Android Development] rsswga:
getting great battery life
[Fascinate Android Development] StDevious:
this, I work in the basement and signal searching is the main cause of battery loss, even with data and wifi off.
[Fascinate Android Development] deafptl4ever:
Great battery life here too. Charge once a day but still not run out completely at end of the day.
[Fascinate Android Development] deafptl4ever:
RT @nitsuj17: @adrynalyne we are gonna have com rom 2.0 ready for testing by wednesday...3 versions: otb 1.5, pbj kernel, and (cont) http://tl.gd/apqseb
[Fascinate Android Development] deafptl4ever:
RT @nitsuj17: lets see about getting com rom 2.0 tests out today...... (no peeing in pants allowed) My quote not @nitsuj17
[Fascinate Android Development] tbone004:
Swype Theme Fix for V1.3

Is there any mirrors for the Swype Theme Fix for V1.3? Looks like the mediafire link is having issues.

EDIT: Nevermind, the link is working now.

Thanks
[Fascinate Android Development] nfrederick:
I'm getting FANTASTIC battery life. ComRom 1.3 with OTB 1.5 kernel. Easily going a full day and still at 50%. Not a HEAVY user but I still mess with my phone constantly (texts/new apps/rss reader). Can't ask for anything better. Thanks to all the dev's who are working on these.
[Fascinate Android Development] dr_w:
My battery life is terrible. No wifi, no roaming, etc... I can literally watch the battery level drain before my eyes. I hope 2.0 helps this.
[Fascinate Android Development] beenz:
Getting great battery life here too. I listened to music (off the SD card, not streaming) for about 6 hours yesterday. The rest of the day was moderate usage. Battery was at 28% when i went to bed last night. It's usually at 35% when i go to bed.

2 common battery tips:

When you aren't connected to wifi, turn it off

Look at your time without signal (settings - about phone - battery use - cell standby) If it is higher than like 10%, toggle airplane mode on and off.

Edit: Haven't touched voltage settings
[Fascinate Android Development] hazard666:
Same here, had to install JuiceDefender to last longer than a normal work day.
[Fascinate Android Development] jkat797:
wasn't the 2.0 update supposed to come out today?

Sent from my Samsung Fascinate running Community Rom 1.3. Woof
[Fascinate Android Development] AlexDeGruven:
Today isn't over yet. You should say "Isn't it supposed to come out today?", instead.
[Fascinate Android Development] nitsuj17:
i believe i said 2.0 would go into testing wednesday/thursday....and it has :)

if all goes well in the next day/day and a half the xda release should take place then

for those that really want it, its in in #teamsbrisenmod irc...i ask that no links be posted on xda as we dont like tests generally in forums

(yes i know we did that with miuiwiz) :o
[Fascinate Android Development] bluevolume:
I have had the same experience. Running OTB 1.5, OC up to 1.2GHz, and -50mv across the board. I actually went a day and a half before needing a charge; literally amazing from where this phone started.

I was having problems with the camera, however, that seem to be resolved by going to PBNJ -50. So I didn't stay on the 1.5 for long, but it was great when i was ;)
[Fascinate Android Development] jkat797:
whats an irc? sorry for being a noob. hahaha

Sent from my Samsung Fascinate running Community Rom 1.3. Woof