Database Users

New Sprint Rom Is Here ???

New sprint rom?? http://forum.ppcgeeks.com/showthread.php?t=10293&page=3
http://download.america.htc.com/RUU_...PL106_Ship.exe

It's been confirmed. That is the new official ROM for Sprint. It fixes the Bluetooth issues among others. No Rev. A or GPS of course, but that was expected.

question is, is this really "better" than the alltel rom that has been available for a long time already over at PPCgeeks...
The alltel rom fixed the BT and alarm problem as well. I'm excited to see that Sprint finally caught up, but I'm wondering if this is better than the setup I currently have.

Well I for one am happy and upset.. I would like to see REV A , as I need the faster upload speeds for sending big files from my 4gb micro sd.

I havent tried the Alltel rom, but the new sprint rom fixes the keyboard lag + wm6 responsiveness problems.

After reading all of the threads over at PPCGeeks, it seems like there are some mixed results on the ROM (to be expected I guess, you can't appease everyone.)
-Most are reporting the BT fix worked correctly.
-I didn't see anyone say that the Alarm fix didn't work
-People are reporting that the OS seems a little faster and better at managing memory, such as reclaiming more when you close an app, etc.
-The radio version on the Sprint ROM is 1.47, compared to 1.40 of the Alltel, some were reporting better reception between this one and the stock rom (1.32 I believe)
-the most widely spread issue I saw was that some users were having issues with their dpad not working. At first, someone pinned it down to sprinttv, as it worked after they removed it, but then others said that the problem returned.
-YMMV, but some reported that when they skipped the sprint customization of the rom (when it starts initially, after the 3 second delay where you can soft reset) it caused issues on their phone. One person said that a workaround for this was to let it install EVERYTHING initially, and then do a hard reset and skip the customization process. It makes sense that if it were something with the EXTRom that it might put something in there that you needed, but again, not sure on this one.
-I can't believe how many people were stuck on the idea that they would be able to use Sprite Backup or SPB Backup to restore all of their stuff. Let me say this again, because I don't think it can be said enough. Unless you are just restoring folders such as your documents or something non-system related, you CANNOT use these programs. You WILL overwrite the new files with the old ones, causing a boatload of issues, if it even works at all. So don't do it, or you will cause yourself some headaches. Activesync remembers the apps you have installed, so just sync afterwards and click the boxes. For your other stuff such as contacts, back those up with a contact backup app or sync with outlook if you've got it.
just my two cents.

kmartburrito said:
After reading all of the threads over at PPCGeeks, it seems like there are some mixed results on the ROM (to be expected I guess, you can't appease everyone.)
-Most are reporting the BT fix worked correctly.
-I didn't see anyone say that the Alarm fix didn't work
-People are reporting that the OS seems a little faster and better at managing memory, such as reclaiming more when you close an app, etc.
-The radio version on the Sprint ROM is 1.47, compared to 1.40 of the Alltel, some were reporting better reception between this one and the stock rom (1.32 I believe)
-the most widely spread issue I saw was that some users were having issues with their dpad not working. At first, someone pinned it down to sprinttv, as it worked after they removed it, but then others said that the problem returned.
-YMMV, but some reported that when they skipped the sprint customization of the rom (when it starts initially, after the 3 second delay where you can soft reset) it caused issues on their phone. One person said that a workaround for this was to let it install EVERYTHING initially, and then do a hard reset and skip the customization process. It makes sense that if it were something with the EXTRom that it might put something in there that you needed, but again, not sure on this one.
-I can't believe how many people were stuck on the idea that they would be able to use Sprite Backup or SPB Backup to restore all of their stuff. Let me say this again, because I don't think it can be said enough. Unless you are just restoring folders such as your documents or something non-system related, you CANNOT use these programs. You WILL overwrite the new files with the old ones, causing a boatload of issues, if it even works at all. So don't do it, or you will cause yourself some headaches. Activesync remembers the apps you have installed, so just sync afterwards and click the boxes. For your other stuff such as contacts, back those up with a contact backup app or sync with outlook if you've got it.
just my two cents.
Click to expand...
Click to collapse
i took the plunge yesterday, i skipped out on all the sprint customization and everything turned out ok....haven't tested bluetooth yet but everything you said seems to be on point...

kmartburrito said:
-YMMV, but some reported that when they skipped the sprint customization of the rom (when it starts initially, after the 3 second delay where you can soft reset) it caused issues on their phone. One person said that a workaround for this was to let it install EVERYTHING initially, and then do a hard reset and skip the customization process. It makes sense that if it were something with the EXTRom that it might put something in there that you needed, but again, not sure on this one.
Click to expand...
Click to collapse
Just to clarify this is part. A hard reset will completely erase any carrier customizations there is absolutely no reason for installing extrom, hard resetting then skipping. Just start out with the hard reset, skip customizations and you'll be good to go.
Although there are still the other bugs with the update =)

Just installed it a while ago, skipped the sprint customizations, everything seems to be running good and actually noticeably quicker than before. New startup screen is cool too, no problems thus far =)

do yourself a favor and wait for the next rom. If you didn't already experiance it, your device will lock up and go to sleep requiring a soft reset...very unusable. and BT will turn off after a few minutes randomly.
load the colonel's rom on, it's much better imho

Seems to only happen to some people though. I have had my phone on pretty much straight since the rom update.

there seems to be a major bluetooth issue where the BT just shuts off periodically.. Not sure how,but they found a way to make bluetooth even worse!
I can't carry on a conversation without BT shutting off on me.. (or use the gps without it shutting off/etc..)
-mark

I haven't updated yet, plan to over the weekend, but I would suggest anyone having problems to stop and consider their setup first...
1. What programs are installed that could cause problems?
2. What registry hacks have been done that may cause problems?
3. What configuration settings might need reset that may cause problems?
For example, after a hard reset, Enhanced Network over USB is enabled by default, and this often causes Active Sync to have issues. Likewise, power management tweaks will have reverted to defaults and you may like a more finely tuned setup.
As for memory leaks being better/worse, you may have programs installed that are out of date/buggy.
I realize it's easier to jump on the "this sucks" bandwagon, but it doesn't help you or other users with legitimate problems when no consideration is given to what is causing a given problem.
These situations are precisely why the instructions tell you that EVERYTHING will be erased. This is a good thing since it forces you to clean house, but it also means you have to pay attention to those things you often neglect or may have changed ages ago and forgotten.
Finally, if all else fails, try the ROM update again. Sometimes things go wrong.
Sorry if this seems like a rant, I just want people having issues to place blame where it truly belongs. After considering these matters, if you still have problems, definitely let HTC and the rest of us know.
Best Regards,
Aaron

GoodThings2Life said:
I haven't updated yet, plan to over the weekend, but I would suggest anyone having problems to stop and consider their setup first...
1. What programs are installed that could cause problems?
2. What registry hacks have been done that may cause problems?
3. What configuration settings might need reset that may cause problems?
For example, after a hard reset, Enhanced Network over USB is enabled by default, and this often causes Active Sync to have issues. Likewise, power management tweaks will have reverted to defaults and you may like a more finely tuned setup.
As for memory leaks being better/worse, you may have programs installed that are out of date/buggy.
I realize it's easier to jump on the "this sucks" bandwagon, but it doesn't help you or other users with legitimate problems when no consideration is given to what is causing a given problem.
These situations are precisely why the instructions tell you that EVERYTHING will be erased. This is a good thing since it forces you to clean house, but it also means you have to pay attention to those things you often neglect or may have changed ages ago and forgotten.
Finally, if all else fails, try the ROM update again. Sometimes things go wrong.
Sorry if this seems like a rant, I just want people having issues to place blame where it truly belongs. After considering these matters, if you still have problems, definitely let HTC and the rest of us know.
Best Regards,
Aaron
Click to expand...
Click to collapse
My experience is as simple and "vanilla" as it gets:
-Loaded new ROM
-Hard reset
-Stopped customizations
-Installed NO apps, did not turn on BT, made no calls, did nothing else
-3 DSODs in 4 hours
-Did a second flash (from a second computer with a freshly downloaded ROM)
-Hard reset
-Allowed customizations to run
-Again no apps, BT or calls
-DSOD within an hour

wsparvis said:
My experience is as simple and "vanilla" as it gets:
-Loaded new ROM
-Hard reset
-Stopped customizations
-Installed NO apps, did not turn on BT, made no calls, did nothing else
-3 DSODs in 4 hours
-Did a second flash (from a second computer with a freshly downloaded ROM)
-Hard reset
-Allowed customizations to run
-Again no apps, BT or calls
-DSOD within an hour
Click to expand...
Click to collapse
Sounds atypical to me, given that most users are updating without issue and experiencing better results. I have no reason to doubt your experience though... it sounds like you have faulty hardware, but here's a download link to the previous firmware if you're interested in trying it out first:
http://www.htcamerica.net/support/mogul/software-downloads.html

No, "most" users are not experiencing better results. I've been using this ROM with poor results, as have many others. Read this thread for many sad tales of woe:
http://forum.ppcgeeks.com/showthread.php?t=10302
Basically, the new ROM does fix a bunch of things, but breaks others, so I would not recommend installing this ROM.
1) Locks up when changing from Sprint to roaming. You can test this by manually switching from Sprint to roaming and back a few times, you WILL get a phone lockup.
2) BT turns off randomly for many users.
3) Turn on BT, let unit sit for a few minutes until it goes to sleep, turn unit back on, dpad no longer works. I have seen this myself many times.
Don't install this update --- use the Alltel ROM or wait for another update.

GoodThings2Life said:
Sounds atypical to me, given that most users are updating without issue and experiencing better results. I have no reason to doubt your experience though... it sounds like you have faulty hardware, but here's a download link to the previous firmware if you're interested in trying it out first:
http://www.htcamerica.net/support/mogul/software-downloads.html
Click to expand...
Click to collapse
1) You're incorrect in stating that most users have no problems, etc. Some do, some don't. Read the posts at ppcgeeks, pdaphonehome, BAW, hofo. I am not at all alone in having problems.
2) I downgraded 2 days ago, and my Mogul runs fine again - just exactly like it did for the 1st 3 months I had it. It's not my hardware! It's a bad ROM release.

Not everyone uses the phone in the same way at all. So of course some people will not see the same problems that others do.

If you never use Bluetooth and never roam, then this ROM will work for you. Otherwise, it will cause problems. For me, Bluetooth works much better in 2.09, and I rarely if ever see lockups as I have with 2.16. So, I'm going with 2.09 for now. The alarm problem IS fixed in 2.16 but I never use alarms on my phone so it's not an issue for me. Freezes when roaming ARE a problem.

cbunting said:
do yourself a favor and wait for the next rom. If you didn't already experiance it, your device will lock up and go to sleep requiring a soft reset...very unusable. and BT will turn off after a few minutes randomly.
load the colonel's rom on, it's much better imho
Click to expand...
Click to collapse
is colonels rom built on the alltel core rom? if so it may be our best bet as of now.

Why does my phone shutoff?

Rooted my Hero and it doesn't matter which custom Rom I've tried(Fresh, Damage, others) my phone will shut off most of the time it goes into sleep. I don't know its off until I go to wake it up by hitting the end button. When I restore back to the stock Rom(still rooted) it works fine. I do a wipe and a Dalvick wipe prior to flashing. I'd like to get this figured out so I can use one of the nice Roms. Thanks.

If you're running A2SD and you have the Dalvisk on a slow sd card you phone can reboot or shut off. Try moving it off of the SD

patkin said:
Rooted my Hero and it doesn't matter which custom Rom I've tried(Fresh, Damage, others) my phone will shut off most of the time it goes into sleep. I don't know its off until I go to wake it up by hitting the end button. When I restore back to the stock Rom(still rooted) it works fine. I do a wipe and a Dalvick wipe prior to flashing. I'd like to get this figured out so I can use one of the nice Roms. Thanks.
Click to expand...
Click to collapse
WOW! You are the first person that has had the same problem I have...I was never able to resolve the issue. I used that bastard 2.1 test leak.......read my posts and what I went through.
http://forum.xda-developers.com/showthread.php?p=6268366#post6268366
My phone works fine now with gumbo 1.5, but I cant use any 2.1 roms or the problem comes back......

kyouko said:
If you're running A2SD and you have the Dalvisk on a slow sd card you phone can reboot or shut off. Try moving it off of the SD
Click to expand...
Click to collapse
I am not positive what A2SD is. I have a new 8MB SD card that came today. If I pop that in what will happen. Should it be partitioned? Thanks.

Chaid said:
WOW! You are the first person that has had the same problem I have...I was never able to resolve the issue. I used that bastard 2.1 test leak.......read my posts and what I went through.
http://forum.xda-developers.com/showthread.php?p=6268366#post6268366
My phone works fine now with gumbo 1.5, but I cant use any 2.1 roms or the problem comes back......
Click to expand...
Click to collapse
Thank God I thought I was the only one. I searched but didn't see your thread. Weird problem.

Same problem here too since the new leaked 2.1 test ruu from damaged. The only 2.1 Rom that works for my needs without rebooting every 3rd or 4th time I wake it using the end call/power button is Damagedtrev 2.01, the updated 2.05 Rom in his thread just makes my phone reboot as described above. I don't have a link to his thread, but it would be interesting to see if it worked on your phone too. Other's have claimed a battery shorting might be causing this issue, but I'm not buying that. I've looked at /proc/lastkmsg for clues, but nothing obvious there. I hope the official Sprint update doesn't have this bug or sprint will be giving me a new phone. /end rant

I can't seem to find Damagedtrev 2.01
So I can't test it.

Here's the link to the thread.
I cannot post links, because of some restrictions,but here is the last part of the url.
forum.xda-developers.com/showthread.php?t=653622
here's the link for the full rom
Oops cannot post link to rom on 4shared, look in the bottom of the first post in the thread for a link to the full rom of DamagedTrev_v201
Please let us know if the rebooting stops for you. Maybe one of the devs could find where the problem is. Pretty please!! I could post any info needed.

Ok, downloading......stay tuned.
I really hope this 2.1 ROM works.....I'm kinda sick of 1.5.
Edit:
P.S. I'm reading that there is a battery issue....do you have that?

kyouko said:
If you're running A2SD and you have the Dalvisk on a slow sd card you phone can reboot or shut off. Try moving it off of the SD
Click to expand...
Click to collapse
Hey good news. I put the new SD card in after backing up the other one, partitioned it and copied the files and folders back on then flashed ALOYSIUS and so far so good. I have woken it up about 10 times in a row. Looking good.
I had tried that perticular Rom before with no success.

Interesting.....I'm using the 2 gig sd card that came with the phone....I wonder if that is my problem?

Well it started again. This was right after setting my Gmail and POP3 mail accounts. It shut off on the first sleep after this. Hmmmmm.
I'm re-flashing now and not setting up the mail accounts. Will report back later.

Waldo447
Please let us know if the rebooting stops for you. Maybe one of the devs could find where the problem is. Pretty please!! I could post any info needed.
Well, my friend. You were correct! full rom of DamagedTrev_v201 works on our phones for some strange reason. And updating his ROM caused the re-booting to start again. So whatever was changed from 2.0.1 to 2.0.5 is causing our particular problem. I'm not a dev by any means and don't know much about his stuff, but this is encouraging. Perhaps someone can figure out what it is?
I did notice that ALL the other 2.1 ROM's I have used that cause my phone to re-boot from sleep mode, is that when I hit the menu or power button to turn it on, the lights turn on, then reboot phone. With DamagedTrev_v201 that doesn't happen. The screen just pops up to unlock it.....don't know if that helps, it's just something I noticed.
Heres to crossing our fingers that someone can fix this!
P.S. I wiped and went back to Gumbo 1.5c as that 2.1 ROM was way to slow for me and I couldn't get bluetooth to work and audio would cut in and out.

reboot
i would like to know if its a full reboot or just a soft like where it hes to the sprint or boot animation

kwajr said:
i would like to know if its a full reboot or just a soft like where it hes to the sprint or boot animation
Click to expand...
Click to collapse
It's a full reboot. The phone actually turns off when it goes into sleep. You don't know it's off until you hit the button to wake it up and the phone boots up.
Now for the good news. After re-flashing and not setting up the email accounts it was still shutting downconfused so I started looking elsewhere so I opened up what I thought was a likely culprit in Autokiller and none of the presets where selected so I picked Moderate and haven't had a shutdown since which has been over an hour. Fingers are crossed. I'll report back later.

That's it I've wasted way too much time on this. Phone works great on the stock ROM. They must have planted some devious anti-flash widget in this phone. I'll leave it rooted for now.

patkin, dude, I felt the same...I gave up on 2.1.
download, wipe then flash Gumbo-1.5c-BARE-signed.zip after it reboots, download and flash Gumbo-Sense-signed.zip.
You flash Gumbo-Sense-signed.zip over the Gumbo-1.5. No need to wipe or anything, it just adds to the ROM. Fast as hell and works PERFECT.
http://www.4shared.com/file/217809392/5fcf1f5d/Gumbo-15c-BARE-signed.html
http://www.4shared.com/file/217811195/3afb5fcf/Gumbo-Sense-signed.html
Give it a shot....I think you will like it......let me know =)
Gumbo thred so you can read up if you like. http://forum.xda-developers.com/showthread.php?t=630221

Chaid said:
Waldo447
Please let us know if the rebooting stops for you. Maybe one of the devs could find where the problem is. Pretty please!! I could post any info needed.
Well, my friend. You were correct! full rom of DamagedTrev_v201 works on our phones for some strange reason. And updating his ROM caused the re-booting to start again. So whatever was changed from 2.0.1 to 2.0.5 is causing our particular problem. I'm not a dev by any means and don't know much about his stuff, but this is encouraging. Perhaps someone can figure out what it is?
I did notice that ALL the other 2.1 ROM's I have used that cause my phone to re-boot from sleep mode, is that when I hit the menu or power button to turn it on, the lights turn on, then reboot phone. With DamagedTrev_v201 that doesn't happen. The screen just pops up to unlock it.....don't know if that helps, it's just something I noticed.
Heres to crossing our fingers that someone can fix this!
P.S. I wiped and went back to Gumbo 1.5c as that 2.1 ROM was way to slow for me and I couldn't get bluetooth to work and audio would cut in and out.
Click to expand...
Click to collapse
Glad to see your rebooting issue was fixed with this rom even though you went back to gumbo 1.5. In my mind, this just confirms that it is not a battery issue. I never use bluetooth and have never experienced any audio loss with this rom, but apparently even people on the same hardware and firmware versions have different problems.
kwajr said:
i would like to know if its a full reboot or just a soft like where it hes to the sprint or boot animation
Click to expand...
Click to collapse
Full Reboot here too.
patkin said:
That's it I've wasted way too much time on this. Phone works great on the stock ROM. They must have planted some devious anti-flash widget in this phone. I'll leave it rooted for now.
Click to expand...
Click to collapse
Yeah, got my phone beginning of march 2010 and I also think there is something in the 2.1 test ruu or hardware that is keeping the phone from functioning properly with an altered 2.1 rom.

Just wanted to let people know what happened to resolve this. I went back to 1.5 then when 2.1 official came out last week I said what the heck if I can't enjoy a rooted custom 2.1 I'll try the official and guess what. Same problem as the other 2.1's.........phone shuts off randomly! Except this time they are replacing it with a new phone. Yeaaah! I'm probably going Evo now though since I found out I can get a new phone. Anyone need a new Hero?

I'm having the same problem.. One question. Does DarchDroid automatically move dalvik-cache to the sd

Screen Locked on Froyo & Desire after Timeout help

I just need to start off by saying you guys are awesome! I'm actually enjoying my phone for the first time since I got it the first week it came out. Keep up the awesome work!
Main concern is that when the screen times out in either my Froyo or Eclair Roms, I cannot get it to wake up. Anything I press will initiate the back-light and nothing more. I've pressed several times using each button and nada, I have to pull the battery. All issues occurred prior to installing the latest zImage, running the task29 and formatting my sdcard.
Additionally, I've noticed the Camera Flash doesn't work in either Rom and no picture is shown in the Froyo build. Other then that, I have found no issues. Mild delays but that's probably attributed to the Class 2 card and early Android builds. No real concern here. None of these issues occur in the Windows Mobile environment.
So I pretty much put everything I am using in my signature. I have the Froyo build in \Android and the Desire files are all in the root of the SD. I have task 29 the system and used Panasonic's SDFormatter v2.0 to wipe the SD. I have nothing installed but exactly what I have listed in the signature. I haven't even copied over the Transformers movies. My issues are consistent even if I haven't set up any account information or anything. I'm not complaining and I've read some others express similar issues but haven't figured out an answer. So that's about it. If I find any answers to my few issues, I'll post here. And again, I'm freakin excited for the development of the Android Roms and NRG's WinMo Rom has never let me down. I just prefer Android but like having both options. Thanks for all the help and if there's nothing that can be done right now, well again, I'm not complaining... Stay at it Chefs, you guys are awesome!

OK I didn't think to try a different zimage but I used the July23rd one and my screen timeout issue is fixed. Now to resolve the no camera issue in my Froyo Rom and I'm set. The other issues are fairly minor and will likely get worked out in time.

Does your zImage charge the phone, too? I'm facing the same problem, sometimes the screen doesn't come on and at other times it's unresponsive even if it does.

Look around, the newest zimage causes this for some ppl. Chill for a new zimage release.

[Q] Screen Issue - Bright negative on wakeup.

Just done a search about this prob and there is a couple of similar threads but they are not really same issue.
This has happened 3 times now with different roms over past month and not sure what is causing it. Phones screen seems to go bright white on wakeup, looks like a negative.
Is there any experts out there who could shed some light on it. Does it sound like a slow hardware failure or is it more likely a software issue. As I say its only happened a few times and a reboot brings it back to normal but it just concerning
Has anybody else had this same issue on wakeup before?

My first reply post here...
I have the same issue...reboot will recover it...but ones it recovered after normal stand-by upon wake up...I assume it is just some incompatibility of Android with HD2 graphic processor, minor issue.
Current ROM
Omega WM6.5.x v14
Current Android Build
NexusHD2 v1.8

I used to have the same problem and put it down to an incompatibility. Since moving to a Nand ROM it seems to have gone away.

TheATHEiST said:
Phones screen seems to go bright white on wakeup, looks like a negative.
Has anybody else had this same issue on wakeup before?
Click to expand...
Click to collapse
I used to have this issue, but only on SD builds, and very, VERY rarely. From about 5-6 months of SD Android, I probably had it about 4 or 5 times.
I agree with madmillsy that I've not seen it on a NAND build, but I don't think I'd seen it on recent SD builds either.
Is it an SD build you're running, and if so, how old is it?
Edit: Forget that last question - just saw your current ROM in your sig.

I saw this effect twice, never in WM, only in Android. First time with SD build, but second time, last week with gauner's HD NAND build.
As it was already described, there is probably some incompatibility regarding graphic, when waking up from idle mode. I do not think it is related to SD builds only, they handle graphic same way, with same kernels.
By the way in gauner's build I noticed also problem with activating sound from idle mode time to time. So maybe it is not directly graphic driver part, could be somewhere else and this is just consequence.
At the end, it is rare and minor issue, the only discomfort is because of restarting the phone.

Had a few times this issue, and didnt need to reboot to make it worn off. Just put it in a colder environment, and it will go away after 10 minutes orso. So I honestly thing is has todo with the temp of he device. Mostly it came up after a long phonecall I had, which maked the phone a little 'hotter'.
Just a speculation though, didnt have this issue since I use NAND. But I guess it can come-up randomly, but I don't worry it to be honest.

Its happened twice on SD builds and once on NAND build.
I was concerned that I was starting to get a hardware fault but im relieved to hear that others have had it so it must be simply a soft bug.
It rare anyway so no big deal.
Thnx for replies guys.

happened to me once with NAND - sorted with a reset. Scared the hell outa me

F-bone said:
happened to me once with NAND - sorted with a reset. Scared the hell outa me
Click to expand...
Click to collapse
same here, including the scared bit.

sodeknetters said:
same here, including the scared bit.
Click to expand...
Click to collapse
the weird thing is that since I posted in this thread it happened to me twice today!...total 3 times so far... Im getting worried...

Never happened to me with an SD build (after 3 months of use) but happened twice to me with DFT's NAND, reboot fixed it as stated and yes...it scared the **** out of me the first time lol

For anyone that might be debugging the issue - it might be connected with calls.
I receive a call. After I'm done with talking, i turn on phone and it's on negative. Alright, i restart it. After restart it works fine, until i call somebody. After call, again negative screen. It happened two times in a row.
Also i don't really need solution to this problem. Only some kind of workaround that will allow us to fix problem manually without restarting phone. Maybe a script that will reset display driver or something?

[Q] long time watcher and rom user. first time poster.

Hello my name is Xan Steel. I've been trying out roms on this forum for my Epic 4G. However I've run across a lot of bugs in this rom "ACS ICS V6". I would love to be able to post them in the development thread pertaining to the rom, but since I'm under the 10 post limit to post in a dev thread. I would like to ask how I go about doing this the correct way without breaking forum rules.
Thanks in advanced
Xan Steel

Tell us what your problems are here.

1st you have to have 10 post. Go to other threads and comment on stuff like the off topic forum. Then you should be able to post on dev threads. Or you can pm them and let them know.
Sent from my SPH-D700 using xda premium

Well as Neckberg has said to post my issues here (Thanks) I shall.
[ROM] ACS ICS V6.
Where to began.
I came from ACS SyndicateFrozen 1.1.1 I could never get 1.2 to run. And this ROM was based on GB. Really wanted to see what GB was like. SO after installing the ROM. Everything started out normal (no issues at that point). It was sluggish which made me wonder if Carrier I.Q. was still in the ROM. It wasn't listed that it was removed.
SO I started trying things out. Everything was going good until I turned on the Wireless WiFi Tether. It crashed outright. Tried again, and crashed. It would open to a black screen and then crash. So I did some digging, and apparently this is a known issue. So I got a different one from the market that worked (Open Garden WiFi Tether).
I installed Opera. I like Opera for it's desktop mode that actually works over Dolphins. I would type in a address, and hit go, and it would act like its going, and then stop and remove what I had typed. Tried again, and it would load a blank page. Tried a third time, and got the HTML header to load the page in a text format. Uninstalled and reinstalled same thing happen. So I left it alone, and about 3 hours later it had uninstalled itself/completely missing on the phone and market stated it wasn't installed. Rebooted phone, still gone. Not idea where it went. After reinstalling it again. it would do the same thing.
So I flashed and wiped X3. And reloaded the ROM. Thinking I have a bad load.
reinstalled all my apps and even though Opera is still doing it's thing I mentioned earlier, it hasn't uninstalled itself... yet.
Now after the reload of the ROM. Last night I lost cell service (couldn't make calls) but I had data. Which was odd to me. Rebooted the phone, and same thing. Had data but not cell service. After about and hour or so, I have cell and data back together. Maybe it was someone working on the tower in the area at 11pm, or maybe the ROM decided it would be funny.
Another thing I noticed. If you hit the menu button to pull menus in apps and on the home screens. They are white on black. White text and image, on a black background. Now if you go into any sub-menu from the main menu, its black on black. You can't read anything unless your lucky to have a bright white page behind it, so that it can try to bleed through some of the transparency.
The battery icon when charging in portrait goes from normal to skinny (blinking), while in landscape mode it goes from normal to fat (blinking).
Also two music apps is not really needed. One is fine. Trimming down on unneeded apps would help save on space. Also remove Carrier I.Q. if it hasn't been yet.
Adding that super brightness, is actually bad. Not thinking about it, it's actually crashed the video HW of the phone. On a plain white screen at max brightness, it starts to artifact, and if what ever your trying to do doesn't complete. The video HW crashes, and you get a pretty rainbow on the screen until you pull the battery. Basically acts like a dying or dead video card in a PC. Also it can (and has happened to me) cause screen burn in. If you want a image of it let me know and I'll post one.
Also Rom Manager does not recognize any ClockWorkMod Recovery, if you manually install the recovery yourself.
If I find anything else buggy I'll post and update here.
Thanks
Xan Steel
Phone: Epic 4G
ROM: ACS ICS V6
Recovery CWM 3.1.0.1 purple

Note, I haven't tried this rom myself.
No, carrierIQ is not removed on this rom, nor has it been removed on any GB rom that I know of. Still, removed or not, it won't make any difference in the performance of the device.
Any apps that you fine are useless can easily be uninstalled, even if they are installed system/app folder. Rom chefs correct attitude about roms is that they build for themselves first. I personally have 3 music players installed.
We don't have official Rom Manager support so that will be an issue on pretty much all non AOSP roms for the epic.
Your lack of service issue it probably a carrier issue and not a rom issue.

shane6374 said:
Note, I haven't tried this rom myself.
No, carrierIQ is not removed on this rom, nor has it been removed on any GB rom that I know of. Still, removed or not, it won't make any difference in the performance of the device.
Click to expand...
Click to collapse
Ah makes sense. It's relatively new, and most likely not been worked on yet.
Any apps that you fine are useless can easily be uninstalled, even if they are installed system/app folder.
Click to expand...
Click to collapse
Ah, then I should be able to remove them myself fairly easily.
We don't have official Rom Manager support so that will be an issue on pretty much all non AOSP roms for the epic.
Click to expand...
Click to collapse
Do you know if that is something being worked on?
Your lack of service issue it probably a carrier issue and not a rom issue.
Click to expand...
Click to collapse
It's a good possibility since it only happened the one time, but since it is a beta, and I'm using it for the first time. I felt it needed to be brought up just in case it wasn't. Heh beta tested a lot of new software, and got into the habit of reporting everything, even if it looks like something else is the issue and not the software.
Many Thanks
Xan Steel