Related
Hello.
I use "RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1" and i like it except wifi issue.
All works good with static IP, all connecting using DHCP, but there is not traffic when DHCP is using ("Destination Host Unreachable" for any host after gateway)
Full description you can read in this post
Is there any fixes for Incredible S? Or maybe not binary fixes for other phones, i can try to make patch for IS.
I found solution:
* cdumpp.blogspot dot com/2011/09/wifi-dhcp-android-233.html - Description (RU, you can use Google Translate for English version)
Change /system/etc/dhcpcd/dhcpcd-hooks/95-configured
Code:
#setprop dhcp.${interface}.gateway "${new_routers%% *}"
gateway=`echo ${new_classless_static_routes}|egrep -o "0.0.0.0/0 [0-9\.]*"|cut -c 11-`
if [ -n "${gateway}" ]; then
setprop dhcp.${interface}.gateway "${gateway}"
fi;
I can confirm this work for HTC Desire with Leedroid 3.08.2 ROM aswell
Modded the file and disabled "Wifi-Static" to test it
Works good again now using DHCP on the old Routers
Thanks for the solution !
SebastianFM has kindly agreed to provide support to fix issues.
That i think is a fantastic news
so please show your appreciation by thanking for the SFM 3.0.2 Magic|Android 2.3.3|Sense 2.1 ROM
Click to expand...
Click to collapse
I REQUEST/ENCOURAGE ANY DEV OUT THERE WHO WOULD LIKE TO TAKE OVER
OR START A FRESH TO BUILD GB-SENSE ROM PLEASE DO SO,
THIS THREAD IS MAINLY FOR INFORMATION PURPOSE
Click to expand...
Click to collapse
warning/disclaimer:
I am not maintaining this ROM, i have only transported this from SFM 3.0.2 Magic|Android 2.3.3|Sense 2.1
initial attempt was on SenseonFire ROM from wildfire
please don't bother this thread with trivial questions
this ROM is only for testing purpose and inspiration for further development only
I started this, with intention of porting the ROM, only to realize that I am not smart enough to fix most things.
I am not claiming to be dev as i am not, so posting the info for you to proceed or dump the project.
WIP <- working in pause (not work in progress)
I thank
SebastianFM for the first porting, which made possible most of the other device ROMs SFM 3.0.2 Magic|Android 2.3.3|Sense 2.1
all those involved in SenseonFire ROM project on wildfire especially VigiDroid,
and Arco for building an awesome kernel and nFinityGB v1.13 ROM for tattoo and some of the files were taken from this ROM
and dsixda's Android Kitchen
Click to expand...
Click to collapse
The main reason I have opened this thread is, to make you aware of the promising future out there for sense lovers using tattoo
and sow some seeds of inspiration for a dev out there who could fix this for us.
What i did
I took the SFM 3.0.2 Magic|Android 2.3.3|Sense 2.1 ROM used dsixda's Android Kitchen utility to transport and then adjusted few libs and binaries to get the phone started
Used Arco's 2.6.35.14 kernel and files from his nFinityGB v1.13 ROM
and added Robot font from following thread http://forum.xda-developers.com/showthread.php?t=1316156
i moved system/app folder to cache/systemapp and symlinked to system due to less space in system partition
Click to expand...
Click to collapse
things like gps, fm and camera are not working on tattoo, many apps need resizing or font size needs reducing.
when i did benchmarking using cf-bench apk, the score i got was more than 500 close twice to what i got with tatfroyosense. Benchmark done at 633 Mhz max cpu
rom link and snapshots
Download links
SFM port version 1.2.1
mediafire
4shared
Changelog
V1.2.1
Pooled all patches together and few minor changes
V1.2
Few apks resized
ROM is by default Overclocked
framework symlinked from cache partition
wipe cache, data before flashing the ROM
First boot takes about 5-10 mins
Main issues:
GPS
Camera
FM
Media player sound OK - video is white
no notification lights (but button lights OK)
Battery drain - if wifi on
and other issues from user (??)
old versions
SFMportv1.2
http://www.mediafire.com/?uzutj2tura75oyr
SFMportv1.1
http://www.megaupload.com/?d=KXLUD91K
SenseonFire port link
http://www.megaupload.com/?d=UYZ4V0WJ
the rom has edify scripting and is unsigned, could be installed with clockworkmod recovery
Click to expand...
Click to collapse
This is cool. I never expected Tattoo to run anything heavy like this.
Feeling proud of you, man! With tears in my eyes.
Sent from my HTC HD2 with my fast fingers.
Waiting for news!!
Umm well, regarding eth0 and tiwlan0, they are just hardware access points for the required device. The Unix/Linux system often puts all devices as files in /dev/. So when it needs to call a particular device, it calls that file and output to that device is piped back into the file.
So eth0 refers to the Ethernet (Wired LAN) interface, while tiwlan0 is the WiFi (Wireless LAN). The problem with older kernels (ralle.gade) is that they list WiFi as standard wired LAN device. Newer kernels list them properly (Arco's kernel). So its just a matter of changing /dev/eth0 to /dev/tiwlan0 in the wpa_supplicant and other wifi config files and wifi will run as needed. i am saying this as far as what i know about configuring desktop linux.
and about camera and videorecorder, u can get the drivers from CM7 and merge with this. For FM, u could get get drivers from CM7 and replace the HTC FM app with the one from CodeAurora or MIUI.
I am interested to help. But it seems I have got some other priorities to attend to. I will be free after April 2012. Then I will brush up my C++ skills and see if I can help u all.
...
too bad,this rom would be perfect if bt, gps, wifi, camera would working on tattoo...
sunitknandi said:
Umm well, regarding eth0 and tiwlan0, they are just hardware access points for the required device. The Unix/Linux system often puts all devices as files in /dev/. So when it needs to call a particular device, it calls that file and output to that device is piped back into the file.
So eth0 refers to the Ethernet (Wired LAN) interface, while tiwlan0 is the WiFi (Wireless LAN). The problem with older kernels (ralle.gade) is that they list WiFi as standard wired LAN device. Newer kernels list them properly (Arco's kernel). So its just a matter of changing /dev/eth0 to /dev/tiwlan0 in the wpa_supplicant and other wifi config files and wifi will run as needed. i am saying this as far as what i know about configuring desktop linux.
Click to expand...
Click to collapse
I dont think this is issues with old and new kernel, they all had access points as tiwlan0 (fyodor, ralle.gade and arco).
So far to my understanding it is device specific (see below).
Dexter seems to have tweaked the module and wpa_supplicant from ralle.gade's kernel to work with Froyo, i dont know what was changed. to get wifi working
EDIT: eth0 limitation is with hardware used in the device
Devices like: Wildfire, Wildfire S, Icon-G and Explorer -have their the access point setup as eth0 and they all have broadcom chip
while Tattoo, Magic and Hero -have tiwlan0 as the access point and they all seem to TI chip
in that case, lets ask dexter. he can help.
sunitknandi said:
in that case, lets ask dexter. he can help.
Click to expand...
Click to collapse
I asked him, he still hasn't responded...
P.S.
i get this from the logcat: " wifi_load_driver end error 2" and from dmesg i get something like: "firmware_path unknown value"
I researched and foundout that the deire had similar problems, but they had a previously working dirver and just couldn't conect....
So that leaves me nowhere again... (sadface)
Few things that i have't mentioned earlier:
Following are the commands in wpa_supplicant script for tatfroyosense
Code:
/system/bin/insmod /system/lib/modules/wlan.ko
/system/bin/wlan_loader -f /system/etc/wifi/Fw1251r1c.bin -e /proc/calibration -i /system/etc/wifi/tiwlan.ini
/system/bin/wpa_supplicant.bin -Deth0 -ieth0 -c/data/misc/wifi/wpa_supplicant.conf
As it is tiwlan0 interface in Arco's kernel, i have copied wlan_loader, wlan_cu, wpa_supplicant, wpa_cli binaries from nFinityGB rom along with /system/etc/dhcpcd folder and the wifi module. (These are already in the ROM attached)
As some of you might have noticed:
module wont load at boot
so i have tried to execute following commands from shell (they are in the init.rc script except insmod of module)
Code:
/system/bin/insmod /system/lib/modules/wlan.ko
/system/bin/wlan_loader -f /system/etc/firmware/Fw1251r1c.bin -e /proc/calibration -i /system/etc/wifi/tiwlan.ini
/system/bin/wpa_supplicant -Dwext -itiwlan0 -c/data/misc/wifi/wpa_supplicant.conf
module loads fine but then wlan_loader give following error
Code:
rtnl_open: Protocol not supported
Hello mate. Is it possible to provide a github repository with the code?
ntenisOT1948 said:
Hello mate. Is it possible to provide a github repository with the code?
Click to expand...
Click to collapse
I dont think HTC source code out there for sense andriod phones.
The time line for this ROM is as follows:
HTC Salsa was ported to Sapphire
http://forum.xda-developers.com/showthread.php?t=1025330
From Sapphire to wildfire
http://forum.xda-developers.com/showthread.php?t=1067868#13557996
wildfire then updated to this
http://forum.xda-developers.com/showthread.php?t=1269485
From above ROM to this ROM
Following files were taken from nFinityGB v1.13 ROM to this ROM
Code:
Filename Folder
wlan_loader system\bin
wpa_cli system\bin
wpa_supplicant system\bin
vold.fstab system\etc
dhcpcd.conf system\etc\dhcpcd
brf6300.bin system\etc\firmware
brf6350.bin system\etc\firmware
Fw1251r1c.bin system\etc\firmware
tiwlan.ini system\etc\wifi
wpa_supplicant.conf system\etc\wifi
Clockopia.ttf system\fonts
DroidSans-Bold.ttf system\fonts
DroidSans.ttf system\fonts
libwpa_client.so system\lib
copybit.bahamas.so system\lib\hw
gps.bahamas.so system\lib\hw
gps.goldfish.so system\lib\hw
gralloc.bahamas.so system\lib\hw
gralloc.default.so system\lib\hw
lights.bahamas.so system\lib\hw
sensors.bahamas.so system\lib\hw
sensors.goldfish.so system\lib\hw
wlan.ko system\lib\modules
bahamas-keypad.kcm.bin system\usr\keychars
bahamas-keypad.kl system\usr\keylayout
AVRCP.kl system\usr\keylayout
vim system\usr\share
colors system\usr\share\vim
filetype.vim system\usr\share\vim
ftoff.vim system\usr\share\vim
indent.vim system\usr\share\vim
indoff.vim system\usr\share\vim
scripts.vim system\usr\share\vim
blue.vim system\usr\share\vim\colors
darkblue.vim system\usr\share\vim\colors
default.vim system\usr\share\vim\colors
delek.vim system\usr\share\vim\colors
desert.vim system\usr\share\vim\colors
elflord.vim system\usr\share\vim\colors
evening.vim system\usr\share\vim\colors
koehler.vim system\usr\share\vim\colors
morning.vim system\usr\share\vim\colors
murphy.vim system\usr\share\vim\colors
pablo.vim system\usr\share\vim\colors
peachpuff.vim system\usr\share\vim\colors
ron.vim system\usr\share\vim\colors
shine.vim system\usr\share\vim\colors
slate.vim system\usr\share\vim\colors
torte.vim system\usr\share\vim\colors
zellner.vim system\usr\share\vim\colors
VoiceDialer.g2g system\usr\srec\config\en.us\grammars
wlan_cu system\xbin
Great news guys
I got wifi and bluetooth working
As i mentioned the history of the ROM in previous post,
It occured to me, may be i can start fresh from Sapphire ROM
So i went to the follwoing post and started with SFM 3.0.2
http://forum.xda-developers.com/showthread.php?t=1025330
and with rough porting i could get wifi and bluetooth working and i bet gps would also work.
you know it was quick and dirty port (huge size and bad layout),
now we can do proper port with relayout and resizing the framework and would be better ROM
Cool... Keep up the hard work. Once u finish the port, we can get someone to optimise it.
Have you updated the download link? Iwould like to have a look to graphics to know if I can do anything about them.
Edit: I can see you don't. But I'm going to start trying to resize some graphics as a practice for future.
2nd post updated with new rom port
some of the applications are not working and poor layout.
Alternative launcher like adw working fine
I't seems there's many other people waiting for news: http://bbs.hiapk.com/thread-2741601-1-1.html
I don't know if it's chinese, or what!
Enviado desde mi HTC Tattoo usando Tapatalk
sense zero on tattoo
Now that i could port (transport) GB sense, i wanted to have a crack at sense zero (it was to decide which one would be best carry on)
so I did try port Hintay Zero 0.14 (Sense 3.5 Android 2.3.5)
and i could get it booted on Tattoo,
but have to set lcd density to 100, so that you can see launcher work.
But most of other things look decent if it is set to 120.
And you can see that layout and size are bad.
but i have to say it takes lot of memory and gets very slow.
framework moved to cache to make space in system.
takes 10 mins on first boot
here the link
http://www.megaupload.com/?d=X1B721BZ
and snapshots
GbermuG said:
I't seems there's many other people waiting for news: http://bbs.hiapk.com/thread-2741601-1-1.html
I don't know if it's chinese, or what!
Enviado desde mi HTC Tattoo usando Tapatalk
Click to expand...
Click to collapse
Yes, its a chinese forum. Gave a try using BabelFish and Google Translate, but it is very messy.
Text like HTC Tattoo intelligent handset gets HTC Sence 3.0 on Peace Outstanding 2.3. (read as smartphone gets htc sense on android version 2.3)
F**k translators. I preferred to read no more.
sunitknandi said:
Yes, its a chinese forum. Gave a try using BabelFish and Google Translate, but it is very messy.
Text like HTC Tattoo intelligent handset gets HTC Sence 3.0 on Peace Outstanding 2.3. (read as smartphone gets htc sense on android version 2.3)
F**k translators. I preferred to read no more.
Click to expand...
Click to collapse
That's what I can understand using translators: they've tried it, and like it. They thik is smooth and powerfull, but ram memory is low. Someone is asking about Sense 3.0, but the tread is not updated, so they only tried SenseonFire (first port). Simply (as I said), they're waiting.
Cifs.ko module for galaxy tab 7.7 for stock galaxy kernel.
EDIT - pinkowl has updated the cifs module with nls_utf8 support.
Please see use his updated download link from post 12.
cheers
Should allow mounting of windows/samba shares.
from terminal (connectbot, script etc)
$ insmod cifs.ko (where you saved cifs.ko path)
Please could you test. For me it is working. however a few issues:
but video players stutter but so far bs player lite works best me for media network streaming.
edit - is it down to poor wifi performance - however same files play fine over http streaming from nas!
so proper dev required to looked into performance issues.
Using cifs manager to mount share & es explorer free edition allows you to copy to root etc.
Looks good to me ~8mins for 501M (what are you aiming for?):
P6810(wifi), RTN-16 router,Fedora16 samba share
bash-4.2# insmod cifs.ko
bash-4.2# mount -t cifs -o user=XXX,passwd=XXXXXX //192.168.2.113/XXX /data/local/tmp/mnt
bash-4.2# pwd
/data/local/tmp
bash-4.2# cd mnt
bash-4.2# ls
Desktop
Documents
Downloads
Music
Pictures
Public
Templates
Videos
eclipse
workspace
bash-4.2# time cp /data/local/tmp/junk_1 junk_1_back
real 8m20.644s
user 0m0.275s
sys 0m35.175s
bash-4.2# time cp junk_1_back /data/local/tmp/junk_2
real 7m46.706s
user 0m0.240s
sys 0m24.630s
bash-4.2#bash-4.2# md5sum ../junk_2
b6cee9135f8f4fd8ed03bfcc641de7b1 ../junk_2
bash-4.2# md5sum ../junk_1
b6cee9135f8f4fd8ed03bfcc641de7b1 ../junk_1
bash-4.2#
bash-4.2# ls -l ../junk*
-rw-rw-r-- root root 524288000 2012-01-22 03:42 junk_1
-rw-r--r-- root root 524288000 2012-01-22 04:35 junk_2
Awesome - worked perfectly with the root pack from this forum as well.
Now.... do you have tun.ko for this tab as well please?
Ive found a couple of versions - but they have not been compiled for this rom from the looks and do not load correctly.
Is the tun.ko file available at all yet?
Did another run with some optimisations:
Locked router to N mode instead of mixed
Discovered busybox cp poor performer, used /system/bin/cat instead
Tried kernel setting on
echo 1 > /proc/sys/net/ipv4/tcp_low_latency
Which definitely helps my ssh session, but not sure much impact on this test.
#same 501M file as previous post
#copy server to 7.7
time cat junk_1_back > ../junk_1_47
real 6m52.908s
user 0m0.240s
sys 0m24.390s
#copy from 7.7 to server
bash-4.2# time cat ../junk_1 > junk_1_xxx5
real 3m35.079s
user 0m0.040s
sys 0m19.890s
#copy server to /dev/null on 7.7
bash-4.2# time cat junk_1_xxx3 > /dev/null
real 6m45.223s
user 0m0.115s
sys 0m15.695s
All files intact, I think your module is good, I think kernel tcp params or wireless may need tweaks as suspected in wireless problem thread.
---------- Post added at 11:29 AM ---------- Previous post was at 11:17 AM ----------
cbdrift said:
Awesome - worked perfectly with the root pack from this forum as well.
Now.... do you have tun.ko for this tab as well please?
Ive found a couple of versions - but they have not been compiled for this rom from the looks and do not load correctly.
Is the tun.ko file available at all yet?
Click to expand...
Click to collapse
? Its built-in to kernel:
bash-4.2# uname -a
Linux localhost 2.6.36-P6810DTKL5-CL604290 #3 SMP PREEMPT Wed Dec 14 18:05:58 KST 2011 armv7l GNU/Linux
bash-4.2# ls -l /dev/tun
crw-rw---- vpn vpn 10, 200 2012-01-24 08:23 tun
ezynow:
thanks for sharing the cifs.ko module.
willl you be kind enough to teach me how to get my Windows 7 home premium hooked with cifs?
i tried and search the www and the closest solution i had is to view my shared folder using Ghostcommander with SMB plugin.
however, i cannot mount the share drive as a folder using either
cifsmanager or mount manager
i have tried to do regedit in my Win7 home premium since there is not "local security policy" program for this version of Win7.
Sorry for disturb
Plz, can anybody tell me what is this and how to use it?
i got an error when i add the iocharset=utf8 in the option at cifs manager, how can i make it use utf8?
I place this file in root directory of my sd card.
use terminal emulator program and type
insmod /mnt/sdcard/cifs.ko
but I got
insmod: init_module '/mnt/sdcard/cifs.ko' failed (Operation not permitted)
what should i do
Sent from my GT-P6800 using xda premium
theerachai said:
I place this file in root directory of my sd card.
use terminal emulator program and type
insmod /mnt/sdcard/cifs.ko
but I got
insmod: init_module '/mnt/sdcard/cifs.ko' failed (Operation not permitted)
what should i do
Sent from my GT-P6800 using xda premium
Click to expand...
Click to collapse
try from root
su
then insmod /pathtocifs.ko/
solved, thank you very much
Sent from my GT-P6800 using xda premium
The issues with video playback is not really with cifs, but with caching done by the players.
Typically, a player streaming over http expects a long delay and will use a larger buffer. Playing over cifs, the player will think it's locally stored and no buffer is necessary. That lack of buffer is causing the problems.
I have compiled the nls_utf8.ko module as well as recompilied the module cifs.ko for those of you that needs it. Files are attached in this post.
This is for the stock kernel from the LA2 firmware which I am using. If you are using the stock kernel from Samsung, this should work for you.
If this helps you, pls click on the "thanks" link.
Thanks for this module. I've known about cifs but never tried it before. Now I thought I'd give it a go and it's great. Had a few initial noob problems but now all OK. And using Cifs Manager makes mounting my NAS a breeze.
I can watch all my 720p video files stored on my NAS. Using BS player as suggested by ezynow.. Thanks ezynow!
Thank
Tested ,work well .
pinkowl said:
If this helps you, pls click on the "thanks" link.
Click to expand...
Click to collapse
I'm new here.
can you tell me where the "thanks" link is? pls
because your file helps me a lot~
pinkowl said:
I have compiled the nls_utf8.ko module as well as recompilied the module cifs.ko for those of you that needs it. Files are attached in this post.
This is for the stock kernel from the LA2 firmware which I am using. If you are using the stock kernel from Samsung, this should work for you.
If this helps you, pls click on the "thanks" link.
Click to expand...
Click to collapse
Nice one - i will update the main thread & creditation to you for this
Thanks a lot for these modules. I use them to access shares on my home network.
I found only one small problem accessing shares on my Windows 7 x64 host. If I use iocharset=utf8 as a parameter I can see the segmentation fault message when trying to mount a share from this host. Without iocharset parameter it works ok (apparently all unicode filenames are not shown correctly)
Exactly the same setup works fine with shares from my router and unicode filenames are displayed correctly.
@original poster
Can you rebuild this for ICS, please?
m0bster said:
@original poster
Can you rebuild this for ICS, please?
Click to expand...
Click to collapse
You can't rebuild this until Samsung release the ICS source code used to compile the kernel. Hopefully they do so soon but I am not holding my breath.
New kernel released. Can anyone compile cifs.ko and nls_utf8.ko?
Hi guys,
i need some help with wifi tethering/Portable Hotspot
right now i using CM7.2 GINGERBREAD V10 (ALFS kernel V7 ICS) with ALFS V7 ICS kernel.
As i read in the CM7.2 thread, i install Wifi Tether attach in post #2,
i start the wifi tether, and it say, "start with error, please check the log" or something like that
Please check the attachment for the log.
What did i do to solve this problem :
Start Fresh, Wipe data, cache, dalvic cache, format system
install stock ROM + Kernel (E15i_2.1.1.A.0.6_RU.ftf) using flash tool,
and Install NAA kernel 11 + MiniCM7-2.1.9 (As i read NAA + miniCM rom support Native GB hotspot) - The result is : when i start Portable Hotspot it start ok, connecting ok, but cannot browse the web, in the laptop it says "DNS ERROR"
So i flash again ALFS V7 ICS kernel over NAA and flash CM7.2 GINGERBREAD V10,
trying again with wifi tether and no luck
My Question :
1. What happen with my phone? is this something i do wrong when flashing?
2. Is it possible the carrier/operator blocking Tethering?
3. Is there someway to solve this problem?
Please note :
1. Before i was successful starting Portable Hotspot with NAA kernel, but because a2sd error i think i try to start fresh with NAA kernel + MiniCM rom, n thats when this problem occurs
2. I can connect to wifi or Adhoc wifi with no problem
Thanks Guys n sorry for the bad english
Looking at the two screenshots where you got errors reported it would seem as the wireless tether thingy doesn't find the required kernel modules, although they should be part of both kernels you mentioned - though I'm not sure if the "CM7.2 GINGERBREAD V10" ROM is compatible with Alfs.
I would ask in either Alfs' or nAa's thread about what may be wrong here; from my viewpoint it's missing modules that should be part of the kernel already.
B.Jay said:
Looking at the two screenshots where you got errors reported it would seem as the wireless tether thingy doesn't find the required kernel modules, although they should be part of both kernels you mentioned - though I'm not sure if the "CM7.2 GINGERBREAD V10" ROM is compatible with Alfs.
I would ask in either Alfs' or nAa's thread about what may be wrong here; from my viewpoint it's missing modules that should be part of the kernel already.
Click to expand...
Click to collapse
hi... thanks for ur reply
can we check it? i mean for the module?
maybe we can look on a folder n check that the module is there or not?
for the CM7.2 GB V10 ROM, i think it only using ALFS Kernel (ALF V7 ICS), so it should be compatible.
i really like to post on the NAA and ALFS thread but as u can see, iam lack of post
lanjor said:
hi... thanks for ur reply
can we check it? i mean for the module?
maybe we can look on a folder n check that the module is there or not?
for the CM7.2 GB V10 ROM, i think it only using ALFS Kernel (ALF V7 ICS), so it should be compatible.
i really like to post on the NAA and ALFS thread but as u can see, iam lack of post
Click to expand...
Click to collapse
Errr.... no, you won't find the modules as files - they should be compiled into the kernel (hence "part of it")
What you can try is to look into this thread, though that modules shouldn't be needed on Alfs or nAa, just on stock kernel.
However, if it works afterwards it might be worth trying.
B.Jay said:
Errr.... no, you won't find the modules as files - they should be compiled into the kernel (hence "part of it")
What you can try is to look into this thread, though that modules shouldn't be needed on Alfs or nAa, just on stock kernel.
However, if it works afterwards it might be worth trying.
Click to expand...
Click to collapse
i check n read the link above, n i think i just jump to
"You can use iptables executable now and check if works:" Part :
because like u say, this module should be part of the kernel, n if i flash the kernel right, the module should be there, dont u think.
so i try run the command via terminal :
- iptables -L
the result are :
Code:
$ export PATH=/data/local/bin:$PATH:.
$su
# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
#
- iptables -t nat -L
the result are :
Code:
$ export PATH=/data/local/bin:$PATH:.
$ su
# iptables -t nat -L
Chain PREROUTING (policy ACCEPT)
target prot opt source destination
Chain POSTROUTING (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
#
- cat /proc/net/nf_conntrack
The result are :
Code:
$ export PATH=/data/local/bin:$PATH:.
$su
# cat /proc/net/nf_conntrack
ipv4 2 tcp 6 431959 ESTABLISHED src=10.89.156.230 dst=216.155.195.253 sport=42914 dport=80 src=216.155.195.253 dst=10.89.156.230 sport=80 dport=42914 [ASSURED] use=1
ipv4 2 tcp 6 431972 ESTABLISHED src=10.89.156.230 dst=173.192.219.136 sport=44146 dport=443 src=173.192.219.136 dst=10.89.156.230 sport=443 dport=44146 [ASSURED] use=1
ipv4 2 tcp 6 431876 ESTABLISHED src=10.89.156.230 dst=61.145.124.115 sport=41129 dport=5222 src=61.145.124.115 dst=10.89.156.230 sport=5222 dport=41129 [ASSURED] use=1
ipv4 2 tcp 6 426586 ESTABLISHED src=192.168.0.5 dst=216.155.195.253 sport=52694 dport=80 src=216.155.195.253 dst=192.168.0.5 sport=80 dport=52694 [ASSURED] use=1
ipv4 2 tcp 6 426570 ESTABLISHED src=192.168.0.5 dst=61.145.121.120 sport=56854 dport=5222 src=61.145.121.120 dst=192.168.0.5 sport=5222 dport=56854 [ASSURED] use=1
ipv4 2 tcp 6 431982 ESTABLISHED src=10.89.156.230 dst=216.155.195.253 sport=56242 dport=80 src=216.155.195.253 dst=10.89.156.230 sport=80 dport=56242 [ASSURED] use=1
ipv4 2 tcp 6 426550 ESTABLISHED src=192.168.0.5 dst=173.194.72.188 sport=58555 dport=5228 src=173.194.72.188 dst=192.168.0.5 sport=5228 dport=58555 [ASSURED] use=1
ipv4 2 tcp 6 220 ESTABLISHED src=10.89.156.230 dst=209.85.175.188 sport=56186 dport=5228 src=209.85.175.188 dst=10.89.156.230 sport=5228 dport=56186 [ASSURED] use=1
#
Only this one is different from the result expected
-----------------------------------------------------------------
so what do you think ? the module is there? n why is the last command result is different?
Well, the last output you got HAS to be different because "nf_conntrack" reads, fully spelled: Net Filter Connection Tracker
This means the nf_conntrack in /proc/net shows entries of connections currently established on your phone (outgoing and incoming).
It actually looks like as if the modules are in the kernel (as they should) - otherwise you would have gotten a error message from iptables.
Now don't ask me why the "tethering-update" ZIP from Alfs won't work or why nAa's tethering doesn't like you...
B.Jay said:
Well, the last output you got HAS to be different because "nf_conntrack" reads, fully spelled: Net Filter Connection Tracker
This means the nf_conntrack in /proc/net shows entries of connections currently established on your phone (outgoing and incoming).
It actually looks like as if the modules are in the kernel (as they should) - otherwise you would have gotten a error message from iptables.
Now don't ask me why the "tethering-update" ZIP from Alfs won't work or why nAa's tethering doesn't like you...
Click to expand...
Click to collapse
oh.. okey
at least i know the module is there
just last question B.Jay, if it's ok with u,
1. is there a possibility something wrong with superuser?
thanks for ur help B.Jay
Don't think so, you were able to run "su" commands in the terminal.
Just check with some app that requires superuser rights ... like Titanium Backup or Root Explorer ... when they get su granted then Superuser should work.
B.Jay said:
Don't think so, you were able to run "su" commands in the terminal.
Just check with some app that requires superuser rights ... like Titanium Backup or Root Explorer ... when they get su granted then Superuser should work.
Click to expand...
Click to collapse
Ok thanks B.Jay
---------------------------------------------------------------------------
Still trying to figure out the problem
Well check the ROM info maybe the tethering is not working.... or its just a kernel bug....
HIT THANKS IF I HELPED!
ZeWhiteRabbit said:
Well check the ROM info maybe the tethering is not working.... or its just a kernel bug....
HIT THANKS IF I HELPED!
Click to expand...
Click to collapse
if u read the first post, i already write it, before it was working good
----------------------------------------------------------------------------
Anyway i figure it out, it is my carrier/operator
i tried to change sim card from different operator n
the tethering works really good
i dont know what they do, but i cannot change proxy, i cannot change DNS, and i cannot use wifi tethering/portable hotspot
but at least the problem solved thanks to B.Jay for helping me
On mini+nAa wifi tether works really good
Sent from my E15i using XDA App
DISCLAIMER: You should know by now that anything you do can and probably does void warranties, can and may brick your devices, etc etc yada yada.... This is my first ever attempt at a port, second ROM to ever build. The base for this is CM10.1 maintained by the official devs for the B&N Nook Tablet (acclaim), so complete props to everyone who has gone looney to get us here. This port isn't very usable and as such is no daily driver by any means.
I will try to explain the details of building as best as I can remember to anyone who wants to know. I had to comment out certain lines here and there and add my changes below them. Being new to this all, I have yet to set up a git for the sources. I just wanted to get this up as I haven't seen anyone else post this for Nook Tablet. From what I know, this should work for the 8g and 16g as this is based off the Official CM10.1 for us. Again, your risk, there are plenty of ways to unbrick this device and plenty of guides.
Discussion thread:
[ROM][DISCUSSION] Ubuntu Touch B&N Nook Tablet
For those of you just wanting to take it for a spin:
(name change as I am building using two different sets of repos, one with only a local branch based off the cm repos, and my own that I will push updates to)
Download Device Specific Build:
Build 5: ut-cm-20130610-acclaim.zip - 35.72 MB
Older Builds:
(The following builds screen displays stop working for newer Ubuntu fs builds)
Build 4: ubuntu_touch-20130529-acclaim.zip - 35.54 MB
Build 3: ubuntu_touch-20130524-acclaim.zip - 34.94 MB
Build 2: ubuntu_touch-20130513-acclaim.zip - 34.90 MB
Build 1: ubuntu_touch-20130511-acclaim.zip - 34.90 MB
Download Ubuntu FS File:
Saucy is the new Raring
http://cdimage.ubuntu.com/ubuntu-touch-preview/
Installation:
1) put both files on your sdcard by your method of choice
2) go into recovery
3) format data/factory reset <-- NOTE: If you want to save data, new builds should backup stuff, not sure what all though.
4) format system to ensure clean install
5) flash Custom build and flash Ubuntu fs file
6) reboot and pray it works.
After boot up notes:
- May have to push power button to get initial display.
-To get a chroot shell from your computer's terminal:
Code:
$ adb root
$ adb shell
$ ubuntu_chroot shell
- Keyboard does not currently work on Home screens. In Raring I would restart ubuntu-session. I do not see it in Saucy. 2013-06-15: playing around and starting the 'killprocs' service, keyboard worked afterwards.
Code:
[email protected]:/# service killprocs start
- Wifi seems to need a reboot to work correctly currently
- Added a script to change the display size.. If you do not like it or want to mess around with it, you can adjust the display through the chroot by editing the acclaim.conf file. After editing, reboot.
Code:
/etc/ubuntu-session.d/acclaim.conf
Build notes!
Build 5:
- Updated ubuntu sources, resulting display seems fixed for newer builds! (circa June 1st or maybe a little sooner)
- Honestly not sure atm if build 4 has it, but added a script to auto fix the display size (adds acclaim.conf for you), Saucy images seem to not require a reboot, Raring images do (or an ubuntu-session restart).
Build 4:
- Using wpa_supplicant 8 instead of 8_TI
Build 3:
- Wifi works with some terminal junk!
Build 2:
- Videos stopped working for some reason, need to debug.
- Apps no longer force close
- Wifi still down
Build 1:
- It boots
- Display works
- Sound Works
- Videos Work
- No wifi
- All apps force close after a couple of seconds
- No rotation
I'm new to all this git stuff, but figured I'd try it out:
https://github.com/dejello/android_device_bn_acclaim
https://github.com/dejello/android_kernel_bn_acclaim
I will be adding a wiki or readme on the device repo that shows dependencies and other edits needed to build your very own.
-dejello
Build 2! and some pics...
THIS POST IS NO LONGER REQUIRED, but kept for informational purposes
Updated - Build 3 now up!
Wifi seems to be working with some terminal junk. I followed this page as a reference after figuring out the wlan module wasn't being loaded: http://www.omappedia.com/wiki/Mac80211_based_open_source_architecture#Procedure_to_build_WLAN_and_test_on_Ubuntu_FS
NOTE: The module is apparently being unloaded after a while, possibly to do with going to sleep, not sure atm. If you have installed the terminal core app you can get back online without plugging back in..
I did the following commands and checked the browser and I was online!
Code:
[email protected]:/ # adb shell
[email protected]:/ # ubuntu_chroot shell
[email protected]:/# sudo mount -t proc proc /proc
[email protected]:/# lsmod
[I]Module Size Used by
wl12xx 189125 0
mac80211 384303 1 wl12xx
pvrsrvkm_sgx540_120 336017 34
cfg80211 181275 2 mac80211,wl12xx
compat 2718 0 [/I]
Notice: It did not show wl12xx_sdio - which has wlan0.
Code:
[email protected]:/# insmod /system/lib/modules/wl12xx_sdio.ko
[email protected]let:/# tail -3 /var/log/kern.log
[I]May 25 23:23:09 ubuntu-phablet kernel: [ 377.563903] wl12xx_set_power: 1
May 25 23:23:10 ubuntu-phablet kernel: [ 377.900939] wl12xx_set_power: 0
May 25 23:23:10 ubuntu-phablet kernel: [ 377.911682] wl12xx: loaded[/I]
[email protected]:/# ifconfig wlan0 up
[email protected]:/# tail -3 /var/log/kern.log
[I]May 25 23:25:04 ubuntu-phablet kernel: [ 492.360870] wl12xx_set_power: 1
May 25 23:25:05 ubuntu-phablet kernel: [ 492.839141] wl12xx: firmware booted (Rev 6.3.10.0.133)
May 25 23:25:05 ubuntu-phablet kernel: [ 492.864288] ADDRCONF(NETDEV_UP): wlan0: link is not ready[/I]
[email protected]:/# iwconfig wlan0 essid "tinyguest"
[email protected]:/# dhclient wlan0
[email protected]:/# ip addr
[I]......
7: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether 58:67:1a:53:b1:bd brd ff:ff:ff:ff:ff:ff
inet 192.168.2.13/24 brd 192.168.2.255 scope global wlan0
inet6 fe80::5a67:1aff:fe53:b1bd/64 scope link
valid_lft forever preferred_lft forever[/I]
Note: "tinyguest" is my test guest network with no security atm, insert the SSID of your network. I have not tested yet to see if this will work with security on.
Not sure how stable everything is, but hey, it's a dev preview so
UPDATE: I just had a realization.... After insmoding wl12xx_sdio.ko and bring the wlan0 up, I simply restarted the network manager service and now the gui shows up! I do need to check my wpa_supplicant file as I had been playing with it. <-- Fine unedited. I am also running a new minidroid build compiled using wpa_supplicant 8 vs wpa_supplicant 8_TI that I have yet to upload. I will need to see if this has any effect. I was having an issue compiling the TI version and was getting annoyed trying to figure it out New commands are as follows:
Code:
[email protected]:/ # adb shell
[email protected]:/ # ubuntu_chroot shell
[email protected]:/# insmod /system/lib/modules/wl12xx_sdio.ko
[STRIKE][email protected]:/# ifconfig wlan0 up[/STRIKE] <-- DIdn't even up it this past time, seems that restarting the network-manager service up's it.
[email protected]:/# service network-manager restart
Will be updating this post and adding a pic..
Doing great . Keep up. And why not tranfering it to nt dev thread?
Στάλθηκε από το Barnes & Noble Nook Tablet μου χρησιμοποιώντας Tapatalk 2
demetris_I said:
Doing great . Keep up. And why not tranfering it to nt dev thread?
Στάλθηκε από το Barnes & Noble Nook Tablet μου χρησιμοποιώντας Tapatalk 2
Click to expand...
Click to collapse
Thanks nothing in comparison to what you've been up to lately though. I probably should see about getting this thread moved over shouldn't I....
I'm really excited, I hope your project takes off in a big way
I admit to confusion, though - you say the base of this is the great work done on cm10.1 nightlies by the devs here, so is this actually ubuntu touch, or a skin over android? I'm not being critical, just looking to understand.
Thanks!
tmoulder said:
I'm really excited, I hope your project takes off in a big way
I admit to confusion, though - you say the base of this is the great work done on cm10.1 nightlies by the devs here, so is this actually ubuntu touch, or a skin over android? I'm not being critical, just looking to understand.
Thanks!
Click to expand...
Click to collapse
Sorry for the late reply, yes, currently Ubuntu Touch is running in a chroot on a mini build of android.
Other notes, today I started trying to figure out what exactly breaks the display on the newer ubuntu fs images.
dmesg shows ubuntu-session terminating with: "terminated with status 139". I still have an image from May 24th that works, and upon updating libplatform-api1-hybris or ubuntu-platform-implmentation-android (both of which will install the other) the display breaks with ubuntu-session terminating with: "terminated with status 127" or depending on what I've done ocassionally some other error.
More searching to follow....
UPDATE: see Build 5 notes, I hadn't fully updated my ubuntu sources apparently Display seems to work now!
PS - the git stuff isn't current atm, but the edits should still work. the wiki dealio needs work.
dejello said:
Sorry for the late reply, yes, currently Ubuntu Touch is running in a chroot on a mini build of android.
Other notes, today I started trying to figure out what exactly breaks the display on the newer ubuntu fs images.
dmesg shows ubuntu-session terminating with: "terminated with status 139". I still have an image from May 24th that works, and upon updating libplatform-api1-hybris or ubuntu-platform-implmentation-android (both of which will install the other) the display breaks with ubuntu-session terminating with: "terminated with status 127" or depending on what I've done ocassionally some other error.
More searching to follow....
UPDATE: see Build 5 notes, I hadn't fully updated my ubuntu sources apparently Display seems to work now!
PS - the git stuff isn't current atm, but the edits should still work. the wiki dealio needs work.
Click to expand...
Click to collapse
You say build 5 should fix the display not showing? I tried it and the "Current" Saucy phablet image and got nothing.
I'm about to try the Raring image and see if it works...
ajbiz11 said:
You say build 5 should fix the display not showing? I tried it and the "Current" Saucy phablet image and got nothing.
I'm about to try the Raring image and see if it works...
Click to expand...
Click to collapse
Nope...Saucy bootloops...I don't know how to get a logcat through fastboot, will look it up...
there was a period recently where they were breaking things alot with changes... I have a working version I can upload, but if they update hybris and/or the platform-api again it'll break until i update the build.
Sent from my SCH-I510 using xda app-developers app
Nook HD?
Great work! Any idea if you might get around to making a similar build for the Nook HD/HD+?
iCello said:
Great work! Any idea if you might get around to making a similar build for the Nook HD/HD+?
Click to expand...
Click to collapse
That is in my plans as I just got the HD+, not sure just yet as to when.. I need to pm verygreen or someone else and see what all I need to build cm10.1 first as I am missing something. Once I get a working build I will work on Ubuntu.
Sent from my SCH-I510 using xda app-developers app
dejello said:
That is in my plans as I just got the HD+, not sure just yet as to when.. I need to pm verygreen or someone else and see what all I need to build cm10.1 first as I am missing something. Once I get a working build I will work on Ubuntu.
Sent from my SCH-I510 using xda app-developers app
Click to expand...
Click to collapse
Alright, sounds good!
iCello said:
Alright, sounds good!
Click to expand...
Click to collapse
Ok, seems I just wasn't paying attention.. Replaced the boot image in the zip with the apparent non-sdcard version >.> CM10.1 booted so I will work on a build in a bit. For the moment though the tv is calling me
Are you planning non starting a new thread for ubuntu on the HD+?
Sent from my Nook HD+ using Tapatalk 2
Not sure atm.. If not I will update the title of this one
Sent from my SCH-I510 using xda app-developers app
So... if the Ubuntu will be available for HD+, changing a pair of things would make it for HD, is it correct?
Thank you!
dejello said:
That is in my plans as I just got the HD+, not sure just yet as to when.. I need to pm verygreen or someone else and see what all I need to build cm10.1 first as I am missing something. Once I get a working build I will work on Ubuntu.
Sent from my SCH-I510 using xda app-developers app
Click to expand...
Click to collapse
I would love this on my Nook HD (not HD+), I have ubuntu installed on all of my systems and love it over windows.
Sent from my Nook HD using XDA Premium HD app
Once I get working builds again (with the new stuff they've added for booting) I will build one for the HD for which I will need testers as I do not have an HD. Honestly did not really work on it today as I am really tired. Looks like I managed to get that one build in before they added this stuff.
dejello said:
Once I get working builds again (with the new stuff they've added for booting) I will build one for the HD for which I will need testers as I do not have an HD. Honestly did not really work on it today as I am really tired. Looks like I managed to get that one build in before they added this stuff.
Click to expand...
Click to collapse
I'll gladly test a build for Nook HD
Sent from my Nook HD using XDA Premium HD app