Quote:
Originally Posted by eyeb
don't know if it matters, saw it on last startup file for Rhod400 (Didn't check other ones)
but the line that says
Shouldn't it be
I don't know if the startup thing sees the set part when it is part of another word, I put the space in mine though when I saw it, just forgot to comment on it until I looked to see if anything changed in startup with this update
|
a) don't use Windows
b) don't use notepad
If you looked at this file with Linux, or Notepad++, it'll show up just fine. Sorry, not going to fix a trivial issue that only effects users when they actually look at the startup.txt's.
Quote:
Originally Posted by wizardknight
Found what might be a minor issue. I tried to run updates from the market, and superuser gave "Package file was not signed correctly."
Anyone else get this error?
It is not that big of a deal, but might want to peek at it before it is is released.
|
Yup, this is the correct way to fix it:
Quote:
Originally Posted by eyeb
the superuser error is common, there is an app in market called superuser fix or something like that, it happens when devs put superuser/root roms that uses an older signed thing (don't know correct name), but the superuser app guy talks about it on his webpage
|
If you go to update SuperUser, at the bottom you'll see SuperUser Fix. Install that, it'll go thru its paces... it actually failed on mine at first, but the next run it said it was fine. Then update SU like any other app, should work fine.
I tried to fix this issue in the build, but it seems we can't if we want to build from source. Oh well... I didn't see any issues with SU being an older version, so there's by no means a requirement to update.