yashsingh1/xdaforums huggingface dataset:
[G1 General] brummiesteven:
Dunno if anyone else has picked up on this but it looks like google might have solved the problem of the G1's (and other phones) low ROM and newer android updates.

Question went something like this:

Q: "Why does the Nexus One have limited storage space for Applications?"

A: "We want to protect our apps and developers however we are working on encrypting apps and allowing them to be stored on the SD".

So basically we have A2SD (legit) coming up soon.

Which means 2.0,2.1,2.5,3.0 etc etc should fit fine on the G1 right?
[G1 General] jubeh:
um, not really

The storage limitation they're referring to deals with the 79 MB size of the /data partition on the Dream.

The android system, though, is installed at the /system partition, 70 MB big. Newer releases add new features, for example, in 1.6 the tts (text-to-speech) service was introduces. In higher capacity devices, there's a folder in /system called /tts (5.9 MB big) that holds the voice data for speech synthesis. On the Dream, however, though the feature is there, the voice data has to be downloaded from the market to be usable, and it's stored on your sdcard.

If future android releases can rely on external resources downloaded to sdcard (plugins, libraries, etc), then the life of the device can be extended, but space is running out and there's no way to add new features without removing others.

What they were talking about in the N1 conference was about the other partition, the /data partition, which stores your personal data, e-mails, mms, settings, and programs. I personally believe the sdcard should have initially been used for that purpose, giving more space to /system, and that way a wipe would require nothing but formatting your /sdcard, however, because of copyright protection of apps (which is useless against a root-user anyway) apps are kept internal, spaced robbed from /system, and sdcard used only for user's files.

What they're now trying to do is to (possibly) have apps now be moved to sdcard, but have those apps encrypted so that they can only be read from the particular system. That way the limit of apps you can install is as big as your sdcard.

I still think all phone ssd should be reserved for /system (and maybe a tiny bit 10 MB /data partition) and leave mms, e-mails, and other infos into xmls in the sdcard so that allows you to move from device to device and keep your data with you without having to re-customize.
[G1 General] daveid:
In theory your idea of using the sdcard for all userdata sounds great. However, what about the user who wants to have multiple sdcards for media storage beyond 16GB. Right now, I have like 4 8GB sdcards that just sit around collecting dust (full of tv shows formatted for my G1), because I run A2SD and can no longer swap cards.

The proper way is similar to how Symbian UIQ3 (not sure if other OS's used the same model) gives the ability to store on the removable storage. When you install an app it prompts you to install internally or to the media card. If you chose the external storage - that app is written to that card, where that app stores it's data is up to that app. This way, you have the ability to place lesser used apps, or larger apps, on your removable storage device. While maintaining the ability to swap cards and still have a functioning phone.

I for one, am not satisfied with 16GB of storage for my portable media appetite.
[G1 General] lbcoder:
The only limitation is against OVER THE AIR UPDATES.

Dream has *TONS* of space.

Only 50% of the space that could be used for system images is actually used!

Actually LESS than 50% since the stock /system image isn't even full.

Whatever doesn't fit in /system can *VERY EASILY* be moved into /cache.

In building a newer system image, there is also no reason why ALL features must be included! Some features can simply be LEFT OUT.

Maps for example. Leave it out of the system image and force it to be installed from market.

Further compile-time optimizations can also be used to make the compiled image smaller than usual.
[Nexus One General] grifforama:
Seriously WTF is up with T Mobile ?

Trying to open a brand new account comes up with this.

We are currently unable to process your request for service with T-Mobile.

T-Mobile's servers are busy or unreachable.

You can try again later, or you can purchase the unlocked phone without service.

Ordering one contract free obviously goes straight through to the ordering screen.

SORT IT OUT TMO

:mad::mad::mad:
[Nexus One Q&A, Help & Troubleshooting] humancyborg:
A cheap/dirty little hack to increase idle CPU frequency and increase performance in general (don't blame me when your battery runs dry in about 3 hours):

(must have root first!)

cat /proc/cpuinfo (use this to see cpu speed, you will see at idle its 162.54mhz)

adb shell

echo "performance" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

cat /proc/cpuinfo (now idling at 662.40mhz!)

If you want to switch back:

adb shell

echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
[Nexus One Q&A, Help & Troubleshooting] Freezey:
Id be affraid to tweak this things speed.

Is there a possibility that it could crash from being to fast?

Just curious
[Nexus One Q&A, Help & Troubleshooting] gobslotch:
Yeah the only thing I miss about my g1 is the extended battery.
[Nexus One Q&A, Help & Troubleshooting] melterx12:
no, but it can crash from overheating. and based on how fast this chip is compared to how thin this phone is, It may be possible for the chip to overheat on a hot day.
[Nexus One Q&A, Help & Troubleshooting] coolbho3000:
Protip: SetCPU (download link in my sig) can switch you between governors without the need for using the shell.

By the way, bogomips in /proc/cpuinfo is not 1:1 with MHz on the Scorpion.
[Nexus One Q&A, Help & Troubleshooting] Wii60:
It is literally too snappy to set the cpu. No need to bother. (Though I do appriciate the help)

However, the need to root still exists for tethering.
[Nexus One Q&A, Help & Troubleshooting] Sashin:
So setcpu will work for this already?
[Nexus One Q&A, Help & Troubleshooting] Mi|enko:
Yes. 10char
[Nexus One Q&A, Help & Troubleshooting] melterx12:
hmm its interesting to note that by default idle CPU speed is ~160mhz. I think the battery would not last 4 hours on or sleep mode if the CPU was constantly at 1Ghz.
[Nexus One Q&A, Help & Troubleshooting] humancyborg:
It's actually 254mhz, I was mistaken in my original post!
[Nexus One Q&A, Help & Troubleshooting] melterx12:
I checked it myself - Lowest Idle setting is ~160mhz
[Nexus One Q&A, Help & Troubleshooting] humancyborg:
Apparently not. Use SetCPU to confirm the below.
[Nexus One Q&A, Help & Troubleshooting] melterx12:
I used quicksystem app. Check for yourself.
[Nexus One Q&A, Help & Troubleshooting] humancyborg:
Problem reading incorrectly as well. What coolbho said is accurate, you will notice that using quicksystem or reading /proc/cpuinfo never shows a speed above ~660mips/mhz regardless of how heavy the load is, whereas SetCPU will show it at 998mhz under the same load.
[Nexus One Q&A, Help & Troubleshooting] no6969el:
so no luck getting over 1ghz?
[Nexus One Q&A, Help & Troubleshooting] Shatterv2:
Why the hell would you need to?
[Nexus One Q&A, Help & Troubleshooting] Terracnosaur:
What are the other legal and respected options in

/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

Other than

performance, ondemand

Would like to know, thanks for the tip!

Terracnosaur
[Nexus One Q&A, Help & Troubleshooting] humancyborg:
# cat scaling_available_governors

ondemand userspace performance
[Touch Diamond, MDA Compact IV General] dirtdiva:
I am having problems with the threaded SMS texting on my diamond. When I have a conversation box open and am texting back and forth with someone it does not show the messages as read. When I close out of the conversation and go to my SMS inbox it shows that I have new messages (as many as the person sent). The only way for me to clear these messages as read is to open and close the conversation as many times as there were messages sent. Does anyone know how I can fix this problem. Thanks
[myTouch 3G, Magic Android Development] ahmgsk:
This shd be in general Thread >> I think!!!!!
[myTouch 3G, Magic Android Development] Abrasher:
Let me knwo if this seems liek a wasted idea

Will begin to Update as I start testing ROMs again, give it a week or so.
[myTouch 3G, Magic Android Development] BlackElvis79:
ROM:in sig...

Widgets:Facebook, Pandora, Power control, Weather FlipClock, Audio Manager

Battery Life about 6 hours before reaching 15%

Type of user:Power user...heavy messaging, browsing, etc...

Side note: Screen is usually at 40% brightness, GPS off, no wifi use, no bluetooth, no auto sync
[myTouch 3G, Magic Android Development] Survivor.Sole:
Good topic :)

I did batery tests and i had similiar results... Thats why i keep using Cyanogen :)
[myTouch 3G, Magic Android Development] eyegor:
ROM : CursorSense 1.0 RC1

Widgets: flip clock, htc battery, taskiller, people, gps on/off, mobile on/off, wifi on/off, bt ob/off, photo frame, bookmarks, calendar, htc.search

Battery life : 12+ hrs, i always plug it in during the night

Type of user: power user. Lots of messaging, browsing, at least 1h a2dp Music daily

Side note : wifi and gps always off, brightness 50%

P.S the rom is faster and more stable than cyanogen. Downside -> specific radio/spl + cupcake

EDIT: and 32A only :-/
[myTouch 3G, Magic Android Development] Abrasher:
Good To See

I just wanted to thank you all for hoping on board. I hope we continue to Build this thread. Keep Testing...Keeping Posting!
[myTouch 3G, Magic Android Development] cursordroid:
I understand and appreciate what you are doing here, don't get me wrong.. But I think this should be moved to the General section. :)
[myTouch 3G, Magic Android Development] tmhung:
Rom:[32B/Dream][Dec23][Dwang][Donut][Speed and Stability][v1.17.1]

Widgets: Facebook, Clock, music, Power Settings,

Battery: Average 21 hours

Type of User:Normal user

Anything Worth Mentioning: Only 2g , brightness defaut
[myTouch 3G, Magic Android Development] travon802:
Rom: [32B/Dream][Dec23][Dwang][Donut][Speed and Stability][v1.17.1]

Widgets: SportsTap, Beautiful Widgets Flip Clock, Cachemate, Power Settings,

Battery: Average 18-20 hours

Type of User: Normal user

Anything Worth Mentioning: Auto sync on, WiFi/GPS usually off, Brightness @ 41%, Use Advanced Task Mgr to end apps every hour
[myTouch 3G, Magic Android Development] domenukk:
I would love to have also like a satisfaction Rate or personal opinion whateverthingi. (runs smooth? looks good out of the box? comment)

After all, battery live is not the only thing that matters.

(Yeah, I know this thread is about battery life, but why not?)

(or is it possible to rate single posts somehow? so we could do it that way)

just asking :)

And thanks for the thread (ok im already messing it up by posting something else... :P)
[myTouch 3G, Magic Android Development] Abrasher:
Battrey Life

It is begining to llok as if Super D mixed with Pure Widgets, and MXPlayer is the best way to make your MT3G (myTouch) into a stable version of HERO.
[myTouch 3G, Magic Android Development] d33dvb:
Good stuff, maybe some speed test results would be awesome, you should talk to @AndroidSpin and get it added to the ROM database.
[myTouch 3G, Magic Android Development] Abrasher:
SuperD vs CSDI

Do not get caught up in the hype!!!!! The numbers read faster with CSDI but SuperD is more stable, and innovative! Take a look at the latest. SuperD Roms are continually doing what others aren't! Now with the BEST MUSIC WIDGET IN EXISTENCE!!!
[Windows Mobile Software Development] gazmac:
I am having a problem with remote connections via ICS on WM6 when using 3G tethered modem. OpenVPN connection is stable.

It is not possible to change the remote network from 192.168.0.0/24.

PAN uses 192.168.0.0/24 as well. This means that routing through OpenVPN etc. will not work.

I have searched the registry on the Jasjam but could not find where the PAN network is defined.

Does anyone know how to make it use a different network?
[Windows Mobile Software Development] rhu-1alnd:
In the registry, go to :

[HKEY_LOCAL_MACHINE\Comm\RNDISFN1\Parms\Tcpip]

Add the following :

"IPAddress"="192.168.10.1"

(change to whatever you want instead of 192.168.10.1).
[Nexus One General] Jak Crow:
I'm getting this A LOT. It doesn't affect apps that I'm currently using, but obviously its restarting the homescreen way too often for my tastes.
[Nexus One General] Ryanmo5:
Same here i get it every now and then. Gonna wipe and see if that helps any.
[Nexus One General] eJLIFe:
Haven't had any issues with FC's on the Launcher.. if anything *knocks on wood* I've yet to have any serious issues or even minor issues. The touchscreen seems to act funny if I'm holding the phone with my fingers too close to the edge of the screen.. but if I move them it works fine.
[Nexus One General] BrooklynAvi:
I'm desperately looking for a solution to this issue. I've had it since the beginning.

Wiping will "solve" the problem but it will come back once you add your apps again. This issue needs to be elevated because I guarantee that more people have this problem and just don't know it. I have spent so much time on this that I've yet to completely build my N1 to the way I like it.

This is because you are used to holding it like you hold your myTouch (or other touch screen device) and the inside of your thumb at the bottom where it meets your hand is touching the screen at the same time. It took me some time to realize why it acted funny when using with one hand and not at all when using two hands.
[Nexus One General] JoshHart:
yeah i get this too, maybe a common app or widget we have running? It refreshes so fast that its not that annoying and doesnt happen too often but still strange.
[Nexus One General] r3pek:
Looks like a bug in here:

or somewhere along the callstack.

Anyway, it's in the Android Stack, and as there's no AOSP 2.1 yet, we just have to hope the Google Devs already saw it...
[Nexus One General] BrooklynAvi:
I've been working to figure out if it is an app and while it's a possibility, you have no idea how tedious it is. I've been installing one app at a time and testing after each (almost 200 apps and widgets), even rebooting and saving nandroids of working installs to revert and continue. But I end up thinking there's nothing wrong and then it suddenly starts happening (I can replicate as often as I need to). So I started reversing the process by uninstalling and testing. Nothing so far. BTW, a fix permission in recovery does not help. I truly believe it is an error on Google's end and that it is an "easy" fix for someone who knows how. I'm done testing. I put more hours into this than I care to admit (believe me, you don't want to know).
[Nexus One General] Jak Crow:
I wiped my phone and the problem has gone away, so its definitely an app causing the problem. I don't have a lot of apps so I may discover the one causing my issue sooner.
[Nexus One General] BrooklynAvi:
Please do. If you'd like, download aTrackDog (if you don't have it already) and PM your list of apps so I can compare against my apps. I've been at it for so long that I can't do it anymore and have given up for the time being. In aTrackDog, click Menu > Export Apps List. I need to get my N1 set up and then I'll look at it again. If anyone else wants to PM me their app list, I'd appreciate it (only if you have the FC, of course).
[Nexus One General] iVisionX01:
Are you guys that have the problem using Live Wallpapers? If so which ones?
[Nexus One General] Jak Crow:
I've tried both live wallpapers and regular ones. The laucher close was happening with either.
[Nexus One General] BrooklynAvi:
The Live Wallpaper (Polar Clock) is a known issue. Google is even aware of it and is supposed to eventually offer an update. I'm still hoping people will send me a list of their installed apps (using aTrackDog) so I can try and figure out which app is the offender. It's nearly impossible without another app list.
[Nexus One General] BrooklynAvi:
Can't Test Anymore

I can't test this issue anymore. I've spent too much time on it and I just don't care that much anymore. I'm not sure what app, if any, is causing the problem. Hopefully someone can come up with something more concrete and post it here.
[Nexus One General] poisons:
I had the same problem with MyTouch, after many tests it seemed it not was an app in particular, but the number of apps running together.

Every time I back to the home, it restarted the launcher.

I supposed it was the lack of memory of the MyTouch device, but if it happens with the nexus too maybe it's the concomitance running of two apps.

I've MyTouch broken, so I cannot send you the apps list, but as soon I'll receive the nexus I'll install the same apps and we can begin to compare.
[Nexus One General] SpyderMS:
Happens to me as well. I haven't noticed it recently, but definitely when I first got the phone. If I see it happen again, I'll make sure and get my list of apps from aTrackDog
[Nexus One General] joeavery2:
Here too. I noticed it right away, but then I added apps right away...

I get it when I wake it up, when I launch apps, every few seconds to minutes. I'm hoping google is aware of it and fixes it. I don't mind it other then it shouldn't happen and that it delays me when I return to the home screen.
[Nexus One General] sir*mez:
are you guys using any task managers?? I had the problem with advanced task manager when it did auto end running apps. I had to exclude the launcher and android live wallpapers so that I wouldn't get the launcher to restart on me. I hope I helped.
[Nexus One General] britoso:
post deleted.
[Nexus One General] BrooklynAvi:
Believe it or not I do not have a task manager on my N1. I haven't found the need for it. I found myself clicking the one click end-all widget from Advanced Task Manager about 100 times a day on my myTouch but have not even remotely had that need on my N1. I didn't even get around to installing it when the problem happened. I have since installed and uninstalled the app both before and after wipes. I am beginning to become convinced that this is an issue with the device and needs to be fixed in the OS. I could be wrong but no combination of apps that I have tried seems to make a difference and I have tried hundreds.
[Nexus One General] britoso:
This is a trace that I was waiting for... Kept long pressing and moving widgets around on the desktop, after about 8 moves I got this trace along with the process.com.android.launcher2 force close crash.

01-13 17:13:12.537: ERROR/dalvikvm-heap(7995): 174240-byte external allocation too large for this process.
01-13 17:13:12.537: ERROR/(7995): VM won't let us allocate 174240 bytes
01-13 17:13:12.557: DEBUG/AndroidRuntime(7995): Shutting down VM
01-13 17:13:12.557: WARN/dalvikvm(7995): threadid=3: thread exiting with uncaught exception (group=0x4001b178)
01-13 17:13:12.567: ERROR/AndroidRuntime(7995): Uncaught handler: thread main exiting due to uncaught exception
01-13 17:13:12.617: ERROR/AndroidRuntime(7995): java.lang.OutOfMemoryError: bitmap size exceeds VM budget
01-13 17:13:12.617: ERROR/AndroidRuntime(7995): at android.graphics.Bitmap.nativeCreate(Native Method)
01-13 17:13:12.617: ERROR/AndroidRuntime(7995): at android.graphics.Bitmap.createBitmap(Bitmap.java:468)
01-13 17:13:12.617: ERROR/AndroidRuntime(7995): at android.graphics.Bitmap.createBitmap(Bitmap.java:435)
01-13 17:13:12.617: ERROR/AndroidRuntime(7995): at com.android.launcher2.DragView.<init>(DragView.java:78)
01-13 17:13:12.617: ERROR/AndroidRuntime(7995): at com.android.launcher2.DragController.startDrag(DragController.java:232)
01-13 17:13:12.617: ERROR/AndroidRuntime(7995): at com.android.launcher2.DragController.startDrag(DragController.java:176)
01-13 17:13:12.617: ERROR/AndroidRuntime(7995): at com.android.launcher2.Workspace.startDrag(Workspace.java:996)
01-13 17:13:12.617: ERROR/AndroidRuntime(7995): at com.android.launcher2.Launcher.onLongClick(Launcher.java:1528)
01-13 17:13:12.617: ERROR/AndroidRuntime(7995): at android.view.View.performLongClick(View.java:2383)
01-13 17:13:12.617: ERROR/AndroidRuntime(7995): at com.android.launcher2.LauncherAppWidgetHostView$CheckForLongPress.run(LauncherAppWidgetHostView.java:81)
01-13 17:13:12.617: ERROR/AndroidRuntime(7995): at android.os.Handler.handleCallback(Handler.java:587)
01-13 17:13:12.617: ERROR/AndroidRuntime(7995): at android.os.Handler.dispatchMessage(Handler.java:92)
01-13 17:13:12.617: ERROR/AndroidRuntime(7995): at android.os.Looper.loop(Looper.java:123)
01-13 17:13:12.617: ERROR/AndroidRuntime(7995): at android.app.ActivityThread.main(ActivityThread.java:4363)
01-13 17:13:12.617: ERROR/AndroidRuntime(7995): at java.lang.reflect.Method.invokeNative(Native Method)
01-13 17:13:12.617: ERROR/AndroidRuntime(7995): at java.lang.reflect.Method.invoke(Method.java:521)
01-13 17:13:12.617: ERROR/AndroidRuntime(7995): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
01-13 17:13:12.617: ERROR/AndroidRuntime(7995): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
01-13 17:13:12.617: ERROR/AndroidRuntime(7995): at dalvik.system.NativeStart.main(Native Method)
01-13 17:13:12.657: INFO/Process(2425): Sending signal. PID: 7995 SIG: 3
01-13 17:13:12.657: INFO/dalvikvm(7995): threadid=7: reacting to signal 3
01-13 17:13:12.677: INFO/dalvikvm(7995): Wrote stack trace to '/data/anr/traces.txt'
[Nexus One General] esemar:
This is happening to me as well. On one screen if I long touch, the launcher2 force closes and I can't drag anything into the waste basket. On other screens, long touch will sometimes cause the launcher2 problem and sometimes not.

I have a nexus one with tons of apps on it. I manage the memory quite a bit so there aren't many things usually running at once.

This problem started after I loaded the "Calendar Widget 2" widget into the last screen of my phone. I didn't like it so I uninstalled it without removing the widget from the last screen. After uninstalling, the black boxed "widget not found" (or whatever) box was up. Long touching the box or anywhere on the last screen causes the launcher2 problem and a force close. I can still "drop" apps on the last screen though.

That was happening for two days. I reinstalled Calendar Widget 2, added it to a screen, and the last screen showed the thumbnail. However the launcher2 problem persisted when I long touched the calendar widget 2 thumbnail so I can get rid of it.

This is really annoying.

No matter what I try, I can't get Calendar Widget 2 off the phone and it seems to be the one causing the issues.

I know nothing about programming in the android environment. Are there any xml screen files or something one can manually edit to clean up screens?
[Nexus One General] BrooklynAvi:
This is not exactly the same problem as what I, and others, have been experiencing but I've seen this one too. I, however, was able to easily remove the "widget not found" widget.

There is a sqlite db that you can edit to remove the widget but truthfully, if you are not a very experienced dev I wouldn't even begin to describe the problem by which this can be done. If I had the device in front of me I can probably get the widget off the home screen (I'm good like that, LOL) but I don't have an answer otherwise.

I am more convinced than ever that this is a software issue. Perhaps I/we need to email Google.
[Nexus One General] xocassidychick15ox:
My force closes went away when I removed all apps from the homescreens. I was able to fill the first homescreen back up (2 widgets and the rest apps) with no force closes but anything more than that and they come back.