yashsingh1/xdaforums huggingface dataset:
[Focus General] markcr:
Around 24 hours after upgrading my Samsung Focus (on Rogers) to Nodo, the phone started having a weird notification bug... I think it may be a hardware issue unrelated to NoDo but thought I'd post here in case any one else is seeing this or in case anyone has ideas on how to test/fix it.

Effectively the screen won't stay off and the phone keeps making a notification sound. If you push the screen off button within a second or two it re-lights and makes a "de-de-de" sound (and keeps repeating that sound randomly - anywhere from every half second to every few seconds...). This sound is exactly the same sound as when you plug the phone into the charger. I think the phone must somehow be triggering a charger notification for some unknown reason (note: the battery doesn't show changing nor does it drop down when it makes the alert sound).

What I've tried so far to debug this:

- Removed Battery, restarted phone

- Turned on Airplane mode incase there was some push notification causing it

- Tried fully charging phone (notification started happening when battery was around 1/3rd charged but still happens fully changed)

- Did a hard-reset - still get the sound with no applications installed/setup

- Checked the battery diagnosis menu (doesn't show anything unusual)

Only other step I can think of would be to do a restore from Zune... suspect this won't change a thing though. The phone had worked flawlessly for 4 months and this error started 1 day after installing NoDo - suspect that is just a coincidence though...

For some reason the alert seems to stop for a while (e.g. 5 to 10 minutes) and then restart. I can put the phone in vibrate mode to make it bearable, but battery life is getting drained...

Any one else see this before or having any ideas? Guessing the phone needs repair but thought I'd check.
[Focus General] JamesAllen:
Battery Icon

Yes, I have seen it. My Focus did the same thing, but I believe it may have been a battery icon notification. It has something to do with the mini USB port that is used for connecting to the PC. AT&T told me it is a known problem on Samsung phones but was supposed to be fixed in the update. Mine has stopped doing this but I know it can reoccur at anytime. I am waiting for the AT&T US update to see what happens. Try attaching to your PC, let Zune launch, turn off Zune, turn off your phone screen, disconnect your phone. You may have to do this a couple of times. For me, it stopped doing this whenever the plug was inserted in the phone USB port.
[Focus General] GrayWolf:
Did you happen to get the firmware update package that should be available after installing the March 2011 update?
[Focus General] AngelSpirit:
A firmware update? where?
[Focus General] phoenixnr:
I didnt get this update. Any rogers users that did? I unbranded nodo then rebranded and nodo again and nothing....
[Focus General] JamesAllen:
Update

When I was troubleshooting with the AT&T Tech Support Center for devices I was told it would be in the upcoming AT&T update for the Samsung. I had the impression it was the NoDo release specifically for the Samsung. You need to ask this question of Samsung users who got the NoDo release, more importantly, those users who may have had this problem.
[Focus General] markcr:
Thanks for the post James - good to know I'm not the only one! For me this only started after installing NoDo. I think your PC USB connection might be right/related as shortly before it happened, I had run the windows update checker again to see if there was a firmware update with the phone connected to Zune... (nodo had run fine for 24 hours before - there wasn't a firmware update so I'd just disconnected). Think the problem happened very shortly after that.

Still very odd that removing the battery and even doing a factory reset didn't fix it!

I have a call in to Rogers now to see if they'll swap the phone... may just be a configuation bug but travelling on business and figured if a hard reset didn't fix there must be something off in the hardware - now you have me wondering though! (the bug had stopped for a bit today... that said the notifications where somewhat intermittent).
[Focus General] JamesAllen:
Plug into USB

This does not help all the time, but when it starts that crazy "boinging" sound and the battery icon flashes, plug the USB port into ANYTHING. Charger, PC anything. It will always stop when plugged in, but sometimes, after removing the USB plug, it will remain "fixed" for a while.
[Focus General] LA Ted:
My Experience

A couple of weeks ago, this started on night and continued off and on thru the next day so I ran out of battery before I got home.

About a week later, it happen again.

When it happened the third time, I called AT&T Warranty Support. After a hard reset, the battery icon showed I was charging when I wasn't plugged in. They sent me a new phone, which is working fine, so far...
[Focus General] k-a-s-s-i:
I'm sorry, I know this is an older thread. I had this problem pre-NoDo and it is still persisting after NoDo. Has anyone found any sort of fix, or even just a way to turn off the battery notification? The only thing I've seen is to just plug/re-plug it in, try cleaning the port, and making sure the prongs aren't bent. I had figured NoDo would fix it, but no such luck. Is this more of a hardware issue or a software issue? Thanks for any info.
[Focus General] markcr:
Hi Kassi - I was fortunate enough to get my phone replaced under warranty (hasn't happened since). My thoughts are this is a hardware issue. Out of curiosity, do you (or the few others who had this issue), use any after market chargers (any cables that didn't come with the phone)?

I had a Monoprice Micro USB cable and wondering if it caused damage to the phone's connector port. The flat side of the cable's plug has bumps on it that are larger than the OEM cable and it makes a tight fit in the focus. I wonder if that somehow bent the port... what makes me suspect this is the problem started shortly after upgrading to NoDo and I'd used that cable for the upgrade.... (thinking it might have even started immediately after checking for a firmware upgrade using that cable...)

While it is handy to have extra cables I won't be using those again!
[Focus General] SharpGIS:
I have the same problem on my Samsung Omnia 7. Just suddently started happening when I didn't use the phone (many weeks after getting NoDo). Haven't found any fix for this (I'm in the US with a European phone, so a warranty replacement is a little bit tricky...)
[EVO 4G Q&A, Help & Troubleshooting] Sunsparc:
Just wondering if anyone else is having the same problem with CM7 and LauncherPro.

After rebooting, LauncherPro will hang for about 5-10 minutes before Android will force close it, or if I long-press the back key to manually force close it. It's only slightly annoying, since it functions properly afterwards, it would just be nice if there is a workaround or fix available so that I wouldn't have to do that after my daily reboot.
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
Sometimes it just happens, you may want to check you minimum frequency of your governor.
[EVO 4G Q&A, Help & Troubleshooting] Sunsparc:
Min: 245

Max: 998

Governor: Conservative
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
You can try smartass...and what kernel are you using?
[EVO 4G Q&A, Help & Troubleshooting] michaelvibe:
Yeah I am having the same problem. LP always forcecloses when I restart on RC4. Its not to annoying though.
[EVO 4G Q&A, Help & Troubleshooting] drmacinyasha:
Been happening to me since at least RC2, using stock kernel, minimum frequency of 384.

I'm pinging the devs to see if they know anything about it...
[EVO 4G Q&A, Help & Troubleshooting] Sunsparc:
Latest SavagedZen.

Conservative gives me the best battery life without sacrificing performance. From what I've read about smartass, I wouldn't like it.
[EVO 4G Q&A, Help & Troubleshooting] cordell12:
Try setting memory usage to "high" in LP settings.

Menu>Preferences>Advanced Settings>Memory Usage Settings>Memory Usage preset>Select High.
[EVO 4G Q&A, Help & Troubleshooting] drmacinyasha:
Word from on high: We need some logcats. When I get home from work, I'm going to be flashing N35, no GApps, install LP, reboot, and then grab the log.

Hopefully that'll light some fires under people's arses. ;D
[EVO 4G Q&A, Help & Troubleshooting] dw3bb10:
I have this issue as well.
[EVO 4G Q&A, Help & Troubleshooting] massivebasset:
Just chiming in that I too have this issue, also from about RC2.

Have used stock and Tiamat kernels, both exhibit the same behavior descibed in the OP.
[EVO 4G Q&A, Help & Troubleshooting] Sunsparc:
I flashed Tiamat but the problem still exists, so I'm going to say it's either LP or CM7. Testing out the memory boost for LP now.
[EVO 4G Q&A, Help & Troubleshooting] jedijackie:
I have had this same problem with both my old Hero and now the Evo. LP Pro always hangs 1-2 min at bootup. Alternating between conservative, ondemand, smartass does nothing. I used CM6 on Hero, CM7 & Destroyer on the Evo.

Does not hang when I use SprintLovers.
[EVO 4G Q&A, Help & Troubleshooting] Sunsparc:
Yeah didn't hang when I had Sprint Lovers or Myn's Warm. Def points toward CM7 for me.
[EVO 4G Q&A, Help & Troubleshooting] nate.spangler:
Done think its cm7 either. I've had the issue on a few nightlies but set min CPU to 384 and fix permissions in rom manager and its gone away. Wifeys never complained about it on hers and she complains about everything
[EVO 4G Q&A, Help & Troubleshooting] Sunsparc:
I'll try that out. The thing is, shouldn't the phone be running at full blast on boot? What would the min freq have to do with that?
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
If you have the "set on boot" option checked, then its running at whatever is set.
[EVO 4G Q&A, Help & Troubleshooting] Sunsparc:
I unchecked "set on boot" and moved the min freq up to 384, no dice still hangs.
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
Well you'd have to re-check it after its reset. Are you using a custom kernel?
[EVO 4G Q&A, Help & Troubleshooting] Sunsparc:
Ive used both SavagedZen and Tiamat. Using Tiamat at the moment.
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
Have you tried any other kernel? Your phone may not like it. I use Tiamat, soon again after I get my Evo back, and it hung up a few times, but with the newer versions, I never had the problem.
[EVO 4G Q&A, Help & Troubleshooting] Sunsparc:
I've been using a "beta" build of Tiamat that I was testing for cayniarb, v3.3.5. I've switched back to whatever the latest SavagedZen kernel is and it's still doing it.

Like I've said, I've changed everything but the actual ROM, so that's why I believe it may be something in it. Sense ROMs never gave me trouble with LP. Even changing the min freq to 384 and fixing permissions from CWM didn't help.
[EVO 4G Q&A, Help & Troubleshooting] Abstract520:
Try running rom manager and click on fix permissions and see if that helps.
[EVO 4G Q&A, Help & Troubleshooting] Sunsparc:
You didn't even read my last post, did you?

On a lighter note, after my third permission fix and updating to SavagedZen 1.1.0, the problem seems to be gone. Will report back with more findings later.
[EVO 4G Q&A, Help & Troubleshooting] Android 17:
I've had similar problems with LauncherPro and ADW for a long time. It used to happen to me on 2.2 as well.

For me, it seems to only last like 1 or 2 minutes, and then force closes and works fine afterwards, but it's happened for quite a long while.

Over the course, I've done full wipes, done fixed permissions, tried all sorts of kernels, and completely uninstalled/reinstalled LauncherPro and ADW.

It's a very persistent issue. It's not a huge deal, but still a bit irksome.
[EVO 4G Q&A, Help & Troubleshooting] Sunsparc:
Yeah that's the main point for me. It's slightly annoying but nothing huge. I've never been one to completely blow my lid over something on a cell phone, even less so since I've worked at Sprint.
[EVO 4G Q&A, Help & Troubleshooting] MrDSL:
LauncherPro doesnt FC on me but it takes awhile before it loads on first boot..its really weird and kinda annoying but seems fine after the first boot..

wish it got figured out..
[EVO 4G Q&A, Help & Troubleshooting] raiday:
Same Issue

Hello, I have the same issue with Launcher Pro and NSCOLLAB 1.0.39. Anyone else have find a solution to this could please post it on this forum?

Thanks
[EVO 4G Q&A, Help & Troubleshooting] raiday:
Solved

I have done a fix permission with Rom Manager and the issue disappeared.
[Milestone XT720 General] andemort:
Is there any chanche of this? Will MIUI be for our phone?
[Milestone XT720 General] syrenz:
I think Khal said either him or Dexter (or both?) were working on it. I might be mistaken, but I hope it happens. Checked out MIUI in it's full glory today on youtube and was impressed. Would be awesome to have it for XT720.
[Milestone XT720 General] mintaeroboy:
Prob. not :(
[Milestone XT720 General] sathoholic:
MIUI for XT720 is released!!!

There is MIUI for XT 720 is released!!! (sorry i'm Korean, so I'm poor at English)

Down load link is here

w1ww.megaupload.com/?d=3QI0U5I0 (Erase 1!!!!!!!)

or

w1ww.mediafire.com/?1ak7sdhs8q667oh

How to installation??

1. copy these files (first unzip!!)

2. Install UK 2.1 ROM (Use RSD)

UK2.1 ROM link (Erase 1!!!!!!!!!!)

w1ww.megaupload.com/?d=WJ4JZUKE

or

w1ww.mediafire.com/?ik579jqkvbtt1tj

3. Root the phone (Use Super One Click)

4. Install System Recovery by using OpenRecovery.apk

5. Run System Recovery

6. Choose Install recovery ( Superuser permission allow)

7. Choose Reboot Recovery

8. In Nandroid - Restore, Choose Miui for XT720, Restore All

*CAUTION*

Some problems was revealed (SD card, Wi-Fi, Usim, Senser, Language ...etc)

I'm not Rom developer!!!

This Rom was based on Dexter's Froyo
[Milestone XT720 General] sathoholic:
Sorry!!

This rom was very very very unstable!!!

so, when reboot, usually fail to boot!!!

Solution is...........try,try,try...and try until success
[Milestone XT720 General] syrenz:
Thanks... but having my phone be stable is more important than having MIUI :p

No chance for a stable MIUI for XT720? If not, what's the issue preventing us from gettting it? (not that I'd be able to do anything - just curious).
[Milestone XT720 General] sathoholic:
Um.... Sorry, I'm not Rom developer....so i don't know about advanced knowledge about this....

The reason why write post is propose XDA user's help.....
[G Tablet General] BoulderGeek:
I was excited to get a G-Tablet in the recent Woot sale. Unfortunately, as I have noted in other threads, when I got it, it wouldn't run through the original NTP-WiFi configuration procedure out of the box.

I wiped it and installed VEGAn 5.1.1 and got on with the process of evaluating it.

Am I the only one with touch screen sensor issues? It requires massive fingertip hurting pressure to hit the 'L' key and many of the touch areas along the edge that is adjacent to the Home/Menu/Back buttons. Sometimes I need to press so hard to register a key press, I think that it will crack the LCD. It really impacts my happy factor with this device.

The Market fix isn't as complete as my Archos 70. I saw the thread on changing device type=olympus. I can't vi the /system/build.prop without getting / set to read/write. Too much of a hoop to jump through right now. If I could vi the file, no problem. Still, it is an annoyance.

Weight. I knew it was heavier, but wasn't prepared to the reality of dealing with the mass of this unit.

Screen view. Even with an iPad screen protector on, the color and view angles are annoying. It was unusable to me for reading and regular use before the screen protector went on. Now it is better, but still subpar compared to the A70.

I want to love the gTablet for its technical superiority and future upgrade path to 2.3 and potentially beyond. My Archos device will never be better than FroYo.

However, even though I know it is 'better' I just can't stand actually using it. I feel that the gTab needs to go to flEaBay, since Woot doesn't do refunds.

Anyone else feeling this way?
[G Tablet General] tenet420:
Touchscreen callibration app should fix your touch issues... I had the same problem and that solved it.
[G Tablet General] BoulderGeek:
Yeah, I have the app and tried it. Not much real difference in my experience. :\

I just ran it again, and it is weird. Some areas of the screen work just fine (launcher pro dock when in desktop/finder mode for example). then, when on virtual keyboard, those same pixel areas don't sense well. Might be a keyboard issue, though it seems to be the same with BetterKeyboard and Android keyboard.

I don't know, I want to like this thing, but feel disappointed. Same way with the Samsung Captivate, which i returned after fighting with it for a month.
[G Tablet General] Tester30:
+1. Screen cal should help. Anyway, don't have that problem with TNTL 4.2.5.
[G Tablet General] blasturd:
I wouldn't mind a little tactile feedback or lighting for the 4 side touch buttons. They are hard to find in the dark. Some small protusions on the buttons themselves, or on the side of the case would also have been nice, like the bumps on a keyboard on the f and j keys.
[G Tablet General] goodintentions:
Haha, the 4 buttons in the dark issue was bothering me, too. I guess I stopped noticing it once I have it memorized. Just last night, I was reading before I went to sleep and noticed that I could press with 99% precision the buttons. So, yeah, it's not a problem for me anymore.
[G Tablet General] wd5gnr:
1. I have had "edge" problems that went away when I put a different wall paper up. Try a non-live wallpaper.

2. The Olympus fix works. It just breaks the web site seeing your tablet. Get Root Explorer and it takes about 2 seconds to mount /system rw.

3) I guess the screen is a personal preference thing. I like mine better since I put a urethane screen protector on. Really keeps the fingerprints off of it for the most part and the angles don't bother me.

4) The unlit buttons are a pain in the dark. I put some clear paper reinforcement stickers over mine so they have a little feel in the dark. They are almost invisible from any distance away but you can feel them. These are the little sticky holes you put on loose leaf paper when the holes have torn out. Oh, the other think you can do is get button savior in the market. This gives you nice onscreen buttons (although you know VEGAn has home, menu and back buttons on the status bar). Now the other problem is I tend to hit the buttons when I am trying to grip the tablet. There is a non-free app called remapper (I think) that can turn them off (or repurpose them) but I have not tried it.
[G Tablet General] BoulderGeek:
I don't disagree about the gtablet being a good value.

it's just slightly worse at everything than my existing Archos 70 tablet. So, for more money and double the specs, I didn't really get any appreciable improvement. Perhaps that's what I should have stated.

If I had no Android tablet, I'd be completely happy with my my VEGAn Tab.

However, i can't justify two tablets, and surprisingly, i don't think the gtablet is going to be the keeper. I'm just surprised that is the case.

I just did a factory reset, and will take pictures tonight for flea bay.
[G Tablet General] dfin13:
On the screen sensitivity issue, the one-touch app didn't work for me, and I was considering returning my tab. But then I did the calibration.ini trick, and the difference is amazing.
[G Tablet General] BoulderGeek:
Good to know. Thanks.
[G Tablet General] dfin13:
It may not keep you from selling it, but it sure will help the person who buys it from you :)
[G Tablet General] BoulderGeek:
I think that guy is sitting in the cube adjacent to mine. :-) He's been playing with it all day. Reinstalling the apps that i lost by resetting to factory. :D
[G Tablet General] lgkahn:
you guys do realized that vegan roms have the same buttons on the notification bar.. for just this reason.. to take the place of the side buttons at night.
[G Tablet General] Scott21:
I was personally about to sell my gTablet about 48 hours ago. I was having tons of lock-ups, market issues and was pretty frustrated.

I decided to start all over and reflashed to stock - did a lot of research here and just about have it working perfect with vegan 5.1.1 now. No lockups with flash, olympus thing fixed my market issues - it is simply an awesome tablet. I have had an ipad for a year and really like this in comparison.

If you don't want to put in the effort to modify the build.prop to fix the market it might not be for you though. It was not hard in retrospect but without any context it takes a while to really get familiar with some of the the things you are doing. I ended up using ADB to edit it - using root explorer sounds much easier.

I personally enjoyed getting it all setup right at the end of the day and learned a lot. For the price this thing is a heck of a tablet.

Also wanted to thank everyone for the hard work figuring out these fixes and ROMs - very impressive community!
[G Tablet General] goodintentions:
My take on this is that these fixes should take like 2 minutes to do. Very easy. The problem is that new users are intimidated by complicated instructions. Take the olympus fix for example. Took me less than 30 seconds to do. But because of the way people talk on here a new user would have to read thru 3 pages because nobody was willing to give a straight answer.
[G Tablet General] wd5gnr:
Granted, I'm verbose but I figure if you read the first part of the olympus thread and you knew what edit build.prop and change one line on it meant you wouldn't need or read the long detailed instructions.

There has to be a balance between talking to people who are Android fluent and helping ramp up new users, in my opinion.
[G Tablet General] lostpilot28:
You mean .05 .lbs heavier than the iPad, right? Or were you referring to the iPad2, which is .22 .lbs lighter than the GTab?

I think it's important for people to realize that the GTab COULD weigh less and be thinner, as could the Xoom, but then where would the SD card slot and USB ports go? I think the edges would have slight bulges in them to accomodate the ports. I'm actually fine with the weight of the G-tab...If I noticed a difference of 100 grams, then I'd have to seriously consider working out harder. :D

As for the other annoyances from the OP...I guess some seem legitimate, but I haven't noticed touchscreen sensitivity issues, etc. Mine is fast and stable and works great. Aside from the screen viewing angles, I love the GTab.

One last thing to note...I just spent a week using my GTab on vacation, and also used my daughter's iPad quite a bit, too. I know this is totally subjective, but the iPad seems more like a toy than anything else. I liked the screen, but otherwise was not impressed overall. I burned several movies from DVD to my GTab and it worked flawlessly. After surfing, playing games and watching 2 movies, I had 50% battery life left. Not bad!
[G Tablet General] goodintentions:
My first impression of the olympus thread was "what the hell?" sure I knew what you were talking about but for someone who's new to android and rooting something as simple as editing the build.prop could be the biggest stumbling block.

I know I have the reputation for hating newbies after my wooters thread. And thats fine. But people need to pay attention to their instructions to see if they make any sense to a newbie. Belive it or not i'm actually very friendly toward newbies. And believe me, the initial instructions in that thread make no sense to a newbie.

I am in the process of compiling everything into easy step by step instructions for the technical illiterates. Viewsonic gtab for dummies. I'll launch my website hopefully sometime next week.
[G Tablet General] goodintentions:
It's my experience that people will complain about anything/everything if something does not cost much.
[G Tablet General] Metal_in_Silk:
I'm not a tech illiterate but I am an android newbie. And you are SO spot on. I'll be watching for a link to your site.