yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] AndDiSa:
Not sure, that this is the reason ... I am testing with Genie-Widget for the weather forecast and the situation is the following:

- only mobile network -> no location

- switching on GPS -> no location

- switching on WiFi -> location fix

in the log I can see allways messages like this:

...
D/WifiLocator( 1878): Too many no-location APs. Will not compute a location nor go to the server. hasLocation=0 noLocation=0 cacheMiss=0
D/CellLocator( 1878): Primary cell is in cache with no location.
...

Edit: googled a bit and looks to me, as if there are also other people (even with Nexus S) having the same problem ...
[G1 Android Development] Maxamillion:
yea i am, cuz i have windows. Should i be compiling it there?

i know it sucks, i already found a guide for resizing my virtual disk space.

ima make it 20gb.
[G1 Android Development] AndDiSa:
stay on linux, it's much more easy ... ;)

I would suggest at least 32GB, especially if you want to compile the kernel, too.
[G1 Android Development] Maxamillion:
ok thanks 32gb it is.
[G1 Android Development] tvall:
No but in my experience, vm greatly reduces performence. But a linux vm is better than nothing
[G1 Android Development] AndDiSa:
Depends mostly on the physical memory available ... I am running a 2GB linux vm on a 3GB linux system for compiling building ads_magpie. Performance is a bit reduced, but still better than compiling on a 2GB windows system ;)
[G1 Android Development] tvall:
And cpu. Don't forget that. I compile in a Ubuntu chroot on my cr-48. That'll be slow no matter what I do lol
[G1 Android Development] Poppu:
In this case, may be you should use Wubi.

This allows you to use a virtual disk (no need to partition your disk) but with a real machine (restart windows, select Linux in the Windows Loader Menu).

So it's quite like a real Linux installation except that your Hard Disk is NTFS file. From Windows point of view, Linux is just an application that you can uninstall when you want.

And from Linux point of view, you are not in a virtual machine (therefore you have full capacity over your computer). Only File system is fake and can be theorically a bit slower, but I use it daily without noticing any difference.
[G1 Android Development] muldy:
There's your problem :P
[G1 Android Development] 4qu4rius:
I've been watching closely how SMS come and go and they seem to be handled correctly.

Great work !
[G1 Android Development] Maxamillion:
Thanks! :)

I never knew about this, ima use that instead of virtual box.
[G1 Android Development] AndDiSa:
I have the impression, too, that battery is improved with the new kernel, at least I do not notice any longer massive battery drain as I had some times. But I am still wondering why I get always around 30% - 35% power usage for mobile standby. Consumption for display is more or less in the same range, sometimes even less ...
[G1 Android Development] jdb78:
Installed the latest ADS Magpie and my phone seems to run way faster than before. There was only one of three dalvik directories filled with data, I deleted that using cd /data//dalvik-cache and then rm * and then a reboot to recovery from where I flashed ROM and gapps. After a reboot I did the fix_permissions thing and rebooted again. Now I own a brandnew phone. Thank you guys! You are awesome.

P.S.: Genie Widget finds position flawlessly using 3G
[G1 Android Development] Unrelashade:
Any news on this bug? Would be convenient not to create an ext :) However, I'll try it out with one now, though...
[G1 Android Development] newellj79:
I enabled magpie to use the ext partition and no problems now. Although that doesn't answer your question...
[G1 Android Development] AndDiSa:
Normally there should be at least two different positions for the dalvik cache: /data/dalvik-cache and /sd-ext/dalvik-cache. /data/dalvik-cache is used for applications installed on /system, /sd-ext/dalvik-cache for applications installed on /sd-ext

My GPS problems now vanished, even if I have still sometimes problems to get a location fix in Genie Widget when I have disabled wifi.
[G1 Android Development] roccoadam32:
wow the new beta is so much faster this is really coming along nice thanks terry

still getting a force close when i disable the on screen keyboard in settings other than that everything is great
[G1 Android Development] {davros}:
Its amazing how well ezGingerBread runs on my old g1 way better than any GB Rome run on my moto Droid
[G1 Android Development] 4qu4rius:
Yep, that's really great !

I have an od bug on Superuser.apk update. The update fails with a "no space left" kind of message whereas there IS a lot of space on internal memory, and on sd-ext. any clue? read something a dozen pages ago but can't find it anymore.

EDIT: sorry, seems to be already known:
[G1 Android Development] ezterry:
As far as superuser.apk goes .. if you are getting a space error that is the know bug, but if you are getting an error about the install location that is a feature.. well half of one.

There is a security flaw .. and a posibly serius one in the fact I know ChainsDD's private key for superuser.apk (its in the cm repo, and cloned into ezgb's). This means we do not want apps from third party locations overwritting the superuser application [fake upgrade] or installing a shared app (in theory chainsdd has some protection on the second case)

So its currently blocked.

Now I say half a feature because I don't feel installing from market an update or superuser eliet is a problem. And ought be allowed. Was pondering this and think I have a solution, when only market installs are allowed to let you check a box to allow system app updates. At this point market installs and adb install will allow you to install system apks including superuser without issue.

As for the space error I'm still looking into it.. last week I needed to take some time away from android hacking.
[G1 Android Development] farmatito:
Couldn't it be a solution to use a per user key generated

at rom flash time to sign the superuser apk?

The key could than eventually be stored encrypted on the sdcard to be reused at the next rom flash if found.

Just an idea, cant say how hard it is to implement it

in a update script....
[G1 Android Development] tvall:
And then you wont be able to update it due to different signatures
[G1 Android Development] 4qu4rius:
Ok, thanks for the answer. This is indeed a default location issue for me. I don't know why I would need the latest shiny new Superuser.apk anyway so that's no big deal.
[G1 Android Development] Poppu:
But that means that if you loose your key (e.g. bad SD paritioning, file erased by inadvertance...) you will need to update your ROM, no ?

And as already said it can be a problem for updates.
[G1 Android Development] farmatito:
as you did not install it through the market there will not be proposed updates

so probably next update if any will be at reflash time.

At reflash time:

if signature on sdcard

decrypt it and resign superuser.apk

if not found

if superuser in packages.xml

remove and uninstall

create new key

resign superuser.apk

encrypt key

store it on sdcard

Just an idea, can't say if it could really be done that way
[G1 Android Development] farmatito:
if key is lost

unistall and remove superuser

remove key from packages.xml if still there

create a new key

resign and install

encrypt and store

maybe just reflashing the same rom with resigning mechanism could solve it.

Just a guess.
[G1 Android Development] tvall:
We are talking about the market updates here. We just just sign it with a different key and that would solve the security issue. But then we would completely break market updates
[G1 Android Development] farmatito:
Yes I know, but what good does it to me if I can update a insecure version of superuser

through the market with another insecure version. Isn't better to keep my old secure version?

OTOH new version could be downloaded from market and resigned with personal stored key if you really want to update it.
[G1 Android Development] roalex:
Well, we could sign superuser with a private key and simply add an option somewhere to UNinstall Superuser which would point to a script which will delete the apk from system and perform pm uninstall, then you should be able to install the market version.
[G1 Android Development] ezterry:
I think if you remove the current one (but leave su) and reboot you can already do that.. or take the actual updated apk and just replace the one on system.. in the later case I think you keep the protection as well.. best just to let the clean update from market when the user opts to in the long run
[G1 Android Development] farmatito:
Simple instructions to install self-signed Superuser app:

1) create your private key:

openssl genrsa -out key.pem 1024
openssl req -new -key key.pem -out request.pem
openssl x509 -req -days 9999 -in request.pem -signkey key.pem -out certificate.pem
openssl pkcs8 -topk8 -outform DER -in key.pem -inform PEM -out key.pk8 -nocrypt

2) resign it

java -jar /path/to/signapk.jar /path/to/certificate.pem /path/to/key.pem Superuser.apk signed-Superuser.apk
rm Superuser.apk
mv signed-Superuser.apk Superuser.apk

3) uninstall old Superuser from adb shell or terminal

busybox mount -o rw,remount /system
rm /system/app/Superuser.apk
pm uninstall com.noshufou.android.su

4) install self signed Superuser.apk

adb push Superuser.apk /system/app/
adb remount

This worked for me. NO WARRANTY. USE AT YOUR OWN RISK.

To install Super user from Market perform step 3 first.

To update the resigned Superuser.apk yourself

keep the keys you have generated so that you can reuse them

in resigning process.
[G1 Android Development] ezterry:
.. somehow just installing the version in the extras section of rom manager seems the easier way to get the new release.

That or wait a week or two for me to merge it.. and fix the update.
[G1 Android Development] ldrifta:
im having trouble on step 13. when i got to unzip the file it says no such file or directory.. but everything before that works fine... i have jave jre. jdk and apk manager installed.. can anyone help?
[G1 Android Development] Maxamillion:
try this:

chmod +x unzip-files.sh

and then this:

./unzip-files.sh

hopefully it works..
[G1 Android Development] Maxamillion:
are you talking about the next build?ima lil confused??
[G1 Android Development] ezterry:
There is a new version of Superuser out as indicated with most of yesterday's chat, it was put by koush/chainsDD into rom manager in the "Extras" section/developer for use on any rom with an older version. (if you poke a bit you can get a raw link to the update.zip rom manager is linking to)

Regarding ezGingerbread: The next release [over the weekend if one is ready.. over the following weekend if one is not] will have the changes but i've not merged it yet. In addition it will have a patch to make it possible to override the safety policy that prevents you from installing items signed with the Superuser private key. Thus directly install market updates or Superuser elite
[G1 Android Development] Maxamillion:
thanks for that explanation, look forward to your next build.
[G1 Android Development] ezterry:
Stand Alone ezGb kernels

EzGingerbread Kernel Post

Here are stand alone auto-any-kernels for the ezgb2636 kernel builds. There are two versions of these installers:

Gingerbread: the same format as the included ezGingerbread kernel for use on gingerbread and other roms designed to be used with gingerbread kernels, note this kernel requires a gingerbread ready vold and build in zram compcache scripts and modules.sqf support

Froyo: The same kernel but with a backwards compatible USB mass storage implementation, and ramzswap module to work with most existing froyo rom's vold+compcache, last the modules in this version are not contained in a squashfs.
​

While I provide these for people to experiment with in other roms; please note I cannot promise the kernels will work in all roms:

ezgb-2636-v1.5.2: (git tag ezgb-2636-v1.5.2-20111106)

Gingerbread: ezgb-2636-v1.5.2_S.zip md5: 244be107ab1a32b8f8b96301eedb5f94

Froyo: ezgb-2636-v1.5.2f_S.zip md5: 20a010b6cb86a70dc09dbc93d324a150

ezgb-2636-v1.5.1: (git tag ezgb-2636-v1.5.1-20110820)

Gingerbread: ezgb-2636-v1.5.1_S.zip md5: 5b02e44aa976a7217a4febdba6f940dc

Froyo: ezgb-2636-v1.5.1f_S.zip md5: 3074b8b76880e66e3612cf047f8d1df5

ezgb-2636-v1.5: (git tag ezgb-2636-v1.5-20110706)

Gingerbread: ezgb-2636-v1.5_S.zip md5: 00841def2178c96500d585eaa385c4ba

Froyo: ezgb-2636-v1.5f_S.zip md5: ab42eeab2a82f717204704e1777173b6

ezgb-2636-v1.4: (git tag ezgb-2636-v1.4-20110615)

Gingerbread: ezgb-2636-v1.4_S.zip md5: 642066b8c2c36784a7bc4aaf76fb6740

Froyo: ezgb-2636-v1.4f_S.zip md5: 9f59a7ef3fed85d99674d7d72b0837bf

ezgb-2636-v1.1: (git tag ezgb-2636-v1.1-20110504)

Gingerbread: ezgb-2636-v1.1_S.zip md5: e15dd17b24259bdbbed94800caf639a4

Froyo: (this build was prior to froyo support on the 2636 tree)
​

Information about the source code and building

The source code is the tag indicated for each version (follow link for the github view and source download links). All kernels (froyo and gingerbread) are built with the ezGingerbread kernel build script [as described in the op] before being packaged by hand in the update.zips.

For froyo kernels a small change is made to the build script to use the froyo conigs:

-configtmpl='ezgb_%s_defconfig'

+configtmpl='ezgbfroyo_%s_defconfig'

To unpack the sqf files created in the froyo version I loop mounted them over the update.zip template while building the image on the build box.

---------------------------------------------------------------

** Bookmark this post for future updates :)
[G1 Android Development] jdb78:
Take all the time you need. We are all happy about the progress you make to this ROM but there is no need for losing all your private life above that. So if you feel like coding or not or if you rather be with your family (which anyone is supposed to understand) - it's all up to you. Like I said, take your time - and thank you for all your efforts...
[G1 Android Development] ldrifta:
na im sorry it didnt work.. i dont know what im doing wrong.. i have java jre and jdk installed, i have sdk manager and all that and im following this guide exact!! untill step 11-13 i cant download nighties or unzip them if they are downloaded.. can someone tell me exactly how they did this? should i use a different version of ubuntu? i have 11.04
[G1 Android Development] Maxamillion:
try these:http://www.cyberciti.biz/faq/run-execute-sh-shell-script/
[G1 Android Development] ldrifta:
well i checked in the location that it supposed to download the latest nightlies or something and there is no .zip file in there... but im typing everything correctly..
[G1 Android Development] muldy:
Just a little question:

Google Talk is a little bugged right?

Some force closing... (must be the video/audio thingy)

Still is totally usable.

Did anyone tried Updating it to a more recent gapps?

Thanks.
[G1 Android Development] hrk:
The problem lies in the binary library, yep. The solution is not just a more recent gapps package, but one which is tailored to our CPU (MSM72*)... such as the LG Optimus One, which is going to receive Gingerbread in the next days (at least here in Italy) so I do really hope it comes with the new Gtalk even if it lacks a front camera...
[G1 Android Development] muldy:
Thanks for the information :)
[G1 Android Development] farmatito:
The inquirer reports:

"THIRD PARTY Android distributions such as Cyanogenmod has been targeted by malware that exploits the use of publicly available private keys.

The vulnerability in third party Android distributions stems from the use of private keys that are available publicly in Google's Android Open Source Project. Android by default allows the installation of applications without user intervention that have the same private key as the operating system itself.

Read more: http://www.theinquirer.net/inquirer...are-targets-unofficial-releases#ixzz1PYzMN3ib

The Inquirer - Computer hardware news and downloads. Visit the download store today."

I'm wondering what would happen if I simply change the test keys we are using with personal generated keys, are there any downsides?

BTW: "The popular Cyanogenmod distribution has fixed the security hole with its Cyanogenmod 7.0.3 release", have we already imported this fixes?

One more interesting article:

http://www.h-online.com/security/ne...resses-Google-s-long-term-memory-1262405.html

Couldn't we a add a setting to randomly change the wifi mac address at every connection?

​

​
[G1 Android Development] tvall:
I already use my own keys wen I build anything and it ain't broke nothin yet.

And this rom ithink has it's own (lesser known but still public) keys so if we weren't patched against this someonewould have to target us specifically. (If I were to attempt that I would target something as large as possible )

And I'm pretty sure ezterry fixed it around the same time cm did
[G1 Android Development] ezterry:
Of course I did it was that alpha labled security update that [nearly] no one downloaded ;)

Of course we have had two beta releases since both seem well distributed
[G1 Android Development] roalex:
Yeah Terry took care of it long time ago also, CM had the fix for ages.
[G1 Android Development] farmatito:
I supposed that it was already fixed, nonetheless this increases my feeling that we should find a way to sign everything at flashing time with "per user" generated keys (if this doesn't break something else as it seems). This will close every security problem related to the keys as to be honest from a paranoid point of view it makes no difference that the keys are public or not as long as someone else has them.
[G1 Android Development] :
+1

Call me paranoid too :D
[G1 Android Development] ezterry:
Before continuing this line of thoght, ask yourself this question: when are the keys checked over the lifetime of an application, and when are they partly or fully checked? And what do they mean to the system.

My opinon you are taking a deadlocked metal door and asking to replace it with a brick wall. Its a headache to enter a house when all the doors are bricked up.. but this is true for both the theif and owner.

If you are building from source for your self its easy to change the platform key.. but If someone else wants to give a update.zip the changes phone.apk while its important that the end user trusts the one distributing the app its imposible without rebuilding the entire rom without the key being known to the one updating the app.

Also if you are hoping to keep the key around how do you save the key as to actually provide higher security than disallowing installs of apps using the key as is done now?
[G1 Android Development] ldrifta:
hey ezterry sorry to bother you but i was wonderin if you or someone here could help me out.. maybe tell me exactly which ubuntu to use or something because when i got to step 11 its not downloading anything.. im doing everything else right as far as i know but maybe you can jus clearify the steps for me a little? i dont know what im doing wrong but its killing me lol i tried like 20 times re installed ubuntu and everything i just cant figure it out..
[G1 Android Development] ezterry:
I think you need to ask yourself what the curl is supposed to do:

curl http://sandbox.devnull.name/android/gingerbread/GINGERBREAD-DS-CheckPoint-20110501.zip > sapphire_update.zip

this command is supposed to simply download the file GINGERBREAD-DS-CheckPoint-20110501.zip (same as if you clicked on the link in post 2) and spit it to standard out.

Since its a large binary file is not very useful when sent to screen we are redirecting standard out to the file: sapphire_update.zip. (ie the '> sapphire_update.zip' part of the statement)

Thus all we are doing in this step is downloading one of the builds with the most resent proprietary files, and saving it as sapphire_update in the root of the build tree.

curl is a very basic command on many posix boxes.. really why I didn't respond earlier .. I'd figure you would have figgured out the line.. or gave up downloaded the file in firefox/iceweasel and move it in place.
[G1 Android Development] ldrifta:
lol well the thing is my friend is teaching me how to make custom roms and how to customize them and learn about scripts and everything so one of the things he wanted me to do wat get your rom download from source through ubuntu in terminal.. so i am very new to the whole typing in cmd thing.. i just learned fatboot and adb and still dont really use it that much.. so sorry if i seem helpless lol but we all have to start somewhere... all i know is when i do step 13 is says that no such directory exisits.. so im doin somethin wrong...
[G1 Android Development] farmatito:
Before I can answer your question I have to think more about it. One more question, in build/target/product/security/README it is written:

Is there a easy way to generate a reference list to see what exactly is signed with which key? This would give me a starting point.

What do you think about random mac address?

This should be easier to implement, but i would need help for the gui as i have no java knowledge at all.
[G1 Android Development] hrk:
... can't you ask your friend instead of posting here those questions?
[G1 Android Development] ldrifta:
lol i would but he from uk and im from us so he sleeps when im awake.. lol i was hoping i could get this done without asking him a hundred questions lol im just not sure what im doin wrong.. i tried different versions of ubuntu also
[G1 Android Development] AndDiSa:
Today I've found some time to add at least a preliminary configuration script to the ROM. With this script you are able to add / remove buttons to the PowerWidget and to define their order. Unfortunately I still do not have the time to completely integrate the configurations options into the ROM ...
[G1 Android Development] creezalird:
tested your latest ones and the pwsetup script is working.

btw, i've noticed one small apk name typos in the backup script inside the rom, which will render car home app useless after a rom update.

typo : carhomegoogle.apk

right : googlecarhome.apk
[G1 Android Development] AndDiSa:
Thank you for the hint, I will correct it in the next version.
[G1 Android Development] jonnyj771:
i am guineapigging this kernel and testing it on yoshi 1.2. will post any problems sunday night. thanks ezterry.
[G1 Android Development] dw9906:
Help!!

Removed!!!!!!!!!
[G1 Android Development] BibleBelt:
repo probs?

Maybe nothing?

When I try to sync the repo, I get:

hw@BibleBelt /mnt/usbstick/android/ezGB $ repo sync

Fetching projects: 1% (3/167) fatal: The remote end hung up unexpectedly

error: Cannot fetch platform/bootable/diskinstaller

Standard Discalmer: It worked flawlessly yesterday.

Maybe they have probs at GitHub? Can anyone confirm / disconfirm this?
[G1 Android Development] dw9906:
Removed!!!!!!!
[G1 Android Development] roalex:
cd dir

rm -rf *

rm -rf .*

repo init -u https://github.com/ezterry/manifest-gingerbread-DS.git -b gingerbread

repo sync -j16
[G1 Android Development] AndDiSa:
Did a repo sync five minutes ago without any problems, but that doesn't mean anything, because my route to github for sure is different than yours ... ;)
[G1 Android Development] dw9906:
Removed!!!!!!
[G1 Android Development] AndDiSa:
That's ok, now you can init the repo ...
[G1 Android Development] AndDiSa:
What version of Ubuntu do you have installed?

What version of python?

What version of repo? Probably an old one?

(I saw an error message in an older post from you when linking repo to /usr/local/bin/repo)
[G1 Android Development] AndDiSa:
It's most likely due to an incompatible python version. I am compiling on Ubuntu 10.04 and python 2.6 without any problems ...
[G1 Android Development] BibleBelt:
Yep, seems to be a server problem.

I followed the advice given in

http://groups.google.com/group/repo-discuss/browse_thread/thread/8ad44c12a3a63a82

and repo synced again.