yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] StDevious:
that's what I thought too, so checked in the required place but no go.

NM: Even though it showed white in the middle circle, guess it wasn't so. Clicked on a color near white, and saved, works now.

All those with problems with launcher pro, i moved to GO Launcher EX, much much smoother on homescreens and drawer. It works like iOSish hardware acceleration smoothness.
[Fascinate Android Development] nitsuj17:
if you are plugged in, remove the plug and reboot
[Fascinate Android Development] justinjbaron:
hi folks and amazing job on the rom.

this is more of a launcher2 question than anything, but is there any way to remove text below home screen shortcuts?

I can't seem to make a custom shortcut with this rom, where I could specity the name of the short cut to be just a space.

alternatively, any easy way to specify that the shortcut text should be black? this would have the same effect for me as I use a simple black background.

many thanks.
[Fascinate Android Development] hecantbreathe:
It's definitely a kernel issue for me.

Coming from com 1.2 using otb 1.3 no theme would get stuck on samsung logo. Wiping everything did not help.

What I did was wipe dalvik and cache from com1.2 with otb 1.3 flash com rom 1.3 then flash otb1.3 right after. Booted up fine and everything seems to be okay now.
[Fascinate Android Development] mbh87:
Was the kernel for me also, flashed nemisis2all's OTB 1.3 kernel and it booted right up.
[Fascinate Android Development] representingcochran:
I have had no issues at all coming from 1.2 with a tri write of partition and dalvik before flashing 1.3.

Sent from a KANGBANGED v1.3 fassy!
[Fascinate Android Development] nitsuj17:
for those having issues again...we need logcats....

just for the hell of it i just flashed rom with data/cache/davlik wipe on both cwr 2.5 and 3.0

and then did the same without wiping data in both and had no issues and nothing in the log looks funky either (to me at least)
[Fascinate Android Development] hecantbreathe:
Would love to provide you guys with a logcat but im on a mini vaction till Monday.

Hopefully people having the same issue can.
[Fascinate Android Development] chefthomas99:
Got any mirrors for 1.3? Nothing is working as far as downloading it.
[Fascinate Android Development] mbh87:
Didnt even think about grabbing one, if I remember later I will. Also it doesnt convert voodoo (obviously) since its not booting.

Use zshare, usually the fastest, for me anyways.
[Fascinate Android Development] djk21108:
Thanks nitsuj, much appreciated.
[Fascinate Android Development] BrwnSuperman:
http://dl.dropbox.com/u/11414960/community_rom_1.3_test2.zip

Here's another mirror for 1.3
[Fascinate Android Development] syaoran12:
to get rid of the shutdown sound just go into root explorer and goto system/media/audio/ui and rename shutdown.ogg to shutdown.old
[Fascinate Android Development] xgunther:
Can't get the time to show up on the status bar with TSM. Also, with the MIUI lock, I get a force close error when trying to unlock to messaging.
[Fascinate Android Development] djk21108:
I have the same issue with the clock. Any assistance would be much appreciated.
[Fascinate Android Development] nitsuj17:
the clock wont show or the clock color is black? unplug your phone if you are plugged in change clock color to #ffffffff or whatever thats not dark and reboot
[Fascinate Android Development] pdc21:
For first part see Nit's post above. For the MIUI lock, make sure you set the app to messaging in the lockscreen settings after you select MIUI lock. It works like the 4Tab where you can modify that application
[Fascinate Android Development] mike420:
i cant get the clock on the bar to show up i have made sure its visible and the color is not black i have made it several different colors and rebooted phone each time and no its not plugged up to a cable. pls help this is very annoying
[Fascinate Android Development] nitsuj17:
dont know what to tell ya works for me every time
[Fascinate Android Development] mike420:
well that sucks so either 1.2 and my phone rotates all the time no matter what or 1.3 and no clock ugh
[Fascinate Android Development] nitsuj17:
the clock should appear if you check on/off and then rotate the phone...if its the text color issue...change it once or twice and reboot with the phone unplugged
[Fascinate Android Development] tjthebest:
So with the alarm app when I try to set an alarm for the next day. And click on the "just once" button its supposed to set the alarm for the next day. Its actually setting it for the same day that it is. Has anyone else noticed this?
[Fascinate Android Development] kwinders:
It seems obvious for some, but for others having trouble, like me when they say to select or set a color to white, press the center dot in the color wheel to save color shown, then reboot. That is what did it for me.

Luvin the rom!!!!!

Sent from my Ultimate KangBang 1.2 Fascinate on XDA Premium

Much <3 to all the AWESOME developers
[Fascinate Android Development] deaffob:
MIUI lockscreen's SMS button doesn't work. It gives me a reboot.

When I try to set the custom app --> choose application --> nothing happens.
[Fascinate Android Development] the_passenger:
After you flashed v1.3 make sure you go get a cup of coffee or go do something else and comeback after 5-10 mins. It takse awhile to boot up the 1st time.

I did not wipe anything when I upgraded from 1.2 to 1.3 and everything seems to be working fine so far. Thanks guys.
[Fascinate Android Development] devlp1213:
if I just want the framework changes cann I just pull the folder and paste it over the current one and reboot? I personally mix and match themed apps and what not from several places so my phone is always my own and just don't want to go throw the hassle of pulling apps again

Blue WP7 2.2 Community, Fascinating 1.2GHz
[Fascinate Android Development] dtm_stretch:
Alright I have been trying to get you a logcat for the stuck at samsung issue. I am having an issue getting the logcat.

I run adb then run the logcat, adb states waiting for device, I connect the device reboot through CWM and let it run for a few minutes. Adb never changes from the waiting for device line. Then I check the folder and the .txt file just says * daemon not running. starting it now on port 5037 *

* daemon started successfully *

any suggestions?
[Fascinate Android Development] nitsuj17:
try it again....should work
[Fascinate Android Development] nitsuj17:
there were changes to the framework-res, service.jar, android.policy.jar, tsmparts.apk, psychdup.apk and...maybe framework-jar (i dont recall)...so its not just one thing that has to be changed
[Fascinate Android Development] djk21108:
Another issue that I've noticed is in recovery. Before I wipe dalvik, it says something about sd ext not found or something.

It then claims dalvik was successfully wiped.

Should I be concerned?
[Fascinate Android Development] pntballer505:
I know times_infinity released an updated CWM3.x yesterday

which fixes "SD-Ext error when wiping dalvik cache," so if you don't already have then yeah.... http://xdaforums.com/showthread.php?t=1046905
[Fascinate Android Development] nitsuj17:
this rom doesnt flash recovery

im assuming your talking about times_infinities cwr 3.0....we dont have sd-ext on our phones...so its just an error that he has (i believe) since commented out with jt's help

check his thread for updated recovery
[Fascinate Android Development] dtm_stretch:
I guess no need to link to drop box this is all I am getting in the logcat:

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

--------- beginning of /dev/log/main

I/ARMAssembler( 2709): generated scanline__00000077:03545404_00000000_00000000 [ 29 ipp] (43 ins) at [0x17cd58:0x17ce04] in 200166 ns

I/ARMAssembler( 2709): generated scanline__00000077:03545404_00000A08_00000000 [ 30 ipp] (52 ins) at [0x17e108:0x17e1d8] in 134541 ns
[Fascinate Android Development] mike420:
nitsuj17 your the best fixed my keyboard problem for yall that dont like the gingerbread keyboard and prefer the android keyboard from superclean or wherever just delete the gingerbread keyboard app through super manager or another file manager with root permissions and add in the latinME app and lib from the superclean rom and you get the awesomeness android keyboard
[Fascinate Android Development] nitsuj17:
just try adb logcat and it ll generate the log in your terminal then ctrl c to copy it
[Fascinate Android Development] mike420:
with this phone stock or even running superclean when listening to pandora through the speaker of the phone or perhaps any app i guess i could hit the power button+volume down and it would auto mute so volume turned all the way down very quickly instead of having to unlock phone then hit volume down like 10times. but now running this rom the phone wont do that anyone know a way to fix this
[Fascinate Android Development] dtm_stretch:
Ok so I am having some difficulty running the logcat. Here is what I am doing.

1. With adb up enter adb logcat

-adb then states waiting for device I plug in device (fascinate is currently at CWM)

2. This is when I get this --------- beginning of /dev/log/main

I/ARMAssembler( 2709): generated scanline__00000077:03545404_00000000_00000000 [ 29 ipp] (43 ins) at [0x17cd58:0x17ce04] in 200166 ns

I/ARMAssembler( 2709): generated scanline__00000077:03545404_00000A08_00000000 [ 30 ipp] (52 ins) at [0x17e108:0x17e1d8] in 134541 ns

3. Then I hit reboot from CWM. Then nothing happens. Adb next command line then pops up with no logcat.

The difficult part is I have no way to really boot the phone with out it hanging at the samsung screen or going into CWM.
[Fascinate Android Development] Pfredd:
Rebooting fixed the problem.

Thanks!

Sent from my Samsung Fascinate
[Fascinate Android Development] pntballer505:
So to get the time and other notification icons back from tsm, changing

the color and rebooting works?
[Fascinate Android Development] dtm_stretch:
I installed OTB TW v 1.3 and I was able to boot past the samsung logo finally. Sorry I couldn't generate the logcat for you. Maybe someone else can.
[Fascinate Android Development] djk21108:
Thanks for that nitsuj. You've been very helpful today.
[Fascinate Android Development] triddirt:
Here's what I've got

File: community_rom_1.3_test2.zip

MD5: d65058498f603a26e0ace716f75861e3

From Windows File Properties dialog

Size 170 MB (178,307,452 bytes)

Size on Disk 170 MB (178,311,168 bytes)
[Fascinate Android Development] rivaaaa253:
What bugs are still around in 1.3 ?
[Fascinate Android Development] StDevious:
For me, megaupload is the best. Yes you have to wait 45s with a free account, but you can download with a download manager.
[Fascinate Android Development] bwheelies:
I had to go back to ota ed01 then flashed without data wipe. Smooth like Keith Stone.
[Fascinate Android Development] jobu3434:
one thing i have found has to do with it freezing up when rebooting from power options. the shutdown animation goes through and then the screen goes blank but the buttons are still lit up and it just doesnt shut down. it seems to happen when it is plugged into the charger or just unplugged. anyone having this issue
[Fascinate Android Development] neyenlives:
Really? Because I modified Launcher2 that came with this rom and applied it no problem. I even merged it into the rom and repackaged it. I made the hotseat transparent and was thinking on going back and changing the colors of icons when attenuated. Not a big fan of the orange and green theme. But it wasn't a problem to modify it.
[Fascinate Android Development] MattRussNC:
Same here for confirmation D65058498F603A26E0ACE716F75861E3
[Fascinate Android Development] GrainOsand:
1.3 is installed and running smooth. Took me a minute to figure out status bar options but all in all AWSOME work.
[Fascinate Android Development] neyenlives:
Few questions before I flash this, coming from the earliest 1.3 build from like a week ago btw.

So I modified Launcher2 to my liking and plan to move it over to this one. So does this still use Launcher2?

Secondly I hate the Gingerbread keyboard and always delete it and replace with stock Android keyboard. What is the name of the new GB keyboard that was changed per the notes so I can be sure I delete the right one?
[Fascinate Android Development] nitsuj17:
you really dont understand what i was saying

you cant "modify" launcher 2 on the phone like you can with adw/lpp whatever..where u can change speed/look/ui/app drawer etc

you can edit the apk on your computer..yes..just like any other apk

and whether you like how this laucher2 looks is beside the point...its virtually identical to the official gb aosp laucher from the nexus...i didnt really do much to it other than play around with some files to make orientation correspond to various mods...if you wanted to edit for yourself and were able to do it..great
[Fascinate Android Development] nitsuj17:
you would really hate the nexus s then

but its been renamed to latinime.apk just like the stock keyboard package
[Fascinate Android Development] neyenlives:
I would never have thought about editing it on the phone lol. Neat idea but ill stick with doing it on the Pc. :-)
[Fascinate Android Development] Eris _2.1_2010:
Mines hangs when going into cwm and shutting down, but still shutsdown after awhile. And do wipe dalvik cache with 1.3?
[Fascinate Android Development] neyenlives:
Roger that, thanks. So I assume Launcher2 is still default?
[Fascinate Android Development] nitsuj17:
i have found cwr 3.0 is signficantly slower than 2.5 when booting/flashing...i reverted to 2.5...i dont endorse this for others...but its what works for me currently
[Fascinate Android Development] nitsuj17:
yes...however the launcher has been edited to work with orientation toggling from the power controls (thanks to latest tsm parts)

you may want to copy your edits over from the apk you previously edited
[Fascinate Android Development] syaoran12:
I am still using 2.5 as well. Doesn't the newest version run both scripting?
[Fascinate Android Development] 4GivenByChrist:
So far so good with 1.3

Only had one Launcher Pro FC on the first boot and none since. Browser seem snappier and battery seems better but will need a few days for true test.
[Fascinate Android Development] neyenlives:
Gotchya. Thanks.
[Fascinate Android Development] stereoblind:
1.3 is running well. The only issue I've had is that the browser doesn't let me save pictures from sites. I get an FC when I try.
[Fascinate Android Development] breaker911:
Is anyone having issues with opening up link in the browser? On the com rom 1 the browser worked fine but now it won't open links.
[Fascinate Android Development] nitsuj17:
2.5 supports amend and edify (although has some issues with certain edify scripts) 3.0+ only supports edify
[Fascinate Android Development] nitsuj17:
there is the previous (twbrowser) browser in post #2 under the op...just flash it
[Fascinate Android Development] hecantbreathe:
Can you change the color of the actual status bar itself like the change log states or just the text color?
[Fascinate Android Development] phatmhat:
i came from a working 1.2 with ed01 radio.

i wiped everything and then installed 1.3.

its been hanging for like 10 mins now on "samsung" boot now since restarting edify. whats up?
[Fascinate Android Development] deaffob:
Screen on whenever I press volume button is annoying. I stopped using widgetlocker because of this.
[Fascinate Android Development] Eris _2.1_2010:
Do we wipe dalvik with 1.3?
[Fascinate Android Development] nitsuj17:
no, just the text in said status bar...the status bar itself is an image
[Fascinate Android Development] nitsuj17:
couldnt hurt
[Fascinate Android Development] nitsuj17:
well both ed01 "roms" have this built in....atm you would have to use the stock verizon rom to avoid this
[Fascinate Android Development] dwight28:
Sigh. No clock in status bar. Already unticked the "hide clock" box under TSM parts. still no luck.
[Fascinate Android Development] nitsuj17:
rotate your phone after unchecking then rechecking it
[Fascinate Android Development] matthe4292:
Can anyone confirm if you can record audio as a mms attachment with 1.3? Thanks guys.
[Fascinate Android Development] breaker911:
I flashed the old browser and it didn't change anything. When I try to open a link it just says web page not available. When I write everything and install com rom 1 everything is ok. If I install any patches, 11 or 1.2 the browser is broken. It is almost like a different file that handles how the links are decoded gets changed when updating from version 1 and just by flagging the older browser that file does not get changed. Any ideas?
[Fascinate Android Development] Suicide Shift:
Set the settings you want then reboot. That worked for me. After that I did not need to reboot for setting changes to take effect.
[Fascinate Android Development] cckeeler:
Everything is working great so far! Thanks devs for another great release! I love the miui unlock screen!
[Fascinate Android Development] breaker911:
I had to gore into text color and change it to a different color to make out work. Then just changed it back to white.
[Fascinate Android Development] rivaaaa253:
Is the 3G issue resolved?? I really want to know all the difficultys with this ROM before flashing, I hate the hassle with bootloop and every other thing that could go wrong...
[Fascinate Android Development] nitsuj17:
there were no browsers in 1.1 and 1.2 there were just patches that didnt affect that particular apk
[Fascinate Android Development] nitsuj17:
the rom has no 3g issue...3g issues are spread amongst anyone and everyone
[Fascinate Android Development] breaker911:
Thats why it makes me think that there is another file that gets altered in patches 1.1 and 1.2 that affects how the links are decoded. Could it have anything to do with framework files? Pure speculation.
[Fascinate Android Development] BrwnSuperman:
Did you reboot afterwards?
[Fascinate Android Development] tripacer99:
Flashed 1.3 as I normally do, but it wouldn't boot. Couldn't get past the samsung logo. Went into recovery and tried flashing again (wiping cache/dalvik 3x, obviously), but no dice. Had to reflash 1.2. And my clock is now gone for some reason...
[Fascinate Android Development] nitsuj17:
adb logcat or nothing can be gained from bootlooping
[Fascinate Android Development] tripacer99:
Will do. Busy at work atm but i'll post one up later tonight.
[Fascinate Android Development] mrmidnight:
3g issue isn't with rom. It's vzw and to me they didn't want to do a data reset
[Fascinate Android Development] piiman:
I had same issue with both 1.2 and 1.3 it seems my phone doesn't like the OTB kernel and I have to flash another kernel to get it to boot. So give that a try. Other than that its works great.
[Fascinate Android Development] piiman:
Hell that's half the fun! :D

And isn't the 3g issue a verizon 2.2 thing not the ROMS?
[Fascinate Android Development] gunnermike:
If anyone is having issues getting past samsung logo, flash a different kernel. My guess is its a voltage control issue, but thats purely a guess. I do know flashing a new kernel will fix it.
[Fascinate Android Development] Dobloro:
Can I go directly from 1.0 to 1.3?
[Fascinate Android Development] gunnermike:
Um.... Try it and tell us :)
[Fascinate Android Development] Dobloro:
Well that doesn't sound very promising XD
[Fascinate Android Development] DirgeExtinction:
I can't save images from the browser. Everytime I try, I get a FC.
[Fascinate Android Development] Eris _2.1_2010:
do we wipe data and all that jazz with 1.3
[Fascinate Android Development] edgeupgx:
I can 2nd the issue with no clock in status bar unticked the hide option rebooted several times still no dice
[Fascinate Android Development] sneakysolidbake:
Coming from 1.2 all I did was a dalvik wipe and I was all set. Your mileage may vary.

Try changing the text color and reboot. If theres an open black space where the time usually is, then its being displayed in black.
[Fascinate Android Development] chopper the dog:
Did you change the text in "text Color" option in tsmparts? Change to a different color and tap center of color selector and reboot (this has been beaten to death in this thread). All other settings do not require rebooting.

good day.
[Fascinate Android Development] gunnermike:
Lol. How do you think we stuuf like that, we try it, and then we know.
[Fascinate Android Development] 4GivenByChrist:
Same here... Though personally I never tried with the old browser so I can't compare.
[Fascinate Android Development] gubiguy:
So... for anyone who's wondering what happens if you DON'T clear the dalvik cache or do anything fancy, and just patch it... I HAVE NO CLOCK... lol

EDIT: wiped dalvik cache, re-applied patch: still no clock. help?
[Fascinate Android Development] tk1o48:
Came from 1.0 with only a dav and cache wipe. No issues whatsoever. -100 on 100, 200,400,600. -75 on 800, 900. -50 on 1000 & 1200
[Fascinate Android Development] chopper the dog:
Did you change the text color in tsm parts for the status bar? Hint after choosing color tap center of color chooser and reboot.

good day.
[Fascinate Android Development] Pfredd:
Try changing the text color to something else, then change back to white, then reboot.

That fixed it for me.
[Fascinate Android Development] gubiguy:
Rebooting now... I will update with an edit..

EDIT: It worked! "Brilliant, bloody brilliant!" P.S. This ROM has now attained awesome status.
[Fascinate Android Development] minho422:
For those of you who doesn't have clock showing up, or have two charging icons...uncheck all TSM status bar options, plug out the cable and reboot, then plug in the cable.
[Fascinate Android Development] chopper the dog:
The only setting in TSMparts that requires a reboot is the text color. Depending upon the refresh time determined by the frameworks of all other taskbar items is the time it will take for them to appear or not be shown. It has also been mentioned that switching to landscape and back will trigger a redraw of taskbar items.

good day.
[Fascinate Android Development] shorttripp86:
Anyone getting FC's when trying to use the "Bookmarks" widget in LPP?
[Fascinate Android Development] upsidedownaaron:
had to odin back to dlo9 to stop the boot loop. started with permasung too.
[Fascinate Android Development] bratliff:
Flashed this today, it's running great.. thank you to all the devs
[Fascinate Android Development] rawrwar:
came from 1.2 (wiped cache and dalvik)

worked successfully

thanks!
[Fascinate Android Development] skynet11:
Hey chopper, maybe you should copy your reply text and just keep pasting it for every user who can't seem to read the last 2 pages or so and makes another post saying "I have no clock! Please help!"

As for you users who do take the time to read the last couple of pages, there are 2 options short of flashing a theme to make the status bar clock visible:

Option 1 - toggle screen rotation, turn phone to landscape and back.

Option 2 - change text color in TSM Parts (remember to tap the center circle after selecting your color) and reboot.

Another Fascinating post by my XDA app...
[Fascinate Android Development] minho422:
Ah it must be different from me then...my fix was to disable al lthe settings, and did not change the color setting.

However I'm still seeing two charging icons if I boot while it's plugged in. It disappears if I plug out and in again.
[Fascinate Android Development] shorttripp86:
Ahh, I see why I was getting FC's with the LPP Bookmarks widget. Modified CM6 Browser was included in 1.3.

Okay well, there's my bugfix submission then :)
[Fascinate Android Development] Wolfkmann:
Was running ComRom 1.2 with ED01.

Downloaded the file community_rom_1.3test2.zip (170mb)

Every time I try flashing it I get the error

"E:can't open /sdcard/community_rom_1.3test2.zip (bad)

Installation aborted.

I was on voodoo cwm 2.5.x updated to 3.0 via the link found a few pages back, still doesn't work.

Tried wiping davlick, still get the abort message.

Any suggestions?