Jump to content

lcg

Members
  • Content count

    33
  • Joined

  • Last visited

Community Reputation

0 Neutral

About lcg

  • Rank
    Newbie
  • Birthday 10/30/1979

Contact Methods

  • Website URL
    http://
  • ICQ
    0

Profile Information

  • Your Current Device(s)
    Nexus One
  1. lcg

    Custom Rom 2.3

    I am sorry you see it that way. I am very happy with Froyo and I would not lose any sleep if my phone would remain on Froyo forever. As for car manufacturers not beta testing in the field: what about manufacturers regularly calling new cars back to the shop during recent years? Have you missed those? I am well aware that I exaggerated. I believe, however, that this is sometimes necessary to get people to think. Too much stuff on the Internet is simply blurted out too quickly, without thinking. And of course new features on newer cars usually involves changing hardware. And that costs money, I know that. It doesn't mean that developing new software for any electronics device is for free, even though deployment of that new software may be cheap. Anyway, I am well aware of the flaws of my analogy; it's an analogy, it's supposed to slightly differ from the original situation. Otherwise, it wouldn't be an analogy, it would be ... well, the same. Feel free to think that it doesn't fit the situation, I am not going to debate the validity of an analogy further. My main point still stands, though, and that is the fact that it's funny how people seem to expect phone manufacturers to provide them with feature updates throughout the lifecycle of their device. For free. (And I am not talking about security updates here. All manufacturers should provide those, although I must admit that that is also often not the case. But that is a very different discussion.) If it is really that important for people to receive the latest software for their device, I guess they could probably negotiate a service contract with the device manufacturer for regular updates during the time of the contract. But people might be surprised how expensive this is going to be. (And before anybody feels the need to point it out, I know that this is provocative; it is again just meant to provide some food for thought.) lcg.
  2. lcg

    Custom Rom 2.3

    Thanks for mentioning it ... What was I thinking? You obviously didn't get the analogy, so let me explain: Developing new features costs money. Anti-lock brakes, ESP, ... cost a lot of development money. And somehow, car companies have the audacity to not retroactively equip their already sold cars with these new features. Yet a lot of people expect a phone manufacturer to invest the money to produce new firmware versions with new features for their phone. Strange, huh? I am sorry, but people are really losing perspective in this thread. Being "disappointed" by Google, because the Nexus One didn't receive Gingerbread before any other phone? That's ridiculous. The Nexus One will receive a Gingerbread update (even though economically this isn't the most sensible thing to do), it just wasn't on top of the priority list. I hope this clarifies things. lcg P.S.: BTW, modern cars can indeed receive software updates. Not OTA but ... details ...
  3. lcg

    Custom Rom 2.3

    And if you buy a car, do you also expect the car company to backport the features from their latest model to the one you bought? And doing so before they even release the new model? For free? Google will make Gingerbread available for the Nexus One. It's just not the top-most priority on their list. Can anybody imagine what would happen if Google were focusing on their current device and then a competitor announces a new device with much better specs. Everybody who now desperately wants Gingerbread on the Nexus One would turn on Google and say things like "ah, they were lazy", "too comfortable with their current device", "no longer an innovative company", blah. Regards, lcg
  4. lcg

    Custom Rom 2.3

    If you agree with me, I don't see a problem. :D Are there still carriers that offer the Nexus One? Because I thought that most carriers had dropped the N1 due to its low availability (which was due to the shortage of the screen, but that isn't the point). At least in my corner of the world, the only way to still get a Nexus One is via Google as a developer phone. But even if it's still available, if somebody is desperately looking for a new phone with Gingerbread, they can buy the Nexus S. And if they want to buy the Nexus One, they know that they will have to wait a little while before they get Gingerbread for their phone. That's the trade-off. And it will receive Gingerbread eventually. But if you argue that the developer phone needs to run the latest OS version, I respectfully disagree. IMO, the point of real hardware for development is real world testing: Does the app feel comfortable to use? Do users find it intuitive? Does it work with data from the device sensors? These sorts of questions. If you want to make sure that your application runs on all your targeted OS versions and on different phones (i.e. screen sizes), that's what the emulator is for. A single developer phone can never offer that kind of flexibility. Now, the only valid point would be someone developing a Gingerbread-only app right now and wants to do real world tests on a phone. But I doubt that any developer at the moment would be willing to limit its potential customer base so severely. Your point being? If you focus all your resources on one device, it doesn't matter if one device takes a back seat or ten. "The only stuff". That almost sounds trivial. While it is true that most of the device-specific adaptations is in hardware drivers, that task is far from easy. I would assume that a small group of Google engineers could make Gingerbread run on the Nexus One over a long weekend. However, that is only the smaller part of the problem. After that, you need to test the thing, find bugs that crept in due to newer drivers, their interactions, changes in the kernel and what not. That is the hard part and the thing that takes the most time. And believe me, those users that are now vocal about delaying Gingerbread for the Nexus One would be equally vocal about receiving a buggy Gingerbread or a general delay of Gingerbread to simultaneously release for the Nexus One and Nexus S. Whatever Google's choice, there will always be people who like to complain about them not getting what they think they deserve. Actually, I am pretty sure that is exactly what they do. Not every single device, since the possible hardware combinations are astronomical, but a large number of machines which cover the most hardware scenarios. I am not sure if it was Microsoft, but I remember an article a while back about a software vendor with a sizeable amount of test computers, just to make sure that new updates don't blow up customers' computers. And if you remember some of the cases of anti-virus updates killing computers and the bad press from that, you can see why a company can't afford such a publicity debacle and will invest money into these tests. Don't get me wrong, I am also looking forward to running Gingerbread on my N1; I am just arguing why Google had good reasons to delay the release. Regards, lcg
  5. Honestly? Install an original ROM and completely wipe your device. I and a lot of the others don't have the same problem as you do, so I can only speculate what's causing it. But if you require absolute stability, you need to take a custom ROM out of the equation. Install the original stock ROM for your phone, it doesn't get any more stable and vanilla than that. If that still doesn't help, you need to look into the applications you installed. I once tested a wifi management app, which would enable and disable wifi depending on the cell IDs the phone sees. My phone started crashing and stopped when I removed that application. Regards, lcg
  6. lcg

    Custom Rom 2.3

    There is a huge difference between "hey, we compiled Gingerbread AOSP to run on the N1, it sort of works ... partially ... sometimes" and "here is the fully working and supported version for your phone which won't eat your data". I guess that the Google engineers were busy getting Gingerbread ready and adapting it for the Nexus S and simply didn't have the necessary resources to work on the release for the Nexus One at the same time. Well, they could probably have taken half of the team working on the Nexus S and have them work on the Nexus One ROM, postponing the Nexus S and overall Gingerbread release by maybe one or two months. But at least the Nexus One owners would have been happy. Makes perfect sense, right? (Hint: in a world where you want to take market share from your competitors, it doesn't.) Especially, as you pointed out, since the Nexus One isn't available any more, it's not like a new OS version will generate massive sales. On the contrary, now Nexus One owners might buy the Nexus S just to get their hands on the new Android version (at least the geekier types; which I usually am, but this time the difference between the N1 and the NS is simply too small for my taste). Regards, lcg
  7. While shootnospam has answered your questions quite thoroughly, I'd like to add one comment. Basically, the 'su' binary is called by a process that requires (or simply wants) superuser (or root) privileges. Most rooted Android phones tie this 'su' binary to a Superuser.apk, which maintains permissions about which process is actually allowed to gain root privileges. This way, a useful application such as Titanium Backup can obtain the necessary privileges to backup all applications and settings, which are usually strictly separated by Android's security concept. However, you can choose not to enable superuser privileges for another application, which requests it but for which you have doubts about its legitimate use of these privileges. That at least maintains some of the original integrity of your phone. I am not sure if you could have a 'su' binary that you can call without such a privilege check from a remote (ADB) shell but not from applications running on your phone. And if you couldn't, then any application could gain root privileges without you knowing it, doing whatever they want with your phone. HTH, lcg
  8. What you are asking is simply not possible. An official OTA update is meant to modify and/or replace files from an official ROM. You are using a custom ROM, with already modified files. How should an OTA update modify those without breaking everything? lcg
  9. I honestly have no idea what you did to your N1 and what mixture of guides you followed. All MCRs, including the Desire sense port you installed, are already rooted (somebody correct me if I'm wrong). Over this already rooted ROM, you installed nexus-addon-0.1-signed.zip (presumably from here). From what I can gather, this dates back to January 2010, to root the stock firmware back then. It lists a custom kernel being in there, which, in all likelyhood, is not compatible with your current radio. Doing that is pretty much like dropping a 1960s Porsche engine into a Prius and then wondering why the Prius is acting up. So, IMO, your phone is way beyond being fixed right now. I suggest you start over, flashing your phone completely back to stock. You can start from scratch using these steps (and these steps only): Grab the latest stock firmware FRG83 in image format (not update.zip) from here Download the Nexus One Desire port from here; use one of the prebakes just to make sure your problems aren't caused by something you put in or left out Put the prebake .zip on your SD card Shut down your phone, from here on you either use the recovery or fastboot for the following; avoid booting your phone inbetween (it shouldn't be harmful, but it's not necessary either, so let's avoid it) Flash the latest recovery via fastboot, either AmonRA or Clockwork are fine From the recovery, do a factory reset of your phone Use fastboot to flash all parts of the firmware, except for recovery; check the page with the stock ROMs for instructions how to use fastboot Use the recovery to install the prebaked Desire port from your SD card Start using your phone and check if everything's working (<- This is the first time after the explicit shutdown before that you are actually fully booting into Android) If any of these points are unclear, you should read up on that or ask back. Do not simply install anything because it was mentioned in some guide, maybe for a completely different phone or ROM. Also, I suggest you read the guide for your specific MCR you want to install and follow it to the letter. To quote Paul "READ THIS WHOLE POST BEFORE YOU START! No, really, it contains everything you need to know." HTH, lcg
  10. lcg

    [Q] Trackball Wake

    It should be no problem if you only change this one feature. Just to be on the safe side, you can make a nandroid backup from the recovery before flashing. This lets you reset your phone to the exact state when you made the backup, just in case anything goes funky with the new ROM. And if that happens, just go back and you can then think about alternative strategies such as a wipe and Titanium restore. HTH, lcg
  11. Hello, First of all, I don't really use the Sense port (if I wanted Sense, I would have bought a Desire ;) ). So take my comment with a grain of salt. Hmmm, it works fine on my Nexus One with the rooted stock ROM. But somebody else who knows the Desire port would have to comment on this one. Hmmm, to me, this sounds like a problem with the radio image. Both the GSM/radio part as well as the camera use the radio image to access the hardware, AFAIK. Did you update your phone's radio when you flashed the Desire port? (I am not sure if this is necessary for the Desire port, so it's probably better to ask another user of that particular ROM.) Sorry I couldn't be of more help. lcg
  12. lcg

    System Upgrade2.29.405.2

    So, you won't be installing an official update on a custom ROM (which would fail anyway), because you are unhappy with the custom ROM? That is quite a logic. And for the other claim of crying for help several times, you are currently listed with 3 posts, this includes the one I am replying to. In the other two, you are talking about a GSM problem, not about any of the things you mentioned here. These things, BTW, all work fine for me and probably most other users here, otherwise we'd see more questions about them, I guess. Maybe you can start a new topic, list your problems, list what you have already tried to fix them, and then somebody can try to help you out. Other than that, there are always the stock ROMs or other custom ROMs if the ones here don't fit your needs. HTH, lcg
  13. Simple, because the radio chip they used was probably cheap and had that feature. Developing an application for that would have cost more development money and was probably judged not worth the effort. So they simply let the FM tuner lie there, unused. lcg
  14. You mean the links where the text reads "Uploading now"??? I wonder why that is ...
  15. Both Clockwork and AmonRA recovery work fine to install MCRs. Or any other update.zip for that matter. There may be issues if you have a Nexus One with SLCD screen but if your recovery works it should be able to install any ROM from a zip file. HTH, lcg
×

Important Information

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