Jump to content

15/May r6.1 - BigBearMDC and Paul's Pulse 2.1 ROM


Recommended Posts

Guest Josh04
Posted

Tbh I didn't know you could do it with just /system, for a long time I've been doing mount -o rw,remount /dev/block/mtdblock1 /system

Guest jonathonf
Posted
My r6 booted fine, i've removed the sd card just for the first boot.
For me r6 (or r5) would not boot no matter what I tried, r4 boots fine though. I might do a nandroid and try creating /system/sd though.
Guest MarcusHenrique
Posted

That's it guys.

"mkdir /system/sd" brought a2sd back :)

Guest jonathonf
Posted
Tbh I didn't know you could do it with just /system, for a long time I've been doing mount -o rw,remount /dev/block/mtdblock1 /system

It's because /system exists in /etc/fstab so it knows where to look (and which device you're talking about). It's the magic of Linux - I'd recommend it! ™

Guest Josh04
Posted

I'm ex-linux. For all the stuff I could make it do, I couldn't make it do the stuff I needed.

Guest eckengucker1
Posted

Found a hint for the vibprob. Driver seems to be in the vibrator.c file at hardware/libhardware/vibrator. But on 1.5 I can not find such a file? I'd a look into the filesystem using Astro-filemanager but where isn't any file called vibrator.

Wayne, maybe it's helpful 4 our linux-cracks :)

BTW: GN8

Guest ogiogi
Posted
That's it guys.

"mkdir /system/sd" brought a2sd back ;)

Yes working now. Clean first boot. Don't need to remove the card :).

Guest Josh04
Posted

Just for reference, the T-Mobile contacts app does *not* do any of the cool contacts stuff possible in 2.1. I just tried :)

Guest MarcusHenrique
Posted
Just for reference, the T-Mobile contacts app does *not* do any of the cool contacts stuff possible in 2.1. I just tried :)

The same as T-mobile gallery, althought you can install the sweet version.

Luckly BoBo will succeed in flashing Vanilla 2.1 tomorrow =)

Guest Dalius
Posted

Paul ,the vibration problem may due to the different boot.img,those who have the China UNICOM version phones have not such problems ,so wound you fix it

Guest devilb
Posted

I updated my phone to R4 before and successfullly. However my phone have been stopped at "Android"'s Screen when I Flashed the R6 APP2SD ver... I had wiped all items and partition already before flash the ROM... Please help!!!

Aslo I try the R6 NO APP2SD VER. and there is no problem...

Guest marcox1987
Posted

root exlorer

open system maps and mount rw

let's creating new folder and add name is sd

and restart

boot-android- tmobile ring round- input sim pin

and tadaaaaa :) working

Guest robertopero
Posted

I use r5. I copied the contact.apk from an other verison. It is works, but the starting time is more than 10 seconds, is somebody experienced the same?

I hope the official 2.1 release date is near :)

Guest escudo
Posted

Alright, been using this R6 without a2sd since yesterday evening.

First boot went good, kept it running for one hour without any trouble/reboots or anything.

Now this morning i found the following:

- Pressing the Call button, normally gave me the dial option, now it goes to call history...wtf?

- Trying to send a text message to a contact, filling in part of a contacts name, it won't find all contacts. Even though i have them all placed in my google account contacts.... Anyone got te same problem? (It does find some people... but not all..)

- Had 4 reboots in a row. One trying to open Market, one trying to open contacts and the others just random.

That's it for now.

Still it's bloody good to see 2.1 on my Pulse.

Guest robertopero
Posted
Alright, been using this R6 without a2sd since yesterday evening.

First boot went good, kept it running for one hour without any trouble/reboots or anything.

Now this morning i found the following:

- 1. Pressing the Call button, normally gave me the dial option, now it goes to call history...wtf?

- 2. Trying to send a text message to a contact, filling in part of a contacts name, it won't find all contacts. Even though i have them all placed in my google account contacts.... Anyone got te same problem? (It does find some people... but not all..)

- 3. Had 4 reboots in a row. One trying to open Market, one trying to open contacts and the others just random.

That's it for now.

Still it's bloody good to see 2.1 on my Pulse.

1. This is the "normal" with the T-Mobile brand ROM. This is one reason why we need Vanilla ROM. :)

2. I tried it, but i saw all of my contacts.

3. No reboots for me. My uptime is 19 hours without restart.

Guest escudo
Posted (edited)
1. This is the "normal" with the T-Mobile brand ROM. This is one reason why we need Vanilla ROM. :)

2. I tried it, but i saw all of my contacts.

3. No reboots for me. My uptime is 19 hours without restart.

1. On my Dutch 1.5 Stock ROM the Dial button would bring me to the dialer ;)

2. Odd,.. Gotta check for the right contacts in my google account again then.

3. I've got it running for 1 hour straight now as well, did nothing with it tho (@ work)

:D

Edited by escudo
Guest Epohax
Posted (edited)

I'm experiencing random reboots as well, without doing anything. I know that this is a beta, and I am not complaining but the phone is currently almost unusable.

As I'm sure that everyone is already doing their best to provide this beta (as a preview) to us, when is the real release expected? I might go back to 1.7 for the moment because I actually need my phone sometimes ;-).

Anyway, great work, as always.

edit: reboot no. 5 in less than an hour. Without any programs running. I even killed EVERYTHING using Advanced Task Killer (only Voice Search and ATK were running).

edit2: Preliminary thought, but the reboots seem to be caused by my choice to "wait" on the errorscreen of the acore application. Last time I pressed Force Close, and no reboot so far. No idea if this info is worth anything.

Edited by Epohax
Guest mr.a
Posted (edited)

OK for anyone who can't flash R6 with APPS2SD:

(this has been tested on Windows XP)

DO A NANDROID BACKUP BEFORE FOLLOWING THIS PROCEDURE

make sure that you have ADB installed and set up on your computer

Boot your phone into recovery mode ( red (end)+menu + power button)

Go to "wipe" and wipe to factory reset, wipe dalvik, and wipe SD:ext

Go back and choose "partition"and partition your sd card as follows:

Swap = 0 , Ext2= 512 (recommended), Fat32 = remaining

Go back and choose USB-MS toggle and copy the update.zip folder to teh sd card

Disable USB-MS toggle and go to flash zip, and choose the update.zip folder.

when the flashing process is done go to command prompt(cmd.exe) in your computer.

type the following commands:

adb remount

when its been successful type:

adb shell mkdir /system/sd

when thats done reboot your your phone phone via th recovery mode by choosing "reboot"

and you are ready to go ( it can take 1-3 minutes to go past the Android logo)

At no point should the SD card be taken out the phone (during this whole process).

The chance that you will brick your phone with this is 0.000001% but i am still not responsible for whatever

happens to your phone. :)

Edited by mr.a
Guest niko1986
Posted

Its a beta and it is annoying having the random reboots and even running zeam i'm having stability issues but hopefully they'll be ironed out. Overall 2.1 ftw.

Also I'm extremely impressed by the camera performance now. Whereas it used to take forever to scan a barcode or autofocus its almost instant now, props to Huawei for sorting it and to BigBear and Paul getting this out.

Guest Neron
Posted
Its a beta and it is annoying having the random reboots and even running zeam i'm having stability issues but hopefully they'll be ironed out. Overall 2.1 ftw.

Also I'm extremely impressed by the camera performance now. Whereas it used to take forever to scan a barcode or autofocus its almost instant now, props to Huawei for sorting it and to BigBear and Paul getting this out.

I have got to agree running Zeam and R6 now and got to say awesome! Thanks BigBear and Paul!

Guest robertopero
Posted
I have got to agree running Zeam and R6 now and got to say awesome! Thanks BigBear and Paul!

Zeam is very buggy for me. Stop many times with force closes... :S And use more memory than the default home! :)

Guest gusthy
Posted

Just a short comment:

The T-Mobile dial is a horrible and very unstable stuff, it causes lots of instability.

Guest niko1986
Posted
Zeam is very buggy for me. Stop many times with force closes... :S And use more memory than the default home! :)

Are you running A2SD? I have never had a good experience with A2SD on any MCR, always increases stability problems in my experience.

Guest marcox1987
Posted

finished a phone call, the phone was off and restarted.

When a call is restarted 4 times

annoying error

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.