Database Info

mt3g green screen problem

First let me start by saying hello to everyone and how much i love this website for its plethora of information!! I am have attempted for 6 hours today in attempt to fix my problem and will only post a thread as last resort. I have reached my last resort. Here is how it all started....
Today i decided that i wanted to have the new updated Android Market so i could pay for apps using my tmo account. i noticed that my cyanogen 4.2.15.1 and the previous ones before do not use the updated market (from what i have found, it causes some problem), but i was unable to find a way to just update the market. i have also been toying with the idea of switching roms (i have used cyanogen since i rooted my phone almost a year ago) and was thinking of a super fast Hero rom. From my research, i found one that i thought was the best of the best. getting in a little over my head and doing the proper research and educating myself, i jumped in (not a normal move for me, i tend to collect as much info as i can before a make this type of move but i was work and bored ). so i downloaded and flashed a new rom. here are a few things i did wrong:
I did not wipe before i updated to the new rom
I mistakenly flashed a Hero rom for a 32A phone, thinking mine was 32a (idiot)
I did not change my radio or spl's (from what i am now reading, that was a big mistake too)
so, obviously, the rom did not take and it froze on the green mytouch 3g screen for 40 minutes. no big deal, i thought a would just wipe it, then try again. same result. ok, i will just restore to my nandroid backup........unable to restore . panic started creeping in. ok, i will just redownload the 4.2.15.1 cyanogen i had and WIPE and flash it. after attempting this many many times, it still freezes on the green mytouch 3g screen. i even thought of using an older cyanogen, 4.2.9.1 i believe, thinking they use old info that was still on my phone. no luck. i have a feeling i am missing something very obvious and will feel totally stupid when you guys help me, but, i am stuck.
I would love to have a kick ass Hero rom and if someone can explain to me the proper way of doing so with a recommendation of the most kick assey one, that would be greatly appreciated, or if someone can kindly assist me to get back to my original cyanogen rom, that would also rock. thank you in advance and i know you guys will make whole again!

USB Debugging not functioning.

Hello guys, this is my first post so hi there. First of all I lurked this site for quite sometime but finally a decent need to make a account arose. I rooted my phone, Galaxy S 4G obviously, with intentions to put a custom ROM on there. I couldn't tell you which ROM it was as I forgot. But one of the higher rated ones available for this model. I was 2.2 at the time. I mistakenly flashed it to the official 2.3 ROM (from Samsung) and at first there were no issues. Until I realized I needed to flash it again because Superuser wouldn't work. Okay no issue. I go and turn USB debugging on so I can root it. I plug the phone it my computer via USB and the debugging icon doesn't show up. I tried unplugging and replugging it while turning the setting off and on. I don't know what to do. Stock ROM is pretty buggy on here. Any help is appreciated.

If your on GB the debug icon doesn't show in the status bar. If you turn it on from the phone rest assured it's on.

I wanna believe that. But when I used...Superoneclick I think the rooting didn't work. I'll have another go at it however.
EDIT: Well, my phone didn't even recognize my phone plugged in however I could turn on USB storage...could be apart of it.

I haven't used super one click in a while but I'm pretty sure if you are trying to root GB you have to use hte most recent version of SOC. If that doesn't work you can always flash this http://forum.xda-developers.com/showthread.php?t=1380331through heimdell. Or flash one of honks kernels through odin.

I'm rooting my phone as we speak, and I uninstalled superuser because I was getting pissed off how slow my phone was. Is there any good ROMS for this phone that increases performance?

Yeah theres a bunch of good ones in the dev section. I like valhalla black ice edition. Super smooth, great battery life. Just look over there you won't be dissapointed.

AJTeamkiller said:
I'm rooting my phone as we speak, and I uninstalled superuser because I was getting pissed off how slow my phone was. Is there any good ROMS for this phone that increases performance?
Click to expand...
Click to collapse
Yea! For example there's Octane 3.0, Valhalla, Valhalla Black Edition, ICBINB, and AOSP style. Go try them and see which one you like.
-Sent From My Amazing SGS4G-

iHelper said:
Yea! For example there's Octane 3.0, Valhalla, Valhalla Black Edition, ICBINB, and AOSP style. Go try them and see which one you like.
-Sent From My Amazing SGS4G-
Click to expand...
Click to collapse
I have my eye on that Valhalla black edition, but a lot of my decision goes into the UI. Black Edition apparently has a decent ICS launcher. Which makes me interested as ICS reminds me a lot of the Windows Phone UI to some extent.
Octane 3.0 looks a lot like ICS as well. Can anybody help me with the pros and cons of each? I need something to discuss while my phone is rooted. It takes forever.

Should I be worried my screen won't turn on in the middle of rooting it?...

Once your rooted and get cwm just take Ihelpers suggestion and try a few ROMS and decide for yourself. It's hard to give someone suggestions about personal preference. I really like IPA's but my best freind prefers Pilsner. You get the idea.

Before I delve to deep in that....It says running rageagainsthecage. Okay cool, my phone vibrates to tell me its done charging, okay cool. The screen won't turn back on. What damage could I do if I pull the battery?
EDIT: went ahead and did it. Did not brick. I honestly didn't know what would happen if I did so don't judge me D: but, I went ahead and tried it again. Got up to the same point, and then my computer stopped reading my phone for a second. My computer recognizes it right now but superoneclick still says waiting for device....

How long have you had it going? I remember it taking alot longer than I thought it should. But that was on froyo. Don't pull the battery unless your absolutely sure it's not working. If that's the case study up on ODIN or heimdell.

hechoen said:
How long have you had it going? I remember it taking alot longer than I thought it should. But that was on froyo. Don't pull the battery unless your absolutely sure it's not working. If that's the case study up on ODIN or heimdell.
Click to expand...
Click to collapse
I guarantee it froze, I know its not rooted. But gonna try superuser and see what happens. After I rooted on froyo it was really slow until I rebooted.

If it boots up just DL root ckecker from the market. Run it and it will tell you whether it's rooted or not.

Weird, Superuser doesn't autoclose yet it says my device isn't rooted.

No root for you! Seriously look at my 4th post and just go one of those routes(or roots). Take your time and remember to enjoy a nice IPA along the way.

It keeps looping and stops recognizing. Guess I'll use another method to root. I think I might just do that tomorrow. Getting up there into the night.

Any other method of rooting thats simple and reliable(main reason I liked SOC) Also very odd bug where the screen would come on for no reason, just odd.

AJTeamkiller said:
Any other method of rooting thats simple and reliable(main reason I liked SOC) Also very odd bug where the screen would come on for no reason, just odd.
Click to expand...
Click to collapse
Heimdall my kernel. Search the general forum for '[REF]' and you'll find a thread I started about rooting. Either will get you root, but my kernel will get you cwm.
Sent from my Gingerbread on Dream using xda premium

bhundven said:
Heimdall my kernel. Search the general forum for '[REF]' and you'll find a thread I started about rooting. Either will get you root, but my kernel will get you cwm.
Sent from my Gingerbread on Dream using xda premium
Click to expand...
Click to collapse
Well, gonna try one SOC one last time, gonna let it go and I'ma go grab a ice tea from my convenience store, which would take 30 minutes, how long on average for this phone would it take?

My first flashing... (no trenchcoat involved)

So, I finally flashed a ROM onto my Atrix 2 for the first time the other day.
Synopsis
​Long story short the twitter app crashed my phone and threw it into a boot-loop, I did some research, quickly learned the in's-and-out's of flashing ROM's, flashed the stock-ROM for my device, fully updated my device, and became a better man for it...okay, well maybe not that last part!
The nitty-gritty
​What happened was I was trying to update my twitter when the app locked up after hitting the 'submit' button. I tried to force-close the program but to no avail. Then I had the bright idea of shutting down my phone. This is where the fun began.
After re-booting my phone, I discovered that it was stuck in a boot-loop. Now, my phone has been rooted for a little over a month. There were no issues that occurred after I rooted my phone up until that point. This is what leaves me to believe that Twitter corrupted some app data.
After this happened I took to the internet and scoured over forums (this one chief among them), articles, videos, and even asked a few fellow-android users here in the real world. Everywhere I looked lead me to this term I had feared up until this point: Flashing.
I understood that flashing a ROM was just like installing a new operating system. I had toyed around with Linux before just a bit and am savvy-ish when it comes to computers. However, I was so terrified of bricking my phone in trying to flash a new ROM onto it (I would have been track-phoning for around a year until my next manufacturer subsidy came out on my account.)
After discovering terms like deodexed, CM7, stock, AP Fastboot, RSD Lite, and hardware-key reset, I felt like I was finally able to attempt the flashing. The first few attempts failed as I didn't realize I didn't have enough battery life to sustain the flashing process.
After charging it up, I flashed the stock ROM onto my phone. The moment it went from the red M puddle screen to the dripping AT&T sphere, then onward to the ROM was a moment of pure joy (not to sound corny.) I felt like I had beat-the-system. A problem that would have forced others to return their phone to the store was a problem that I fixed myself.
Final Thought
​I know this is rather cinematic for it being a simple flash job on an android device. But, for me, this was quite exhilarating. I'm not comfortable flashing anything lower than full-release ROM's (beta and alpha ROM's are a bit beyond my scope right now.) But, I do look forward to testing out various full-release ROM's as they become available.

AscottW said:
So, I finally flashed a ROM onto my Atrix 2 for the first time the other day.
Synopsis
​Long story short the twitter app crashed my phone and threw it into a boot-loop, I did some research, quickly learned the in's-and-out's of flashing ROM's, flashed the stock-ROM for my device, fully updated my device, and became a better man for it...okay, well maybe not that last part!
The nitty-gritty
​What happened was I was trying to update my twitter when the app locked up after hitting the 'submit' button. I tried to force-close the program but to no avail. Then I had the bright idea of shutting down my phone. This is where the fun began.
After re-booting my phone, I discovered that it was stuck in a boot-loop. Now, my phone has been rooted for a little over a month. There were no issues that occurred after I rooted my phone up until that point. This is what leaves me to believe that Twitter corrupted some app data.
After this happened I took to the internet and scoured over forums (this one chief among them), articles, videos, and even asked a few fellow-android users here in the real world. Everywhere I looked lead me to this term I had feared up until this point: Flashing.
I understood that flashing a ROM was just like installing a new operating system. I had toyed around with Linux before just a bit and am savvy-ish when it comes to computers. However, I was so terrified of bricking my phone in trying to flash a new ROM onto it (I would have been track-phoning for around a year until my next manufacturer subsidy came out on my account.)
After discovering terms like deodexed, CM7, stock, AP Fastboot, RSD Lite, and hardware-key reset, I felt like I was finally able to attempt the flashing. The first few attempts failed as I didn't realize I didn't have enough battery life to sustain the flashing process.
After charging it up, I flashed the stock ROM onto my phone. The moment it went from the red M puddle screen to the dripping AT&T sphere, then onward to the ROM was a moment of pure joy (not to sound corny.) I felt like I had beat-the-system. A problem that would have forced others to return their phone to the store was a problem that I fixed myself.
Final Thought
​I know this is rather cinematic for it being a simple flash job on an android device. But, for me, this was quite exhilarating. I'm not comfortable flashing anything lower than full-release ROM's (beta and alpha ROM's are a bit beyond my scope right now.) But, I do look forward to testing out various full-release ROM's as they become available.
Click to expand...
Click to collapse
In all technicality all you're doing when flashing a rom (at least now) is installing some tweaked files such as build.prop or some tweaked system files for themes. By no means is it a new OS. But once a main kernel Dec finished up with a CM7 kernel we should be able to flash a custom kernel which is the meat of what really runs your phone. Really the stuff we can do right now only really have to do withtl the UI.
But anyways welcome to the world of android development!
Sent from my MB865 using XDA

Congrats on flashing your first ROM . Sorry to hear it didn't completely work out for your. Quick question: did you wipe the Dalvik Cache as part of the flashing process?
By the way, most of the ROMs labeled "beta" are pretty stable. If a ROM has had more than a few updates and it's still in beta, it's mostly because the developer is either planning on adding more features for the full release or is a perfectionist
Well, as you can tell it's a sharp learning curve. But welcome to the world of Android hacking/modding/whateveryoucallit, and happy flashing

wait, are you telling me that there are actually people who do research before complaining about some little thing they don't know how to do?!?!?!?!?!?!?
FINALLY
Sent from my MB865 using XDA

LOL.. good story/nice read.. Welcome!

I would say it worked out pretty well. I will probably flash a custom ROM later on this week. I will also keep reading up on the whole process and the it's and out's.
I cleared both user data and the dalvik cache as well. Pretty much at that point I was desperate. Lolz
Sent from my MB865 using xda premium

lkrasner said:
wait, are you telling me that there are actually people who do research before complaining about some little thing they don't know how to do?!?!?!?!?!?!?
FINALLY
Sent from my MB865 using XDA
Click to expand...
Click to collapse
Hahaha.. Well, with this involving my phone (for which I don't have the hundreds of dollars to buy one outside the manufacturers subsidy) I wanted to make sure I was doing things right.
Sent from my MB865 using xda premium

AscottW said:
I would say it worked out pretty well. I will probably flash a custom ROM later on this week. I will also keep reading up on the whole process and the it's and out's.
I cleared both user data and the dalvik cache as well. Pretty much at that point I was desperate. Lolz
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
its really easy, so you should go ahead, the roms we have are way better than stock. Lithium is y favorite right now.

alteredlikeness said:
LOL.. good story/nice read.. Welcome!
Click to expand...
Click to collapse
Glad you enjoyed it! I am happy that my twitter app decided to crash, now.
Sent from my MB865 using xda premium

AscottW said:
Hahaha.. Well, with this involving my phone (for which I don't have the hundreds of dollars to buy one outside the manufacturers subsidy) I wanted to make sure I was doing things right.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I second that.. better to take your time to research, and do things right the first time...
lkrasner said:
its really easy, so you should go ahead, the roms we have are way better than stock. Lithium is y favorite right now.
Click to expand...
Click to collapse
^Total opinion about stock and custom... I'm on stock/odex/modded/tweaked with some bells and whistles... nice, responsive, and stable..
Sent from my mind using XDA

alteredlikeness said:
^Total opinion about stock and custom... I'm on stock/odex/modded/tweaked with some bells and whistles... nice, responsive, and stable..
Sent from my mind using XDA
Click to expand...
Click to collapse
I agree. Spent this weekend working on the Stock 2.3.6 rooted/odexed. Added the Superv6, and other mods, hotspot wifi fix, removed bloat. Definitely more fun this way. Then again I had a buttload of practice on my original ATRIX.
And thank god for the bootstrap and FXZ !!!!

dicksteele said:
And thank god for the bootstrap and FXZ !!!!
Click to expand...
Click to collapse
Yes without that I would of had an expensive paperweight to many times

dicksteele said:
I agree. Spent this weekend working on the Stock 2.3.6 rooted/odexed. Added the Superv6, and other mods, hotspot wifi fix, removed bloat. Definitely more fun this way. Then again I had a buttload of practice on my original ATRIX.
And thank god for the bootstrap and FXZ !!!!
Click to expand...
Click to collapse
How exactly do I identify bloatware? I have two programs to do that Titanium backup and Rom Manager as well as a few 3p uninstallers. However, I never know exactly what to delete?

AscottW said:
How exactly do I identify bloatware? I have two programs to do that Titanium backup and Rom Manager as well as a few 3p uninstallers. However, I never know exactly what to delete?
Click to expand...
Click to collapse
DON'T ever delete any programs. It is better to use something like bloat freezer, and freeze these apps, than to delete them.
The updates check for missing "bloatware" and will fail to install the updates due to ANY missing apps, that came with the stock image.
If you want a debloated image, then use one of the more custom ROMS like lithium, or Supercharged, etc.
If you use a debloated ROM, then you can always flash the fxz back before any updates come out, we tend to start screaming pretty load on here when updates start to arrive as you may have already seen this week with the ICS leaks.
P.S. It is VERY hard to hardbrick this phone, it took me killing the signature on the kernel to get my first hardbrick, and I have had 3 more hardbricks. I have the warranty through att, so I never worry about things like that, since I am a dev and take my phones life into my own hands, and ATT always has exchanged my phone on the spot for over 12 years now.... You can softbrick (bootloop), but that is an easy fix with the FXZ (lifesaver). So not too much to worry about hurting your phone with flashing...

jimbridgman said:
DON'T ever delete any programs. It is better to use something like bloat freezer, and freeze these apps, than to delete them.
The updates check for missing "bloatware" and will fail to install the updates due to ANY missing apps, that came with the stock image.
If you want a debloated image, then use one of the more custom ROMS like lithium, or Supercharged, etc.
If you use a debloated ROM, then you can always flash the fxz back before any updates come out, we tend to start screaming pretty load on here when updates start to arrive as you may have already seen this week with the ICS leaks.
P.S. It is VERY hard to hardbrick this phone, it took me killing the signature on the kernel to get my first hardbrick, and I have 3 more hardbricks. I have the warranty through att, so I never worry about things like that, since I am a dev and take my phones life into my own hands.... You can softbrick (bootloop), but that is an easy fix with the FXZ (lifesaver). So not too much to worry about hurting your phone with flashing...
Click to expand...
Click to collapse
LOL, I was laughing so hard when XDA crashed last night. I was sure we caused it with our ICS Freak out!!!!

lkrasner said:
LOL, I was laughing so hard when XDA crashed last night. I was sure we caused it with our ICS Freak out!!!!
Click to expand...
Click to collapse
I though the same thing, and I was kind of glad it did crash though, so that I could find that article with the interview of cyanogen that was posted on the XDA-dev home page.

AscottW, I am like you -I read and researched and forum'd my evening/early morning hours away with regards to the whole rooting and flashing and so on. I have never done such things with a phone before, but being fairly computer savvy myself felt like after several hard weeks learning as much as I could, flashed MY first ROM. (Did a little happy dance myself when I saw the custom boot animation for the first time, think I even let out a little school boy squeal as well! -Glad no one was around to hear that)
Still reading and researching and forum'ing at every free moment I have (girlfriend and kids think my laptop has become permanently attached to my, well... lap!) and am really interested in possibly getting myself to a point where I can be of some usefulness in the dev world.
Admittedly, after flashing for the first time, I got foolish with CWM and did basically what seemed like deleting the system partition and told the Android OS to get lost. Big mistake. Got stuck in a crazy splash screen loop and wouldn't load Android OS for the life of me. That said, with the help of the good people here on this forum, I was able to be walked through a AP Fastboot FXZ file fix, updated back to 2.3.6, and started over -making damn sure I knew what I was doing before doing ANYTHING! lol

Feel like: "I just had sex"
http://www.youtube.com/watch?v=lQlIhraqL7o

PhoenixNghi said:
Feel like: "I just had sex"
http://www.youtube.com/watch?v=lQlIhraqL7o
Click to expand...
Click to collapse
lol @ this!

[Q] HELP!! status/notification bar gone!!!

ok. I started my phone from scratch earlier. Everything was fine. Flashed Final-fixed. Everything was fine. Got a few apps back, everything was fine. After a while, I flashed the Booster... rebooted, and now my status bar/notification bar is GONE! On boot, I get an error about systemui problem had to force close. How can I fix this?

Exact error, which came up when in SetCPU, which is also giving me problems:
The application Status Bar (process com.android.systemui) has stopped unexpectedly. Please try again.

Final fixed already comes with booster. You're constantly having problems no one else is. You're not reading. You're flashing randomly. You're not doing things right. If you don't want problems go back to stock, or you can read carefully and not just flash willy nilly

FBis251 said:
Final fixed already comes with booster. You're constantly having problems no one else is. You're not reading. You're flashing randomly. You're not doing things right. If you don't want problems go back to stock, or you can read carefully and not just flash willy nilly
Click to expand...
Click to collapse
No man, I DO READ. I read it all. Sometimes I get a little confused about what some things are, but I'm not a dev, and this is my first smart phone. I'm NOT flashing randomly, either. Jesus, man not everyone can just jump right into this stuff and know it all. If you didn't want to offer a little help or a solution, don't be an ass. I'm trying to learn ffs. I was under the impression that val final and val black were different.

Seriously man? 6 posts in a row:
http://forum.xda-developers.com/showthread.php?p=27290880#post27290880
If someone had help to offer you're gonna have to wait for it. You're spamming the hell out of the board, so how about YOU quit being an ass.
I don't think you're reading at all. You're doing more typing and flashing than reading. If you don't understand how something works, why are you flashing it? You should be trying to understand how it's going to affect your device.
My advice: reflash valhalla final, don't install any tweaks. Valhalla final is one of the most stable roms out there and it's been used as the base for at least 3 roms that have been posted.
Here's a lot of reading for you:
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S/SGH-T959V

FBis251 said:
Seriously man? 6 posts in a row:
http://forum.xda-developers.com/showthread.php?p=27290880#post27290880
If someone had help to offer you're gonna have to wait for it. You're spamming the hell out of the board, so how about YOU quit being an ass.
I don't think you're reading at all. You're doing more typing and flashing than reading. If you don't understand how something works, why are you flashing it? You should be trying to understand how it's going to affect your device.
My advice: reflash valhalla final, don't install any tweaks. Valhalla final is one of the most stable roms out there and it's been used as the base for at least 3 roms that have been posted.
Here's a lot of reading for you:
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S/SGH-T959V
Click to expand...
Click to collapse
Thanks, that's better man. FYI, i'm not posting the same stuff everywhere. I'm reading and learning stuff, then trying to see what I can do. It's not all the same posts, just like the last 5 of mine have been about the notification bar, but all different querys. I'll clean it up tho, after I get sorted out. Also, I've already read the whole wiki, and the ENTIRE threads for all the things I've considered flashing.

Oh, how do I get into my phone if I cant pull down the notification bar to connect USB?
Never mind. I know already. Mount USB in CWM sry.,

Just an update after lots of troubleshooting, in case anyone might run across the same problem and did as I did:
I added the paid version of SetCPU to system/apps in the zip of the ROM I was flashing. I guess that's what was causing the issues, because now everything is stable. I kept Paid ADW Launcher, replacing the stripped down version, also a modified SystemUI.apk, framework-res.apk, and twframework-res.apk. All three from the zip I got from UOT Kitchen. So, now this great rom is even greater, and HIGHLY customized. Dont know why the modified crucial apks will work, but it wouldn't take the addition of setcpu...

If you pushed those apk's without rebooting to recovery and fixing permissions that will throw all the force closes.

eollie said:
If you pushed those apk's without rebooting to recovery and fixing permissions that will throw all the force closes.
Click to expand...
Click to collapse
After I figured out what you meant by 'pushing', I got it sorted out just like you said. Thanks man!

Can't seem to get CWM on SK4G.

I'm trying to get CWM going on my SK4G, but with little luck. I've replaced recovery in /system/bin, and put the update.zip on the root of the SD. But after doing so, it will still stick on the boot screen, and not go anywhere. It is not softbricked, however, as I can adb reboot, and it goes right back into the normal OS.
I then tried ODIN-ing back to stock and trying once more, but no dice. What do I do from here?

Search the forum. I reposted sduvick's fake flash utility already. Find it and use it.

Hop on the short bus, newbies.
Here's the CWM fake flash (again).
http://www.mediafire.com/?cedw9551tl1riu5
Root your phone with shortfuse's one click utility first. Then, use this utility. After you get this going, make a backup. Next, ODIN your phone back to stock. Then, root the phone, use this utility again, and use CWM to restore your backup. Now, you know how to handle disasters and you won't need to ask dumb questions.
After that, install one of AYOTEDDY's roms. Skip the new ones because there's nothing new. You just want a stable rom and a kernel with Voodoo lagfix/sound/CWM.
Enjoy.

I see you jump directly to insults. Short bus, mhm.
I'm hardly a newbie, this phone is just being a pain in the arse for something that looks so simple. My main is a GS3 which I flash ROMs frequently, and have used ODIN before. Before that it was an HTC Aria. I picked this one up cheap because I like a physical keyboard.
CWM (Though I prefer TWRP any day of the week) is indeed helpful if you screw up, and ODIN as a last resort. This one is just being a pain in the arse though, and keeps getting stuck on the sidekick logo when going into recovery. (I copy it to the SD then move it into place via Root Explorer)

So, the fake flash isn't working for you?

orange808 said:
After that, install one of AYOTEDDY's roms. Skip the new ones because there's nothing new.
Click to expand...
Click to collapse
Hahaha....nice. Why don't you try and make something new, then?

Meh. Theming, scripts, and swapping out apps is easy enough.
I have made KJ2 my own with some dirty hacks, but the biggest benefit over stock is Platypus Egg--and the credit for that goes to ayoteddy.
As for roms, I hacked away at windxixi's and sduvick's source for quite a while. At some point, it's just not worth it anymore... Samsung could have made this easier on everyone... Samsung's "open source releases" are a joke.
bhundeven appears to have also hit a wall, but it sounds like he has more experience and more help at his disposal. More power to him there. Because, a true stock Froyo is really what this device needs to push things forward.
I'll be getting a Relay soon enough, so it won't amount to a hill of beans to me...
And, speaking of new, I've had the most luck avoiding it entirely on the market. Updates these days are getting too bloated to run on this device--and more and more apps have decided it's ok to run as a service. At some point Android needs to crack down on developers that ignore the life cycle that was diagramed when the SDK debuted... Then again, that would make Google hypocrites because Maps ignores the guidelines... To make a long story short, run apps that were actually designed to run on Froyo. It will save you heartache. And, if things are running all the time as a service, it will eat memory and this phone will crash eventually.. every time, guaranteed.

orange808 said:
Meh. Theming, scripts, and swapping out apps is easy enough.
I have made KJ2 my own with some dirty hacks, but the biggest benefit over stock is Platypus Egg--and the credit for that goes to ayoteddy.
As for roms, I hacked away at windxixi's and sduvick's source for quite a while. At some point, it's just not worth it anymore... Samsung could have made this easier on everyone... Samsung's "open source releases" are a joke.
bhundeven appears to have also hit a wall, but it sounds like he has more experience and more help at his disposal. More power to him there. Because, a true stock Froyo is really what this device needs to push things forward.
I'll be getting a Relay soon enough, so it won't amount to a hill of beans to me...
And, speaking of new, I've had the most luck avoiding it entirely on the market. Updates these days are getting too bloated to run on this device--and more and more apps have decided it's ok to run as a service. At some point Android needs to crack down on developers that ignore the life cycle that was diagramed when the SDK debuted... Then again, that would make Google hypocrites because Maps ignores the guidelines... To make a long story short, run apps that were actually designed to run on Froyo. It will save you heartache. And, if things are running all the time as a service, it will eat memory and this phone will crash eventually.. every time, guaranteed.
Click to expand...
Click to collapse
Good for you. I will be releasing a CM 6.2 clone based off of the Epic 4G rom tonight. All with the easy theming, scripts and app swaps. Nothing new but I still have fun making it.
Sent from my SGH-T839 using xda app-developers app

Glorious overdose
RicAndroid said:
Hahaha....nice. Why don't you try and make something new, then?
Click to expand...
Click to collapse
How do you like that Glorious overdose 4.1?