Search results

It hasn't been a consistent problem for all users. That said, if you experience it, it is a real pain. This appears to be a similar, if not the same, problem that has been happening in cyanogenmod nightlies about 145 to 163ish. I follow the thread on cmnightlies on xda...

Thanks! I will try that! Update: --Deleted current Browser.apk from /system/app --Downloaded the Browser2.apk you gave, thank you much! --I used Root Explorer (because I am at work with no computer with adb) and moved the Browser file into the /system/app file --set permissions as...

Perhaps give me an assist in what you did. I have removed the old browser, pushed the new (old) browser - browser2.apk - into the system/app directory, set permissions to rw-r--r-- , which was how the permissions were set on the current browser and installed it. I get nothing but force...

Well spoken, that is exactly what it is doing. And like I said, I pulled the browser.apk from previous builds that had the old browser, removed the new one and installed this and no go, it FC's. I read a post that said it had to be named Browser2.apk instead of browser, and that also FC's...

Voice search appears to work, but when the browser launches it goes to the start page of the browser and the info does not load into it. I saw a post about loading a previous browser and loaded from 1.6.24 to 1.7.22 with no luck, it will not work and just FC's. Thought it should be reported.

I haven't had the call delay since 1.7.15 on my nexus one. Just curious, was that a clean wipe and install or flashing over a previous build.

I think I replied to this in the other thread, but............ Redownload the rom and language pack. Reboot into recovery. Connect the phone to the computer and mount the sd card in recovery. Copy the new download of the rom to the sd card. Wipe everything three times (e,g, wipe cache...

Is that with a clean install or flashed over a previous build? I would redownload the rom (to rule out a bad download - it happens). Then I would either wipe and start fresh or load a nandroid backup of a previous build, then wipe dalvik and cache and reflash the rom. That generally fixes...

NFC or Near Field Communication, is a method that allows one to use their cell smart phone device to exchange funds or information with other devices that are so equipped. You can exchange data and connections to a reader that is close ( e.g. near field). It is used, or going to be used as a...

Miui seems, in my experience, to run best with an ext3 partition. I have used ext4, and it does mount, but at times seems to be seen as ext2 in use and it can be buggy. Easier to just partition as ext3. Generally, unless you are using gparted in linux, repartitioning the card wipes it. As...

Just a clarification.... There are several ways of moving apps from internal to sd. One is (for lack of a better name) apps2sd - the froyo type that moves apps from internal to the FAT section of the sd card. Problem with this is that it only moves part of the app, and certain parts of it...

nexus 1 lists 2.3.5

I think I would go on over to sdx and see if someone has a solution. That is a samsung dev site http://www.sdx-developers.com/

I have had that happen before, usually a reboot fixes it. If not, an uninstall and reinstall like you did usually fixes it.

I am also experiencing a fairly strong battery drain. I didn't install google+ or anything else new. I installed 1.7.8 clean, full wipe, and reinstall of all the same apps I always use fresh from market.

Since this a2sd+ is, I believe based on DarkTremor's DT-A2SD, you may want to check out that (rather lengthy) thread at XDA. That said, a2sd+ /DT-a2sd symbolically links the sd-ext with the internal /data/app files and so they are on the sd-ext. you can look at what is being done using...

Make sure your apps are not moved manually onto the sd card. You can check in miui file explorer and then sd card. If they are on the sd card (using the froyo style apps2sd) the a2sd+ in the rom will not load the apps into the ext partition you made. Put them back on internal and then either...

A2SD+ requires that you have an ext partition on the sd card. It really should be at least 512mb to 1gb in size. A2SD+ uses the ext partition and symbolically links it to the internal memory. It should be transferring the apps over and using this automatically. You can see the a2sd+...

This is something I have noticed since the gingerbread builds.

My feeling is that I would back up what you want to save from the sd card on the computer. Then reformat the sd card. Repartition the sd card using rom manager or amon_ra recovery (or gparted on the computer). Use ext3 for the partition, between 512mb to 1gb in size. I flash back and forth...