iDroid MoJo 1.0.4.1 Release Announcement

[t3l0_b4k4r]

very nice for play music but after restat always scan Media Scanner.
problem if install direct download idroid Mojo v.1.0.4.1 from bootlace wifi not connect but if manual install wifi not problem. what wrong?
and ADB can't connect.
how to fix?

[saidias]

How do get ringtones? 

/var/sdcard/media/ringtones   ?

Scanned Media, but still don't see any. 

[Zeta0134]

Well I'll be damned. It actually charges when plugged into my computer now, even when it's playing music. That's downright exciting!

I'm in a 3G, install went perfectly, I'm still playing around with it. I can't say anything for wifi, but it's definitely smoother and more responsive than the previous version was. Great job so far. ^_^

-Zeta

EDIT: Aww bugger, the multitouch driver seems to have crashed. One hard-reset, coming up. I can't test it now, I'm in class, but I suspect it still doesn't like headphones very much.

[ddominator]

Well I'll be damned. It actually charges when plugged into my computer now, even when it's playing music. That's downright exciting!

I'm in a 3G, install went perfectly, I'm still playing around with it. I can't say anything for wifi, but it's definitely smoother and more responsive than the previous version was. Great job so far. ^_^

-Zeta

EDIT: Aww bugger, the multitouch driver seems to have crashed. One hard-reset, coming up. I can't test it now, I'm in class, but I suspect it still doesn't like headphones very much.

There's an unfixed bug that while booting with the headphones, iDroid will crash... Sorry

[Zeta0134]

I had the same problem with adb tool, my workaround was to configure manually "IP settings" (IP address, Gateway, DNS, etc) for my WiFI network.

Where do i go to edit the "IP Settings" ?
Thanks

To edit IP/DNS settings on Android, go to Settings -> Wifi Settings, then press the Android Menu [iPhone Home] button and click on Advanced. You need to use a static IP in order to set DNS settings, make sure it's in the right range and all, not going into that here.

EDIT: Aww bugger, the multitouch driver seems to have crashed. One hard-reset, coming up. I can't test it now, I'm in class, but I suspect it still doesn't like headphones very much.

There's an unfixed bug that while booting with the headphones, iDroid will crash... Sorry

Actually, I'm aware of this bug, and this seems to be unrelated. I'm not yet sure how I triggered the firmware crash, but android was already booted / playing music when it happened. The process went sort of like this:

Install Android via Bootlace
Boot into Android (with headphones out)
"OMG Android! It's freaking awesomer! *looks at clock* holy crap I have class!"
Quick Media Scan
*Plug in Headphones*
Start music playing
Freak out because damn, that's really loud
Go into Settings, decrease volume
Lock phone, apply pocket, walk to class (I live on campus)
Get to class, remove phone, remove headphones
"Well crap, it's still playing"
Attempt to unlock phone via touchscreen
Kill phone because touchscreen isn't responding
Edit post on iDroidProject forums

That's the abridged version at least. I'm trying to narrow down what went wrong between the lock and the crash, which I'm testing right now.

Anyway, wifi confirmed working, but I'm chiming in on the DNS bug, Android doesn't seem to be getting DNS from the DHCP correctly. I set it to static IP and manually entered DNS servers (I'm using the google public ones at 8.8.8.8 and 8.8.4.4) and it works beautifully.

-Zeta

EDIT: More aww... It doesn't charge when plugged in and connected to Wifi. That appears to be too much of a battery drain for it to charge properly. Sadness. (it does drain very slowly in this case.)

[jack]

I had the same problem with adb tool, my workaround was to configure manually "IP settings" (IP address, Gateway, DNS, etc) for my WiFI network.

Where do i go to edit the "IP Settings" ?
Thanks

Follow the menu "Settings" --> "Wireless & Networks" --> "Wi-Fi settings", now press "home button", select "Avanced";  here you can modify the IP settings.

[oztiz]

It is possible to fix dns with the Terminal app.  I did:
$su
#setprop net.dns1 8.8.8.8

[campi9]

please help. ipt1G with bootlace 2.1.4 e idroid Mojo 1.0.4.1. I've got problem with wifi,i can connect mi device to internet but i can't browse web page . I fixed dns manually from the terminal or by settings,but i'm still having problem...why?? help!!!

[lenarto]

@campi: well jack's suggestion to configure advanced settings manually worked for me, are you sure you used the correct dns from your isp ? did you try to ping a website directly with it's ip to make sure internet works ? maybe reinstall wifi driver, or revert to 1.0.3 as a last resort...

[JayWheel]

You don't need the DNS of your ISP, just point to your router (in my case 192.168.1.1)
That does it for me (Linksys WRT54G).

[Rekoil]

You don't need the DNS of your ISP, just point to your router (in my case 192.168.1.1)
That does it for me (Linksys WRT54G).

That works because your router is actually supplying your ISP's DNS through it's own DNS server. You could also point it at 8.8.8.8 which is one of Googles DNS servers.

[sneevand]

Hi,

Things seems fine so far, But we never heard about fixs for the following

1.Camera
2.Bluetooth [A2dp]
3.Sound [Its not pefectly fixed, still have issues]

when can we expect them to be fixed. Can we fix them or not.

Still trying to fix same old issues in every release. But no progress on above issues.

Your guys even reject them as issues and metion they are known. But we dont have a proper answer on whther you can fix them r not. But enjoy d............

Regards,
Sneevand

[Rekoil]

Hi,

Things seems fine so far, But we never heard about fixs for the following

1.Camera
2.Bluetooth [A2dp]
3.Sound [Its not pefectly fixed, still have issues]

when can we expect them to be fixed. Can we fix them or not.

Still trying to fix same old issues in every release. But no progress on above issues.

Your guys even reject them as issues and metion they are known. But we dont have a proper answer on whther you can fix them r not. But enjoy d............

Regards,
Sneevand

They can be fixed, there's a guy working on camera at the moment actually. The majority of developers working on the project at the moment are concentrating on newer devices like the 3GS and i4.

[Droid_junkie]

although this isnt really the place to be discussing this, I think yall should stop release different "versions" go back to 1.6 and get everything working for the iphone 2g once you have that working get 1.6 fully working for the 3g/3gs/4/ipod touches THEN release a 2.2.1 version.  I personally hate the way yall are doing the releases because you are not really fixing anything you are just coming up with "hacks" and "workarounds", I mean seriously yall have the source code get it working before releasing "updates" without fixing known issues.  Since I can not program/reverse engineer/code kernels/etc., etc., etc. everything I said is null and void but it is my opinion.

[Rekoil]

although this isnt really the place to be discussing this, I think yall should stop release different "versions" go back to 1.6 and get everything working for the iphone 2g once you have that working get 1.6 fully working for the 3g/3gs/4/ipod touches THEN release a 2.2.1 version.  I personally hate the way yall are doing the releases because you are not really fixing anything you are just coming up with "hacks" and "workarounds", I mean seriously yall have the source code get it working before releasing "updates" without fixing known issues.  Since I can not program/reverse engineer/code kernels/etc., etc., etc. everything I said is null and void but it is my opinion.

Since you're not a programmer or a reverser you clearly have no clue what goes on behind the scenes, and I can tell you right now that we're not "just coming up with 'hacks' and 'workarounds'". Having the source code for Android means we can compile Android for supported hardware... but the iPhone isn't supported hardware is it? No that's what we're here to correct, and it's an insanely difficult process. Most of the time the developers are working blind, guessing stuff by trial and error etc, this is because they have no references to look at (we need a sensible ARM decompiler/disassembler for that and they are not cheap or easy to get access to).

The fact is that since it takes such a long time to develop drivers, (this is generally due to the lack of people with the knowledge of how to do it... and their lack of time to devote to it) repackaging the drivers with new versions of Android is a comparatively quick process which helps us gain media attention which again serves to help us find new driver guys.

So why don't yall quit bitching and try to help out instead? Spread the word, show it to someone you know who might be able to help us, donate money towards devices for developers and hosting... and don't bitch about the hundreds of hours per week most of us on the team pour into this project, especially not if it's only your uneducated opinion.