Hi everyone,
I have been working on an android build for the HTC Titan for a while and I have been trying to get the wifi to work. I have all of the drivers in the system.sqsh but now the problem lies with the init.rc. A sysinit.rc came with the drivers, and there was an unmodified version, and then one with just the needed wifi fixes. Neither of them boot on my device, however when I leave the sysinit.rc out of my system.sqsh, the build uses "/ion.init.rc". This file works like a charm! I have searched the rootfs, and system.sqsh but cannot find this file. Can somebody point me in the direction of finding it? If I can get this file then I am confident that I can get the wifi to work. Thanks in advance for your help. - Jemilio3
Related
Hi all, I'm sorry if I posted this in the wrong place.
I have an Archos 32 and I have an ad-hoc wireless network at my home. I've been trying to get my Archos 32 to connect to it and the only way that I have done so is through UrukDroid 1.0. UrukDroid however won't allow me to run some applications such as Camera and WeatherBug that I really would like to be able to run (they just crash). So I downloaded the GPL Source Code from Archos and made the changes to the wpa_supplicant source code via the patch that is found online. I've followed the guide on CNXSoft (can't post the link) for compiling the entire source on Ubuntu 10.10 (although I'm running 11.04). I have successfully created a zImage and a cramfs file, as well as a squashfs file. What do I do now? Are there any more steps that I need to do as far as installing it on my device? I've searched high and low and can't find anything so I figured I would post here. If someone could help me I'd appreciate it.
Lol I can't believe this is such a hard question that nobody knows how to answer it.
Anyway, I got it sorted, sorta. With wifi on the device turned off, I deleted the wpa_supplicant.conf from /data/misc/wifi, and changed the WifiAdhoc value to 1 in /data/misc/wifi/tiwlan.ini, then pushed it over, as well as a patched wpa_supplicant file via ADB over to the device. Now I can connect to my adhoc network on 2.3.26, and still have WeatherBug and the Camera and all the other apps that crashed on UrukDroid. The only drawback is that the wpa_supplicant file gets replaced with the original one everytime I reboot the device. Not sure how to avoid that. So everytime I reboot the device I have to copy the patched wpa_supplicant file again. But other than that it works great.
Anyway thanks for reading.
I've been trying to build a ROM over on the US variant all day (T-Mobile) but I can't get the Cygwin Kitchen to work properly (its something with the updater-script that's causing an installation abort). I played with it for a while and figured out (or I'm assuming at least) that it's related to /tools/edify_defs folder needing the creation of the necessary "d2tmo" file to point out mounting points.
I've read over and over and over the template for creating the file, but I can't seem to figure out how to script the necessary file. I lack the experience. I've tried referencing the SGS2 template, as well as others, plus referencing the original updater-script to try and find the mount points, but I can't seem to get it.
There aren't very many of us on the US variant just yet, due to the small quantity release, so there aren't many people to reference for help.
Any help at all would be GREATLY appreciated...
uoY_redruM said:
I've been trying to build a ROM over on the US variant all day (T-Mobile) but I can't get the Cygwin Kitchen to work properly (its something with the updater-script that's causing an installation abort). I played with it for a while and figured out (or I'm assuming at least) that it's related to /tools/edify_defs folder needing the creation of the necessary "d2tmo" file to point out mounting points.
I've read over and over and over the template for creating the file, but I can't seem to figure out how to script the necessary file. I lack the experience. I've tried referencing the SGS2 template, as well as others, plus referencing the original updater-script to try and find the mount points, but I can't seem to get it.
There aren't very many of us on the US variant just yet, due to the small quantity release, so there aren't many people to reference for help.
Any help at all would be GREATLY appreciated...
Click to expand...
Click to collapse
Ok, we got all the proper mounting points now but we're getting no SIM card reading now.
Any suggestions?
Sent from my SGH-T999 using xda premium
Here is our progress if anyone could be so nice to give it a look over and see if you could lend a hand.
http://forum.xda-developers.com/showthread.php?t=1729966
hey, I'm in the process of trying to build for tmoUS too. using dsixda kitchen but keep getting stuck at the "extracting ROM", the process just doesn't seem to want to complete. any help?
Hello!
I need help from developers or those familiar with the file structures of the android system.
Let me explain, I have a Chinese touch pad. I tried to install several custom rom (CM9, AOKP, etc ...) as well as Roma manufacturer of tablet very similar to mine (A90 Ampe, Sanei N90, etc ...).
The flash firmware or install via Recovery is done very well. The android starts very well. However, the only problem I have is that my touchscreen is not responding.
Indeed, I have to connect a mouse to use my tablet.
So here the object of my request. I love and I think it is possible created a sort of patch to apply via the recovery or via command ADB with the "drivers" of my touchscreen from my original rom.
For info, I already decompiled the image of my ROM so I have access to the entire file structure. But I do not know enough to identify which files that match the drivers of the screen.
Ya-til someone help me on the files or the place where he could find?
Thank you for your help.
For help, please find attached a complete list of the file structure of the ROM manufacturer.
list HTML
list txt
Help please!
Hi there,
I recently bought the wonderful Samsung Note 10.1 2014 and am looking to add loop device support to the kernel for the sake of booting *nix using the good old VLC trick. Even though I'm a software engineer and no stranger to Linux (or fstab), I'm very green when it comes to Android development.
When trying to run the bootup script, I recieve "mknod /dev/block/loop255 b 7 0". I.E my kernel doesn't support loopback devices.
I have extracted the kernel contents (ramdisk and init img) but was wondering whether anyone can give me a shove in the right direction when it comes to setting up the device.
So far, after a brief investigation, I have found the fstab.goldfish file which strikes me as looking just as I'd expect to see it on a normal box. Can anyone provide a quick shove in the right direction for knowledge (preferred) or even has a snippet from an existing unpacked kernel I may "borrow", Google was not my friend in such pursuit.
--Edit--
Looking through the build.prop, would simply disabling selinux give root permission to create a loop device? This again boils down to my warped inherent knowledge of Linux in general, sorry if it seems a poor question.
--Update--
I guess if the kernel wasn't compiled with support (as it appears it wasn't) there is no hope of modifying the stock ROM to achieve my goal? On the Samsung OSC, they have SM-P605_HK SM-P605_HK_JB_Opensource.zip so, I'm taking a look in there and will keep you posted just in case anyone is the least bit interested.
--Resolution--
I guess this thread can be ignored now, I'm pulling the config from my tablet, changing the kernel compile config and will test it out tomorrow. If in doubt, compile
symbal said:
Hi there,
I recently bought the wonderful Samsung Note 10.1 2014 and am looking to add loop device support to the kernel for the sake of booting *nix using the good old VLC trick. Even though I'm a software engineer and no stranger to Linux (or fstab), I'm very green when it comes to Android development.
When trying to run the bootup script, I recieve "mknod /dev/block/loop255 b 7 0". I.E my kernel doesn't support loopback devices.
I have extracted the kernel contents (ramdisk and init img) but was wondering whether anyone can give me a shove in the right direction when it comes to setting up the device.
So far, after a brief investigation, I have found the fstab.goldfish file which strikes me as looking just as I'd expect to see it on a normal box. Can anyone provide a quick shove in the right direction for knowledge (preferred) or even has a snippet from an existing unpacked kernel I may "borrow", Google was not my friend in such pursuit.
--Edit--
Looking through the build.prop, would simply disabling selinux give root permission to create a loop device? This again boils down to my warped inherent knowledge of Linux in general, sorry if it seems a poor question.
--Update--
I guess if the kernel wasn't compiled with support (as it appears it wasn't) there is no hope of modifying the stock ROM to achieve my goal? On the Samsung OSC, they have SM-P605_HK SM-P605_HK_JB_Opensource.zip so, I'm taking a look in there and will keep you posted just in case anyone is the least bit interested.
--Resolution--
I guess this thread can be ignored now, I'm pulling the config from my tablet, changing the kernel compile config and will test it out tomorrow. If in doubt, compile
Click to expand...
Click to collapse
I believe "CONFIG_BLK_DEV_LOOP" is the config option you are looking for.
Hi everybody,
I compiled my own CM-11 for my Galaxy Tab 2 10.1 (P5110) following this guide and got the following issue.
It is not possible to switch on the WLAN. When I move the switch to 'On' no WLANs are shown and it says "To see available networks, turn Wi-Fi on" that's it?
For testing purposes I've installed cm-11-20160320-NIGHTLY-p5110, there Wlan is working.
Any ideas or hints to figure out what's wrong?
Regards Pete
Cause I suspected missing drivers, I've adapted the script 'extract-files.sh' to pull the proprietary files out of the ROM mentioned above.
Thereafter I recompiled my ROM, but Wifi is still not working. The output of logcat and dmesg is attached.
Thanks for any help!
Regards Pete
...I'm a step further.
To have the same conditions as in the nightly, i build a ROM with the 'build_manifest.xml' out of the nightly. After a comparison of both, I've found out that in my ROM in the directory '/system/etc/wifi' the following files are missing:
Code:
bcmdhd_p2p.bin
nvram_mfg.txt
nvram_net.txt
I've copied these files from the 'nightly' to my ROM and guess what... WLAN is working now!
But there's still one question left, why aren't these files compiled with my ROM?
Does anybody know the answer for this?
Regards
Pete