Guest iYowo Posted April 3, 2013 Report Posted April 3, 2013 C3C0, sorry for the stupid question, but can you create a rom for Samsung Galaxy Note 2? Please!!! http://mobigees.info/samsung-galaxy-note2-n7100-custom-rom-list .... HyperNote 0.4 and Omega is nice :) http://forum.xda-developers.com/showthread.php?t=1926506&postcount=1
Guest robboardman Posted April 3, 2013 Report Posted April 3, 2013 Just done a complete wipe, and reinstall, not upgraded, and I'm now getting version compatiblity problems in google play, Ive tried to remove the google account but it wont let me, and advice would be great Thanks Robb
Guest Nofan Tasi Posted April 3, 2013 Report Posted April 3, 2013 (edited) New build available. This is the final release of this ROM from me. Changelog 03/04/2013 - the final release - Limit on number of background apps --- set to 8 by default in build.prop (sys.mem.max_hidden_apps) - Fixed rare graphical glitches in navbar/status bar - Final FM Radio audio routing fixes - Updated Effem app - Updated gapps (new Gmail, GooglePlayServices) --- make sure to uninstall Gmail and GooglePlayServices updates from data partition if present - Updated SuperSU --- make sure to uninstall SuperSU update from data partition if present - Upgrade without wiping data possible Thanks so much for this "the final release" !!!! Edited April 3, 2013 by Nofan Tasi
Guest WiiSky70 Posted April 3, 2013 Report Posted April 3, 2013 (edited) I've noticed issues with the software version compatibility on the Play Store which can't be reversed . Edited April 3, 2013 by WiiSky70
Guest C3C0 Posted April 3, 2013 Report Posted April 3, 2013 Switch to Stock UI to install/update apps. I will try to provide multi-dpi gapps as I did for 4.2 ROMs.
Guest WiiSky70 Posted April 3, 2013 Report Posted April 3, 2013 Switch to Stock UI to install/update apps. I will try to provide multi-dpi gapps as I did for 4.2 ROMs. Thanks . It's working now :D
Guest WiiSky70 Posted April 3, 2013 Report Posted April 3, 2013 (edited) Issues with software compatibility still present on Stock DPI Edited April 3, 2013 by WiiSky70
Guest C3C0 Posted April 3, 2013 Report Posted April 3, 2013 You have to clear data for GoogleFrameworkServices and Play store and reboot.
Guest Nofan Tasi Posted April 4, 2013 Report Posted April 4, 2013 Some hints for Link2SD users who regularly run short of internal /data space. Remember, Link2SD always needs some spare internal memory to do its operations, so, even if you seem to have, say 20Mb, free, it is possible that the update of a big app fails. 1) if, like I did, you bought several apps, then, apparently, they now go into /mnt/asec (or is it /mnt/secure/asec ?), anyway, they go somewhere where Link2SD cannot handle them. Trick is to back them up with Titanium, uninstall them, and restore them with Titanium who, kindly, puts them in /data/app for Link2SD to not choke on them. 2) if, like I have, your /system has spare room (say 20Mb or even more), then, consider installing (and perhaps paying for) systemcleanup which allows (among many other things) to odex system apps, and delete their /data dalvik cache (reboot needed). Agreed, odex apps are perhaps not perfect, but, odexing big dex ones sure helps to increase some necessary free internal space. As always, be careful Hope this helps others like sure it helps me.
Guest ziofunk Posted April 6, 2013 Report Posted April 6, 2013 Hi, Back to the not working Wifi/Bluetooth tethering on this rom, I did some test with the information provided in previous posts and with the latest rom (2.81) but tethering still does not work. So, with older ROMs it works properly (ICS 2.3.5 / 2.3.7) but with this one the computer connects (I tried with a Win7 machine and a OSX one) but in both cases it does not access the internet through the phone. I could not use the patch because it is not there to download anymore, yet, the IP segment conflict seems very a reasonable hint. So here are the results: After connecting to the 3G network with the phone (teethering not activated), using the android terminal I can see the following: ifconfig rmnet0 rmnet0: ip 10.204.209.189 mask 255.255.255.252 ping google.com 84 bytes from .... (173.194.45.64) traceroute google.com 1 * 10.62.61.201 (...) ... 9 * (173.194.45.64) Then I activate the tethering and On a OSX machine, I connect to the phone AP and the IP assigned to the OSX is 192.168.43.161 Now when I try to ping from there (OSX) i get a timeout (yet addresses are resolved) when I do a traceroute from OSX I get: traceroute to google.com (173.194.45.34), 64 hops max, 52 byte packets 1 192.168.43.1 (192.168.43.1) 6.397 ms 2.657 ms 2.146 ms 2 * * * 3 * * * 4 * * * 5 * * * 6 * * * 7 * * * ... and so on Now, connecting a windows 7 to the phone qnd... it's pretty much the same (DNS fine... but all trhe rest does not work) C:\windows\system32>ipconfig /all Wireless LAN adapter Internal WiFi: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Broadcom 802.11n Network Adapter Physical Address. . . . . . . . . : 74-2F-68-2D-38-B3 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IPv4 Address. . . . . . . . . . . : 192.168.43.29(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Saturday, April 06, 2013 20:48:34 Lease Expires . . . . . . . . . . : Saturday, April 06, 2013 21:48:33 Default Gateway . . . . . . . . . : 192.168.43.1 DHCP Server . . . . . . . . . . . : 192.168.43.1 DNS Servers . . . . . . . . . . . : 192.168.43.1 NetBIOS over Tcpip. . . . . . . . : Enabled C:\windows\system32>tracert google.com Tracing route to google.com [173.194.45.39] over a maximum of 30 hops: 1 5 ms 3 ms 3 ms 192.168.43.1 2 * * * Request timed out. [....] 9 * * * Request timed out. Now, I really don't know what to do with all this ;-) but if you have any idea or some test I could do... Addresses do not seem to conflict (right?) yet the connection does not work. It's obviouly something related with the combination of ROM and mobile network, because it works with the same SIM with a different ROM, and I can see not many people have this problem, so I guess it works with other operators...
Guest C3C0 Posted April 6, 2013 Report Posted April 6, 2013 (edited) Thanks for detailed info. It's hard for me to fix it if I can't reproduce it. But at least maybe it would be interesting to see some other info. Post outputs of the following commands. Do them in android terminal while tethering active. $ su # ifconfig rmnet0 # ifconfig wl0.1 # busybox route -n # iptables -L -v # iptables -t nat -L -v You could also try to execute the following command (again in android terminal) and test connection from PC afterwards # iptables -t nat -I POSTROUTING -s 192.168.43.0/24 -j MASQUERADE Edited April 6, 2013 by C3C0
Guest hizer07 Posted April 7, 2013 Report Posted April 7, 2013 Sure. I'll PM you my address where Note 2 could be sent to :P Just there CM 10.1 buggy, and you would have made it stable .... PLEASE!
Guest ziofunk Posted April 7, 2013 Report Posted April 7, 2013 (edited) Hi! About Tethering... First I have to say that the last command you suggested last did solve the problem! Now, I do not understand what it does, but it works ;-) If you have time to write a short explaination it would be greatly appeciated... otherwise, no problem, I'll study... PS. also USB teethering works after that. Here are the responses to the list of commands you gave. Thank you very much for your time and work! root@android:/ # su root@android:/ # ifconfig rmnet0 rmnet0: ip 10.201.126.181 mask 255.255.255.252 flags [up broadcast running multicast] 255|root@android:/ # ifconfig wl0.1 wl0.1: ip 192.168.43.1 mask 255.255.255.0 flags [up broadcast running multicast] root@android:/ # busybox route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.201.126.182 0.0.0.0 255.255.255.255 UH 0 0 0 rmnet0 10.201.126.180 0.0.0.0 255.255.255.252 U 0 0 0 rmnet0 192.168.43.0 0.0.0.0 255.255.255.0 U 0 0 0 wl0.1 0.0.0.0 10.201.126.182 0.0.0.0 UG 0 0 0 rmnet0 root@android:/ # iptables -L -v Chain INPUT (policy ACCEPT 96 packets, 42763 bytes) pkts bytes target prot opt in out source destination 40698 16M bw_INPUT all -- any any anywhere anywhere Chain FORWARD (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 3806 233K bw_FORWARD all -- any any anywhere anywhere 3806 233K natctrl_FORWARD all -- any any anywhere anywhere Chain OUTPUT (policy ACCEPT 101 packets, 11362 bytes) pkts bytes target prot opt in out source destination 51110 43M bw_OUTPUT all -- any any anywhere anywhere Chain bw_FORWARD (1 references) pkts bytes target prot opt in out source destination Chain bw_INPUT (1 references) pkts bytes target prot opt in out source destination 662 949K all -- !lo+ any anywhere anywhere ! quota globalAlert: 2097152 bytes 96 42763 costly_rmnet0 all -- rmnet0 any anywhere anywhere 216 6311 RETURN all -- lo any anywhere anywhere 36980 16M all -- any any anywhere anywhere owner socket exists Chain bw_OUTPUT (1 references) pkts bytes target prot opt in out source destination 633 30535 all -- any !lo+ anywhere anywhere ! quota globalAlert: 2097152 bytes 101 11362 costly_rmnet0 all -- any rmnet0 anywhere anywhere 216 6311 RETURN all -- any lo anywhere anywhere 50348 43M all -- any any anywhere anywhere owner socket exists Chain costly_rmnet0 (2 references) pkts bytes target prot opt in out source destination 0 0 REJECT all -- any any anywhere anywhere ! quota rmnet0: 9223372036854775807 bytes reject-with icmp-net-prohibited 197 54125 penalty_box all -- any any anywhere anywhere Chain costly_shared (0 references) pkts bytes target prot opt in out source destination 0 0 penalty_box all -- any any anywhere anywhere Chain natctrl_FORWARD (1 references) pkts bytes target prot opt in out source destination Chain penalty_box (2 references) pkts bytes target prot opt in out source destination root@android:/ # iptables -t nat -L -v Chain PREROUTING (policy ACCEPT 2627 packets, 377K bytes) pkts bytes target prot opt in out source destination 2627 377K idletimer_nat_PREROUTING all -- any any anywhere anywhere Chain OUTPUT (policy ACCEPT 2254 packets, 187K bytes) pkts bytes target prot opt in out source destination Chain POSTROUTING (policy ACCEPT 2832 packets, 223K bytes) pkts bytes target prot opt in out source destination 2832 223K idletimer_nat_POSTROUTING all -- any any anywhere anywhere 2832 223K natctrl_nat_POSTROUTING all -- any any anywhere anywhere Chain idletimer_nat_POSTROUTING (1 references) pkts bytes target prot opt in out source destination Chain idletimer_nat_PREROUTING (1 references) pkts bytes target prot opt in out source destination Chain natctrl_nat_POSTROUTING (1 references) pkts bytes target prot opt in out source destination Edited April 7, 2013 by ziofunk
Guest rivomanana Posted April 7, 2013 Report Posted April 7, 2013 Hi, Why my phone doesn't detect my WIFI after installing this Roms Thanks
Guest Nofan Tasi Posted April 7, 2013 Report Posted April 7, 2013 (edited) external card remounts on different device Hi all I bought a new 32Gb SD card which I partitioned 30Gb vfat (external SD) 1Gb ext2 (for Link2SD) 2Gb swap First two are mounted /dev/block/mmcblk0p1 /storage/sdcard0 /dev/block/mmcblk0p2 /data/sdext2 and everything works great! But invariably after some time (say 1 day, but sometimes 1 hour) apps start force closing and sometimes system says it is safe to remove SD card. When I look at the block devices I notice mmcblk0 is gone and now I have /dev/block/mmcblk1 /dev/block/mmcblk1p1 /dev/block/mmcblk1p2 /dev/block/mmcblk1p3 And /data/sdext2 gives IO errors. Does this ring a bell? Note that I also upgraded to latest 2.81 and I am not sure if that matters ... Thanks! update: Some google-ing reveals many complaints about SD cards being removed unexpectedly. Unfortunately I already gave away previous, slower, card. I may need to buy other card(s) perhaps and see what they give.... Edited April 8, 2013 by Nofan Tasi
Guest Nofan Tasi Posted April 8, 2013 Report Posted April 8, 2013 ... sorry to reply to my own post: I replaced 32Gb SD card with older slower 16Gb one and the unexpected SD unmount, so far, does not happen anymore. have a nice day
Guest FINTA96 Posted April 15, 2013 Report Posted April 15, 2013 Hi! About Tethering... First I have to say that the last command you suggested last did solve the problem! Now, I do not understand what it does, but it works ;-) If you have time to write a short explaination it would be greatly appeciated... otherwise, no problem, I'll study... PS. also USB teethering works after that. Here are the responses to the list of commands you gave. Thank you very much for your time and work! root@android:/ # su root@android:/ # ifconfig rmnet0 rmnet0: ip 10.201.126.181 mask 255.255.255.252 flags [up broadcast running multicast] 255|root@android:/ # ifconfig wl0.1 wl0.1: ip 192.168.43.1 mask 255.255.255.0 flags [up broadcast running multicast] root@android:/ # busybox route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.201.126.182 0.0.0.0 255.255.255.255 UH 0 0 0 rmnet0 10.201.126.180 0.0.0.0 255.255.255.252 U 0 0 0 rmnet0 192.168.43.0 0.0.0.0 255.255.255.0 U 0 0 0 wl0.1 0.0.0.0 10.201.126.182 0.0.0.0 UG 0 0 0 rmnet0 root@android:/ # iptables -L -v Chain INPUT (policy ACCEPT 96 packets, 42763 bytes) pkts bytes target prot opt in out source destination 40698 16M bw_INPUT all -- any any anywhere anywhere Chain FORWARD (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 3806 233K bw_FORWARD all -- any any anywhere anywhere 3806 233K natctrl_FORWARD all -- any any anywhere anywhere Chain OUTPUT (policy ACCEPT 101 packets, 11362 bytes) pkts bytes target prot opt in out source destination 51110 43M bw_OUTPUT all -- any any anywhere anywhere Chain bw_FORWARD (1 references) pkts bytes target prot opt in out source destination Chain bw_INPUT (1 references) pkts bytes target prot opt in out source destination 662 949K all -- !lo+ any anywhere anywhere ! quota globalAlert: 2097152 bytes 96 42763 costly_rmnet0 all -- rmnet0 any anywhere anywhere 216 6311 RETURN all -- lo any anywhere anywhere 36980 16M all -- any any anywhere anywhere owner socket exists Chain bw_OUTPUT (1 references) pkts bytes target prot opt in out source destination 633 30535 all -- any !lo+ anywhere anywhere ! quota globalAlert: 2097152 bytes 101 11362 costly_rmnet0 all -- any rmnet0 anywhere anywhere 216 6311 RETURN all -- any lo anywhere anywhere 50348 43M all -- any any anywhere anywhere owner socket exists Chain costly_rmnet0 (2 references) pkts bytes target prot opt in out source destination 0 0 REJECT all -- any any anywhere anywhere ! quota rmnet0: 9223372036854775807 bytes reject-with icmp-net-prohibited 197 54125 penalty_box all -- any any anywhere anywhere Chain costly_shared (0 references) pkts bytes target prot opt in out source destination 0 0 penalty_box all -- any any anywhere anywhere Chain natctrl_FORWARD (1 references) pkts bytes target prot opt in out source destination Chain penalty_box (2 references) pkts bytes target prot opt in out source destination root@android:/ # iptables -t nat -L -v Chain PREROUTING (policy ACCEPT 2627 packets, 377K bytes) pkts bytes target prot opt in out source destination 2627 377K idletimer_nat_PREROUTING all -- any any anywhere anywhere Chain OUTPUT (policy ACCEPT 2254 packets, 187K bytes) pkts bytes target prot opt in out source destination Chain POSTROUTING (policy ACCEPT 2832 packets, 223K bytes) pkts bytes target prot opt in out source destination 2832 223K idletimer_nat_POSTROUTING all -- any any anywhere anywhere 2832 223K natctrl_nat_POSTROUTING all -- any any anywhere anywhere Chain idletimer_nat_POSTROUTING (1 references) pkts bytes target prot opt in out source destination Chain idletimer_nat_PREROUTING (1 references) pkts bytes target prot opt in out source destination Chain natctrl_nat_POSTROUTING (1 references) pkts bytes target prot opt in out source destination Ok now tethering runs perfectly with these commands... But wifi tethering has problems. Other bug from the rom is when the phone is turn on 5 minutes, after, the camera don't save my photos. And could you expalin my how to sync with the latest cm and pa repos?
Guest sakiboj Posted April 18, 2013 Report Posted April 18, 2013 I am getting some error. symlink: some symlinks failed(status7), anyone knows why is that?
Guest plegdroid Posted April 18, 2013 Report Posted April 18, 2013 I am getting some error. symlink: some symlinks failed(status7), anyone knows why is that? your system partition is not big enough to fit the rom and gapps into. try a 200meg tpt. :)
Guest sakiboj Posted April 18, 2013 Report Posted April 18, 2013 (edited) I think I am already using 200meg tpt but if not I will have to do clean install of system? Using this tpt 200MB system, 2MB cache, 238MB data Edited April 18, 2013 by sakiboj
Guest omegavesko Posted April 18, 2013 Report Posted April 18, 2013 I think I am already using 200meg tpt but if not I will have to do clean install of system? Using this tpt 200MB system, 2MB cache, 238MB data Use FreeSpace or something to check first. Don't want to waste time for nothing. :P
Guest sakiboj Posted April 18, 2013 Report Posted April 18, 2013 Yes I checked, using 200mb system, 238mb data and 2mb cache and getting this error, I am updating system since i am using version from february I think
Guest plegdroid Posted April 18, 2013 Report Posted April 18, 2013 (edited) Yes I checked, using 200mb system, 238mb data and 2mb cache and getting this error, I am updating system since i am using version from february I think what version of cwm are You using? also, could try wiping system only before flashing the update :) Edited April 18, 2013 by plegdroid
Guest FINTA96 Posted April 18, 2013 Report Posted April 18, 2013 @C3CO Are you looking the native tethering usb?
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now