Jump to content

jsl.com

Members
  • Content Count

    14
  • Joined

  • Last visited

Community Reputation

0 Neutral

About jsl.com

  • Rank
    Newbie

Profile Information

  • Your Current Device(s)
    NexusOne
  1. Sounds great. I'm glad that the MCR is working for you. If you ever run out of RAM and decide to use A2SD, you may encounter the boot looping issues that others (including me) have had. If you ever need to use the VPN features of your phone, rest assured that they will not work with the ROM that you are using. None of the 4 VPN choices will work under any conditions. My research led me to believe that this is due to an incompatibility between the kernel used in the MCR and the corresponding ppp-dialer dalvik code.
  2. I ran MCR for over a year and it was great but not so much anymore. The gingerbread MCR VPN is broken and that is fatal as far as I'm concerned. If the VPN worked, I might have been willing to live with the weekly crash and reboot loops. Now I don't have either problem. I gave up on the gingerbread MCR and installed the CM7 RC a few weeks ago. CM7 stable was released today. I updated to the stable release today and it works well. In fact I cannot tell the difference between CM 7.0.0 stable and RC4. They are both very stable. Everything works great and there are lots of new features to explore. Jeff
  3. Both USB tethering and WiFi tethering have been working fine for me with R26. I wish that I could say the same about PPTP VPN....
  4. I've been running R26 on my Nexus One for several weeks and it has been mostly stable. There was one time last week when I opened the camera app and the phone froze. I had to pull the battery to recover. Late last evening I was browsing the web and the phone rebooted. I set it down for a few minutes and when I came back it was in a loop, continuously rebooting. Pulling the battery stopped the loop and the phone is back to "normal" now. This MCR is nice but it is not as stable as R24 was. Jeff
  5. At first I was willing to hunt for the binaries and go through the key generation process but I wanted to do it from a shell with a real keyboard so I tried running telnetd. Oddly enough it would accept a connection and then immediately disconnect before even prompting for a user name or giving me a shell prompt. Telnetd has worked for me in the past but maybe there has been some security added... During my searches I came across QuickSSHd ($1.50 US in the Marketplace). It works great and even has a GUI that lets you change your password. As a plus, it accepts inbound SSH connections on port 22 where they belong. Cheers! Jeff
  6. Am I the only one who wants to shell into his phone? The r26 version has such a long string in the kernel version (About Phone) that the SSH password isn't visible. Now I couldn't ssh into my phone even if the ssh daemon were running (which it isn't). Could somebody please explain how to use the dropbear ssh feature? I included it in the ROM and I (used to) see the ssh password displayed after the kernel version. How do I get the phone to accept ssh connections? Thanks in advance, Jeff
  7. OK everything is looking pretty good on my Gingerbread Nexus One now. I have one remaining issue with the dropbear ssh server. It appears to be active because the password shows in "About Phone" but all attempts to connect are refused. Is the port still 2222? nmap -v -p1-65535 <my phone> Starting Nmap 5.00 ( http://nmap.org ) at 2011-03-02 15:55 PST NSE: Loaded 0 scripts for scanning. Initiating Ping Scan at 15:55 Scanning 192.168.2.100 [2 ports] Completed Ping Scan at 15:55, 0.34s elapsed (1 total hosts) Initiating Parallel DNS resolution of 1 host. at 15:55 Completed Parallel DNS resolution of 1 host. at 15:55, 0.02s elapsed Initiating Connect Scan at 15:55 Scanning <my phone> (192.168.2.100) [65535 ports] Increasing send delay for 192.168.2.100 from 0 to 5 due to max_successful_tryno increase to 4 Connect Scan Timing: About 13.60% done; ETC: 15:59 (0:03:17 remaining) Connect Scan Timing: About 21.15% done; ETC: 16:00 (0:03:47 remaining) Connect Scan Timing: About 30.25% done; ETC: 16:00 (0:03:30 remaining) Connect Scan Timing: About 39.35% done; ETC: 16:00 (0:03:07 remaining) Connect Scan Timing: About 48.45% done; ETC: 16:00 (0:02:41 remaining) Connect Scan Timing: About 67.24% done; ETC: 16:03 (0:02:33 remaining) Connect Scan Timing: About 76.03% done; ETC: 16:03 (0:01:48 remaining) Connect Scan Timing: About 85.13% done; ETC: 16:03 (0:01:05 remaining) Completed Connect Scan at 16:02, 422.29s elapsed (65535 total ports) Host <my phone> (192.168.2.100) is up (0.0012s latency). All 65535 scanned ports on <my phone> (192.168.2.100) are closed Read data files from: /usr/share/nmap Nmap done: 1 IP address (1 host up) scanned in 422.81 seconds
  8. I've baked, downloaded, and flashed a few times today. In all cases the Titanium Backup application is not appearing for me. I suppose that I could just download it from the Marketplace but I *DID* check the box to include it in the ROM. Any ideas?
  9. Thanks for the update Paul! I've got a question about your disclaimer (and no I'm not a lawyer). Should I interpret your message to mean that this will definitely be the last MCR for the Nexus One? Another interpretation could be that you are not planning any future N1 MCR updates but that you MAY produce some. A third interpretation is that you plan to do N1 MCR updates sparsely but you don't want to commit yourself for life. Which one of my interpretations best represents your position? Best regards, Jeff
  10. Thanks for the report Alan. Which wireless problem are you having? I've had no troubles on my Nexus One using 802.11n both as a client and as a WAP.
  11. That's great advice but it assumes that the latest version of the custom ROM has a kernel that is current. In the case of the Nexus One and the Modaco Custom ROM, there hasn't been an update since November 2010 and there has been an OTA update available for weeks. There is a hack posted on another thread that will make the OTA update stop bugging you if you want to keep your MCR. Otherwise you can restore a stock ROM and let it OTA update to the current release (and lose all of the benefits of having a custom ROM). Alternatively you can get a different custom ROM from the XDA developers site. They seem to update their ROMs a *LOT* more often than Paul does. I hope that this information has been helpful.
  12. OK so nobody has answered my question yet. I'm on my third version of the MCR now and this new one looks like a major upgrade. It's still using Froyo (2.2) though. I'm a little nervous about installing it given all of the posts describing various problems. The screen-shots look remarkably different from the N1 (Passion). I haven't used a Desire phone. What's new and what's missing? If I'm going to invest several hours in an upgrade, I'd like to have some idea in advance of whether or not it's worth it.
  13. There are so many features available in this MCR that I don't know which ones to choose. I've never heard of many of the applications included. Is there a source of documentation that describes each application in detail so I can make an informed choice about what I want included in my MCR? Thanks.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.