yashsingh1/xdaforums huggingface dataset:
[Android Software Development] nikki_n:
Hi ,

I'm working a project on android sdk 2.2 , but I' don't understand how I can terminate an

outgoing call, becouse in the newest android sdk isn't a method.

Help me Please.

Thank in advance.
[XPERIA X10 Themes and Apps] damirbusic:
First Ive had some weird problem and when I send some email it hangs with red letter "Sending" and never sends it until I hit Refresh. And then I have found some tips on google that I should go in Settings/Aplications and there Clear Data in Gmail and Delete Data in Gmail Storage and now I got only "Your email will appear shortly" stupid message and no inbox or anything else.

Can someone help me to get this Gmail app to work on Xperia X10 ? This app came with the phone.

Tnx a lot
[XPERIA X10 Themes and Apps] Nocturnal310:
working fine on mine.

what connection are u using?

i had trouble sending test mail for the first time coz i was on weak wifi signal
[XPERIA X10 Themes and Apps] damirbusic:
I am using WiFi and 3G but I get always red letters saying "Sending" and only after refresh it dissapears and I can see that the message is sent...
[Nexus One Q&A, Help & Troubleshooting] jdmoore81:
There should be a way to filter content like the porn girls even though it don't show nothing I don't my kids to have the option of seeing it on the market if this is the wrong section mods please edit

-------------------------------------

Sent via the XDA Tapatalk App
[Nexus One Q&A, Help & Troubleshooting] Vandam500:
That I know of there isn't anything provided by Google. Would be nice if they implemented some of the parental controls that Apple has on their iPhone OS.
[Nexus One Q&A, Help & Troubleshooting] Paul22000:
I'm sure there will be much better sorting and filtering once the web browser version of the Market launches.
[Nexus One Q&A, Help & Troubleshooting] jdmoore81:
You would think they would have a filter even if it was just a app come on Google. Internet should be a tool but not one to exploit girls or guys

-------------------------------------

Sent via the XDA Tapatalk App
[Nexus One Q&A, Help & Troubleshooting] craigacgomez:
For now, you could try appbrain... it allows filters...
[Nexus One Q&A, Help & Troubleshooting] tomfreay:
There should be a filter, I haven't seen the apps myself. But depending on how graphic they are they might not even be allowed on the market

http://www.android.com/market/terms/developer-content-policy.html
[Nexus One Q&A, Help & Troubleshooting] ChillRays:
Wait, whats wrong with porn girls????

(rereads)

Oh your kids.. nevermind XD
[Nexus One Q&A, Help & Troubleshooting] Old MuckenMire:
I filter them by scrolling past them :)
[Nexus One Q&A, Help & Troubleshooting] Amdathlonuk:
I filter them by installing them and checking the content.... :D
[Nexus One Q&A, Help & Troubleshooting] ChillRays:
lol YES :D
[Nexus One Q&A, Help & Troubleshooting] herrwinkler:
Easy fix. Get an iPhone.

Seriously, it is annoying.
[Nexus One Q&A, Help & Troubleshooting] logger:
Seems to me the more apps in the market the happier Google are. They don't seem to give a rats if they are absolute junk like many of them. They just want the app count up asap so they can brag about the growth. The [apps>Just in] option should be renamed [apps>Junk]. I do not think Googles approach is particulary fair on developers of genuine apps which drown in the mire of rubbish.

I mentioned in another thread how surprised I am the Top Paid app in the productivity section of the android market can only appeal to such a small portion of users. Seems to me the Market is not really gaining genuine momentum, if thats the best it can do. It is just filling up with fluff.

At least as craigacgomez says, Appbrain does a half decent job of hiding the rubbish.
[Nexus One Q&A, Help & Troubleshooting] Mokurex:
The thing that annoys me most about the Android Market is that they won't give access to paid apps in many countries.

Why on earth would they block paid apps in some countries is just beyond me. I have a credit card, I want to pay for the apps, I want to spend money, so pleaseeee let me spend Google!!!
[Nexus One Q&A, Help & Troubleshooting] codesplice:
Am I way out of line for thinking that a kid who is old enough to carry a $600 phone should also be old enough to know a little bit about the world? I see more provocative images on billboards on the side of the interstate and ads on the side of Facebook for crying out loud.
[Nexus One Q&A, Help & Troubleshooting] logger:
No I think that is a fair comment.

But if I understand correctly the OP was actually asking for a way to filter content. His pet hate is porn. Others are OK with the porn but want to filter the Spam apps. So to my mind user configurable filtering of the market would be a good thing.
[HD2 General] badboysuhail:
Hi

i had to hard reset my phone yesterday, and today i realised that the unknown album on the htc music player has disappeared and there is no way to access them songs from the httc sense player

any help please

Thanks in advance
[Desire Android Development] gr0gmint:
To make the HTC Desire boot from a 1gb file on your SD-card:

Instead of having to partition the SD-card to make this work,there is another solution; that is to make a "virtual" EXT2 partition as a file on the FAT32 partition.

You can make this file as big as you want. 1gb is a fitting size though. .. you will probably need a linux box to make this work.... The file has to be called altboot.ext2 and lie at the root of the SD-card

NOTE: The initfiles and the modified kernel in this guide is 2.6.32 ONLY. I understood this may be an inconvenience for some. This kernel also disabled the "Android Paranoid Networking" feature, which is a useless pain-in-the-ass feature.

1. To make a 1GB empty file, issue dd if=/dev/zero of=altboot.ext2 bs=1M count=1000

2. Make a EXT2 filesystem on the file: mkfs.ext2 altboot.ext2

3. Mount the file as a loopdevice: mount -o loop -t ext2 altboot.ext2 <mountpoint>

4. Copy files from the attached initfiles.zip to <mountpoint>

5. Copy all files from a rom of your choice to <mountpoint>

6. Issue a chmod -R 0755 <mountpoint>

7. Issue umount <mountpoint>

8. Copy altboot.ext2 to the root of the SD-card

9. Flash my kernel image

10. Reboot your phone, and press the Home key repeatedly

Good luck :D

The source code changes for this kernel can be found at http://github.com/gr0gmint/kernel_msm

(Here is the source code for the two "special" init files)

executable in the ramdisk:

#include <unistd.h>
#include <sys/stat.h>
#include <sys/mount.h>
#include <linux/loop.h>
#include <fcntl.h>

#define BB_LOOP_SET_STATUS LOOP_SET_STATUS64
#define BB_LOOP_GET_STATUS LOOP_GET_STATUS64
typedef struct loop_info64 loop_info;

int main (int argc, char * argv[]) {
int dfd,ffd;
loop_info loopinfo;

mknod("/sd2" , S_IFBLK|S_IRUSR| S_IWUSR, makedev(179,1) );
mknod("/lo5" , S_IFBLK|S_IRUSR| S_IWUSR, makedev(7,5) );

mkdir("/sd", 0755);
sleep(7);
mount("/sd2","/sd", "vfat",0, NULL) ;

ffd = open("/sd/altboot.ext2", O_RDWR);
dfd = open("/lo5", O_RDWR);

ioctl(dfd, LOOP_SET_FD, ffd);
memset(&loopinfo, 0, sizeof(loopinfo));
strcpy((char *)loopinfo.lo_file_name, "/sd/altboot.ext2");
ioctl(dfd, BB_LOOP_SET_STATUS, &loopinfo);
mkdir("/chrootenv", 0755);
if (mount("/lo5", "/chrootenv","ext2", 0, NULL) != 0 ) {
execv("/init", argv);
}
execv("/chrootenv/altinit", argv);
}

executable on the SD-card:

#include <unistd.h>
#include <stdio.h>
#include <sys/stat.h>
#include <sys/mount.h>
int main (int argc, char * argv[]) {

if (chroot("/chrootenv/") == 0) {
chdir("/");

execv ("/init", argv);
}

}
[Desire Android Development] shawe_ewahs:
Any error on execution?
[Desire Android Development] gr0gmint:
Yes it reboots, and resumes with a normal boot. I made some error checking, and it seems the init binary gets executed, but there's trouble with mounting the SD-card. I will try with manually mknod'ing in a moment.

EDIT: That didn't help either.
[Desire Android Development] kubino99:
I'm not sure but when you do chroot you propably lost system folders. Maybe you can try this :

#include <unistd.h>
#include <sys/stat.h>
#include <sys/stat.h>

int main (int argc, char * argv[]) {

mkdir("/dev", 0755);
mkdir("/dev/block", 0755);
mknod("/dev/block/mmcblk0p2" , S_IFBLK|S_IRUSR| S_IWUSR, makedev(179,2) );

mkdir("/mnt", 0755);
mkdir("/mnt/sdcard", 0755);
mount("/dev/block/mmcblk0p2","/mnt/sdcard", "ext2",0, NULL);
chroot("/mnt/sdcard");

mkdir("/dev", 0755);
mkdir("/proc", 0755);
mkdir("/sys", 0755);
mount("tmpfs", "/dev", "tmpfs", 0, "mode=0755");
mkdir("/dev/pts", 0755);
mkdir("/dev/socket", 0755);
mount("devpts", "/dev/pts", "devpts", 0, NULL);
mount("proc", "/proc", "proc", 0, NULL);
mount("sysfs", "/sys", "sysfs", 0, NULL);
execv("/init", argv);
}

Edit : of course you need to firstly create special file /dev/block/mmcblk0p2

Edit2 : tryed to add code for creating /dev/block/mmcblk0p2, not sure if it will works I didn't test that ;-)
[Desire Android Development] gr0gmint:
Thanks for the input, but it still reboots:(
[Desire Android Development] kingchris:
i read something like this here

http://xdaforums.com/showthread.php?t=594077

you can try to contact the user
[Desire Android Development] kubino99:
edited my previous post with code for creating special file. you can test it once more.
[Desire Android Development] gr0gmint:
Thanks for the effort, but it still fails at the mounting.

I wonder if the mmc bus needs "activating" :confused:
[Desire Android Development] gr0gmint:
dmesg | grep -i 'mmc'

EDIT: I can see i probably need to sleep a few seconds before i mount. Will try later

[ 4.355255] bravo_init_mmc()+
[ 4.355438] bravo_init_mmc()-
[ 5.939910] mmc0: MMC_BUSCLK_PWRSAVE is enabled
[ 5.940185] mmc0: Qualcomm MSM SDCC at 0x00000000a0300000 irq 24,0 dma 8
[ 5.940185] mmc0: Platform slot type: Not defined
[ 5.940185] mmc0: 4 bit data mode enabled
[ 5.940216] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 64000000 Hz
[ 5.940216] mmc0: Slot eject status = 1
[ 5.940216] mmc0: Power save feature enable = 1
[ 5.940246] mmc0: DM non-cached buffer at ffa06000, dma_addr 0x3b331000
[ 5.940246] mmc0: DM cmd busaddr 0x3b331000, cmdptr busaddr 0x3b331300
[ 5.940704] mmc1: MMC_BUSCLK_PWRSAVE is enabled
[ 5.941192] mmc1: Qualcomm MSM SDCC at 0x00000000a0400000 irq 26,0 dma 8
[ 5.941192] mmc1: Platform slot type: SD
[ 5.941192] mmc1: 4 bit data mode enabled
[ 5.941223] mmc1: MMC clock 144000 -> 50000000 Hz, PCLK 64000000 Hz
[ 5.941223] mmc1: Slot eject status = 0
[ 5.941223] mmc1: Power save feature enable = 1
[ 5.941223] mmc1: DM non-cached buffer at ffa07000, dma_addr 0x3b335000
[ 5.941253] mmc1: DM cmd busaddr 0x3b335000, cmdptr busaddr 0x3b335300
[ 6.173095] mmc1: Command timeout (cmd= 5 mci_st=00000004)
[ 6.179077] mmc1: Command timeout (cmd= 5 mci_st=00000004)
[ 6.185119] mmc1: Command timeout (cmd= 5 mci_st=00000004)
[ 6.191101] mmc1: Command timeout (cmd= 5 mci_st=00000004)
[ 6.711578] mmc1: host does not support reading read-only switch. assuming write-enable.
[ 6.711791] mmc1: new high speed SDHC card at address 673b
[ 6.712432] mmcblk0: mmc1:673b SD16G 14.9 GiB
[ 6.712921] mmcblk0: p1 p2
[Desire Android Development] gr0gmint:
It boots now, but is stuck at the HTC logo, although adbd runs.

Some of the errors it loops constantly:

E/FramebufferNativeWindow( 484): Couldn't get gralloc module

E/libEGL ( 484): eglGetDisplay:632 error 300c (EGL_BAD_PARAMETER)
E/libEGL ( 484): eglInitialize:646 error 3008 (EGL_BAD_DISPLAY)

I/Zygote ( 483): Exit zygote because system server (484) has terminated
I/ServiceManager( 55): service 'media.audio_flinger' died
I/ServiceManager( 55): service 'media.player' died
I/ServiceManager( 55): service 'media.camera' died
I/ServiceManager( 55): service 'media.audio_policy' died
I/ServiceManager( 62): Waiting for sevice SurfaceFlinger...

E/AudioHardwareQSD( 507): Cannot open /dev/audience_a1026 -1
I/AudioHardwareQSD( 507): set_tpa2018d1_parameters() not present

E/Zygote ( 512): setreuid() failed. errno: 17
[Desire Android Development] kubino99:
seems like you need to create special files in /dev folder check via adb which files are present.
[Desire Android Development] Kali-:
/dev/audience_a1026 <- nexus one rom?
[Desire Android Development] kingchris:
quick OT Question.

do you think it is possible to create a recovery which is bootable with this method?
[Desire Android Development] gr0gmint:
It's working! We can now do multibooting on Desire!

I will post a guide tomorrow with files!
[Desire Android Development] myth1001:
Though I have no idea what this is for, but GREAT WORK mate!

Great to see new breakthrough for our Desire!

Thanks for the hard work! :D
[Desire Android Development] gr0gmint:
Thanks ^^

It means you can have both Froyo and 2.1 on your Desire for example.

You basically have an extra ext2 partition on your SD card with another OS
[Desire Android Development] rolfd:
Can we now flash a new rom just onto the SD card, boot from it, and if it goes tits up just remove the card without fear of upsetting the handset and bricking?
[Desire Android Development] StuMcBill:
Does this mean we can store /system on our SD card and choose between booting the SD card stored software or the software stored on the Flash of the device?

Dual-booting between Internal Flash and SD card essentially? So you could have Froyo (when released) on SD card and 2.1 on the device as normal?

Or could you have recovery stored on the SD card and run it from there?
[Desire Android Development] gr0gmint:
Yes. Only limitation (so far), is they have to share to same kernel.

And no. I don't think you will have write access to the system partition.
[Desire Android Development] StuMcBill:
Cool, thanks for the explanation! :D

Good work! Thanks!
[Desire Android Development] TheAshMan:
Great work. Nice way to test ROMs.

And what happens when you connect phone to computer in Disk Drive mode? :)
[Desire Android Development] rolfd:
I wonder if this could possibly be a temporary fix for people with bricked handsets? Just boot from SD after putting the files on it...
[Desire Android Development] ahmgsk:
great work bro this will help in making recovery work from device itself wait for ur files that i shall try recovery
[Desire Android Development] The Professor:
Well done, gr0g. Most impressive, and thanks for keeping it up.
[Desire Android Development] gr0gmint:
Works great :)

edit: except froyo has a problem with multi-partitioned SD-cards of course.
[Desire Android Development] sruon:
It's amazing all we got today... good work.
[Desire Android Development] TheAshMan:
Top stuff man, looking forward to the release (not in a "Paul, when can we have Gingerbread?" kind of way)
[Desire Android Development] shawe_ewahs:
This can be a way for have recovery acces from SD?
[Desire Android Development] Qliratu:
This is great id love 2 get my hand's on the files ;-)
[Desire Android Development] Jpcurrie:
Re: [ITS WORKING] Boot from SD card

Is it possible to boot a recovery image from the card?

-------------------------------------

Sent via the XDA Tapatalk App
[Desire Android Development] PaoloWeckl:
dual boot could means we can install a linux distro like debian or ubuntu on our desire? with working connection and all?
[Desire Android Development] JDouce:
like the 3rd post down for ahmgsk says "this could help with recovery"
[Desire Android Development] fstluxe:
Indeed this is Wonderful solution to boot recovery...
[Desire Android Development] JDouce:
can we put the recovery files on a seperate ext partition and use an identical hold home and power on to boot from that partition.

may require a modified recovery tho.

or we could assign another key to the recovery boot and make another ext partition lol

the source code in the first post shouldn't require much editing to make this work

think you could try this grog with Ahmgsk's recovery?

-edit ahmgsk already said he would try

also can someone with usb brick try this :)
[Desire Android Development] Kali-:
i didn't think this help fix usb-brick

the problem is in the SPL which load recovery image with different parameter

this is very useful, help to bypass the fuking RO /system

nice work
[Desire Android Development] JDouce:
may not fix brick but means that usb brick can have different roms now... and are no stuck with whatever that got when they bricked
[Desire Android Development] Kali-:
usb-bricked can't flash kernel :/
[Desire Android Development] GhostSoldier:
USB-bricked phone

I would love to try this, but I dont know how.

I am a beginner in flashing Android-phones. Therefore - my bricked Desire.

But if someone would like to point me in the right direction, that would be great!´
[Desire Android Development] st0kes:
Wow this has massive implications for rom management and rom flashing going forwards. Great work!
[Desire Android Development] xtcislove:
We will be all bricked in near future ( i am) !! So its much better to work on a solution for the USB Brick AND a Full Root ! The ROMS are working ****ing bad with APPS2SD in my Opinion! If i am unbricked i wait for Froyo with FULL root =) Then the flashing can begin!
[Desire Android Development] JDouce:
if we can get the recovery working like this is would be a MAJOR step forward
[Desire Android Development] cedeel:
Probably not. The bricking occurs pseudo-randomly (Many bricks, but very few devs have bricked).
[Desire Android Development] gr0gmint:
Apparently i was a bit fast. It DID work. Now i'm trying to figure out how. :eek:
[Desire Android Development] gr0gmint:
Anyway here are the kernel patches to make it execute /altinit instead of /init, if the Home key is pressed.
[Desire Android Development] ephumuris:
This stuff is miles more interesting than all this froyo talk I nearly missed it. Keep going good work.
[Desire Android Development] rolfd:
I can't agree more! Once this is going then I imagine we can stick froyo on the sd card and have a play :D
[Desire Android Development] Kali-:
for that we need the richardtrip froyo kernel diff

gr0gmint thanks for sharing

but, almost working only because the patch need more testing?
[Desire Android Development] gr0gmint:
I've tested recovery, and it does not seem to have write access to the protected partitions. I get these errors:

Formatting BOOT:...
Writing BOOT:...
E:No space left on device
E:Error writing BOOT:
E:Failure at line 5:
write_raw_image PACKAGE:boot.img BOOT:

Installation aborted.

:(
[Desire Android Development] Kali-:
when boot from SD, the FAT32 FS on the card is not available to the system (/sdcard) ?
[Desire Android Development] gr0gmint:
Yes it is, but looks like Froyo has a hard time managing it. It has booted before, but always only the first time.

I've tried with a 2.1 rom, boots fine every time.
[Desire Android Development] Kali-:
looking your kernel zip there is no altinit, this is correct?
[Desire Android Development] gr0gmint:
Please excuse my forgetfulness :o hehe..

its now attached to first post
[Desire Android Development] JDouce:
well u jsut made rom development a WHOLE lot less painfull... no more millions of flashes.... just mount the sd and edit away

jsut need to use ur awsome skills on the recovery
[Desire Android Development] Kali-:
thank's

i really appreciate your work
[Desire Android Development] jcdz92:
This looks far more very interesting than flash again and again !

How do you proceed from the begenning to install :

altboot + altinit on EXT2 ( how to locate where ext 2 is )and then try a 2.1 rom (as I understand 2.2 not fully working with this method) ... until you boot pressing repeatedly on "home" button

Thanks, great work
[Desire Android Development] gr0gmint:
Now this is weird. I can usually make Froyo boot, by killing 'system_server' a few times.

EDIT: okay this was a lucky strike -_-
[Desire Android Development] Nekromantik:
this sounds promising.

if someone can get the froyo port working using this method then I will try as I dont really wanna flash the current ROMs of froyo.

good work guys

On a side note, I need to start to learn programming for android, I got some java skills so will need to look the SDK up.
[Desire Android Development] dreamdealer:
if only booting to the recovery menu was just as simple.
[Desire Android Development] StuMcBill:
Re: Boot from SD-card

Has this functionality been built into any kernels yet?

I am keen to try some more froyo builds, but it would be good if I could test them on my SDcard before flashing them for good?

Thanks

StuMcBill
[Desire Android Development] marksteel:
I've just read through this thread and still have no idea what I'm meant to do to get this working.

Flashing involved?

Location of files? (i did gather the altinit file goes to the root of SD card though)

Do we need to create an additional partition?

Zipped or unzipped?

help please
[Desire Android Development] alias_neo:
Basically, it replaces/modifies your boot partition with an alternative that provides an option to boot from the SD card. Then it gives a method of involking your own init script to load an alternative kernel/OS from your SD card.
[Desire Android Development] marksteel:
I had an idea as to what it did, I just need a guide as to how.
[Desire Android Development] AdamG:
these kernels need recompiling, wifi doesn't work, at least on Altboot_2ndext.zip it doesn't
[Desire Android Development] gr0gmint:
I didn't include any *.ko files in the zips, thats the problem
[Desire Android Development] Nekromantik:
can we use this to try out the froyo ROMs?
[Desire Android Development] AdamG:
gr0gmint: I followed your instructions perfectly and I couldn't get this to work.

My SD was FAT32,EXT2(A2SD),EXT2(ALTBOOT)

I tried altboot 2&3 because I was unsure which to use.

I extracted the RAM disk to the EXT2 partition along with the altinit and a copy of a 2.1 ROM to the system folder, I then proceeded to hash out all 'mount mtd' I could find in the init.rc and then did a chmod -R 0755...

The Desire booted when I didn't hit the home key with my usual ROM but when I kept hitting home it just kept rebooting after ~10s, am I missing something out?

--The RAM disk was an unedited stock one along with a stock ROM on the EXT2 parition.
[Desire Android Development] gr0gmint:
I can't really tell you whats wrong with your setup. If it reboots immediately, it's probably because it fails to mount the EXT partition in the first place.

Right now im making a minimal boot environment, and i'm trying to make it boot from a loop-file on the FAT partition this time. So no hassle is needed with EXT partitions and such.
[Desire Android Development] gr0gmint:
I forgot to mention that you have to comment out everything with "rootfs" in the init*rc files too. Sorry. Thread updated ;)
[Desire Android Development] AdamG:
That could have been why lol, your FAT32 loop idea sounds cool, I hope this works out, would certainly make some of our lives easier :)
[Desire Android Development] gr0gmint:
I got it working! With a 2.6.32 kernel. And it's much faster than i anticipated. :D

I will post a guide tomorrow
[Desire Android Development] rolfd:
Nice one.. Well done, and thank you :D
[Desire Android Development] AdamG:
The echo on the 2.6.32 kernel is horrendous though, everybody I ring complains :(
[Desire Android Development] gr0gmint:
Guide updated ;)
[Desire Android Development] alias_neo:
I'm curious to try this but have some questions.

I'm on MCR, how much difference will replacing my kernel with this one make? Can I even do that?

I'm using APPS2SD+, will it work?

Wouldn't mind giving it a go to run froyo but only if I can keep MCR running exactly as it is now. Can't see why you'd make something that doesn't work this way though.
[Desire Android Development] deovferreira:
The echo isn't a problem of the kernel, it's a problem of 2.2 frameworks, that's why you only see it on Nexus roms. Cyanogen+bravo 2.6.32.9 doesn't present any echo at all.
[Desire Android Development] alias_neo:
So I guess the fact I'm getting it on MCR is just network? I got rid of the piece of **** iPhone because of the echo. I really hope it isn't my network.
[Desire Android Development] p65174:
nobody works on that ??