which one is better? FB17 or FB21? i haven't had time to test fb21. if anyone has tested both. give me some info lol. thanks
I really don't see a large difference between them, however, when I installed the stock fb21 I got a couple launcher fc's that I didn't get on Fb17, but running TNZ's Blend ICS I haven't had any FC's at all and is running pretty smooth for a test build
They're basically the same. Pick your poison.
Is scrolling wallpaper back in ics ?
Sent from my SPH-D710 using xda premium
From what i hear the FB21 is alot worse than the FB17, but personally i am just sticking out with FB17 until the official release is out (for now).
I don't notice a difference between the two builds. Definitely stable enough for a daily driver in my opinion.
One issue I'd consider major is GPS though. After locking GPS and turning it off, it still says GPS locked in the drop down menu and murders the battery. A reboot shuts it up.
Definitely something to keep in mind.
I tested them both. I had more issues with 17 than I did with 21. Quarky things like BT bugs where i could connect to some devices and not others. Also, I could not get a lock on GPS with 17 and I could with 21. Both of these issues are hit or miss. It appears some users had the issues, and others reported that they did not experience it, or experienced it exactly opposite (21 to 17) of what I experienced. It could be a matter of the order in which you flash the modem and ROM or other factors during install.
Other than that, the only other noticeable difference between the two was that in FB21, a double tap on the home button launched VLINGO.
In either case, I am going to Calks 2.9.1 until we get a stable ICS ROM with recovery. Now that FB24 is posted, I expect that it may take some time. I have to take a break though...I think I sprained my flashing thumb.
thanks all. im just sticking with FB17 for now then
I Think they both are bad the 3g is so slow I have like .20 MBPS down and .13 up
Related
Way back in the 30's I was getting fantastic results with CM7 and tiamets kernel. I recently wanted to go back to it until the Sense 2.1 guys ironed out a few more bugs for me to comfortably daily drive them. I installed n63....had issues 7.0.3.1.... had issues.... n65.... had issues.
By issues I mean random restarts, force closes, 3g won't stick, overall signal for 1x was horrible, no amount of gps fixing would keep my gps locked in or lock better than 20 meters and mms won't work.
I tried stock kernel, tiamets, SZ ect.... clean install, clean wipe, reinstall apps from market vs restore from TB. Tried the mms fix, gps status app, msl reset trick, you name it I have tried it. My phone does not like CM7 right now at all. It's like feeding a baby strained carrots.
I was just curious if anyone else is having similar "no amount of tweaking will fix it" issues. I had to go back to Konis just for some sanity after 3days of this. I know all these Roms that are not based on actual Evo source are experimental but can a guy get some CM love?! lol
I am having pretty much the same issues on my evo. Tried just about the same tweaks to try to rectify them. Right now I'm going to under clock and see if it helps. I noticed a lot more things residing in memory after a restart than usual, including fota kill which is a cm product. All I think I can do now is fire up catlog and see if anything is obvious. I'm no genius so likely I'll just send it in and hope for the best. I was almost sure my hardware was failing, but now not so much.
Haven't had any issues gonna try the latest stable build of cm7 I always use amon 2.3 for a full wipe a lot of the time that fixes issues for people .
ginjeet said:
I am having pretty much the same issues on my evo. Tried just about the same tweaks to try to rectify them. Right now I'm going to under clock and see if it helps. I noticed a lot more things residing in memory after a restart than usual, including fota kill which is a cm product. All I think I can do now is fire up catlog and see if anything is obvious. I'm no genius so likely I'll just send it in and hope for the best. I was almost sure my hardware was failing, but now not so much.
Click to expand...
Click to collapse
Well, n66 after a day on tiamets 4.0.1 kernel seems stable. Let me know how the undervolting goes. I tried vipers v2 and it started freezing after about 20 minutes. The -50 script did the same thing. -25 actually worked out pretty well right up until this morning. My alarm went off and I hit snooze and it threw it into constant reboot.
I'm going to run just n66 with 4.0.1 all day no script and see what I get. I dunno what has changed for my phone but it seems to have leveled out. *knocks on wood*
Sent from my PC36100 using XDA Premium App
So far on the 7.0.3.1 build GPS works like a champ market mms and everything camera and such you tube app plays everything on hq. Picky at time at times tho on HQ.
blizzard1017 said:
Way back in the 30's I was getting fantastic results with CM7 and tiamets kernel. I recently wanted to go back to it until the Sense 2.1 guys ironed out a few more bugs for me to comfortably daily drive them. I installed n63....had issues 7.0.3.1.... had issues.... n65.... had issues.
By issues I mean random restarts, force closes, 3g won't stick, overall signal for 1x was horrible, no amount of gps fixing would keep my gps locked in or lock better than 20 meters and mms won't work.
I tried stock kernel, tiamets, SZ ect.... clean install, clean wipe, reinstall apps from market vs restore from TB. Tried the mms fix, gps status app, msl reset trick, you name it I have tried it. My phone does not like CM7 right now at all. It's like feeding a baby strained carrots.
I was just curious if anyone else is having similar "no amount of tweaking will fix it" issues. I had to go back to Konis just for some sanity after 3days of this. I know all these Roms that are not based on actual Evo source are experimental but can a guy get some CM love?! lol
Click to expand...
Click to collapse
Are you u using amon 2.3
Cm7 is running great for me. Used nightly 65 for a week with no problems. Flashed 7.0.3.1 2 days ago and it is running like a champ with sz 2.1.0 cfs. Did GPS fix back on nightly 30 something and it has been fine ever since. Maybe you just made your phone mad and its retaliating lol. I do have the receive mms problem though . Tried multiple fixes for it with no luck.
Update* just received an mms with 7.0.3.1 and it worked
A1Lonestar said:
Cm7 is running great for me. Used nightly 65 for a week with no problems. Flashed 7.0.3.1 2 days ago and it is running like a champ with sz 2.1.0 cfs. Did GPS fix back on nightly 30 something and it has been fine ever since. Maybe you just made your phone mad and its retaliating lol. I do have the receive mms problem though . Tried multiple fixes for it with no luck.
Click to expand...
Click to collapse
What recovery are you using man? Anything better using nightly 66 advantage wise?
reaper24 said:
What recovery are you using man? Anything better using nightly 66 advantage wise?
Click to expand...
Click to collapse
Well 66 plays nicely, but I think the mms bug where you can't receive, but using 3.3.7/4.0.1 with bsm v2 and it plays nicely.
teh roxxorz said:
Well 66 plays nicely, but I think the mms bug where you can't receive, but using 3.3.7/4.0.1 with bsm v2 and it plays nicely.
Click to expand...
Click to collapse
Well, I just went back to Koni's..............again. I was running 66 all morning with 4.0.1 and no script and while everything was working ok the battery was draining somewhat fast. It wasn't a wake issue and I even tested an hour or so on PRI177 with the same results. The battery was tolerable because Mondays are really busy for me so I know on a normal day I wouldn't complain but my data connection still drops to 1x a lot and I think the drain might have something to do with the connection searching constantly.
If I can get that Viper script moving along and figure out the data and signal drop I think I am getting somewhere.
@reaper, yes I am using Amon Ra latest and greatest.
Off topic, I love the Nand backup option. My Vibrant only uses Clockwork and even then it was not fully functional. Some of the basic options would brick the phone.
The latest cm7 stable works great.
Sent from my PC36100 using XDA App
flashing back to sense after "GPS FIX"
I have a few issues with CM7 and I keep switching back to Sense roms because they have been stable. If I do the GPS fix and stay on CM7 will my GPS still work when and if I go back to a Sense ROM?
Ok, so after having several ROMs and modems since I bought my Epic back in November . . . I continue to have a terrible time getting it to get a GPS lock. Right now I am on Midnight ROM 5.5 and EF02 modem. Is there anything I can do to get the GPS to lock in better? Does everyone still have GPS issues like I am (I even returned the first Epic I got because of this issue, but the second hasn't been that much better).
So there's no hope?
I don't know how much this may be of use to you, or if its in your interest, but I'd like to tell you that I use to have the WORST gps locks when I was on an outdated version of the 'Epic Experience' Rom on eclair, it would take ridiculously large amounts of time to lock on, and most of the time, it didn't! I finally got tired of the outdated Rom and Odin'd to Stock EC05, Rooted, and bloatware removed. I get a lock in less than 10 secs now, if not immediately. I realize you're on EF02, but I just thought I'd let you know this... cheers.
Sent from my SPH-D700 using XDA App
Try one of the Gingerbread ROMs and also flash the gps fix included in the 2nd post of the Swiss Cheese ROM.
I updated to Gingerbread 2.3.4 (EG22) and the GPS locks real fast. Maybe give it a try.
Hi all, I thought I'd share my experience. Without going into too much background, I had been running an FB21 stock ROM since it was leaked, and only had a few minor issues that didn't keep me from using it as a daily driver. Wanting to flash CM9 Alpha, but not having time to do it made me wait until Alpha 5.
I flashed Alpha 5 and started getting sleep of death issues (phone wouldn't wake and would get very warm). I thought it was CM9, so I switched to AOKP to experience the same thing. Switched over to Paranoid Android and still had the issue. On over to Caulk's 1.6 (loved his GB ROMs) and still Sleep of Death.
Feeling that it may be a non-stock issue, I flashed the stock leak of FF11. No joy. Then, I felt it may be 4.0.4, since that version caused the sleep of death on my Transformer TF101 (which reverted back to 4.0.3 to fix). I tried both Caulk's 1.5, and a stock FD26. Still had sleep of death.
I then thought it may be the modem because the SOD seemed to present itself when signal was low (common in my area). I ran CM9, Alpha 5 with the EL29 modem. Again, no luck.
Finally, I tried running Alpha 5 with the Rogue 1.2.1 rev2 kernel (based off FB21). The phone was immediately quicker in its response, screen comes on almost instantly, and I've yet to experience a sleep of death. I've even gone on a road trip to some no-service areas, which caused SOD without fail. My phone wakes with no hesitation.
I'm not sure if a later kernel will work for those experiencing SOD, but I found something that works for me and well enough to be a daily driver.
Maybe you should try using odin to go back to el29 stock everything you were switching to are leaked builds go back to what you know works first then go from there.
Sent from my Epic Blazer 3G Touch
Did that, just left it out of the OP since I didn't want to get too detailed beyond what wasn't working.
One more recent tidbit. Phone is working great now, but the EL29 modem had always caused me a phantom LoS (bars showed, but wouldn't send out calls/texts). Still gave me that issue with the CM9 ROM and FB21 kernel. Flashed the FF11 modem and it seems to be working great.
It might be your hardware.
I tried several JB roms - CM10, a couple of leaks. The all heated up the phone (where the cpu is - at the bottom back of the phone) when simply swiping from screen to screen on the desktop. ICS roms don't do that.
Is that normal or is it a bug? Is it because Project Butter uses more cpu to make things smoother?
I haven't experienced any heat issues with CM10 or any variants of it.
However I have experienced a heat issue with the JB TW leaks yes...but they are just that...leaks.
On a further note, I don't recall having a heat issue with the T-Mobile leak, but that was a month or so ago since I have tried it.
nabbed said:
I tried several JB roms - CM10, a couple of leaks. The all heated up the phone (where the cpu is - at the bottom back of the phone) when simply swiping from screen to screen on the desktop. ICS roms don't do that.
Is that normal or is it a bug? Is it because Project Butter uses more cpu to make things smoother?
Click to expand...
Click to collapse
On the LIH leak that I am using I've noticed that for about 10 minutes after installing the rom the phone ran real hot, seems like there was alot of housekeeping the phone does on initial boot up. It did calm down after that.
poit said:
On the LIH leak that I am using I've noticed that for about 10 minutes after installing the rom the phone ran real hot, seems like there was alot of housekeeping the phone does on initial boot up. It did calm down after that.
Click to expand...
Click to collapse
No, my issues were with swiping home screens for a few minutes.
Another huge issue, which prompted me to restore an lg8 rom, was using the phone at work with remote control and 12121 prl.
I have poor cellular signal at work, so I would normally run 00001 prl to connect to verizon towers or use 12121 prl and use roam control "roam only" to connect to us cellular towers.
The LIH leak had strange behavior with the latter - it would constantly access internet and heat up the phone. It would also drain the battery really quickly.
It would only do that with the combination LIH + 12121 + roam only.
Of course, no ICS rom would do that.
Have you seen anything similar?
byransays said:
I haven't experienced any heat issues with CM10 or any variants of it.
However I have experienced a heat issue with the JB TW leaks yes...but they are just that...leaks.
On a further note, I don't recall having a heat issue with the T-Mobile leak, but that was a month or so ago since I have tried it.
Click to expand...
Click to collapse
I only tried cm10 a month or so ago. Perhaps the newest nightlies don't do that.
What also bothered me in CM10 is how it felt hardware unaccelerated in the browser when scrolling and zooming. It was kind of smooth, but not as smooth as the samsung software.
Which version of CM10 would you recommend for bug-free operation as a daily driver? It's important that voice dialing with a bluetooth car kit is working, which was also very buggy with that older cm10 version.
So I've been having a bit of trouble with my t989 lately, when I try unlocking the phone I will either get a black screen (the lock screen will appear for a split second before going blank if I hit the lock button again) or it won't track my finger movements on the screen. If I manage to unlock the device I end up seeing numerous graphic glitches ranging from the bar at the top w/ the clock/battery meter just gone and the keyboard not working.
I'm runing CM9.0.0 because I had issues with 10.2 (battery wouldn't charge) and 10.1.3 (similar to my lock screen issues but not as severe, still agitating) and also 9.1 which had the same exact issues as I'm having now. I've tried installing with different gapps but the same thing happens. The phone will work for a day or two, then the glitches come. After resetting, everything is normal for a day or so, then it's normal a few hours, etc. The time is getting narrower between reboots and it's a bit frustrating.
Does anyone know what I could be doing wrong, if anything? I flash via twrp and wipe, then install the rom, then install gapps, then reboot, wait 20min, reboot, and go about my business w/ the setup and such. I would be fine going back to 10.1.3 but jellybean roms and snapchat don't really like to work together on this phone for some reason. It's really the only app I use because it seems like the only way my friends want to communicate nowadays, so I'd prefer to stay on ics if possible...
If anyone can give any insight I'd really appreciate it
greenghoul said:
If anyone can give any insight I'd really appreciate it
Click to expand...
Click to collapse
Have you tried using Odin to flash back to stock? That is usually the recommended step if you are having problems with custom ROMs.
And the newest stock is 4.1.2, so at least you wouldn't have to be on ICS.
meekrawb said:
Have you tried using Odin to flash back to stock? That is usually the recommended step if you are having problems with custom ROMs.
And the newest stock is 4.1.2, so at least you wouldn't have to be on ICS.
Click to expand...
Click to collapse
I'll give that a try. Odin is just the program used to root originally, correct? Also, I want to stay on ICS if possible. So after doing that I'm going to try CM9 again and see how that works.
Anyway, the past few days I've been using AOKP mr2 milestone 1 and it's been okay. For some reason the battery life is bad even with juice defender and a task killer taking care of things. In a matter of minutes after clearing tasks I'm down from ~350mb of ram free to 60. Is that normal with that rom?
I'm not sure what to do at this point. I'm not the best with technology but i figured i was smart enough to figure this out...
bump.
I still haven't tried flashing w/ odin yet. Does anyone know where I can find a gingerbread stock rom? I've been looking for a while and can only find the jellybean one. Since I want to stay on ICS what I want to do is go from gingerbread and up to that rather than downgrading from the jellybean stock rom if that makes sense.