yashsingh1/xdaforums huggingface dataset:
[Motorola Droid and Milestone General] tuxor1337:
This is really strange. Maybe your busybox-file is corrupt.

Where did you download the busybox-file?

Which sbf did you flash?

So for explanation-purposes: When you put an executable or script file in any directory, you can execute it by first making it executable ("chmod 755 /system/xbin/busybox"), changing to that directory ("cd /system/xbin") and then executing it by adding "./" in front of it. The dot slash always stands for the _current_ directory. The _parent_directory has two dots "../".

If you want, you may try:

# /system/xbin/busybox --install

instead of

# ./busybox --install

Or maybe try this one:

# /system/xbin/busybox --install -s /system/xbin

Last time, I installed busybox into the directory /data/busybox, which worked brilliantly, but this path turned out to be unpractical. So I wanted to reinstall it in a different directory. I removed everything from /data/busybox including the directory itself and tried to start the whole procedure with /system/xbin. But that time it protested, that there were no files in "/data/busybox/...". Conclusion: The last busybox-install affected the second one. When I remember correctly I rebooted after that and used the app from the market *g*
[Motorola Droid and Milestone General] droidtech1:
My main sbf I flashed was android 2.1(uk version).

I downloaded busybox 1.17.2(won't let me post url here), was from droidforums dot net.

I don't remember if I tried all of his commands, but the last one on that forum seems to have worked.. I think......... it was:

"busybox --install /system/xbin/"

After remounting with your commands and typing the above command, I didn't get any errors, I synced and rebooted and now when I "ls /system/xbin" it shows a bunch of files/names which look like busybox commands. When I type "busybox" it outputs a bunch of commands too... so I am guessing this means it has succesfully installed? I can't say I tried these before attempting install so I have no comparison but I assume I would have a different output if busybox wasn't installed.

So assuming it worked, why would

"busybox --install /system/xbin/" work, and

"/system/xbin/busybox --install" not?

I also managed to install open recovery and do a nandroid backup succesfully :)

I have another short question, not specific to android but happens in all terminals I use, windows and linux alike. Sometimes I cannot execute commands anymore and it just becomes text in the terminal(just re-echo'ing my text output, without executing any functions)... can't remember specifically when it happened on my windows or linux pc shells, but on my android it happens whenever I have to give "SU" permission to the terminal, I have to quickly close the terminal and reload it again to get su access. I'm sure there is a name for this "state" where you are locked out of using commands in the shell and just typing text but I can't find a way to get out of it(without closing and re-opening terminal), there must be some key combination to be able to execute commands again in the current terminal session. If you have any idea what I am talking about?

Thanks for all your help so far.
[Motorola Droid and Milestone General] tuxor1337:
Don't want to try one of the 2.2?

Yes, this sounds very much like installation was successful.

typing "busybox" without the path in front of it worked, because busybox is in the directory /system/xbin, which is already in your $PATH-variable (try "echo $PATH"). So the command interpreter (shell) will automatically look up "busybox" in /system/xbin.

I had a look at the busybox syntax and it's actually

busybox --install [-s] [INSTALLDIR]

So you have to put the directory you want to install in at the end. That's what your last command makes use of :)

Sounds like this is just the state, when shell is busy, i.e. when the last process you started is still running and no prompt ($ or #) is displayed. You may kill the last process in linux using CTRL+C, which will hopefully bring back the shell prompt. No idea which shortcut replaces this on the milestone/droid. I never use any android terminals, but only the ADB-Shell: http://developer.android.com/guide/developing/tools/adb.html
[Motorola Droid and Milestone General] droidtech1:
I'm learning to build apps for android so I thought having 2.1 on my droid would be better for testing (instead of 2.2). I also have a Nexus-S with 2.3 and a tmobile-pulse with 1.5. So I want to keep the most native version on each phone since most consumers won't install custom roms, although some will get updates anyway.

I use my droid a lot when I am out and use the terminal a lot so having busybox too has given me more to play around with. I actually find my droid much better working on than the nexus s, love the keyboard and dpad.
[Nexus S Q&A, Help & Troubleshooting] RickROM:
Hello everyone,

I'm trying to figure out WTF happened to my phone this morning. My current setup is . . .

[ROM] [03/21] NSCollab 1.0.12 | CM 7 [N. #28]

[KERNEL] [GPL] Honity12/14 - cm7 VSV6+BLN V4 / modaco - 2.3.3 - full voodoo

. . . I left my house with a full charge to goto class . . . I noticed that the phone was getting hot in my pocket, but I was busy with school so I didn't have time to troubleshoot it. I should have rebooted it, but I assumed it was alright since the temperature reading said 104 degrees F.

I got out of class, and the phone would not boot at all . . . I started freaking out, but I got home and realized the battery was dead. This is what was supposedly causing the battery drain. Anyone have any ideas what happened?
[Android Software/Hacking General [Developers Only]] xxxsupastar:
I was using ultimate 2.5 rom and decided to install apps2sd. Ever since this install my phone doesn't see my sd. After a phone reboot it was stuck in a boot loop. I've tried a couple Sandisk sd cards. My Vista and XP machines recognize both cards as mass storage devices. I also reformatted both of them with Ext3 and also fat32.

All bootloops aside, I was finally able to get RSD lite to flash my phone back to stock 2.2. Still no sd to mount!!! I also did the OTA Verizon update with no luck. Instead of CW recovery I get the triangle with exclamation point. Please help end my nightmare.
[Omnia 7 Windows Phone 7 Development] slyevo:
Hi Guys

When i got my phone a few weeks ago i used Chevronwp7 to unlock it, I arrived home from a short break today and hooked my phone to my pc only to find that i am unable to unlock it again. I have tried everything i can think of ????

I am on 7004 firmware nothing has really changed on the phone, I have also tried to hard reset it but made no difference.

I would appriciate any help on this one!

Regards

Mark
[Omnia 7 Windows Phone 7 Development] UbiMaiden:
I have 7008, and the only thing thad worked for me was hard reset.
[Android Software Development] scatman25:
sorry for my english:D

here is a android 2.2.1 for GPAD G10...it works all, but the Battery shows only 100 % :confused: can someone fix the error in the rom?

http://www59.zippyshare.com/v/15244802/file.html
[Android Software Development] nikkel:
wooow ...it's good news ...!!!! :)

Can you give me some details ...what is work...what is doesn't work...
[HD2 Android NAND Development] hg3atintin:
On all roms there is a banding problem due to our screens 65 k colors.

But launcherpro fixes the banding problems on widgets :) But on some gingerbread roms it does not.

I have not made this fix.

But I have tested it on some roms. Im am just sharing this.

credit goes to Tytung

who took his time and fixed this in his latest 2.5 rom and GPC + other developers that may have found this already.

I have tried it on Tyweens cm7 rom, Tytungs rom and some other. But it "maybe" works on others to? Like gpc's one?

= When using launcher pro with this fix. The launcher will have no banding problems on widgets and on the homescreen. But other banding problems will still be there like it was before.

So without fix ,the clock widget will look like crap in launcher pro in tyweens cm7 rom. But with the fix it will look smooth.

The zip changes the libsurfaceflinger.so.

Flash in cwm.
[HD2 Android NAND Development] mydoooom:
Thank God, at last! Great stuff
[HD2 Android NAND Development] SH4YD33:
works on tyween cm7.
[HD2 Android NAND Development] mikentucson:
thank you! this is the main reason i switch some roms lol
[HD2 Android NAND Development] malaeus:
will this work on other HD2 NAND roms using launcherpro? like using hyperdroid CM7?
[HD2 Android NAND Development] iamgpc:
The source code

If you are a developer of source code maker, the following is my fix for banding issue. (NOT Tytung, i don't know how he fix it:( )

The source code path :

/frameworks/base/services/surfaceflinger/SurfaceFlinger.cpp

Function position:

sp<Layer> SurfaceFlinger::createNormalSurface(
const sp<Client>& client, DisplayID display,
uint32_t w, uint32_t h, uint32_t flags,
PixelFormat& format)
{
// initialize the surfaces
switch (format) { // TODO: take h/w into account
case PIXEL_FORMAT_TRANSPARENT:
case PIXEL_FORMAT_TRANSLUCENT:
format = PIXEL_FORMAT_RGBA_8888;
break;
case PIXEL_FORMAT_OPAQUE:
//format = PIXEL_FORMAT_RGBX_8888;
format = PIXEL_FORMAT_RGB_565;
break;
}

sp<Layer> layer = new Layer(this, display, client);
status_t err = layer->setBuffers(w, h, format, flags);
if (LIKELY(err != NO_ERROR)) {
LOGE("createNormalSurfaceLocked() failed (%s)", strerror(-err));
layer.clear();
}
return layer;
}

Modified code:

case PIXEL_FORMAT_OPAQUE:
//format = PIXEL_FORMAT_RGBX_8888;
format = PIXEL_FORMAT_RGB_565;
break;

Reason:

It is caused by the display driver is not match with HD2. The gingerbread has fix it on driver level with new pixel format RGBX_8888, however it is still not working for HD2. So we have to force the default pixel format into RGB565 :D
[HD2 Android NAND Development] tytung:
I think I need to clarify something.

Gpc sent a private message and asked me how I fixed the color banding issue on 27th March 2011, 09:50 PM.

P.S.: Admin can confirm this.

Because I was busy at that time, I replied his question by only giving him this link including libsurfaceflinger.so.

Then maybe he fixed this issue from the source code by himself, but he really got hints from me.

Let us go back about 20 days ago.

In fact, I tried to solve this color banding issue since 13th March 2011, and I shared my possible method in my thread.

http://xdaforums.com/showpost.php?p=12049180&postcount=2487

When I had time, I released a modified/recompiled libsurfaceflinger.so on 21st March 2011, and requested other users to test it.

http://xdaforums.com/showpost.php?p=12241393&postcount=2846

Then I included this .so file in my v2.5 ROM.

Gpc saw my change log and sent me a private message, and ...

That's the whole story.
[HD2 Android NAND Development] cbanbury:
what stops this being implemented throughout the UI (i.e. notification bar, buttons etc)?
[HD2 Android NAND Development] Imaginary Enemy:
I'm not getting 3g, only EDGE on this ROM. My APN settings are right and data is definitely on so I don't know what the problem is. I have a T-Mobile HD2 and T-Mobile. Please help.
[HD2 Android NAND Development] Blubster:
Tried this fix, and i am truly impressed! No longer banding using ADW Ex and even XDA App! It does not seem to "fix" only launcher pro to me! :)

EDIT : copilot still has banding though, but not a big deal given the improvements elsewhere! :)
[HD2 Android NAND Development] iamgpc:
humm,

Do you modify the libsurfaceflinger like mine? Do you compile with BOARD_NO_RGBX_8888 := true to fix this isse?

Because my libsurfaceflinger is changed for my personal using. I also modify somewhere else for my testing, so that I cannot use your libsurfaceflinger.

I don't know what you modify in your source code, so I have to find out the root cause.

According to Google search on "android color banding", you can find a JAVA solution on color banding.

http://stuffthathappens.com/blog/2010/06/04/android-color-banding/

It says the PixelFormat will take effect on banding issue. Take a look on surfaceflinger source code, you can find out the PixelFormat.OPAQUE and PixelFormat.RGBA_8888 will cause the different result.

Finally, you just have to modify the PixelFormat.OPAQUE from RGBX_8888 to RGB_565 :cool::cool::cool:
[HD2 Android NAND Development] tytung:
Yes, I compiled with BOARD_NO_RGBX_8888 := true to fix this issue.

BTW, you didn't know how I modified my source code because you didn't say that you want to see my modified source code in the private message.

Anyway, I only changed the color support of the config file from RGBX_8888 to RGB_565.

And you don't need to modify SurfaceFlinger.cpp because setting NO_RGBX_8888 in config file is enough.

Below is the detail.

Before Google released Gingerbread OTA 2.3.3, we could only use Froyo OTA's proprietary files to work with Gingerbread source code when we compiled AOSP Gingerbread 2.3.2 or 2.3.1.

And Froyo's proprietary files are not compatible with Gingerbread source code, so we needed to fix the RGB_565 problem by applying the following two commits at that time.

https://github.com/CyanogenMod/andr...mmit/d06cf2371b2db46ab4ecedea832e4c17f3591165

https://github.com/CyanogenMod/andr...mmit/baa078471f4198bd73819794f2713a845305a227

After Google released Gingerbread OTA 2.3.3, we used Gingerbread OTA's proprietary files to work with Gingerbread source code when we compiled AOSP Gingerbread 2.3.3.

At the same time, I removed these two commits above when compiling a new GB 2.3.3 ROM.

That's why hg3atintin (Thanks to him.) told me that my GB 2.3.3 ROM had the color banding issue but my GB 2.3.2 ROM didn't.

Finally, I added back these two commits and compiled a new surfaceflinger.so.

Then the color banding issue is improved.
[HD2 Android NAND Development] Rando81:
it fixed my launcherpro :P , calculator had severe banding but its fixed too

nice job mate
[HD2 Android NAND Development] ludetekniq:
How do I apply this fix to my AmericAndroid SD build? Any help would be appreciated...

P.S. I searched this thread and others and cant figure it out, please point me in the right direx... What is CWM btw because it says to flash with CWM?
[HD2 Android NAND Development] F-bone:
How does this banding look like?
[HD2 Android NAND Development] godutch:
edit: sorry wrong thread
[HD2 Android NAND Development] YZ:
nice! gonna try this out
[HD2 Android NAND Development] 666Duvel666:
Hi ludetekniq.

You're in the wrong place. This is NAND development forum and not SD development. You can only install this fix if you have a NAND Rom in your HD2.

;)

EDIT: CWM = Clockworkmod Recovery. It's a tool that we use, to help flashing and recover Roms on NAND.
[HD2 Android NAND Development] alaaassem:
silly question..lol

what is the banding problem? :))
[HD2 Android NAND Development] 666Duvel666:
Well... from what I understood, its an issue related to the color depth of HD2 screens. Our HD2 Android is displaying 16 bit color insted of 32 bit because of a driver's issue... it loses quality because it's displaying less colors. With 32 bit you will see a smoother color gradient.

Please devs correct me if i'm wrong!

Cheers from Portugal!
[Touch CDMA Android Development] rhan8706:
Hello guys so installing android on your Touch is very easy. The problem is that there are several ways to install this onto your phone and there is too much unnecessary information present on the web. I am going to show you the fastest and the easiest way to install Android. I get messages and emails with people having problems with installation. So I decided to make a video showing you how to install android 2.2 froyo on your phone. The steps are same for other android versions with the only difference is the androidinstall file.

[YOUTUBE]<iframe title="YouTube video player" width="480" height="390" src="http://www.youtube.com/embed/3uHmMmmwR6c" frameborder="0" allowfullscreen></iframe>[/YOUTUBE]

http://www.youtube.com/embed/3uHmMmmwR6c (in case the video doesn't load)

Please ask any question if they come up and if something is not clear in the video.

Good luck and thanks for your time.

Special thanks to Incubus26Jc for the 2.2 super foryo and NFSfan for WM 6.5.

If you like there work then please donate.
[Desire HD General] taunouibo:
Couple of days ago I noticed that my DHD's volume down button does'nt work anymore. First I didn't pay attention, thought that after restart it will be solved, but it didn't. The volume down function doesn't work in any software (up works just fine). Before I decide to go to warranty, what do you think, is it a software or hardware problem? There is no accidents or any damages happened, I know and physically the button seems to work. Please help!
[Desire HD General] Blackhorse:
Normally buttons are hardware, in your case its easy to tell.

remove the battery. Put it back in. Hold down the volume down then turn on the phone, if it starts normally your button is dead, if you get into bootloader mode it could be software and you should try reflash or wipe in settings
[Desire HD General] pappas99:
Im the same, except now my volume up doesnt work either
[Desire HD General] taunouibo:
Thank you so much Blackhorse!

Although the first try didn't succeed (perhaps I didn't hold both volume down and power button long enough), the second try started the bootloader and I was able to use both volume buttons. After another boot the stock rom started normally and now my volume down function is back! Hopefully it stays so...
[Desire HD General] insty:
Hey guys,

My volume keys have died. Part of the wire strip that is connect to the buttons is torn.

Any ideas if there is a replacement upperboard yet?
[Desire HD General] o reverendo:
having the same issue... going to try blackhorse's solution and see if it works

best regard

André
[Desire HD General] o reverendo:
unfortunately it didn't work. I guess the volue down button is dead, even though I had absolutely no accidents with it.

does anybody have an idea of how to solve this, since I live in Brazil, but bought DHD in Germany?

any help would be very appreciated

best regards

André
[Desire HD General] Locster126:
same problem here, my buttons stop working. What I usually do then is lift the volume keys up slightly and slide some paper underneath to clean some dust and then usually it works again (for a while)
[XPERIA X10 Q&A, Help & Troubleshooting] coconst:
Hi

i had 4.5.7 version and i want to upgrade to 053. Followed instrcuctions and I flashed through xrecovey 6.1.3 v05 and then v053 but in about phone it shows mod version 6.1.3 v05. I assume it would shoe v053. I flashed twice but still the same.

any help/suggestions would be appreciated.

I did not find anyone with a similar problem.

thx
[XPERIA X10 Q&A, Help & Troubleshooting] Vito Andolini Corleone:
If you got the arc launcher as the default launcher on flashing the rom then you have successfully installed v

53
[XPERIA X10 Q&A, Help & Troubleshooting] Vito Andolini Corleone:
And btw, in the phone mod version it will show v5 and not v53 so its nothing to worry about. All users have the same thing displayed. The arc launcher thing was to just reconfirm that you have v53 installed
[XPERIA X10 Q&A, Help & Troubleshooting] coconst:
thanks ady but the arc launcher was there from 4.5.7 anyway. any other way to check?
[XPERIA X10 Q&A, Help & Troubleshooting] tremeree:
Do not worry. if you flashed without anu error message you got it.
[Vibrant Q&A, Help & Troubleshooting] myinnerhollow:
First off, let me say I have searched for an answer prior to posting and asking this question. I am running Trigger v2.8.2 and my Vibrant has randomly started opening apps, switching screens and opening menus. I performed a wipe and reinstalled the ROM. I even went so far as to use ODIN to return to stock and install Trigger again, but I have not seen a change in the phones behavior.

I do not believe this has anything to do with the ROM, just not sure what is going on.

Anyone have an idea as to what the issue might be?
[Vibrant Q&A, Help & Troubleshooting] masterotaku:
Just on the surface of it, it sounds like your touchscreen digitizer is about to go tits up...
[Vibrant Q&A, Help & Troubleshooting] myinnerhollow:
that makes sense, the screen is very unresponsive in addition to the other random issues. It might be time to look for another phone. :(
[Vibrant Q&A, Help & Troubleshooting] Abu-7abash:
Out of curiosity, what causes such an issue?
[Vibrant Q&A, Help & Troubleshooting] myinnerhollow:
I wish I knew, however I do change ROM's frequently.
[Vibrant Q&A, Help & Troubleshooting] xriderx66:
Tell tmo your phone won't turn on, they send you a refurb
[Vibrant Q&A, Help & Troubleshooting] myinnerhollow:
I took your advice and called TMO. I should receive my replacement Vibrant by the 31st of March.

Thanks
[Vibrant Q&A, Help & Troubleshooting] xriderx66:
No problem :D
[Xoom General] pub00515:
Hi guys,

now I'm probably not gonna win a popularity contest posting this but after reviewing the technical specs of the transformer with those of the xoom, I'm a bit surprised - where's the catch?

I mean the transformer is gonna have a dock and as far as I have seen the same basic features the xoom has, only its lighter. And it costs less?!

Normally, when things appear to good to be true, they usually are...

So - where's the catch?

And, where's the hype??
[Xoom General] wynand32:
I find the Asus tablet (the name is just silly, though; "eee pad" for real?) interesting as well, although of course the proof will be in the pudding. The dock looks nice, but if it's an additional $300 or so then I'll not be interested. And I've found that Asus can have really mixed build quality--some stuff is great, others not so much.

The thing that does interest me, though, is the IPS screen. If reviews come out that show it has great build quality (equal to the Xoom, which I consider excellent), it's available for a similar price ($599 or less for 32GB wifi-only), the dock is reasonably priced (say, $150 or less, which might be a stretch since it includes a battery), and it's available from my retailer of choice (Costco), then I might consider returning the Xoom and getting it instead.

The one huge caveat for me, though, is the custom skin Asus is putting on it. I do NOT want anything to slow down updates, and so I like that the Xoom is stock Honeycomb. I don't really know that I'd trust Asus to come out with timely updates...
[Xoom General] e.mote:
The catch is that the Xoom is available now, and the Asus one isn't (unless you're in Taiwan). Ditto with any other HC tablet, which in all likelihood will be cheaper than the Xoom's current pricing. When the mass release comes, my bet is that the Xoom will get cheaper as well. Moto's CEO has said as much, although not explicitly for the Xoom.

BTW, if you are in the States and are looking at the Euro prices as a benchmark, be aware that the US dollar has been slipping as of late, and there is no guarantee that there'll be a 1:1 parity with the Euro pricing. Not sure about the Canucks, but generally they get the same prices as the Yanks'.
[Xoom General] martonikaj:
Also remember that most European countries have a VAT (Value Added Tax) that inflates prices by about 20%-25% depending on the country. Keep this in mind when looking at European prices and converting into USD.
[Xoom General] rjoudrey:
If you own a Xoom now you are in a good position to get early updates and in one year the tablet market should be extremely competitive with great deals. Faster, lighter, thinner better screens, Android 4.0, you name it.

Quite often the hands on with some of these new tabs reveals a lot of cheap plastic, etc. The Xoom is extremely well built and I bet well be very desirable for quite some time.
[Xoom General] Arun01:
Asus has only tablet i'm interested in & that's the Slate tablet..it costs like $1100.Plays 1080p video.Has a full Windows 7 operating system on a 12 inch tablet screen.Plus it has a I5 processor!!! But the all that said this thing has a battery life of only 3-4 hours & if you're watching a 1080p movie then you only get 2 hours :( . If it had a battery life of 7-8 hours i'd be all over it.So nothing can compare to the Xoom but that tablet
[Xoom General] rjoudrey:
I had a win7 tablet and can tell you win7 is a very cumbersome touch interface.