yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] Username+:
Hi everyone! Help me with my little problem please. I flashed FRG83 Stockbar 1.2, then blackbar and then a2sd add-on and changed Launcher2.apk. Finally installed TrackballAlert(free version), but it doesn't work, when I started the app it wrote, that only MCR and Cyanogen rom are supported and so on.

Is there anyway to make it work with this FRG83 rom?
[Nexus One Android Development] Talderon:
Not sure what's up. I am using 1.2 with BlackBar and A2SD addon from Geo and Trackball Alert Pro. I know that Geo has worked on the framework so that it works with Lilhermits app, so may have to see if Geo can chime in here. :D
[Nexus One Android Development] applejosh:
I've successfully used TrackBall Alert Pro with the Stockbar, battery percentage, blackbar, and a2sd add-ons in the past. I haven't tried the free version of TBA. Which version of TBA is showing up?
[Nexus One Android Development] Username+:
it's 1.1.4.

trackballalert worked well with FRG33 and FRG83 from modaco's forums. But after I installed this rom got this problem.

If you guys/girls :) say that Pro version works well with this Geo FRG83 rom, then, probably, I should use it.

P.S. Actually, I almost bought the pro version, but then decided to check if trackball alert will work with this rom using the free version. =)
[Nexus One Android Development] applejosh:
Well, I would first try uninstalling, reboot, reinstall, reboot if you're unsure. Since I never used the free version, I'm not much help. Maybe someone else with experience using the free version will chime in.
[Nexus One Android Development] Wonderboy1:
Hey Geo, I really like your theme, thanks alot!

The only the it lacks is a 720p camera, what are the odds its gonna happen?
[Nexus One Android Development] Talderon:
This requires a custom kernel, which, in turn would make this a Non-Stock ROM. I would suggest trying a custom ROM if you really need 720p. Although, I have not read all of the threads to see if he is even working on a mod for it... :)
[Nexus One Android Development] Username+:
I tried reinstalling, but it didn't really helped me. I bought the pro version anyway and when I got an e-mail it flashed with my custom color, but when I got missed call it flashed with white. So now I rebooted my N1 and I'll see if it helped.
[Nexus One Android Development] Vlad83:
Hey, I am currently on FRF85B, just rooted without unlocking the boot loader. Can I flash this without wiping or do I have to wipe? I am trying to get rid of them damn FRF91 update prompt that keeps popping up...
[Nexus One Android Development] ninj0x:
I didn't enable it. Might have been on though.
[Nexus One Android Development] Mo_Nexus:
i installed frf91 from frf85b (rooted) without wiping and it is working just fine :)
[Nexus One Android Development] Vlad83:
Thanks, going to flash now.
[Nexus One Android Development] cymru:
Flashed and working great. This will keep me happy until Cyanogen ROM.

Cheers
[Nexus One Android Development] Manacit:
I was on the FRF85B build of this, rooted, without unlocking my bootloader, just like you. I also was really annoyed at the damn update prompt. I just installed this right over the FRF85B build without wiping, then installed a custom kernel, and now all is well! I would highly recommend using this build if you want a sleek, rooted, FRF91 build without that (imo) annoying green text and other bull**** that comes with most custom roms. It's only had stuff removed, nothing huge added, and after I installed a custom kernel I was benching in the mid 1500s with Quadrant :).
[Nexus One Android Development] pceslayer:
make sure you have the froyo radio
[Nexus One Android Development] ninj0x:
Updated to RA 1.7.0.1. Wiped everything. Still get boot loop. Sad face.
[Nexus One Android Development] pceslayer:
try installing this

xdaforums.com/showpost.php?p=6784858&postcount=1006
[Nexus One Android Development] ninj0x:
I've had the Froyo radio for awhile now. Since FRF50 came out. Is this different?
[Nexus One Android Development] efishta:
Hi all, I was on a stock, rooted frf91 rom and had a bunch of apps installed with about 40 mb of internal storage free. I installed this over it and everything seems fine except that now I'm showing 17 mb of free internal storage.

Are the additions to this rom 15-20 mb over the stock frf91 rom? How else can I explain this?

EDIT:

A google search (as usual) answered my question. Deodexing decompresses files so yes, it does indeed take up more space. I'll have to live with a few less apps till more devs allow SD installations. Since I took the leap to this point, I'm going to go ahead and try Pershoot's 6.35 kernel to go along with this. This takes me back to my Windows Mobile days, where many roms were built with bleeding edge leaked OS versions.

I'd go with Cyanogen's roms but I'm not a fan of reinstalling/restoring all my stuff again. Then again, i'm considering it due to Titanium Backup's awesome abilities.
[Nexus One Android Development] robiatti:
I am stuck in a boot loop as well and do have the Froyo radio
[Nexus One Android Development] leonnib4:
Did you wiped dalvik-cache?
[Nexus One Android Development] robiatti:
Yes, I did a full wipe..

I will rewipe and see what happens.
[Nexus One Android Development] blisk:
Me as well. I did a fatory reset after I was stuck on the boot loop. Then the boot loop seemed as though it started crashing about 4 seconds in and restarting. I didn't do any other cache clearing etc. in the recover options. Doing a nandroid restore atm.

edit: And I'm back to my old install. God I love this titanium backup and nandroid... now I know what I was missing out on not being root.
[Nexus One Android Development] leonnib4:
What shows you the logcat?
[Nexus One Android Development] robiatti:
ok just re-wiped everything and I am still looping.
[Nexus One Android Development] leonnib4:
What shows the logcat?
[Nexus One Android Development] J.L.C.:
Which Kernel are you using?

:)
[Nexus One Android Development] blisk:
I'm new at this stuff. What would be the best way to get a logcat when I try this again? Since I can simply just nandroid back to my old stuff no problem I'm mor then willing to keep trynig and figure out what's going wrong for others.
[Nexus One Android Development] lyingit:
I just installed this rom today (followed by battery %, blackbar, and a2sd) - I tried using the theme linked in the OP, but I think it's not set up for FRG83 yet.

but I got the free version of trackballalert, and it's running perfectly fine on mine.
[Nexus One Android Development] Papa_I:
Geo,

Have you put any thought into putting your Rom in to "Rom Manager"? Would be nice if this supported OTA updates through "Rom Manager". Thanks for your great Rom.
[Nexus One Android Development] lyingit:
I was curious, anyone running an overclocked kernel with this, and if so, which one are you using?
[Nexus One Android Development] Geo411m:
Sorry I haven't been active here lately, I've been going through a lot of personal problems. I recently got a severe pay cut at work (about $15k). Then my job made a mistake on my taxes, so for the past 4 months they put my taxes in backwards so the IRS was paying me $200 bi-weekly which I never noticed due to the pay cut. That means I have to pay the IRS 4 months of taxes x2 to make up for what they payed me. Finally, I got my oil changed last month and it turns out they forgot to put the oil cap on so my engine seized earlier today. I'm pretty much feeling like Job (bible reference) right now. At least I still got my family and health.
[Nexus One Android Development] crimsondr:
Do you know why the little LED on my N1 doesn't turn on when charging?
[Nexus One Android Development] galaxys:
Geo...family & health are very important! Hang in there!!
[Nexus One Android Development] blitz911:
Keep your head up Geo, hope you and your family get thru these tough times..
[Nexus One Android Development] blitz911:
Using this kernel: 2.6.35_SVS-925mV_CFS_AXI_No720p_1113MHz_082710.zip
[Nexus One Android Development] fzr-r4:
Geo, obviously no need to worry about all of us who appreciate what you share here.

Take care of yourself and your family. For what small comfort it may offer, many of us have reliable, smooth-running phones we love with your help.

Hang in there!
[Nexus One Android Development] applejosh:
This was a bug I've seen reported on more than one FRG83 based ROMs. I thought Geo posted that he fixed it in the latest revision, but maybe I'm thinking of a different ROM/thread. Only been playing with this one for a couple of days.
[Nexus One Android Development] applejosh:
Here's the post about the fixes in the 1.2 update.

(Sorry about the double post. I'm mobile right now.)
[Nexus One Android Development] Txtraveler:
I'll ask forgiveness in advance - I know this is a seriously noob question and I'll accept directions to the wiki I couldn't find as a justifiable chastening, but...

What is the significance of the different titles (FRF91/FRG83/FRG33) in these ROMs?

I've installed Geo's FRG33 Blackbar and I REALLY like it - will probably go for the A2SD version soon - but I wonder how it compares to the others - ie, is the FRF91 a more recent and better release, etc.
[Nexus One Android Development] galaxys:
These are Android versions with the oldest is FRF91 then FRG33 then the newest is FRG83.
[Nexus One Android Development] efrant:
Guys, let's show Geo a little love in these tough times. Who's in? He shares his ROM with us, he's always very helpful and never sarcastic or rude. Thanks dude.

Even though I don't use this ROM, cheers: Confirmation number 4P0996828U2847422
[Nexus One Android Development] Txtraveler:
I'm in! I was planning to do this anyway because of the sense of relief I got when I installed FRG33. I was literally doing the Snoopy happy-dance. For me it only has two flaws, and I know they'll be fixed someday. Getting rid of the update notification (I refuse to install 2.2.1), and the 720p video camera. This thing works great now though, and I'll be happy for quite a while!

Confirmation number: 8J867438UF563564T, more than earned!
[Nexus One Android Development] Nikos_s3:
hang in there geo..wish you all the best from now on..;)

take care..;)
[Nexus One Android Development] ereuveni:
Hope it helps, at least morally...

Confirmation number:	7XH87054V1031381T
[Nexus One Android Development] lyingit:
thanks, I'll give that one a go.
[Nexus One Android Development] applejosh:
If you look around, you can find and copy the fingerprint line from a build.prop in an FRG83 ROM to suppress the update notification. I know enomther's ROM is essentially still FRF91, but the build.prop in the latest has a fingerprint line to fool Google's servers into thinking you are on the latest without actually having to be on the latest. Just an adb pull, a quick edit, and an adb push should work. (nandroid backup of course before doing all this just in case it proves to be problematic. At your own risk, etc.)
[Nexus One Android Development] OutlawPro:
Basically, the version is broken down like this:

FRF91 =

FR (Froyo)

F (Release A-Z)

91 (Revision)

So you would get FRF91 being the oldest, FRG33, then FRG83 the newest.
[Nexus One Android Development] OutlawPro:
Just curious for my own reasons, why do you not wish to upgrade to FRG83? Is there something specific it breaks on your phone?
[Nexus One Android Development] lyingit:
Ok, so the kernel is working great.

only two other things I'd like to put in this rom (just for myself) but I'm having a hell of a time doing it.

cytown's phone mod (must have in my opinion, the blacklist feature is number 1 in my book) - I've tried using the commands he gives in his post, but apparently I'm a moron and don't understand them correctly.

the browser from Cyanogen (not a must have, but I like the ability to switch user agents, and the incognito mode is nice).

anyone want to at least point me in the right direction here?
[Nexus One Android Development] Txtraveler:
I have no real reason not to upgrade to FRG83 beyond the facts that a) I'm enough of a noob that I didn't know that 2.2.1 and FRG83 were one and the same (see my earlier question), and b) I'm so happy with how FRG33 is working for me right now.

First, I'm just being a bit peevish. I bought my phone in Feb second-hand, rooted and running CM5.0.8, or something like that. When Froyo came out I called Google about the upgrade and they said that because my phone was rooted I would never receive any of the upgrades, and there was nothing they could do about that. I figured okay, and set about learning enough to take care of it myself. Now that I have, I'm suddenly getting a notice about a "security upgrade" from Google that I have heard will disable "root" among other things and I'm not having it. If they won't help me when I call and ask, then they need to leave me and my device alone when I don't call. I'll muddle through.

Second, I got the impression that it's not a reversible step.

Third though is I'm wondering just what 2.2.1 is supposed to do for me, really? This might be a better place to get an answer to that. All I've heard is that I will lose root, and I'm too much of a noob to truly understand what that means beyond taking away something that I might want. Will I lose the ability to flash ROMs, or to upgrade my radio or recovery image? Will it interfere with the way my phone is running now, which I REALLY like?

If anyone is willing to dumb the answers to these questions down to the point where someone like myself can understand them, I'd certainly be interested in hearing them...
[Nexus One Android Development] fzr-r4:
Txtraveler, if you use Geo's (or most custom) FRG83 Rom(s), you will preserve root abilities.

As for what else 2.2.1 offers, some of the system apps are updated, though more and more are available through the market as system independent (well, aside from requiring FroYo) updates.

Have fun!
[Nexus One Android Development] tech338:
Check this post out. http://xdaforums.com/showpost.php?p=7441446&postcount=854. Cytown told me it is not possible because Phone.apk is built for AOSP and Geo's based on Google's build.
[Nexus One Android Development] lyingit:
well that explains that then.

dammit, really like this one too - as it's all stock (basically).

off to hunt for an AOSP build then.
[Nexus One Android Development] efrant:
I'll take a stab it.

First, what does FRG83 give you: FRG83 is supposed to fix some issues with WiFi, it updates some apps, and it likely makes some other minor changes, which likely improves stability. It also patches the WiFi exploit, so rooting methods like the "1-click" Androot will no longer work.

Second, what is root: having root access allows you full access to your device's file system, which allows you to, among other things, run applications/widgets that give you features not available via a stock or unrooted ROM (e.g., a reboot widget that reboots your device when you press it). Basically, it is like having administrator rights on a Windows system -- you can do whatever you want.

Third, you will lose your root access if you update via the file pushed to your device by Google, but who cares... just re-root (FRG33 and FRG83 are both rootable via rageagainstthecage exploit) and all is well.

As long as you have root, you can flash ROMs, radios, recoveries, etc. If you do not have root, then the only way you can flash a custom recovery or ROM is by unlocking your bootloader (it voids your warranty (accoding to Google, but users have indicated the HTC did replace N1's with unlocked bootloaders), but i doubt you would need to send in your device anyway (they'll prob send you a refurb, and I wouldn't want that).

Is an update to FRG83 reversable: well, it depends on what you mean by reversible. You can always flash a different ROM overtop, and restore your apps/setting via Titanium...
[Nexus One Android Development] lyingit:
Wait, does Geo's AOSP build here:

http://xdaforums.com/showpost.php?p=7655349&postcount=443

work with A2SD?

if so, I'll just move to it, but there is nothing (that I see) in that post that says whether it works with A2SD or not
[Nexus One Android Development] tech338:
1 - There is a big difference between Root and having a custom ROM. You can have root, but the stock ROM. You cannot have a custom rom without root. Most custom ROMs are *not* based on the OEM/stock build of Android which ships with the phone. Some include rebuild framework (Cyanogen / MUIU) and some are based on AOSP (Android Open Source Project) code (Leo's among others) and some are based on Sense (Evil's). A lot of these ROMs have the system update code removed or modified. This one is so close to the stock build that Google's build that you still get the notification.

Updates generally add functionality and increase security. If you have a custom ROM, you need to wait until the dev of that rom updates it. If you are stock, Google updates it. I know the new update causes you to loose root (bad), but it does close a security hole -- if the hole was left open and some exploit came along, we would all be *****ing about how Google didn't close it.

2 - You can always reverse if you do a Nandroid backup (in recovery) first. It will save a snapshot of your system that you can go back to anytime. Also, I believe you can root FRG83 using the instructions here : http://xdaforums.com/showthread.php?t=792016.

3 - The 2.2.1 update closes a security hole (one-click root method) and adds extra security if you connect to an exchange account with tight security (remote device admin). No real reason to update except to stop getting the update message (also some people claim that there is extra battery drain associated with continually downloading the update file). Why not Nandroid and flash Geo's FRG83. You can flash FRG83 right over your existing FRG33 (I did and Geo said it was fine). If you don't like it after a day or so, Nandroid back to FRG33.

EDIT: looks like efrant beat me to it.
[Nexus One Android Development] tech338:
Why don't you try it and let us know. I asked before Geo's AOSP ROM was released. Should work...
[Nexus One Android Development] efrant:
This part isn't true though...
[Nexus One Android Development] lyingit:
just tried, getting bootloops, don't feel like wiping everything today though, so I'll just restore my nand and come up with a new plan.
[Nexus One Android Development] tech338:
My apologies.

I though you had to install custom recovery to get a non-stock ROM. And to get the custom recovery, you needed root access?

:confused:
[Nexus One Android Development] Talderon:
How is it not true? You can't install a custom recovery without root. Unless I missed something...
[Nexus One Android Development] efrant:
That is only true if you have a locked bootloader. If you unlock your bootloader, you don't need root access or a custom recovery to install a non-stock ROM, recovery, or anything else for that matter. You can pretty much flash whatever you want.
[Nexus One Android Development] tech338:
I stand corrected.

Are there any custom ROMs without root?
[Nexus One Android Development] applejosh:
I think there is at least one over at modaco. Paul has a non-root repack of FRG83.
[Nexus One Android Development] sirgoob:
I've had some issues with the video camera FC and having to reboot the phone to get it working again

Sent from my Nexus One
[Nexus One Android Development] efrant:
I think Geo had one as well in this thread.
[Nexus One Android Development] Txtraveler:
Thank-you to fzr-r4, efrant and tech338 for your replies. You've done a lot to drag me out of the rather clueless place I was in. After reading your replies, I will probably try the FRG83 and add blackbar and A2SD from the links at the start of this thread. With a good nandroid backup, apparently I won't do anything irreversible, and hopefully it will get rid of the notification.

WRT the last few posts, I gather that it isn't root that voids the warrantee, it unlocking the bootloader. As I bought this phone used, does the open lock at the screen bottom during the startup graphic mean my bootloader is unlocked as well as the phone being rooted?

I've already used fastboot to upgrade my Amon_Ra recovery and my radio (without actually fully understanding it) so the instructions around this site are pretty good, even for noobs. If I lose root (I shouldn't, but just in case), I'm sure I can figure out the rageagainstthecage exploit if needed.

Then again, hanging on the coattails of talent like I've seen in this place, I may not need to!

Thanks!
[Nexus One Android Development] applejosh:
Yep. You have an unlocked bootloader.

Edit: And you won't lose root unless you flash/install a non-root ROM. Even if you do, you should be able to boot into recovery and flash/install a rooted ROM.
[Nexus One Android Development] efrant:
Yes, you are correct to a certain extent: its the unlocked bootloader that technically voids the warranty (because at present, you cannot relock the bootloader on a Nexus One, aside from a few exceptions). But it used to be that you needed to unlock your bootloader to get root access, but now with a couple of exploits floating around, you don't need to unlock.

Anyway, since your bootloader is unlocked, you can flash any ROM/recovery/radio/etc via the adb command fastboot.
[Nexus One Android Development] guys234:
upgrading to FRG83

Hi Geo,

I really like your ROM, i'm using it for 3 weeks now and it works really good,

no problems at all - i'm even using the Apps2sd version.

the exact version i'm using is FRG33 Blackbar Apps2sd v2,

and I want to upgrade to the FRG83 version without loosing apps2sd

feature and without doing wipe,

which of your FRG83 Roms should I download and flash in order to get the update

without loosing any data or apps2sd?

Thanks,

Guy.
[Nexus One Android Development] Txtraveler:
Can I pull the build.prop from Geo's FRG83 and push it into the FRG33 without screwing things up, or are the builds too different for that to work? I'm assuming that people with his FRG83 ROM aren't getting the notification any more.

Alternatively, if anyone knows what to put in the fingerprint line of build.prop of the FRG33 ROM to fool the google servers, I'm willing to give that a go. I've been studying up on adb and (I hope) I have a decent enough handle on how to perform that particular surgery.

Even though I've discovered a couple things I'd change (like removing landscape mode on the home screens), if you can't tell yet, I REALLY like this stock FRG33...

Edit: I've compared the two build.prop files from these ROMs and there are only 8 lines that are different - and most of those have to do with identifying and dating the build. It also says

"Do not try to parse the .description or .fingerprint" lines (2 of the 8 that are different), so I'll need a bit of advice here...
[Nexus One Android Development] applejosh:
There's a line with "fingerprint" in it (I think it also has 2.2.1 and FRG83 in that line). I don't know if just pushing the whole thing would work, to be honest, as that action might result in some other unintended consequences (because your device would report to the market, etc., that it was on FRG83 when it really isn't). My understanding is the fingerprint is only used by Google's update servers (but I have not bothered to verify this - standard risk disclaimer applies). The build.prop is in the /system directory (both in the ROM's zip file and on your device). I'd pull the file from the device and edit it on your computer and then push it back followed by a reboot. I highly recommend a nandroid backup prior to any of this.