Database Users

aospGBMod v0.1.2 | AOSP 2.3.1 (Gingerbread) lounge for talking about this ROM

Since the other thread seems to be getting off topic, what topic? Im not sure since there is no development collaboration in the topic...I have created this thread for us to talk about whatever we want (pertaining to this ROM) SO go ahead and cry and whine all you want here, because afterall, thats the topic.
(MOD> PLEASE MOVE THIS TOPIC TO THE CORRECT FORUM, by MISTAKE I ADDED IT HERE)

Thread moved to General.

I'm afraid to see this thread in a day or two.
Anyways, does anybody know where AOSP and his all-knowing powers stand with this? There's plenty of chatter about what version he's on and all, but does anybody know for sure what he has so far?

I say give it some time. It took a while for Froyo to be fully functional. I'm not too keen on rushing the progress.
But as for GB, it looks really neat. Has anybody got any benchmarks data on it and compared it to the latest Froyo release?

i almost got a 5 on linpack, jit enabled. if u enable jit in gb though ive found video playback is screwey and dont work all the time. or maybe thats just the rom itself cause ive been having video playback problems with jit off to

mdhscanes24 said:
Anyways, does anybody know where AOSP and his all-knowing powers stand with this? There's plenty of chatter about what version he's on and all, but does anybody know for sure what he has so far?
Click to expand...
Click to collapse
Haven't been following the IRC. I don't much like the web based one. I follow 3 from Trillian, but I can't access the one he uses (only tried twice).
I do have hunches as to the slience. A lot of things have changed recently I think he might be working out.
-Root issues - being wiped out because of binary update
-ClockworkMOD - change to 3.0.0.2 supporting the new image methods
-gmail - critical to some, he's probably working on this over..
-camera. not critical to next update, but long run would be nice to have working, even to aosp i'm sure.

oohaylima said:
I say give it some time. It took a while for Froyo to be fully functional. I'm not too keen on rushing the progress.
But as for GB, it looks really neat. Has anybody got any benchmarks data on it and compared it to the latest Froyo release?
Click to expand...
Click to collapse
Rest assured I'm not looking to try and rush things. Hell, it's my daily as is.

(Solved using CM7) Finding a ROM where everything I WANT works doesn't seem to exist

Problem Solved. Running CM7 Build 40 (or later).

Do you have a condensed version of this post?
PS. My name is HondaCop and I approve this message.

Sounds like you've experienced a mix of software, firmware, and hardware issues and blamed them all on the ROM.

I use Fresh and can do everything that I read (didn't read the entire wall though, you may want to put in some Cliff notes for the lazy.)
I also run launcher pro.

So make one yourself, nothings stopping you, all the pieces and knowledge are free. Your post on here doesn't really serve a purpose.

Tried Calk's EViO 2, Myn's RLS5, Azrael X 2.1-3.1 over the 1st 3 months after I rooted, all had their various issues. Been on Vaelpak for over a month, love it! Dev is quick to respond to problems, even when they're caused by something in my setup. Currently on v 3.1 RC1 (update 2), v3.2 is right around the corner. Gets better every day!
Swyped on my VaelPak'd Supersonic EVO 4G...

It sounds like you want a rom that does what you want and the good news is...you can get it by making it yourself.
Expecting the devs to make something specifically to your tastes especially when most of it is done free of charge is a bit much to be asking.
If you can't make the rom you like on your own then you had better get cracking at fixing the rom with most of your wants working. You said so yourself you are too lazy to fix even a simple font issue yet you want the devs to make all your "i wants" possible. You should at least put in the effort to try to fix the little stuff (font for example) on your own before expecting the devs to do everything for you.

mswlogo said:
I've tried about 10 ROM's over the past couples weeks and if I could put the best features of all them on one it would be great.
This is in no way a report on disatisfaction from efforts from chefs. They are all sharing there time and effort typically on something they want for themselves.
But it seems you have to give up something to get something else.
I'm hoping someone can shed some light on my issues. Like use ROM X but apply this fix or patch.
I know everybody has different criteria for a "Working ROM" some may feel it's critical that Music plays over bluetooth with the phone going half asleep. Another user may want it to look like an iPhone etc.
But I don't need much (IMHO) but I just can't seem to get there.
Keep in mind I could easily live with most of these ROMs. But when you see something working right on one ROM but want it on another you keep hoping you can find a ROM that does everything the way you want or you can make it do so.
What I say I need may be incomplete because some things I take for granted. Like the phone needs to work, LED's for pending messages need to work etc.
1) ASOP Contacts. Why? So I can Click on Navigate to Address with that contact open. If anyone knows how to make HTC Sense Contacts do this I'd love to know. It can only go to stupid Google Maps.
2) Voice and Google Search to Include Contacts (ideally near the top of the list). I think I may have found a reason why it varies. If you shut off "Search As I Type" it behaves much more the way I prefer and Contacts will come right to the top and if you hit search it will then do a google search.
3) BlueTooth. All I use is simple headset that has worked on TP2 and 5 phones before that. It randomly disconnects after a Voice Search. Then leaves Voice Search prompt stuck on screen. Many (All?) sense based ROMs do this. But CM7 ROMs do not.
3a) Bluetooth Volume Resetting. Some ROM's it gets stuck at a low volume. That I can increase each time but it keeps reverting.
4) Solid 100% GPS. All Sense based ROMs work great. CM7 based ones are crap.
5) Battery as good as Stock or better.
6) ESPT (is a very nice to have but not critical).
7) Don't care about 4G or Eye Candy. But I don't want it to be an Eye sore either.
8) As a poor mans confirmation on Voice Search. I noticed on some Rom if you just say Call Fred Smith (WITHOUT saying on mobile) it will prompt Fred Smith on Mobile or Home. This is great !! So at least you know you got the right person. Then you say Mobile (which it rarely gets wrong). It makes the call. This doesn't work on all ROM's.
9) Good support thread. Some ROMs have very little interaction with chef to help get answers and plugs for some things you'd like to see. Some have very good Chef support but and pounded with stupid chatter and you'd have to live in the thread full time to keep up. It's seems the better support a Chef does pulls in more folks that just want to chat about anything.
10) If Click Send Message from a Contact that could actually FILL the To: Phone Number. A lot of ROM's this doesn't work on. Some depend on a Cache that you have an ongoing thread.
I have not tried alternate kernels with Sense Based ROM's perhaps that would solve some bluetooth issues.
CM7 Build 38 looked promising at first glance. But it fell on its face with GPS. Yes I did all the silly tricks. It always finds location and locks quick. But it just refuses to update while navigating. Will occasionally get an update.
NonSense ROM was very close and I may end up going back to it and perhaps with different Kernels because it suffered from Bluetooth issues. Might be time to upgrade BT headset. It's worked so well for so long I hate to give it up.
These are all stock #15 Kernel with lastest Radio and PRL.
Myn - Over themed (Beauty is in the eyes of the beholder I guess) poor contrasts on Fonts. Yes fixable. But I'm too lazy.
NonSense - Bluetooth is really only issue. Battery about same as Stock.
CM7 BLD 38 - Missed calls GPS will lock but not update.
VP3.70 - This really looks quite good but I just didn't have the time to learn which freaken updates to apply. He leans on theming which is low priority for me.
Rainfreak - Not actually installed, he says he addressed bluetooth issues. But he removed EPST and some other critical Sense based things. Might be easy to put back. But he abandoned support
OMJ - I misspoke in other threads this is a pretty nice stock based ROM and I like his thinking. Fine tune the stock stuff. Currently running. Several of the issues listed above (3,3a, 8).
Sprintlovers - Too close to stock, why bother.
Calkulin - Had stability issues with 1.7.7 (even with undervolt removed). 1.8 seems to have fixed that but still has some of my common issues with Sense Based ROM's with none of the pluses of the Hybrid Sense/ASOP ROMs.
MiekFroyo - Too many ROM's I forget what issues I had but I'm sure in the list above.
Click to expand...
Click to collapse
the bold part made me stop reading until i seen the part about miks roms ... HA its imho the fastest most stablest sense based rom out there !
about the lazy part please unroot your phone then ... lol to lazy to flash a simple file

CheesyNutz said:
the bold part made me stop reading until i seen the part about miks roms ... HA its imho the fastest most stablest sense based rom out there !
about the lazy part please unroot your phone then ... lol to lazy to flash a simple file
Click to expand...
Click to collapse
I don't think his ROM would solve many of my issues any way. If I see a ROM "Over themed" then tend to have different priorities. And I don't want to spend time customizing it. I want one that starts close. Also if the doesn't see this a serious flaw then I suspect I would see other flaws.
Again, nothing against different chefs. Different strokes for different folks.

mswlogo said:
I've tried about 10 ROM's over the past couples weeks and if I could put the best features of all them on one it would be great.
This is in no way a report on disatisfaction from efforts from chefs. They are all sharing there time and effort typically on something they want for themselves.
But it seems you have to give up something to get something else.
I'm hoping someone can shed some light on my issues. Like use ROM X but apply this fix or patch.
I know everybody has different criteria for a "Working ROM" some may feel it's critical that Music plays over bluetooth with the phone going half asleep. Another user may want it to look like an iPhone etc.
But I don't need much (IMHO) but I just can't seem to get there.
Keep in mind I could easily live with most of these ROMs. But when you see something working right on one ROM but want it on another you keep hoping you can find a ROM that does everything the way you want or you can make it do so.
What I say I need may be incomplete because some things I take for granted. Like the phone needs to work, LED's for pending messages need to work etc.
1) ASOP Contacts. Why? So I can Click on Navigate to Address with that contact open. If anyone knows how to make HTC Sense Contacts do this I'd love to know. It can only go to stupid Google Maps.
2) Voice and Google Search to Include Contacts (ideally near the top of the list). I think I may have found a reason why it varies. If you shut off "Search As I Type" it behaves much more the way I prefer and Contacts will come right to the top and if you hit search it will then do a google search.
3) BlueTooth. All I use is simple headset that has worked on TP2 and 5 phones before that. It randomly disconnects after a Voice Search. Then leaves Voice Search prompt stuck on screen. Many (All?) sense based ROMs do this. But CM7 ROMs do not.
3a) Bluetooth Volume Resetting. Some ROM's it gets stuck at a low volume. That I can increase each time but it keeps reverting.
4) Solid 100% GPS. All Sense based ROMs work great. CM7 based ones are crap.
5) Battery as good as Stock or better.
6) ESPT (is a very nice to have but not critical).
7) Don't care about 4G or Eye Candy. But I don't want it to be an Eye sore either.
8) As a poor mans confirmation on Voice Search. I noticed on some Rom if you just say Call Fred Smith (WITHOUT saying on mobile) it will prompt Fred Smith on Mobile or Home. This is great !! So at least you know you got the right person. Then you say Mobile (which it rarely gets wrong). It makes the call. This doesn't work on all ROM's.
9) Good support thread. Some ROMs have very little interaction with chef to help get answers and plugs for some things you'd like to see. Some have very good Chef support but and pounded with stupid chatter and you'd have to live in the thread full time to keep up. It's seems the better support a Chef does pulls in more folks that just want to chat about anything.
10) If Click Send Message from a Contact that could actually FILL the To: Phone Number. A lot of ROM's this doesn't work on. Some depend on a Cache that you have an ongoing thread.
I have not tried alternate kernels with Sense Based ROM's perhaps that would solve some bluetooth issues.
CM7 Build 38 looked promising at first glance. But it fell on its face with GPS. Yes I did all the silly tricks. It always finds location and locks quick. But it just refuses to update while navigating. Will occasionally get an update.
NonSense ROM was very close and I may end up going back to it and perhaps with different Kernels because it suffered from Bluetooth issues. Might be time to upgrade BT headset. It's worked so well for so long I hate to give it up.
These are all stock #15 Kernel with lastest Radio and PRL.
Myn - Over themed (Beauty is in the eyes of the beholder I guess) poor contrasts on Fonts. Yes fixable. But I'm too lazy.
NonSense - Bluetooth is really only issue. Battery about same as Stock.
CM7 BLD 38 - Missed calls GPS will lock but not update.
VP3.70 - This really looks quite good but I just didn't have the time to learn which freaken updates to apply. He leans on theming which is low priority for me.
Rainfreak - Not actually installed, he says he addressed bluetooth issues. But he removed EPST and some other critical Sense based things. Might be easy to put back. But he abandoned support
OMJ - I misspoke in other threads this is a pretty nice stock based ROM and I like his thinking. Fine tune the stock stuff. Currently running. Several of the issues listed above (3,3a, 8).
Sprintlovers - Too close to stock, why bother.
Calkulin - Had stability issues with 1.7.7 (even with undervolt removed). 1.8 seems to have fixed that but still has some of my common issues with Sense Based ROM's with none of the pluses of the Hybrid Sense/ASOP ROMs.
MiekFroyo - Too many ROM's I forget what issues I had but I'm sure in the list above.
Click to expand...
Click to collapse
I actually DID read the entire thing and everything you posted works in king's Ultra Froyo, for the most part

carhauler1969 said:
Tried Calk's EViO 2, Myn's RLS5, Azrael X 2.1-3.1 over the 1st 3 months after I rooted, all had their various issues. Been on Vaelpak for over a month, love it! Dev is quick to respond to problems, even when they're caused by something in my setup. Currently on v 3.1 RC1 (update 2), v3.2 is right around the corner. Gets better every day!
Swyped on my VaelPak'd Supersonic EVO 4G...
Click to expand...
Click to collapse
I may just go to Vaelpak again (Definitely high on the list). I might just wait for V3.2. His updates are bit confusing. If they are primarily to fix "theme" issues I don't care. Again he has a high priority on Themes. That's fine, lot's folks love that stuff. I don't care about themes.
If VaelPak did some refinements on bluetooth (like Rainfreak said he did). Then it would be high on the list to try again. He spends lot of time on high resolution DPI stuff on themes. Just extra band with I need to sift through. But other threads say it's the Kernel that matters regarding bluetooth. That's not clear.

CheesyNutz said:
the bold part made me stop reading until i seen the part about miks roms ... HA its imho the fastest most stablest sense based rom out there !
about the lazy part please unroot your phone then ... lol to lazy to flash a simple file
Click to expand...
Click to collapse
Also sense based Contacts is one of my major issues.
My favorite ROMs are the Hybrids that have some ASOP Gingerbread components that IMHO do it a little better even though not as Eye Candy-ish in some cases.

mswlogo said:
I may just go to Vaelpak again (Definitely high on the list). I might just wait for V3.2. His updates are bit confusing. If they are primarily to fix "theme" issues I don't care. Again he has a high priority on Themes. That's fine, lot's folks love that stuff. I don't care about themes.
If VaelPak did some refinements on bluetooth (like Rainfreak said he did). Then it would be high on the list to try again. He spends lot of time on high resolution DPI stuff on themes. Just extra band with I need to sift through. But other threads say it's the Kernel that matters regarding bluetooth. That's not clear.
Click to expand...
Click to collapse
it is the kernel that matters for bluetooth.

i think its time for you to start learning how to make your own rom but wait your to lazy . i have a feeling no matter what anyone says here will be good enough for you .
enjoy rom hopping ill enjoy my 20 + hours of battery life with miks 4.5 and 17 hours on CM7

matt2053 said:
Sounds like you've experienced a mix of software, firmware, and hardware issues and blamed them all on the ROM.
Click to expand...
Click to collapse
Lot of people with broken hardware then because I've seen many of the issues posted by other folks. In fact co-worked has rooted Droid II and he has some very similar issues. Only hardware that may have issues is my headset. But it worked perfect on TP2.
Part of the problems are Froyo 2.2 and some stupid limitation in Google Apps. Which is why I like Hybrid ROMs that have some Gingerbread 2.3 compoents that address some issues.
Full Gingerbread 2.3 ROMs are not ready for prime time yet (for me). I look forward to an official release.

BK553 said:
So make one yourself, nothings stopping you, all the pieces and knowledge are free. Your post on here doesn't really serve a purpose.
Click to expand...
Click to collapse
I might, I used Calkulins Kitchen for TP2 and stuck with the same ROM for 7 or so months. But it did take months of F'in around with it to know what works well with what.
Trying to avoid that time sink. By the time I get it "right" Gingerbread 2.3 will probably be out and solve many issues.

HipKat said:
I actually DID read the entire thing and everything you posted works in king's Ultra Froyo, for the most part
Click to expand...
Click to collapse
Thanks I had that on my list to look at.

CheesyNutz said:
i think its time for you to start learning how to make your own rom but wait your to lazy . i have a feeling no matter what anyone says here will be good enough for you .
enjoy rom hopping ill enjoy my 20 + hours of battery life with miks 4.5 and 17 hours on CM7
Click to expand...
Click to collapse
Well I was kinda under the stupid assumption when I bought the EVO Android worked !!
Now I have to build my own ROM. Geesh.
Again I don't think my list is too demanding. Some issues are pet-peivish, I admit.
Stock battery life is fine with me.
CM7 battery is looking respectable. But the phone fell flat on it's face before it could make it through one battery cycle to really know. When EVERYONE says GPS works I may give CM7 another go. By then my guess is a leaked GingerBread 2.3 will be out.

mswlogo said:
Well I was kinda under the stupid assumption when I bought the EVO Android worked !!
Click to expand...
Click to collapse
Last I checked it does work, maybe not how you want it to exactly, but work it does
Now I have to build my own ROM. Geesh.
Click to expand...
Click to collapse
QQ
Again I don't think my list is too demanding. Some issues are pet-peivish, I admit.
Click to expand...
Click to collapse
I'll address this in a bit
Stock battery life is fine with me.
Click to expand...
Click to collapse
Then run stock...
CM7 battery is looking respectable. But the phone fell flat on it's face before it could make it through one battery cycle to really know. When EVERYONE says GPS works I may give CM7 another go. By then my guess is a leaked GingerBread 2.3 will be out.
Click to expand...
Click to collapse
How did the phone fall flat on its face? GPS issues?
Basically what you're doing is you're "customering" the developers. You're wanting to take the best pieces of all of them and automagically jam pack them into one ROM completely tailored to your needs. The only way this is going to happen is if you dive in and start helping or you build your own ROM. This post would have served much better purposes had you asked if anyone knows of a ROM that does all of these functions instead of going out and slamming each ROM for what it doesn't have. Each dev is going to take their own work their own way and that's the end of the story. If you don't like it, you have a few options, do your own work or quit your *****ing. There are a lot of things that I would LOVE to see in CM but until I bust out my coding chops or start adding to the development table, there's not much I can really do except thank him for his work, donate, and be happy that there are a ton of people out there donating their time to making this **** better.

I've been having the same problem. Calkulin's is the closest I have come

Decision point on HC downgrade .

Feels like most of us are sufficiently fed up with ICS fiasco.
Some of us are lucky enough to have NVFlashable TF101s.
I am feeling like calling it quits and downgrading to HC, following
http://www.tabletroms.com/forums/tr...stock-3-2-recovery-roms-unbricking-tools.html
The latest upgrade from ASUS didn't address the reboots, SODs & other issues.
I want to return to what I had just a few short weeks ago: a rock solid, pleasure-to-use tablet I could rely on 100% of the time, not the ICS cripple.
To ze barricades ?

rashid11 said:
Feels like most of us are sufficiently fed up with ICS fiasco.
Some of us are lucky enough to have NVFlashable TF101s.
I am feeling like calling it quits and downgrading to HC, following
http://www.tabletroms.com/forums/tr...stock-3-2-recovery-roms-unbricking-tools.html
The latest upgrade from ASUS didn't address the reboots, SODs & other issues.
I want to return to what I had just a few short weeks ago: a rock solid, pleasure-to-use tablet I could rely on 100% of the time, not the ICS cripple.
To ze barricades ?
Click to expand...
Click to collapse
I honestly think you need to stop whining about the Asus firmware and how ****ty ICS is and give AOKP or Team EOS ICS a try. It will change your perspective entirely, because they actually just work - very well in fact.
If there is one most important thing I've learned about Android, its this: hardware manufacturers can't write software for ****. The AOSP versions of Android simply blow everything else out of the water in terms of reliability, stability, and performance. Give it a shot. You won't be disappointed, I promise. Make sure you WIPE your tablet first, and perform a backup before starting, obviouisly.

rashid11 said:
Feels like most of us are sufficiently fed up with ICS fiasco.
Some of us are lucky enough to have NVFlashable TF101s.
I am feeling like calling it quits and downgrading to HC, following
http://www.tabletroms.com/forums/tr...stock-3-2-recovery-roms-unbricking-tools.html
The latest upgrade from ASUS didn't address the reboots, SODs & other issues.
I want to return to what I had just a few short weeks ago: a rock solid, pleasure-to-use tablet I could rely on 100% of the time, not the ICS cripple.
To ze barricades ?
Click to expand...
Click to collapse
No more upgrades for me unless Asus makes an advance announcement and provides a list of changes, improvements and what nots. Seems like we're being kept in the dark without so much as a hint of things to come. This lack of communication is not only frustrating, it's an attempt at improvement that for some of us creates a major setback.
Is there an Asus website that gathers problem cases from users and corresponding solutions that work? Would be nice if we can all just look up a problem and be directed at the right person/place for help.

a.mcdear said:
I honestly think you need to stop whining about the Asus firmware and how ****ty ICS is and give AOKP or Team EOS ICS a try. It will change your perspective entirely, because they actually just work - very well in fact.
If there is one most important thing I've learned about Android, its this: hardware manufacturers can't write software for ****. The AOSP versions of Android simply blow everything else out of the water in terms of reliability, stability, and performance. Give it a shot. You won't be disappointed, I promise. Make sure you WIPE your tablet first, and perform a backup before starting, obviouisly.
Click to expand...
Click to collapse
No, really, Asus needs to fix ICS!!! We shouldn't have to go around trying tons of different ROMS to get something stable. We need to keep complaining to Asus!
That's like saying if the engine in your new car is having problems, don't complain to the automaker - just put another engine it! That's BS...
Sent from my Transformer TF101 using Tapatalk 2

jtrosky said:
That's like saying if the engine in your new car is having problems, don't complain to the automaker - just put another engine it!
Click to expand...
Click to collapse
This.
Moreover, last time I took a cursory glance at third-party AOSP builds they were all signed with the infamous AOSP testkey or built with ro.secure set to 0.
Sorry, but the security tradeoff far outweighs the (supposed) benefits.

There's a difference between free software and expensive engines..
And I will once again say, like I did in all other ICS complaint threads (stop making them..), my tablet works fine as intended. ICS is a huge relief from the (now terrible) Honeycomb interface and bad performance. Sure I have a reboot once in 14 or 15 hours, but is it a problem? No, because it happens either during the day or when it's in my backpack and never really during using it.

No_u said:
... like I did in all other ICS complaint threads (stop making them..)
Click to expand...
Click to collapse
Hey didn't we go to different schools together? I think I have seen this before in maybe 15 other threads.
OP if there is something useful with your post, please make it so, otherwise this thread will go no where, just like all the others.

No_u said:
There's a difference between free software and expensive engines..
And I will once again say, like I did in all other ICS complaint threads (stop making them..), my tablet works fine as intended. ICS is a huge relief from the (now terrible) Honeycomb interface and bad performance. Sure I have a reboot once in 14 or 15 hours, but is it a problem? No, because it happens either during the day or when it's in my backpack and never really during using it.
Click to expand...
Click to collapse
Hmm, excuse me, but I PAID for my Transformer - regardless if Android is free or not, I bought a products that was supposed to work properly. Right now, it doesn't.
I'm glad you are not having issues, but you are in the minority!! So just because you don't have issues, we should be happy?? Give me a break...
Sent from my Transformer TF101 using Tapatalk 2

jtrosky said:
Hmm, excuse me, but I PAID for my Transformer - regardless if Android is free or not, I bought a products that was supposed to work properly. Right now, it doesn't.
I'm glad you are not having issues, but you are in the minority!! So just because you don't have issues, we should be happy?? Give me a break...
Sent from my Transformer TF101 using Tapatalk 2
Click to expand...
Click to collapse
I agree with Jtrosky. You guys should be pissed as Hell. You should complain until your voice is raw and you get what you expect.
I only disagree with your coming to XDA to do it.
We are a modding community. One that is built for the devs, and only the Devs. Devs, who, I am sure, don't care that you have an issue with your device.
This isn't an ASUS forum. Complain to ASUS
This is forum clutter and needs to be closed and removed.

Alright I give up then. If you guys aren't willing to try an option that actually works, is free, and is EASY - fine. I was trying to be helpful and suggest a path that does work, but apparently you guys would rather just complain instead of actually doing something about it.
BTW, you realize that Asus has their own forums for supporting Transformer Tablets. If you really want to whine to them about their ****ty firmware, that is the appropriate place.

To answer your question, yes, downgrade to Honeycomb if you want. It's not going to kill you to not be on ICS. I don't think there's a single app out there that requires ICS. Upgrade back when you feel like it.

People are not complaining just to complain. They have a valid gripe. And whether you like it or not, the complaining on XDA got Asus involved (on XDA as well), so I see no reason why we can't discuss it here. You say we're complaining, we say we're giving feedback...
I've pleaded with Asus to PLEASE allow folks to downgrade to Honeycomb in an easy, support way. If they do that, this problem goes away. People have the option then. Stable or Cutting-edge...
Sent from my Transformer TF101 using Tapatalk 2

jtrosky said:
People are not complaining just to complain. They have a valid gripe. And whether you like it or not, the complaining on XDA got Asus involved (on XDA as well), so I see no reason why we can't discuss it here. You say we're complaining, we say we're giving feedback...
I've pleaded with Asus to PLEASE allow folks to downgrade to Honeycomb in an easy, support way. If they do that, this problem goes away. People have the option then. Stable or Cutting-edge...
Sent from my Transformer TF101 using Tapatalk 2
Click to expand...
Click to collapse
Well, I reported the thread as spam and clutter. If they leave it open then I guess you are right and ill stop trying to get peeps to stop posting out about it. If they close it then how about you do the same and stop helping to clog the forum.
Sorry Guys whining about subjects like these is never productive... it may be cathartic , but not useful to the forum.........
...........THREAD CLOSED..........

EU bug

I keep on hearing this EU bug here and there .....I have some questions regarding this .....
1,why does this happen?
2,will it affect only vibrant running ics or even jellybean?
3.how can I bring back my vibrant to normal? (don't post me regarding those guide I need breif steps).........thanks for helping

Answers (sort of):
akarshfrevr said:
1,why does this happen?
Click to expand...
Click to collapse
1. No one knows why it happens yet. Seems the earliest case had been around February for the Vibrant (before it got a real name like EUbug. Happened to Jasonhunterx)
akarshfrevr said:
2,will it affect only vibrant running ics or even jellybean?
Click to expand...
Click to collapse
2. There has been a crap-ton (this isn't metric or imperial but is a valid form of volume in my realm) amount of speculation, attempts, theories, support, more speculation all in the [Guide] Encryption Unsuccessful - Reset Android thread in the Captivate side of things. Me, Yosup, Mr_Psycho, DerT, Silvercrown, Swehes,...have all contributed to it over time but no one can get to the *root* of the problem. Even Adam Outler and Cyanogen themselves don't know why. There is also a Reference thread going too and is located here ---> [REF][ICS] Encryption Unsuccessful Reference
Here is a recent post I had over there with a brief synopsis of devices effected and ROMs/Kernel.
Bottom line, is there is no solution yet, although some users have reported getting their /data back but have no idea why or how. Further bottom line would be, if you don't want to get hit or roll the dice with the EU bug, STAY ON FROYO OR GB builds. **Sorry for the Bold CAPs but that is an important part that many should read. So far I haven't heard anyone on JB get hit with it, but that doesn't mean it isn't out there. Was Months before ICS users realized what was happening and then it was too late.
akarshfrevr said:
how can I bring back my vibrant to normal?
Click to expand...
Click to collapse
Short answer: You can't (yet). Some really bright minds are working on it but many users on both sides have left the Vibrants and Cappy's behind in pursuit of newer and shiny models. I fear that we might not find a solution and if we do, this device will be close to 3 years old and while it still rocks hard, is considered a dinosaur in mobile phone tech. And that to me is too bad.

agreed @ WOOD im yet to upgrade /update or renew my contract with Tmobile i dont know what i want to do anymore ever since the Vibrant it was like now all i think of is ..is there DEVing going on with this and that phone lol i wanted the Blaze 4g because the dual core SNAP Dragon s3 but i saw little to no dev on there still trooping out the Vibrant hardcore lol with great deal of DEV's was so sad to c FISH leave my heart SANK lol

Woodrube said:
Short answer: You can't (yet). Some really bright minds are working on it but many users on both sides have left the Vibrants and Cappy's behind in pursuit of newer and shiny models. I fear that we might not find a solution and if we do, this device will be close to 3 years old and while it still rocks hard, is considered a dinosaur in mobile phone tech. And that to me is too bad.
Click to expand...
Click to collapse
Since it happened to me also (read my testimony here), I could say this bug is somehow reversible UNLESS ONE HITS THE "RESET PHONE" BUTTON. Do not press it! Pull the battery out and boot to recovery through button combo and restore a nandroid. If you are a flasher and not a noob, always keep a working nandroid backup (it saved me). I'm not sure if I could flash anything else, perhaps it's the same flashing process somehow getting corrupted?

ioancr said:
... I could say this bug is somehow reversible UNLESS ONE HITS THE "RESET PHONE" BUTTON. Do not press it! ...
Click to expand...
Click to collapse
I never pressed Reset (and knew beforehand not to thanks to advice from Woodrube, et al) ... yet I still succumbed to EU.
No one knows a sure fire way to make this "reversible" unfortunately. Those who have had their internal sd's restored seem to have been more lucky than anything else - ie. there's no common thread to link nor duplicate their results.
Maybe one day, this thing gets figured out.

yosup said:
I never pressed Reset (and knew beforehand not to thanks to advice from Woodrube, et al) ... yet I still succumbed to EU.
No one knows a sure fire way to make this "reversible" unfortunately. Those who have had their internal sd's restored seem to have been more lucky than anything else - ie. there's no common thread to link nor duplicate their results.
Maybe one day, this thing gets figured out.
Click to expand...
Click to collapse
Wow, I didn't know that, it seems really worse than I thought of. Sorry if I ask it, but you still were able to get to recovery weren't you? Also, did you have a nandroid backup to try a restore?
Then I was yes very lucky, sorry for you guys and hope someday someone will save your phones too...

ioancr said:
... Sorry if I ask it, but you still were able to get to recovery weren't you? Also, did you have a nandroid backup to try a restore? ...
Click to expand...
Click to collapse
Yes, I could get to recovery, but I couldn't mount the internal sd anymore (and haven't been able to yet to date). So, I couldn't restore a nandroid backup or flash any of the roms I had downloaded on the int sd.
The vold.fstab emmc swap method at least let's me use the phone normally (albeit without the int sd), but I'm keeping my fingers crossed Woodrube & The Gang figure out how to restore access to the int sd ... some day.

I got scared by this bug i left ics itself and now I'm running helly bean ...........I don't have an ext memory card and should I get one? you know just in case if something goes wrong I can use the roms from ext memory card or nandroid backup and come back to normal ...........

This bug appears to be similar to the emmc bug on the note. Essentially, the eprom (programmable chip) on the motherboard of your phone.... for some reason it writes additional bits of code (like 2 bits or 8 bits) on the chip which then basically changes how the cpu sees the index... which then Bricks the phones.
Like Woodrube said...... The Vibe is 3 years old and it Totally Amazes me how great this phone really is.......... it is one of the few that could get ICS or JB ....... think about it this thing was released with Eclair (2.1)...... and still running like that lil bunny......
Oh and BTW CONGRATS TO WOODRUBE..... He is now the latest addition to the Moderator's group here at XDA Congrats to Woodrube.
:victory::victory::victory::victory::victory: ~~~~~ oka1
Woodrube said:
Answers (sort of):
Short answer: You can't (yet). Some really bright minds are working on it but many users on both sides have left the Vibrants and Cappy's behind in pursuit of newer and shiny models. I fear that we might not find a solution and if we do, this device will be close to 3 years old and while it still rocks hard, is considered a dinosaur in mobile phone tech. And that to me is too bad.
Click to expand...
Click to collapse

oka1 said:
... Oh and BTW CONGRATS TO WOODRUBE..... He is now the latest addition to the Moderator's group here at XDA Congrats to Woodrube.
:victory::victory::victory::victory::victory: ~~~~~ oka1
Click to expand...
Click to collapse
:thumbup::thumbup: Congrats, Woodman!! :thumbup::thumbup:
Very worthy bump-in-pay-grade for one of the all-time "counselors" that roam these halls. Great to see that good guys do win.

Note: I'm not sure if the following information is 100% valid for our device, but I've been digging into the problem and how others have gotten it.
How to reproduce:
- After bootup perform sudden power removal
- boot-up interup and reboot.
Click to expand...
Click to collapse
Yup, with encryption support in ICS, Android has become a lot more
picky about having all the filesystems initialized with valid data,
and mistakenly assumes that anything that's not zero or valid is
encrypted, refusing to go any further.
In Gingerbread and before, anything that wasn't valid was expected to
be invalid, and Android would just re-initialize it, regardless of
whether it was zero or not.
Click to expand...
Click to collapse

theexel said:
Note: I'm not sure if the following information is 100% valid for our device, but I've been digging into the problem and how others have gotten it.
Click to expand...
Click to collapse
Interesting stuff. I wonder what would cause part of the file system to become invalid though, seemingly during normal usage.

Not trying to thread jack but I read this quote on team-passion by the dev:
The encryption bug is due to a partition going bad. If it happens to the internal SD then you're done. It's not an ICS bug. It happens on all ROMs and all phones. ICS makes an effort at fixing it. Previous versions don't, or don't make themselves apparent. Bricks have been happening for ever. The Vibrant is 2 years old. Hardware fails. Just like in your PC. This kind of error come up on stock OTA updates, on other devices, as well. Not for SD, as far as I could find. But OTA updates of ICS are for new devices. If there are any corruptions the phone gets returned
Click to expand...
Click to collapse
Is there any truth to this? Can the EU bug happen on any rom? Is ICS as safe as any other rom?

crazexr7 said:
Not trying to thread jack but I read this quote on team-passion by the dev:
Is there any truth to this? Can the EU bug happen on any rom? Is ICS as safe as any other rom?
Click to expand...
Click to collapse
till date it has only occurred on ics roms ......jb roms not even a single case reported .....I'm hoping it won't come to jb .....I got scared by this bug and I moved from ics to jb .......2.2 and 2.3 are safe to escape from this bug

crazexr7 said:
Not trying to thread jack but I read this quote on team-passion by the dev:
Is there any truth to this? Can the EU bug happen on any rom? Is ICS as safe as any other rom?
Click to expand...
Click to collapse
No, there is no truth to this (see my earlier post in this thread for more info).
Not 1 single Froyo or Gingerbread build hsa ever gotten the bug (fact).
The EU bug occurred in early ICS builds for the first time (fact).
It occurred more frequently in Passion versions b1-v13 more than any other ROM out for the Vibrant (fact).
Sounds like there is some spin doctor action going on over there (speculation based on fact).
No one has yet to figure out why,how or when this happens. BUT, it is not from hardware degradation, except for the very small chance that overclocking puts extra heat and strain on the Nand chip (fact and speculation).
Ok so OKA1 said something about the EMMC chip corruption on the Note (which he owns). I was allocated my new forums and lo and behold, one was the Galaxy Tab 8.9 and guess what? They are having a major problem with....CWR and kernels that are making the machines nearly un-usable. Here is a link to the General section that might have some more info with it's multiple threads about the same thing (for now. Muhahaha!)

Woodrube said:
No, there is no truth to this (see my earlier post in this thread for more info).
Not 1 single Froyo or Gingerbread build hsa ever gotten the bug (fact).
The EU bug occurred in early ICS builds for the first time (fact).
It occurred more frequently in Passion versions b1-v13 more than any other ROM out for the Vibrant (fact).
Sounds like there is some spin doctor action going on over there (speculation based on fact).
No one has yet to figure out why,how or when this happens. BUT, it is not from hardware degradation, except for the very small chance that overclocking puts extra heat and strain on the Nand chip (fact and speculation).
Ok so OKA1 said something about the EMMC chip corruption on the Note (which he owns). I was allocated my new forums and lo and behold, one was the Galaxy Tab 8.9 and guess what? They are having a major problem with....CWR and kernels that are making the machines nearly un-usable. Here is a link to the General section that might have some more info with it's multiple threads about the same thing (for now. Muhahaha!)
Click to expand...
Click to collapse
ok so I'm running chimera v1.1 if I want to flash froyo again can I just flash a froyo rom from ics and be ok? or do I have to odin back to stock and go from there?

Gingerbread/Ice Cream Sandwich/Jellybean to Froyo with just a ROM flash = Brick waiting to happen.
ODIN back to stock, bud.

You can go from:
Froyo <-> Froyo:good:
Froyo -> Gingerbread :good:
Gingerbread <-> Gingerbread/MIUI:good:
Froyo/Gingerbread -> ICS/JB:good:
ICS <-> ICS:good:
ICS ->JB:good:
JB <-> JB:good:
ICS/JB -> Froyo/Eclair:bad:
Gingerbread -> Froyo/Eclair:bad:
Do NOT restore cross-OS Nandroids either. Meaning that you cannot restore a Froyo while you are on GB/ICS/JB.

Woodrube said:
You can go from:
Froyo <-> Froyo:good:
Froyo -> Gingerbread :good:
Gingerbread <-> Gingerbread/MIUI:good:
Froyo/Gingerbread -> ICS/JB:good:
ICS <-> ICS:good:
ICS ->JB:good:
JB <-> JB:good:
ICS/JB -> Froyo/Eclair:bad:
Gingerbread -> Froyo/Eclair:bad:
Do NOT restore cross-OS Nandroids either. Meaning that you cannot restore a Froyo while you are on GB/ICS/JB.
Click to expand...
Click to collapse
Thanks guys I'm going to miss ICS but it's just not worth keeping. I would love to flash to JB but GPS and 911 issues are scaring me away.

Did anyone with multitouch download a new ROM?

Did you find it cleared multi-touch issues or improved it at all? Some people say Cyanogenmod fixed things, but I'd just like more confirmation that it'd make a difference

fedreta said:
Did you find it cleared multi-touch issues or improved it at all? Some people say Cyanogenmod fixed things, but I'd just like more confirmation that it'd make a difference
Click to expand...
Click to collapse
I also have this problem. Tomorrow planning to flash on ParanoidAndroid or Cyanogenmod. Tomorrow otpishus the results.

**Menos** said:
I also have this problem. Tomorrow planning to flash on ParanoidAndroid or Cyanogenmod. Tomorrow otpishus the results.
Click to expand...
Click to collapse
I've never tried flashing a ROM before, my device is already unlocked/rooted. What do you do exactly to flash Cyanogenmod?

Just installed Cyanogenmod and saw that the problem is not solved. I fear starting to appear that the problem is hardware. Now have to wait for an update from Google.

IIRC, the screen issue is due to a firmware config that cannot be addressed by flashing a new ROM. An updated firmware package will have to be pushed via Google.

Tony_YYZ said:
IIRC, the screen issue is due to a firmware config that cannot be addressed by flashing a new ROM. An updated firmware package will have to be pushed via Google.
Click to expand...
Click to collapse
Did Google confirm this was the problem? I just need to make sure it is their problem before I go and swap it out since I have 1 more week to decide

fedreta said:
Did Google confirm this was the problem? I just need to make sure it is their problem before I go and swap it out since I have 1 more week to decide
Click to expand...
Click to collapse
From what I have seen, google is aware of all the big bugs and is working on a big update. Looks like screen flicker, multitouch, overheating, corrupted images on startup, gps, wifi performance etc are going to be fixed in a bugfix update. All the nexus devices start their lives like this, one of the few annoying things about being a nexus fanboy, you get to enjoy the bugs before anyone else gets to.
http://www.engadget.com/2013/08/13/2013-nexus-7-multitouch-bug/

fedreta said:
Did Google confirm this was the problem? I just need to make sure it is their problem before I go and swap it out since I have 1 more week to decide
Click to expand...
Click to collapse
I'm trying to remember the source of my information. But it was stated a few times that the second OTA is what causes the screen issues after powering your device up for the first time.

Tony_YYZ said:
I'm trying to remember the source of my information. But it was stated a few times that the second OTA is what causes the screen issues after powering your device up for the first time.
Click to expand...
Click to collapse
Yeah I remember this too, something about the kernel supplying not enough voltage to the touchscreen in an attempt to improve battery life. This has to be a kernel bug.

Try flashing a different kernel as that is what bridges hardware and software.

Aren't all kernels based on stock?
Sent from my Nexus 7 using xda premium

uprightbass360 said:
From what I have seen, google is aware of all the big bugs and is working on a big update. Looks like screen flicker, multitouch, overheating, corrupted images on startup, gps, wifi performance etc are going to be fixed in a bugfix update.
Click to expand...
Click to collapse
I would love to see that happen, but where do you see Google acknowledged and commited to fix all those problems?
If it is just speculation, that doesn't help folks who are within their return period and can get out instead of playing guinea pig.

sfhub said:
I would love to see that happen, but where do you see Google acknowledged and commited to fix all those problems?
If it is just speculation, that doesn't help folks who are within their return period and can get out instead of playing guinea pig.
Click to expand...
Click to collapse
According to the minions on their google+ "they are working on these issues". I by no means know that google is in fact going to be able to fix all of these issues, nor am I able to guarantee what they do, but I don't see that by repeating what their reps are saying is pure speculation. I think that judging by past examples anyone who has bought a nexus device at launch has either knowingly or unknowingly already agreed to be a guinea pig. In the end I am one of the last people to say that someone shouldn't return a defective piece of hardware, but it seems a lot of the issues people are having are being misdiagnosed as hardware issues when in fact they can (and most likely will) be fixed by an OTA.

I can dare to say that the issue is present in Android 4.3 affecting any device running it even Custom Roms I'm on CyanogenMod 10.2 on my d2spr (S3 Sprint) and the issue is present there too. Also that causes reboots too. I could be wrong too.
Sent from my SPH-L710 using Tapatalk 4
Team SXTP

Also the jss build is giving problems in the nexus 4 thread
Sent 4rm my Nexus 7 FLO... Only thing missing is O.G. N7's development...

uprightbass360 said:
Looks like screen flicker, multitouch, overheating, corrupted images on startup, gps, wifi performance etc are going to be fixed in a bugfix update.
Click to expand...
Click to collapse
uprightbass360 said:
According to the minions on their google+ "they are working on these issues". I by no means know that google is in fact going to be able to fix all of these issues, nor am I able to guarantee what they do, but I don't see that by repeating what their reps are saying is pure speculation.
Click to expand...
Click to collapse
No problem with repeating what they are saying, but you seem to have commited them to more than they are saying in their personal comments, not those as official reps.
IMO everyone should get accurate information so they can evaluate for themselves whether it is worth the risk to keep it or just to return the unit.
Personally I think the random reboots and GPS can be addressed in software and the multi-touch is probably 50/50 something that can be worked around in software, but everyone has their own tolerance levels for these kind of issues and "are looking into it or are working on it" and "going to be fixed" are quite different levels of commitment.

I'm sorry but what issues are you having because I exchanged my first n7 because I was having multitouch stuttering and issues with unresponsiveness which made the device unusable. The new device is okay.