yashsingh1/xdaforums huggingface dataset:
[Nexus S General] simms22:
if you REALLY want your battery to reach 100% this is what you do. let the phone charge until it stops charging, unplug it from the charger, plug it back in, then continue charging it with the screen on. do not let the screen go off or it will stop charging. this method work, it just takes a lonooong time to reach 100%
[Nexus S General] navlem:
That method is called Bump charge. It's useful to bringing your battery to 100%

But do not do it often because it reduces your battery's lifespan.
[Nexus S General] soylukral:
I will give it a try. Thanks anyway.
[Nexus S General] kenvan19:
Umm your explanation is why people would see the phone as fully charged at 100% then unplug to find it at a lower percentage. That was because the battery had been fully charged but then stopped charging and had not hit it's bump level. Now however the issue is that some phones seem to just stop charging. Not sure where you got the idea that its bad for them to be fully charged but just think about that statement for a second.

Its bad for them to be OVER CHARGED. Fully charged (4191mV) is great but charging past that point may lead to battery over heating and catching fire as was demonstrated with the trickle charge kernels over on the evo 4g forums. This issue, the one being discussed in the thread is NOT just something people should accept. This is a bug that should be reported to Google.

Sent from my MIUI Nexus S from the XDA Premium app.
[Nexus S General] navlem:
I read it through this page

http://www.androidpolice.com/2010/1...bump-charging-and-inconsistent-battery-drain/

Though it might mention about the problem about "Showing 100% and instant drop after unplug from charger", but I reckon that Google is making Nexus S showing the true accurate charge.
[Nexus S General] kenvan19:
You reckon incorrectly.

I have battery graphs which show the phone is never reaching 100%, or was never reaching 100% (ironically, my phone actually was at 100% for the first time since 2.3.3 this morning). As I said, this is a bug not a feature. Phones should hit 100% then drop to a "bump level" (HTC seems to like 90% whereas I believe Samsung uses 95%) and then charge back up to 100%, as simms said, very slowly. It does this so as to not over-charge the battery because that can lead to severe over-heating issues and can possibly hinder the overall life of the battery. RogerPodacter was able to modify the battery drivers for the N1 so as to prevent this from happening (not quite sure what he modified) but because of the way that Samsung set up the NS battery drivers, this is not possible for us. Again, this is a BUG that should be reported to Google.
[Nexus S General] navlem:
Yeah, i might reckon incorrectly. Doing the bump charge now, it seemed to be really slow at charging from 98% onwards though.
[Nexus S General] JuWa:
I had this issue with galaxy s also with newer firmwares. It is NOT a bug, it's a FEATURE.
[Nexus S General] kenvan19:
LOL The battery not being able to achieve full charge is definitely a feature, ya sure. Absolutely. I can only use 95% of my cars petrol. That's a feature too. Definitely. My paycheck is only ever 95% of what I earned. Its a feature! People think about what you're saying >< a phone not being able to reach its maximum charge is a BUG.
[Nexus S General] JuWa:
Ehm... Are you stupid or something? What is those things got to dot with the battery CHARGING???
[Nexus S General] turbodroid:
The only real solution is to get a spare OEM battery or two and a wall charger to charge them in. The batteries last 2 to 4 more hours because when I plug one in its fully charged to 100%. Plus I rarely ever have to hook my phone up to a charger anymore. Swapping batteries is so much more convenient.

And I agree this 'feature' to save my $7 battery is not a feature at all. You can find extra batteries and chargers on ebay very easily.
[Nexus S General] maltloaf:
I agree with the above post 100%. Since I got a second (genuine) battery and an external charger, both of my batteries charge to 100% and appear to last longer. Since I started charging them in the external charger, they also now charge to 100% in the phone too. As I said in the other thread similar to this, I'm presuming the battery needed a full cycle and the charging circuitry in the phone just wasn't up to the job.
[Nexus S General] kenvan19:
Wow. Just wow. You don't even vaguely understand irony do you mate?
[Nexus S General] JuWa:
Oh, Americans... I just love you guys...
[Nexus S General] kenvan19:
Living in America makes me American, does it?
[Nexus S General] RogerPodacter:
I've looked to make the same driver changes to the nexus s as I did to the nexus one, but the battery chip model and driver is different so the same changes don't make sense.

I've gone on record saying that this issue with the nexus s not charging to 100% is NOT intentional, its a bug inherent with type of driver used in the nexus s. I just don't own this phone to edit the driver and test.

But there is a line of code which I feel if it was removed, this issue may disappear. I know not everyone agrees. But my nexus one will stay at 100% for an hour and a half, every morning. And my nexus reaches 100% every single day, I've never seen otherwise. So its not the way batteries are supposed to work. If it was, they would just make the top end lower and the 96% mark would be the 100% mark. Just my opinion. :-)
[Nexus S General] simms22:
my nexus one always reaches 100%, using wildmonks kernels, ravens kernels, and now redstar kernel. if you would like me to try something on my nexus s, edit/delete files. ill gladly help out :)
[Nexus S General] RogerPodacter:
Well testing for the nexus one I would pull down the source, make my changes to the driver code, and then compile and flash the kernel. I havent pulled the nexus s source yet, only looked at its repository. So if I get a chance I'll give it a shot. Of course if an ATT version comes out I may end up buying it myself:-)
[Nexus S General] tailsthecat3:
The battery is 1500mah while on the ID label of the device it clearly states 1440mah. Seems to me an explanation.
[Nexus S General] BrianDigital:
yes on the graph it just hangs at 95% from reading what people.are saying and being an electrician and now a eletronics tech. Even with power supplies and circuit breakers you never put either at its full potential.
[Xoom Q&A, Help & Troubleshooting] techniq35:
Has anyone else noticed the large amount of ghosting the Xoom display has? Its very prevalent to me, especially when a red or black object moves across the screen (red angry bird (especially when zoomed in), red icon on homescreen while scrolling (pew pew), black bars between gallery images, etc).

Its bothering me to the point of returning it (and looks like I'll have to eat the 15%/$90 restocking fee at Amazon). I'm wondering if the Asus Eee Pad Transformer or Samsung Galaxy Tab 8.9/10.1 will have a better response rate. I know they both should have a better viewing angle with their IPS displays.
[Xoom Q&A, Help & Troubleshooting] kindiboy:
I have an ISF certificate and don't see any ghosting...
[Xoom Q&A, Help & Troubleshooting] techniq35:
Really? Could it be I have a defective unit. I just find it hard to believe I would be the only one to have/see this.
[Xoom Q&A, Help & Troubleshooting] kindiboy:
Listen enable flash, then open this site on your xoom try to go full screen and tell me your findings.

http://www.prad.de/en/monitore/testsoftware/ghosting.html

Btw I have ghosting as well, but never noticed it on before. Thanks for the heads up. Ill reply back when I get more info.

I have no ghosting at all on my nexus one, the screen size have a huge effect on ghosting btw, but just an fyi.
[Xoom Q&A, Help & Troubleshooting] kindiboy:
2 Days ago I've been playing DoodleJump on the Xoom, and noticed the game running faster (you can test this) ofcourse you'll have to be familiar with the usual pace of it on the phone version of the game.

I've suspected the frame rate per second to be higher on the Xoom than the Nexus one...which could also be factored in, in refresh rate and then added to the whole performance. Which could spark problems like the ghosting we are seeing.(if you ever tried emulating a PXS on a PC you'll know what I mean)

I know that the screen response time could be a major factor but I couldn't get any information regarding the specifics of this screen. (btw you could be holding two Xooms with different screens)

So my guess for now, is the problem is with the refresh rate on the screen or the way the JIT compiler emulates...which could be solved with an update or a software tweak. Take what I said about the software side of this with a grin of salt :D
[Xoom Q&A, Help & Troubleshooting] jcaf77:
wow horrendous ghosting!!!!! (Using the ghosting test above)
[Xoom Q&A, Help & Troubleshooting] DroidBee:
Bumping this thread. Just noticed this on my xoom! Is it normal?
[Xoom Q&A, Help & Troubleshooting] DroidBee:
Another test : try going to http://tinyurl.com/xoghost and watch the drumsets at the bottom of the page and the guy in the second last row of second page ghost when you scroll the pages up and down.
[Xoom Q&A, Help & Troubleshooting] techniq35:
Sorry... just saw the responses to the thread. For some reason my email notifications were off.

I ended up returning my Xoom to Amazon while still in the 30 day window so I can't do any further testing. One of the primary reasons for returning was due to the screen ghosting (and overall screen quality). I've also got my eye on the Asus transformer with the IPS display, but it keeps getting delayed. I might just wait until fall reign the next wave of tablets come out... maybe something with a tegra 3 :)
[Xoom Q&A, Help & Troubleshooting] Selbmig:
I'm also seeing quite a bit of ghosting. Is this typical for xoom users?
[Xoom Q&A, Help & Troubleshooting] Kalavere:
It would seem so, It's absloutely terrible using the ghosting test linked. I'm getting a ghost the length of the actual cube trailing on my screen, in full screen. =/
[Xoom Q&A, Help & Troubleshooting] petsoukos:
ASUS Transformer doesnt suffer that much with the links you posted.
[Xoom Q&A, Help & Troubleshooting] boxmander:
There are two different panels for xooms, one being AU optronics brand (typically sited as the cheap/crappy display) and the Sharp brand display which is supposed to be better.

I have the AU Optronics display and going to the ghosting URL linked previously I get terrible ghosting.

Can anyone with the sharp display test this and see what they see?

You can determine the display type by typing dmesg into a term emulator.

Sharp panels say: 'lcd_manfid=SHP'

AU panels say: 'lcd_manfid=AUO'

Now since dmesg is the kernal ring buffer you might need to reboot before you see it in your dmesg output.
[Xoom Q&A, Help & Troubleshooting] zehkaiser:
I'm not surprised by the ghosting on these displays. Every mobile device I've owned has ghosted horribly. Even a lot of monitors around the office do it, but people don't seem to notice or care. I've always used 2ms displays at my home setup because of this. That being said, I paid about twice what other displays of similar size cost. People don't want to see the price of their precious electronics going up without seeing more nice specs on the list. A low response time display won't sell as well as a faster CPU or RAM... If you find a market that is looking at those 2 specs then make them great. Cheap out on the rest.
[Xoom Q&A, Help & Troubleshooting] boxmander:
Actually this ghosting effect is due to the speed at which the pixels can change from one color to another. Some displays have issues with different color transitions.

This is something that doesn't happen on my nexus ones amoled display. And most of my monitors that I have also don't have this issue, at least to the degree of the xoom. It is disappointing to see how cheap the xoom display is.

I bet my droidx doesn't suffer from this either.
[Xoom Q&A, Help & Troubleshooting] navossoc:
Maybe I'm crazy, but I began to notice ghosting on the screen, especially on the desktop after I upgraded to 3.2 Honeycomb.

If anyone can test whether the effect exists in 3.0 and 3.2, I appreciate it.
[Xoom Q&A, Help & Troubleshooting] smsmasters:
UK Xoom Wi-Fi only and I get ghosting too!

lcd_manfid=SHP
[Xoom Q&A, Help & Troubleshooting] okantomi:
Yes, there's some ghosting, but so what? What does it actually affect? I haven't found any effect whatsoever.
[Xoom Q&A, Help & Troubleshooting] smsmasters:
Doesn't bother me. Just posting my findings.
[Xoom Q&A, Help & Troubleshooting] okantomi:
I know...I wasn't shouting or anything ;^ )

I just think this ghosting thing is not a big deal.
[Xperia Play Accessories] marvi0:
jsut been playing with my play, and suddenly rememberd, the battery charging socket is on the side of the phone, not top or bottom, like the other phones, i have used so far, which i understand, because of its gaming feature, however, i think this will cause issues, with many car holders, whats your experience on this, cause all only have my car monday, and i cant help, but worry, about the possibility, of having to change this. Anyone seen a decently priced car holder?, in case, i might have to change mine.
[Xperia Play Accessories] svenk919:
You could use the official SE DK300 docking station, some ductape and a 12V car supply to usb adapter :P
[Xperia Play Accessories] Tornlogic:
DroidX's charge port is on the left side. I find that to be a great place considering the car dock is specific to the X. Maybe wait for a device specific dock?
[Xperia Play Accessories] marvi0:
ye i think i might have to do some diy on it then thanks for the suggestions, so its basically gone be a nightmare to get one,bummer.:mad:
[Xperia Play Accessories] neptune:
LOL
[Epic 4G Android Development] no2chem:
Bionic is libc for Android. It's a target for optmization because most android programs call into Bionic (functions like memcmp, memcpy, strcmp, etc. are all there) - making bionic faster would improve the speed of a lot of other programs at once. So far, 10-50% improvement seen in microbenchmarks on the optimized version of these functions.

changelog:

version 1.0:

-initial release

-backport changes from gingerbread (switches to v6 atomic instructions, faster strlen)

version 1.1 updates: <--current version

-updated memset, memcpy, memcmp, strcmp, strchr, strcat, strcpy, memchr to faster, optimized versions w/neon or DSP instruction support where applicable.

version 1.1: http://www.nuerom.com/bionic/update-1.1.zip

old version 1.0: http://www.nuerom.com/bionic/update.zip

to restore back to the EC05 version, run:

http://www.nuerom.com/bionic/restore-ec05.zip

Most likely it'll only work on something close to EC05, but I haven't really tested.

benchmark with 0xbench - http://code.google.com/p/0xbench/ (libmicro) to see improvements.

you'll need a bunch of binaries installed for libmicro, i've compiled them and provided an update.zip here that will automatically install these for you: http://www.nuerom.com/bionic/libmicro.zip
[Epic 4G Android Development] darkpoe:
Is this the same guy who rocked my wm 6.1 with his awesome mods?
[Epic 4G Android Development] Mutiny32:
Dude, you need to totally help out on the CM7 port for the Epic. Hell, what you're doing could go into the main CM7 git repo.

Simply awesome man and keep up the awesome work!
[Epic 4G Android Development] intx:
It is.

Holy crap.

Welcome no2chem O:
[Epic 4G Android Development] ecooce:
This is promising,now we have a couple more devs in the epic corner.
[Epic 4G Android Development] bryanfritz1:
With what I read of you and your return to the scene with a focus towards the epic, I see great things to come. Maybe someone could drop no2chem a dump of the nexus s 4g rom, I know someone that reads this could probably make that happen :-). Happy development felllas!

sent from "The Other Woman"
[Epic 4G Android Development] Esteway.619:
So do u go to ucsd?
[Epic 4G Android Development] Mutiny32:
This is also working just dandy so far. I don't have any benchmarks to back up any sort of substantial performance gains, but I'm sure the few tweaks you're doing here and there will add-up to a very nice user experience improvement. I have noticed that after this as and the davlik patch were applied, the interface seemed to be much more fluid and smooth without any annoying pauses you sometimes get due to scheduling.

So again, thanks no2chem and definitely keep up the badass work, mi amigo!
[Epic 4G Android Development] volDeus:
No issues so far, running for about 7 hours...
[Epic 4G Android Development] bigray327:
Thanks, no2chem. I loved your WM work.
[Epic 4G Android Development] drizek:
no2chem going to a school that specializes in chem?
[Epic 4G Android Development] p3dr0maz:
Test driving this too!
[Epic 4G Android Development] compuw22c:
Holy crap is right! This guy was KING back in the days of the TP2 (the last time I was privileged enough to own a device he was developing for). He actually seemed to disappear for a while (web page and from forums) so glad to hear he/she is alright and ready to produce some more amazing work. I am suddenly VERY OPTOMISTIC just knowing a great dev is on the task, particularly one that's been dealing with such intricate coding/mods (dude found a way to get extra memory available by disabling the camera, in a way that made the phone HUGELY more useful! For just one example...)
[Epic 4G Android Development] Whosdaman:
Well look who came out of the wood work! no2chem, long time no see. Been awhile since the Vogue days. I didn't even know you had a Epic or even left M$ for that matter!
[Epic 4G Android Development] hussmanne:
No2Chem = Epic community ftw! I loved your WM ROMs.
[Epic 4G Android Development] D3luSi0n4L:
I have to unfortunately say that I have not used your previous work but by the sounds of it your a very talented dev and I'm extremely happy to see you here! I am very interested in this "GreenDroid" project and will definitely keep updated on it! Best of luck with your developments, it seems as everyone says so far so good. Thanks again and I can't wait til there's a really noticeable performance increase!

Sincerely,

D3luSi0n4L
[Epic 4G Android Development] rjmjr69:
No2chem check your PM's please

Awesome work
[Epic 4G Android Development] Whosdaman:
I highly doubt he will join ACS Robert, he has his own team he works on and his own site.
[Epic 4G Android Development] jbadboy2007:
Lol. I bet he is trying to have him help with tv out. Which that would be awesome.
[Epic 4G Android Development] k0nane:
You know what they say about assumptions...
[Epic 4G Android Development] xTmDarren:
I agree.. No2Chem was all over the WM scene for us TP people.. This is awesome news seeing he's on the Epic forums!!
[Epic 4G Android Development] jbadboy2007:
What that everyone has one?? :-)
[Epic 4G Android Development] jnadke:
I thought you're leaving :p

I miss my Vogue, but I like having WiFi and Network Location support. As much as I could never get Vogue GPS working fully right (still a few mysterious crashes), it was still better than the Epics.....

So, no2chem, planning on dev work? The world is suddenly much brighter.

Now to hack an Epic onto Telecom NZ so we can import dzo/Martin :D
[Epic 4G Android Development] no2chem:
Ok, so it looks like I did find a benchmark suite that does indeed show there is some improvement with this new bionic version. 0xbench - http://code.google.com/p/0xbench/ implements libmicro, which benchmarks libc and syscalls.

for strcpy_10, we're looking at a 20% improvement on average, and strcpy_1k, we're looking 300-1000% improvement, not bad. Too bad no real program calls strcpy enough times to notice that much of a difference, but its a start =)

before:

<scenario benchmark="strcpy_10" unit="syscall-nsec" tags="exe:strcpy,">58 57 59 69 259 61 68 57 57 72 57 165 70 57 57 57 60 201 67 59 124 453 75 77 57 57 57 164 140 57 57 57 57 57 214 475 72 111 57 67 59 67 375 68 57 57 67 132 57 57 69 57 60 68 271 88 72 61 57 59 59 57 57 59 373 57 57 57 255 57 57 256</scenario>

<scenario benchmark="strcpy_1k" unit="syscall-nsec" tags="exe:strcpy,">13858 13399 3101 10490 7341 3594 5600 10896 11213 3311 5585 10197 3100 9655 3099 7234 12282 3372 6752 7382 10615 3101 3104 7162 3101 3104 10389 3378 3104 11137 7738 13370 11675 3410 11360 3100 4145 11232 14551 3384 12113 14820 7267 5177 3102 3117 12058 5631 10620 3375 3103 12634 3345 3104 9762 3099 14176 12945 4879 9809 13273 13371 3101 7055 10044 3100 15118 10757 5867 16109 4455 3104</scenario>

after:

scenario benchmark="strcpy_10" unit="syscall-nsec" tags="exe:strcpy,">43 58 43 43 60 137 43 43 54 92 43 43 43 95 53 43 48 43 45 92 43 51 53 50 43 54 54 43 43 262 43 45 214 43 43 47 43 43 43 46 43 43 43 633 43 43 43 243 43 43 43 43 256 43 45 46 43 44 43 209 43 43 43 43 836 49 43 43 43 61 53 217</scenario><scenario benchmark="strcpy_1k" unit="syscall-nsec" tags="exe:strcpy,">1284 1277 1266 1221 4832 1280 1222 1222 2216 2086 8667 3675 7336 1360 1221 1906 1226 1222 1354 7761 1462 4658 2379 1221 1421 1866 1221 1220 1362 5056 1469 1735 2056 1224 1366 2060 1284 1230 6198 2418 1222 1266 1221 1222 4007 1459 1224 1436 1229 3879 9052 1389 2578 1222 1221 7239 1497 1222 1559 1992 1222 1222 1299 5077 1273 1223 7085 1222 6081 2037 1276 1262</scenario>
[Epic 4G Android Development] no2chem:
Also, it appears the improvements in the atomic operations worked too =)

mutex, before:

<scenario benchmark="mutex_st" unit="syscall-nsec" tags="exe:mutex,">1033 258 592 477 258 246 247 246 247 246 702 501 844 246 865 1039 1133 420 901 246 614 339 1218 419 1370 387 641 556 1184 1156 276 472 1201 1109 664 365 246 461 246 363 246 931 246 338 493 938 246 1424 275 267 661 882 246 1012 748 246 246 322 261 246 758 252 246 1790 246 549 661 246 264 246 246 259</scenario>

after:

<scenario benchmark="mutex_st" unit="syscall-nsec" tags="exe:mutex,">114 111 111 508 111 111 470 111 112 111 118 111 111 111 113 113 111 111 132 333 111 111 111 111 111 134 133 172 309 111 131 416 135 129 111 111 480 133 443 116 139 111 111 111 303 406 111 353 130 117 473 132 111 111 111 116 115 111 130 441 134 111 111 130 111 839 135 169 135 676 140 111</scenario><
[Epic 4G Android Development] p3dr0maz:
Nice.. Great work sir!
[Epic 4G Android Development] Decad3nce:
@no2chem

You should submit your patches to AOSP or CM if there are significant gains to be found.

http://source.android.com/source/submit-patches.html

http://review.cyanogenmod.com