Status
Not open for further replies.
Search This thread

abstrucity

Member
Apr 2, 2010
33
0
theres an option in 'spareparts' to stop OTA notifications. But its greyed out.
Anyway to enable it?

Also, is there no one else with the same issue I have ?
 

Jack_R1

Senior Member
Aug 9, 2009
4,362
964
The issue of 2.2.1 OTA coming after changing the build.prop to avoid 2.2.2? Yes, I saw it just before I took the bullet and flashed GB build.
 

paolobacci

Senior Member
Jul 12, 2010
300
8
Niterói
Hi, I'm back after a while to say that I'm experiencing some lockscreen lockups.
I hit power button the screen shines but I can't touch. Simply it doesn't respond at all and doesn't matter if I try to hit power button forever, I have to wait it unlocks for about a minute and all gets back to normal...

any hints?
 

*rizzo

Senior Member
Apr 19, 2010
100
5
so i tried the gingerbread stuff and there were some things that i disliked, so i came back to the GREATEST ROM EEVVVARR!! lol. anyway quick question there is a black bar right under the status bar when enabled. how do i get rid of that?
 

Jack_R1

Senior Member
Aug 9, 2009
4,362
964
Hi, I'm back after a while to say that I'm experiencing some lockscreen lockups.
I hit power button the screen shines but I can't touch. Simply it doesn't respond at all and doesn't matter if I try to hit power button forever, I have to wait it unlocks for about a minute and all gets back to normal...

any hints?

Read my thread in General section, about WiFi/BT MMC driver errors.
Nothing you can do.
 

rts58

Member
Sep 18, 2010
48
2
Read my thread in General section, about WiFi/BT MMC driver errors.
Nothing you can do.

I never had this problem until yesterday. It has probably happened about 10 times since. Extremely irritating. I thought it was because I had recently enabled trackball wake and I was having some conflict with mylock or Tasker. I disabled trackball wake and removed mylock, with no improvement. I happens irrespective of whether BT is on or not. As soon as I shut off WiFi, it cleared up.
 

jemz0r

Senior Member
Apr 17, 2010
103
10
My company upgraded to Exchange Server 2010 with SP1.

Seems like FRG83 has problems with this and FRG83D has some kind of fix.

Any way I can use FRG83D with Enomther?

Currently running 2.14.4.
 

Jack_R1

Senior Member
Aug 9, 2009
4,362
964
Enomther's latest is based on FRG83D.

There is no way you can upgrade his build, without having his sources and tools.
 

katiepea

Senior Member
Apr 28, 2010
854
169
Los Angeles
this problem was originally fixed for me, but i tried an miui rom for a few days, then restored my backup, now this problem exists, bizarre, very very very annoying.
 

katiepea

Senior Member
Apr 28, 2010
854
169
Los Angeles
i have flash it multiple times as well as other people, this problem is persisting for some and not others, it's telling me to update to 2.2.1
 

waylo

Senior Member
May 9, 2010
1,670
489
yeah i flashed that and had succes with it, until i flash a different rom then restored my enom backup, now it won't go away.

Same thing happened to me after I did a backup restore. I thought it was very strange as well.

Heres my fix (after updating with the zip file first)
1. Erase the google update file from the /cache directory (dunno if this is necessary)
2. Allowed the update to occur (may want to backup first)
3. Update fails.
4. No more mention of a system update!
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 20
    Hi everyone :)

    Hello everyone!

    I know it's been a really really long time ... but it is what it is ...

    I've been away for personal reasons ... life was hitting me hard from every single aspect imaginable ... and the pressure was immense. It seemed the only thing I was succeeding at was android :/ ... which while satisfying ... is certainly not enough in the end.

    So in short ... I vowed to myself (on behalf of those closest to me) ... (and for other reasons ... such as feeling like quitting android altogether) ... that I'd take the entire month of Jan. 2011 off android wise. ... meaning no xda posts ... no tweets ... no development ... no nothin (android related) ... period.

    And well ... it paid huge dividends personally ... lots of positive things happened for me during this time. :)

    I am sorry I was unable to post as to my where-abouts/status during this time ... but a promise is a promise.

    To be fair/honest to everyone ... I'm still unsure as to whether I'll be returning soon or not ... there's a lot involved in this decision ... more than I care to explain.

    But do know ... I'd really like to ... albeit in some healthier balanced fashion.

    I have much love for android as a side development hobby ... and much love for the loyal and very respectful following I've acquired in this wonderful community!

    Unfortunately ... between the high development demands of my "real job" ... and the overwhelming personal demands associated with my dearest relationships ... android as a hobby has proven to be problematic when attempting to juggle it all.

    I'm still pondering if there is a healthy balance with this hobby and the rest of my life ... I still haven't become enlightened to any actual solution to that end.

    Just wanted to drop a quick to note to everyone ... it's been wayyyyyyyyy too long.

    As always, I really appreciate all the kind words, support and encouragement this community has given to me.

    Now that my android prohibition promise has expired ... I will keep everyone informed as I become more enlightened about the future of my involvement in this community ... as my hobby. :)

    Love you all!

    :cool:

    ~enom~
    4
    yeah i flashed that and had succes with it, until i flash a different rom then restored my enom backup, now it won't go away.

    Same thing happened to me after I did a backup restore. I thought it was very strange as well.

    Heres my fix (after updating with the zip file first)
    1. Erase the google update file from the /cache directory (dunno if this is necessary)
    2. Allowed the update to occur (may want to backup first)
    3. Update fails.
    4. No more mention of a system update!
    2
    I've updated 2.14.4's build.properties to stop the notification and created update zip that installs it.

    Apply this from recovery and it shall go away.

    Enom, where are you??? ;)
    2
    enom enom enom enom enom we need gingerbread!! :)

    Gingerbread AOSP is out guys!! I'm really looking forward to 2.15.x

    Sent from my Nexus One using XDA App

    :) ... I hear ya ... but to be clear and fair ... "TheOfficial" (mine) .. gingerbread update ... could be a little ways out ... however I am planing a revisional with some minor updates.

    v2.15.x *may* go on hold until the gingerbread build is ready ... and again this could be a little bit in the making :/

    Just don't want to get anyone's hopes up until it's a done deal! :)

    ~enom~
    2
    freaging love this rom

    Me too!

    Can someone comment on the usefulness of the swappiness feature under spare parts?

    It's useless if you had set your swap size on your SD during formatting to 0 right.

    I think I read Enom saying swap partition doesn't do anything much

    Sent from a mobile device using Tapatalk.. from the future

    My God ... I've accidentilied the Thanks button five times now LOL :)

    Freakin new xda feature! ... that's where I expect the "quote" button lol


    .........

    SWAP usefulness ... not really useful at all ... unless you're doing some really memory intensive stuff....

    I include the "option" to use SWAP b/c of my sporadic need to run a full blown linux distro with Xorg (memory-hog) ... on the n1 from time to time.

    So I use it ... but really sparingly ... as it will make your device suffer greatly speed-wise.

    So for the typical user ... 99.9% of 'em ... it's near useless ... but those who may need it ... know why and when to use it.

    :)

    ~enom~