Database Users

How do i know my Moaco was successful?

in the firmware, it says 1.5
kernal 2.6.27
buil says modacoc custom rom 3.1 and what do i do with the password? an software version 1...
I dont see the "new"market place

If you build strings says that it is a MoDaCo build, it has worked fine.
It won't have the "new" Market because this is a feature of ROMs based on 1.6 or above.
The password is for DropBear SSH should you wish to use it.
Regards,
Dave

[Q] Why not compile the tun.ko module with Asus TF101 ROMs?

Hi all,
I've looked at forums in the DEV section and can find a tun.ko module for an earlier kernel of the TF101. None of the ROMs including Clemsys, Revolver's, Netformer's, Prime's and any other I have download include this module in their kernel builds. I would like for this module to be included, which was in Prime 1.2, but that was for a kernel that is no longer in use and that is for Honeycomb 3.0. So my question to the Devs is, why no compile tun.ko for any and all the ROMs you deploy?
Thanks for your response.
In case people don't know, tun.ko is the module that allows a rooted device use an app like VPNC to log into and create a VPN tunnel through a Cisco VPN Concentrator.
jamdev12

Are you sure, TUN isn't in prime 1.6? I see it listed as added in version 1.4, so I don't think that it would have been removed in updated versions.

All the ROMS you mentioned (clemsyn, PRIME, Revolver) include the tun.ko compiled into the kernel. You do not need any external tun.ko module for VPN to work.
However, the trick to get VPNC to work is to rename the file /system/bin/ip to /system/bin/ip.bak. This causes the /system/xbin/ip to be picked up instead while works fine.

guptaavi,
Thanks for the info. I'm stupidfied and you have enlighten me. I know that sounds corny, but I appreciate the help here, because since I did not see the module in the /system/lib/modules folder, I thought it wasn't compiled. Now I know the difference between compiling it into the kernel and compiling it for the kernel.
jamdev

Hi guptaavi,
So I must be stupid, because I did what you just told me about changing the file name for the /system/bin/ip to ip.bak, but the VPNC widget takes forever to start and it just fails. I know the settings are correct because I can run VPNC on my OG Droid without issues. I'm running CWM7.
Do you have any suggestions?
jamdev12

If tun.ko is build into the system, how do we setup OpenVPN to use tun.ko? How do i tell OpenVPN where the tun.ko file is?
Pls help as im using PRIME 1.8.4.
TIA
JL

[Q] Adding Android Open Accessory (AOA) protocol to defy (CM10)

Hi all!
I will try to get the Android Open Accessory (AOA) protocol into our defy/defy+.
Anybody else working on this topic?
Atm I just added the android.hardware.usb.accessory.xml file to /etc/permissions and the com.android.future.usb.accessory.jar to /system/framework (jar taken from the droid sdk API16, my fw is latest quarx CM10).
Right now I can install f.w. the ADK2012 app. So I may on the right way... but I guess that is not all the work... does anybody know if we need to add some kernel modules f.e.?
[Edit] btw... looks like we just need to add a new f_accessory.o to our usb gadget... f.e. see https://www.codeaurora.org/gitweb/q...in;h=5d9d8625e39f815673dedea353f39edccabb1fac
Best regards, Stephan

Like to know this to. If quarx managed to give us sub host, I might be able to use my duomilanove board...
Aren't there other projects for the ADK that doesn't use the protocols?

Please ask all questions in the Q&A section. Thread moved there.

Ok... I gave it a short try with the patch and quarx's linux-2.6.32 but it failed during the compiliation... but meanwhile I noticed that quarx is working on linux-3.0.8 (see its repo in github). There we have our accessory...
So I would say stay tuned for a while and let's if quarx may got this newer kernel working with our defy...

You can find all the steps needed to patch it here:
https://github.com/ezterry/manifest-gingerbread-DS/issues/32
They're saying everywere that you need 2.6.35+ kernel (don't know if it really is mandatory, kernel in the link is 2.6.34)
A kernel with the same chipset that has it enabled can be found here:
https://github.com/XDA-Bam/samsung_kernel_latona_GB
Apparently, you need to enable it in the kernel (config), add the libs to the kernel (driver/usb/f_accesory and include/linux/f_.accesory), add the lib in the framework (might be included from CM side already??), hope it will work (or debug why not).
---------- Post added at 01:21 AM ---------- Previous post was at 01:06 AM ----------
It seems that the files are indeed in the 3.0 kernel.
I already ordered a USB-host shield for my arduino a week ago, I'll try and compile a kernel with it ones it comes in the mail.
Edit:
Tried the changes I listed, will build it tomorrow (or so). Maybe then my shield might arrive to (hate waiting, stupid holidays.. )
Any place to upload it when it works?

Got something build, but it didn't include the /system/framework/com.android.future.usb.accessory.jar and got bootloop without (cause I added the /etc/permision/something_with_usb_accesory.something
Pushed the jar with adb from bootmenu (from another CM rom).
Don't have the usb_shield yet, so can't really test. Will try and install an usb_accessory app. Does someone want the build to try?
Ok, the app fails to launch.

Ok, my repo's:
Kernel: https://github.com/labsin/jordan-kernel/commits/2.6.32
Device: https://github.com/labsin/android_device_moto_jordan-common/commits/jb_2ndboot
But doesn't work. The library isn't build (in framework/base).
And it also doesn't build in the kernel... :/
Anyone??

Might it be possible to check the driver?
Edit: Found it.
It seems to many commits need to be merged in. Can't seem to find a kernel that's not based on the nexus line that has it.

If anyone is still interested in this, I managed to make an Arduino Mega ADK board with the DemoKit application work in accessory mode on my Defy
Quarx backported the USB gadget driver from 3.0.8 kernel into his 2.6.32 based kernel already a while ago. All that was still missing was the accessory configuration in init.usb.rc and the .jar and .xml files. Quarx has already merged my pull request, so in the next CM10.1 nightly with 2.6.32 kernel, USB accessory mode should work out of the box

Thnx. Already saw this actually

[ROM | ZTE OPEN] FFOS 1.2 multilanguage - upgradeable through B2G nightlies

Hello again:
Build B2G for ZTE Open (inari) is tricky. People who want to develop applications with firefox's app-manager extension need to wait for ZTE upgrades or build their own system, which involves some permission modifications in boot.img and some tweaking to recover the bootanimation (lost on custom builds) among other things.
But hey, I've build a production pre-release of firefox os 1.2, and so far so good , and I like to share it with you via a flashable .zip file. Remember this file can be installed ONLY from CWM recovery, cause its not signed
features:
Version 1.2-prerelease (user release):
Build with blobs from version 1.1.0B02 (also known as 1.1.0B06) for ZTE Open (EU version)
Multilanguage - upgradeable through B2G nightlies (for both gecko & gaia)
Compatible with firefox app-manager (firefox 26+)
Includes su & busybox binaries ( busybox is linked with clear, grep, head, less, lsmod, more, nohup, pidof, ping, printf, pstree, sysctl, tail, telnetd, tftpd, traceroute, uname & usleep, for debugging via adb)
No carrier branding, just official firefox os branding
Fastboot enabled | ADB rooted
does *NOT* overwrite your recovery partition (you won't loose CWM recovery )
known bugs: isn't a bug but a security feature: "ADB should not be allowed to connect when device is locked in production builds"
FAQ:
I'm on version 1.x.y of 'some-carrier' build, Will this zip work in my case: Yes, only and just only if you have CWM installed.
There are a lot of strange files inside .zip, why ? this is because ZTE provides upgrades with radio & bootloader firmware (incompatibles between versions) If I want to support this ROM I need to make sure everyone have the same version ( the version that matches with the blobs )
Of course, YOUR WARRANTY IS VOID, and if you brick your phone , this is NOT MY FAULT
the link to the zip file: ul.to/2jwkruhj​
Feedback is welcome

paziusss said:
Hello again:
Build B2G for ZTE Open (inari) is tricky. People who want to develop applications with firefox's app-manager extension need to wait for ZTE upgrades or build their own system, which involves some permission modifications in boot.img and some tweaking to recover the bootanimation (lost on custom builds) among other things.
But hey, I've build a production pre-release of firefox os 1.2, and so far so good , and I like to share it with you via a flashable .zip file. Remember this file can be installed ONLY from CWM recovery, cause its not signed
...
Feedback is welcome
Click to expand...
Click to collapse
Runs great, I will use your build to test and mod some apps with the app-manager.
And please, stay at this good work (updates etc?!)
---edited:
Is your build a development build (of FFOS 1.2)? I cant't open certified apps with the app-manager (I have changed the pref "devtools.debugger.forbid-certified-apps" to false in my profile. But there is no certified app to see or to open in the app-manager. If not, can you - or somebody else - build this development build of FFOS 1.2?

ROM is pretty stable. I don't know if I'm the only one having this issue, but it looks like my data is connecting but then it isn't working. I'm connected to AT&T right now. When I pull down the notification bar, I see that I am getting an "H" (HSPA+) signal but if I try to open firefox and hit a site, it says I'm not connected to the internet.
I'm aware that this is in a prerelease state but do you know how I could fix this?

@martin_s5670: AFAIK there are three types of builds: engineer builds, userdebug builds and user builds. This is an user build, but you can also test privilegied (aka certified) apps on it. If you want to see your installed system apps I'm sorry but you can't do it in this way
@ryanolson7: could you please test your connection via a ping
adb shell
ping www.google.com
if you can't reach google, then I would appreciate if you paste somewhere your logcat in this way:
adb logcat | grep RIL > file.log
and just deactivate data, wait a few seconds, and activate it again.
---
I'll do some further tests on this branch (because some blobs may change from 1.0.1) but here in Spain both 3G & 2G data seems to works well, need to find a place with HSPA+.
Are you in the USA? I'm asking because this rom is based in open_eu release ( AFAIK they are the same except for radio capabilities )
Thanks for the feedback

Great Job!
Thanks! Tried and working. I have even received a update, and still working smooth!

can you tell me about the creating this ROM process?
I'm using US rom, I just want to use these blobs to make a custom builds, but flashing all the images bricked my phone. Can you explain me about the steps you did to package this ROM?

paziusss said:
...
Feedback is welcome
Click to expand...
Click to collapse
@ paziusss:
Maybe a littele bug: The app "calendar" starts everytime when your build will be booted - without open it separetly.

im new here
i want to know if i can use this in my nexus 4 multirom android 4 KK

Need FF OS 1.3
Can anyone please provide me zip file of FF OS 1.3?
Thanks

LinuxHolic said:
Can anyone please provide me zip file of FF OS 1.3?
Thanks
Click to expand...
Click to collapse
Not quite a zip, but, https://daylightpirates.org/b2g_inari_nightly_builds/

Bad Luck
Deathwish238 said:
Not quite a zip, but, https://daylightpirates.org/b2g_inari_nightly_builds/
Click to expand...
Click to collapse
I flashed the latest nightly build and everything went fine but my mobile is sitting on Fox now and restarts constantly

Look
LinuxHolic said:
I flashed the latest nightly build and everything went fine but my mobile is sitting on Fox now and restarts constantly
Click to expand...
Click to collapse
groups [dot] google [dot]com/d/msg/mozilla.dev.b2g/dENpc-7Fbi4/80t6EyS6bwIJ

is the included radio for european or american zte opens?

@hecatae:
blobs were pulled from 1.1.0B02 - UK but radio firmware should be the same for both UK and US versions

paziusss said:
Hello again:
Build B2G for ZTE Open (inari) is tricky.
Feedback is welcome
Click to expand...
Click to collapse
HI!
Can you build with added Russian keyboard?
I wanna use 1,2. Because it have RU locale, but have not keyboard.... (((
At 1.1. have not RU locale, but it have RU keyboard

FM radio doesn't work, no sound.

Japanese?
Could someone enable the Japanese keyboard and provide a ROM? I can explain how to do it, just can't build for it

thanks
thanks for your rom

Wireguard module for stock OOS 9.0.14/15?

Hello,
Can anyone suggest a reasonable method to get wireguard support into the stock OOS kernel? I had hoped I could extract the .ko file from a compatible custom rom (9.0.15's kernel is the same as 9.0.14's), but it seems everything is statically linked (I've done kernel work but not on android before).
I also looked into compiling OOS myself with just the wg tweak but got lost in gcc/clang/cross-compilation and gave up after a while. If there's some build automation someone could recommend I steal from that would be really helpful also.
Appreciate any tips!

teslacuted said:
Hello,
Can anyone suggest a reasonable method to get wireguard support into the stock OOS kernel? I had hoped I could extract the .ko file from a compatible custom rom (9.0.15's kernel is the same as 9.0.14's), but it seems everything is statically linked (I've done kernel work but not on android before).
I also looked into compiling OOS myself with just the wg tweak but got lost in gcc/clang/cross-compilation and gave up after a while. If there's some build automation someone could recommend I steal from that would be really helpful also.
Appreciate any tips!
Click to expand...
Click to collapse
If you are rooted, look around there are a couple of custom kernels with wiregaurd support