yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] SteveCheeseman:
Soooo on this rom (happened on gr-12 as well but I never noticed noticed it on froyo roms) every single time I get a sms notification launcher pro crashes. I've installed, reinstalled, rebooted, reflashed, still no luck. Anyone got any ideas for a fix?
[Captivate Android Development] weldontimbo:
Just had to say this is the most stable GB ROM I have flashed to date having ran Mozaic and Continuum. Still find toichwiz to be flakey, but prefer Launcher PRO anyway. You have a new fan and I am spreading the word. Keep up the good work.
[Captivate Android Development] zippox180:
Hey awesome work excellent rom. Very smooth only problem i have is that i can't download anything. Im trying to download a cwm zip for jk4 but no matter where i download from it says unsuccessful.
[Captivate Android Development] climber1872000:
Download astro file manager from the market. Open the app and hit menu then preferences and check the download option at the bottom of the menu list.
[Captivate Android Development] ninjuh:
Text messages showing up in call logs

No file explorer

I flashed xcals non oc kernel for smoothness & stability, can't stand oc/uv just a headache

My phone gets very hot after little use, anyone else notice that?

Battery draining very fast as well.

I'm not trying to make this a negative post, just giving my feedback.

If this is a Final version of GB, I think we should all go back to using froyo :P
[Captivate Android Development] climber1872000:
File explorer: use polaris office or download one from the market.

I have been using this ROM for about 2 hours and have not had any issues with my device getting hot. I have uninstalled TW launcher and installed the Sony launcher, much better. I themed the battery icon, animations, and window colors to my liking. Drg8 you have done a great job with this one!
[Captivate Android Development] -Perp-:
Nice review. Some suggestions for your next review(s):

You could have shown some features that are unique to the rom you are reviewing. Like, instead of just showing the list of lock screen, you could have chosen both the 4-tab and miui and demonstrated how they look/work with and without audio controls.

And maybe talk about some of the apps that are included with the rom. Some roms will only have the bare minimum while other will have a lot of useful apps.

Also showing startup and shutdown (both animation / time) would be a nice addition to start and end your reviews.

Should help out other members who want a sneak peak of the rom before flashing it :)
[Captivate Android Development] jlt220:
It seems like some of these issues are special to you, also this isn't THE FINAL GB ROM, it is HIS/HER one and only attempt to put THIS rom together.
[Captivate Android Development] caleb4992:
does this color still exist?
[Captivate Android Development] sinichi21:
hmmm anyone getting a not enough space memory when you try to paste a framework? was trying to theme it out then paste the new thme framework though root explorer and it says not enough space and the framework went missing then i just flash the new one on cwm then went good
[Captivate Android Development] aintwaven:
You may want to re flash, and try the stock kernel. I have used it for two days and have tried all the GB roms. I think this is one of the best.

7hrs moderate use 86%
[Captivate Android Development] dhiru1602:
Have you included the Latest version of the Galaxy S II Lockscreen?

As per the latest version, the background window should be visible when the lockscreen is moved. I see from your screenshots that the background wallpaper is visible instead. So just wondering if you have ported the latest version or the older version.

I guess 9 lockscreens in a single release is un-necessary if they are not going to work perfectly when they are together. Instead you could upload different packages with different lockscreens as Addons. So that users can flash the Lockscreens separately based on their preference. I feel its better to have a Single perfectly working Lockscreen than to have 9 lockscreens with issues. The issues seem to be minor, but who knows what issue might pop up in the near future?
[Captivate Android Development] Not2LonG:
+1 totally agreed
[Captivate Android Development] DAGr8:
I m not to sure what to think of your intervention here ... Your entitled to your opinion although i prefer constructive criticism your are welcone to bash me in private all you want :)

What issues? there s no issues on any of them...

As i previously stated in your op i ported the one with no transparency its my preference.. I dont use locksounds either and unless its requested i dont intend to port it either

Fyi I personally change lockscreen s few times a day.
[Captivate Android Development] DAGr8:
Agree on what ?

you found any bug related to the fact they are all together?

cuz i have not
[Captivate Android Development] Dani897:
i just made a big mistake (an impulse buy) and got an infuse. im flashing this on my captivate then giving it to my brother. your roms will be missed! but im prolly gonna return the infuse and get another cappy, or sgs2 if it comes in the right timeframe.
[Captivate Android Development] -Perp-:
All the lock screens work for me too. Even better, all the lock screens have media controls too.

I like the variety of lock screens and appreciate all the work you put into your roms.
[Captivate Android Development] aintwaven:
I am sorry that people want to run down your work when it's free. This is my favorite GB rom so far.
[Captivate Android Development] itdiestoday:
Something to note for me anyways is that phone reboots when using the miui messenger unlock option. Tried three times, all same results.

Rom is nice though, has a nice solid feel to it. Will run this for a few days to see how battery life is.

Sent from my Craptivate
[Captivate Android Development] DAGr8:
hi , I ve seen this been reported numerous of times , cmon guys read the OP , at least the section where its says 'lockscreens explained ' , I mean I take lots of tiem just writing the OP you know :p

Anyways here is the answer : the miui messenger tab has been modified to be a custom one (using the lockscreen menu / custom app ) , witch means you can have it do whatever you want sms or shortcut or any other application , NOW if you DONT set it to a custom app , it will soft reboot your phone ..
[Captivate Android Development] Dani897:
that is not bound to anything by default, it is set be the same setting for the 4tab lockscreen. use the lockscreen app to set it to an app and it should work
[Captivate Android Development] welchertc:
Anybody know if this rom is flashable over Mosaic if I just clear cache and such?
[Captivate Android Development] DAGr8:
yes thats an issue . either do it via adb or make some space that rom is HUGE there is not much space left on the /system partition witch btw is what creates issues for some ppl when flashing....

shoudl be , some ppl have reported issues flashing over XCAL , bu I have tested many times and I have not .. maybe make sure you flash TALON before you flash my rom ... Factory reset phone before flashing definitely helps , becuz CWM sometimes fail at wiping doing it twice will ensure clean format (even tho the rom does wipe your phone ) ..

You know what they say about Formating drives , you can never do it enough to completely wipe stuff , so the more you do it the better /
[Captivate Android Development] Dlev7:
I was on CM7 and then flashed back to stock, then flashed JVB stock gingerbread, and then flashed X'Cals reoriented kernel to get CWM.

After that I flashed this ROM, and all went well but it will not boot up past the "Android" boot animation screen. And im not a noob when it comes to flashing JVB or JVH ROMs, or any ROMS for that matter, I was just on CM7 for fun recently.

But it has been there for about 10 minutes, do you recommend a re-flash of the entire ROM or did I do something wrong.

Thanks.
[Samsung Galaxy S (4G Model)] badb4lyfe:
Help anyone.... pls...!!!
[LG Optimus 2x] ski_power:
Hi,

I'm planning on buying the O2x (after returning the G2x). The screen bleed is bothering me. I just wanted to mention that I'm planning on buying from Expansys USA and was wondering about the screen bleed issue on the O2x.
[LG Optimus 2x] smokie700:
i never minded the screen bleed until most of the threads started up about them, then its like i couldn't help but noticing it more and more. from what was said some phones have it worse than others. MY O2X had bleeding at both top corners but was bearable.
[LG Optimus 2x] ski_power:
Yes, it has gotten worse on my G2x. I think the whole problem is that if you have screen bleed it gets worse over time.
[LG Optimus 2x] Cloudstrife:
Every LCD screen has screen bleed. It's only when the screen is totally black anyway...

Why would you stare at a totally black screen all the time to look for the bleed??
[LG Optimus 2x] MaRcIuPT:
you dont need to stare all the time, when playing games or some apps that have a black background is very noticeable and I saw when I had O2x, that is ugly.
[LG Optimus 2x] Mafs:
It only seems to occur badly on some units.

My LCD hardly has any bleed, just ontop at the very edge it's noticable.
[Xperia Play General] jdz7t8:
Ok so I have been searching for a way to disable the auto light feature on the Play because it's really dark, first of all, and it's really annoying, second of all. I read somewhere that I should get the "Adj Brightness" application and it would allow me to override the auto adjust feature on the Xperia Play regarding it's lighting, however, this did not work. Does anyone have a working way of keeping the screen at it's absolute brightest? Thanks in advance.
[Thunderbolt Q&A, Help & Troubleshooting] gemitero:
i was hoping to get some ideas on ways to set up my phone to minimize random reboots on the new radio, I tried changing kernels but had no luck. Any info would be greatly appreciated. Rom/kernel version and if you are OC and if yes up to what? 4g/3g? And if on cdma or something else Thank you:)
[Thunderbolt Q&A, Help & Troubleshooting] nerozehl:
I read that it isn't so much the phone, but rather the cell towers that were causing the random reboots (this was over in the TB General Forum)
[Thunderbolt Q&A, Help & Troubleshooting] gemitero:
That sux...guess im **** out of luck since the cell tower near me seem to suck and give me random reboots...hopefully the issues get resolved soon...thanks for the info:)
[Thunderbolt Q&A, Help & Troubleshooting] driphter:
I have found most reboots occur when over clocking past 1.3ghz due to voltage spikes or inadequate overvolting at 1.45 and up.

On cm7 and bamf I never had a reboot with either radio using imo kernels keeping oc under 1.42 and using smartass governor

Hope this helps
[Thunderbolt Q&A, Help & Troubleshooting] EEdaesung:
Usual location: West Los Angeles area

I have tried all combinations of radios and several roms available on XDA. I've never experienced a random reboot.

Baseband verison: 1.16.00.0402w_1

Kernel: bamf_4.4.7

build: Das Bamf 1.6.2 Remix

Software Number: 1.13.605.7

PRI Version: 1.41_002, 1.64_002 <- dunno if this matters for anything.

No overclock.

Can't think of anything else. I think I've been lucky.
[Thunderbolt Q&A, Help & Troubleshooting] Tidbits:
Bone Stock and has never rebooted on me as of yet. I live in the outskirts of a 4G tower and it flips in and out. I do have a slightly better battery life compared to before the update.
[Thunderbolt Q&A, Help & Troubleshooting] CJeep:
I've also tried a bunch of combos with no reboots, but I mostly run leankernel "normal" and das bamf remix. Never a reboot.
[Thunderbolt Q&A, Help & Troubleshooting] yareally:
I've never had a reboot using the latest radio (both the LTE and CDMA ones). Im just using BAMF Stripped and adrynalyne's 4.4.7 kernel without voice recording. No overclocking and ondemand governor. I think most of the reboots are probably just caused by overclocking/overheating.
[Thunderbolt Q&A, Help & Troubleshooting] aschnell:
i am running the BAMF roms. I upgraded my radio when it came out. I didnt have reboots for a week or so then i had random reboots and even had my phone just shut off a couple of times. I only have 3G and have the phone set to CDMA auto.

I changed the radio to the .7CDMA and .6LTE and havent had a reboot since?

In that time i also changed kernels and roms also, but did have a couple of days with the same rom/kernel after changing the radio to the .7/.6 combo.

I also did notice that my phone was on 3g revA even though it was set to use eHPRD. Verizon was messing with things and maybe that caused the reboots. Now that they turned eHPRD back on and pushed the update maybe they were the cause of the reboots and maybe it is fixed now?
[Thunderbolt Q&A, Help & Troubleshooting] kriskmk:
I'm running the latest stock everything.. no random reboots in over 3 days.
[Thunderbolt Q&A, Help & Troubleshooting] mike.s:
I'm running the new firmware and radio, rooted and crapware removed, but otherwise stock. No reboots in my local area.

Having said that, running the same stuff, I was getting reboots last week when I was in the Indy area. Based on that, and the timeline of events, I think this is what's happening (I posted basically this yesterday? in another thread):

VZW started rolling out the update, and recognized an issue. That issue was caused by an incompatibility between the software on some cell sites (VZW uses at least Nortel, Motorola and Lucent 3G BSSs, Ericsson and Lucent for LTE, maybe others) and the new TB radio firmware. They believed the root cause to be with the eHRPD software on some cell sites.

So, they stopped the update rollout. They turned off eHRPD. They upgraded the software on the problematic cell sites. They turned eHRPD back on. They restarted the update rollout. That all fits with what we've seen.

I wasn't getting reboots before at home, and I'm not getting them now. I think I'm on a Nortel BSS. When I was getting the reboots in Indy, they stopped when I reverted to the older radio firmware. From that, I assume that VZW uses a different BSS vendor to cover the area of Indy I was in, and the problem was with interoperability of the new TB radio with that vendor's BSS.

People are apparently still getting reboots. It may be Verizon didn't really fix what they needed. It may be that they only fixed one type of BSS, and need to address the issue on another type. They may have only fixed one of multiple issues. It may actually be an issue with the phone's firmware. eHRPD/LTE are new, and this is just some pain they're going through. You find problems when you have 100,000 users that you don't when you have a few hundred.

I don't know whether I'd get reboots today if I went back to Indy and tried again with the new radio firmware. I didn't have any problems switching between old and new radio f/w running my mostly stock image - YMMV if you're running someone's "ROM."

You can get just the radio firmware in this thread.

Finally, I suspect the reboot is caused by something like: phone tries to switch modes or negotiate something with the BSS (we know they're trying to make transitions work better, and that was the claimed reason for the radio upgrade). BSS doesn't respond as the phone expects. Phone retries unsuccessfully X times, then finally gives up and reboots.
[Thunderbolt Q&A, Help & Troubleshooting] gemitero:
The reboots would not have been to bad because it was occasional but the battery drain that happens is what I didn't like. Thank you everyone for their feedback.
[Thunderbolt Q&A, Help & Troubleshooting] nerozehl:
Heh, I just switched from BAMF 1.6.2 to CM7 alpha. Using latest radio leak and leanKernel extreme and I have had absolutely no reboots since switching ROMs.

(In no way should one infer from the previous statement that BAMF and/or Adrynalyne's kernels in any way definitively contributed to reboots. - I changed ROMs a day or so after the new firmware was pushed to unrooted phones.)
[Thunderbolt Q&A, Help & Troubleshooting] hacky486:
Literally, everything stock. I flashed the PB file flashboot, that's it. No reboots, and killer battery life. Half a battery got me through the day.

This is a replacement Thunderbolt...
[Thunderbolt Q&A, Help & Troubleshooting] dc iz 2 legit:
I had two reboots and both happend when my phone was running hot I live in AZ
[Thunderbolt Q&A, Help & Troubleshooting] carycooke:
Bamf 1.6.2 imoseyon lean kernel latest one not overclocked extended battery and in middle tn

Im in a 4g area at all times from home to work and town and I have never had any random reboots

My radio settings have always been on preferred 4g lte only

On new radio
[Thunderbolt Q&A, Help & Troubleshooting] drewfes:
Leankernel 2.4, bamf 1.6.3 remix with leaked OTA, live in LTE area but go into 3G frequently. No reboots ever. Not sure if this matters but I exchanged my phone a week ago due to the wireless radio getting stuck off. New one is working great so far.
[Thunderbolt Q&A, Help & Troubleshooting] dalrym05:
I have been overclocked dice day one on this thunderbolt and started noticing random reboots and I'm not on the newest radio. The weird thigh is I got a random reboot each time I go to my parents place where the signal isn't great by at the same time the other day I returned to stock clock speeds and haven't had a random reboot yet. So its kinda hard to narrow it down. But I'm going with lack of voltage during overlcocming to be the cause. Besides I can't tell a real world difference in performabce when overclocked anyways. Btw I'm using 4.4.5 kernel by adrynalyn.
[Thunderbolt Q&A, Help & Troubleshooting] ericatomars23:
No root. Before the update I had to do a factory reset because I had to data making my phone basically be a paper weight.
[Thunderbolt Q&A, Help & Troubleshooting] gemitero:
So I flashed the leaked radio the other night after 2 early reboots everything settled down and was going good. I was using PS1.4 rom and ziggys 5/3 kernel and its default max1036/122 min and no OC app. Changed the setting to cdma(prl) cuz I dont live in a 4g area and shortly after I started getting reboots again. Then I changed it back to evdo/cdma auto then no reboots. But the searching for 4g was affecting battery life and I didn't see much of a difference between stock and leaked radio except the battery drain. Gps and everything seemed to be the same so I decided to flash back to the stock radio which has been more stable for me and I could keep it at the cdma(prl) setting which is better battery life for me...so ill probably stick to the stock radio until we get 4g. And that is my experience:)
[Thunderbolt Q&A, Help & Troubleshooting] miketoasty:
Bamf 1.6.3 with imos normal kernel. No reboots what so ever after using the new radio for about two weeks now. Full 4g in my area as well with a strong signal.
[Thunderbolt Q&A, Help & Troubleshooting] the_happy_cannibal:
Currently BAMF 1.6.3 w/ control freak 2.0 kernel.

I've been using the new radio since it was posted here without a random reboot on different versions of BAMF with both adrynalyne's and Imoseyon's kernels.

At the edge of a 4G area at work, but never have a problem getting on and a 3G area at home.
[Thunderbolt Q&A, Help & Troubleshooting] lukesdiesel:
No Reboots here

Luke
[Thunderbolt Q&A, Help & Troubleshooting] thegeebo:
The reboots are caused by the radio update for sure, more specifically the new LTE radio. I was having random reboots when I updated the RUU, and decided to unroot and restore factory settings and trade in my TB for another one.

Got the new TB, updated the radio, installed Das BAMF (which was on the previous one as well). I have never had a random reboot since.

Every TB is different. I suggest trading yours in if the new radio gives it problems.
[Thunderbolt Q&A, Help & Troubleshooting] tanium:
I rooted and installed Bamf 1.6 remix.

Then installed 1.6.3 the next day on a brand new out of the box TB.

About 30 or 40 hours time without any reboot issue.

I just use the devs settings.

Life is nice that way :)
[Thunderbolt Q&A, Help & Troubleshooting] Mig1234:
I usewd the new RUU and have had no problems at all and battery life is outragious!!
[Thunderbolt Q&A, Help & Troubleshooting] loonatik78:
In my experience, some radios just do it and some don't. I've had reboot issues with the 1.68 radio a LOT, like 4 times a day at least. It was better, but I still had a few with the 2.07 radio as well. The 2.10 and 2.11 radios have been bulletproof for me so far. My setup is in my sig.
[Thunderbolt Q&A, Help & Troubleshooting] XDAThunderbolter:
On latest Synergy ROM with radio3 and couldn't be happier. Been running it for about 3 weeks without a single random reeboot. Had heat/charge issues with USB2PC once and reboot fixed it.

Haven't found a need to OC, so haven't tried.

Battery life is stellar, compared to others.

Straight 3g or occasional wifi. No 4g in my area so I turned the scan off. I also don't have any issues with OpenGarden tethering, however PDANet is picky at times.

I came from sitting with Bamf for awhile, tried Thunderstick for a bit, as well as a couple other Sense ROMS, but all had horrible random reboots. And it always seemed to happen when I didn't want them to (I'm a toilet power user :D).

I suppose for the night I can try some OC settings and see if anything bad happens. I just haven't wanted to mess with a good thing!
[Acer Iconia A500] tnfsmith:
How can we connect 3/4G via Sony Ericsson X2? I heart that tethering technology is connect from others support 3G/4G on A500 but I do not know how it work?

I need 3G connect for more convenience on the traveling. Who can tell any usb 3g can work on Android Honeycomb devices in common and A500 specify?

Thanks
[Acer Iconia A500] filnet:
Did you do a search on this topic? Try the post in the "Dev" section on this very subject, whilst not SONY specific, it's partially working for "some" USB 3G dongles on root'd devices.
[About XDA developers] paulcman:
I've been following Leedroid and updating with is releases. I wanted to post that I had donated in recognition of the nice fix he did for 3.06 tonight but obviously as a lurker I've been blocked.
[About XDA developers] the_scotsman:
new members are restricted from posted in development threads until they have 10 posts.

Maybe you could PM the dev and let them know in the meantime :)
[About XDA developers] Dirk:
Well played for donating. I think the dev will appreciate the sentiment more than the money maybe, as so few give while so many leech. Welcome to the forums too btw.
[About XDA developers] orb3000:
Once you make 10 posts all XDA features will be automatically unlocked
[About XDA developers] pixlz:
aw man, a whole ten posts? ::slides in another one nonchalantly:: @_@

~le poof~
[About XDA developers] ojdon:
Actually being a newbie myself I completely forgot about this place since it requires 10 posts in order to get into any real discussion. Why is the limit so high? I thought spam bots just do a single post then move onto the next forum? Unless there has been trouble before with bots posting in multiple forums?

The reason why 10 posts seem so high for someone new is that, well for me personally, I have to find topics where I can actually half help someone since I don't want to look like I'm spamming just to get my post count up. This is very time consuming, all I wanted to do is do a reply to a topic then lurk again until another question crops up which I can answer.
[About XDA developers] skumar9988:
^agree with you and I also feel a bit of this 10 post count stuff.
[About XDA developers] TheRomMistress:
Please see the thread "Postcount limit in developmental fora" for a full explanation on the 10 post min.
[HD2 General] T-Macgnolia:
Edit: I updated my Superuser app and my issue just disappeared completely. I know it was something I was not thinking about checking and never thought about the Superuser app being out dated or incompatible. You can also update your Superuser app by just looking it up in the Android Market.

Check out post #5 for more on what I did to solve my problem.