yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 General] callmesmorz:
the galaxy nexus CPU is more than "barely ok". . . .the OMAP4460 is a 1.5 GHZ cpu that is so good, they they can clock it down to 1.2GHZ (where its at) and get the same performance on the phone. the GPU, stock, runs at 200 MHZ. the version in the galaxy nexus is over clocked to 384MHZ. thats almost twice as fast. plus, it has a dual channel memory, which i think other phones dont have. it allows fro better multi tasking so it can get data in and out quickly and simultaneously. also, it has an IVA 3 hardware accelerator that decodes HD video much quicker at much less power. another top new android phone, the RAZR, has an OMAP 4430, at 1.2 GHZ and the same GPU at 304 MHZ. i think its difficut to say this phone is a "let down"

sidenote: the nexus line isnt about bleeding edge hardware, its about bleeding edge software.
[Galaxy Note GT-N7000 General] kunalparwani:
Biggest let-down with the Nexus for me was the lack of sdcard along with just 16 gig of storage. Being on a capped data plan, the cloud isn't a great option for me. Lack of gorilla glass and an inferior SOC to my GSII were just the final nails in the coffin.
[Galaxy Note GT-N7000 General] willstay:
Your reasoning is valid. But from logical point of view, if you were liking Nexus but not happy with its spec, you should get something better of similar size factor. Note on the other hand is a different league device. Don't confuse like - I wanted to buy helicpoter but since I did not like the speed, I am getting Boeing 777.
[Galaxy Note GT-N7000 General] sparkyxda:
Hardware is pretty hard to change. Software however. . . Wait a minute, this is a developer forum . . .
[Galaxy Note GT-N7000 General] kunalparwani:
But i want a device better than my current one(SGSII). And there really isn't anything else on the market right now. And i made a mockup of the phone...so size doesn't seem to be an issue...
[Galaxy Note GT-N7000 General] Gaugerer:
I agree that the vast majority of people here, both owners and those who have objectively read several reviews such as the one from 3G, are impressed with the Note. So it is a pity to sometimes see a disproportionate amount of gripes threads here for they damage the reputation of the Note which may finally result in it's failure because people are persuaded not to buy.
[Galaxy Note GT-N7000 General] koniakki:
I agree. But then again. This phone is not for everyone and I believe most of us agree on this.

Yes, it indeed is too big for a phone, but not that big. Yamaha codec? Yes, could be better. S-Pen? I wish it wasn't there. But to be honest, I had caught my self using my HTC Touch HD stylus sometimes.

Conclusion: Yes, it has it's flaws like many other devices. But are they a deal breaker? Personally: NOT even close..

When it arrives I will use it at it's full glory. Why? Because this is the phone I wanted. Maximum portability(debatable for some) vs maximum performance/screen size. It's a winner in my book. I skipped the SGS2 for this for a reason.
[Galaxy Note GT-N7000 General] Oneiricl:
I'm happy that people are talking openly about their gripes. Everywhere else, it's either apple fanboys trying to shout down the device or android fanboys shutting down negative conversations.

The reason I signed up on this forum and I'm following the discussion here more closely is that that people openly discuss the problems they're facing. As a first time will-be android buyer, it's important to me to know everything I'm getting into. And personally, I'm thrilled that the only problems people have with the Note (other than a few HW problems) are things that are unimportant to me personally, while at the same time, it seems like everything I've ever wanted in a smartphone...
[Galaxy Note GT-N7000 General] keithleyson:
I have already reserved at our local Samsung store here in Singapore. It comes two weeks from the now (that's what they keep telling customers). The main reason I'm getting the Note is because of the 1280x800 res on a 5.3" SAmolled display. The pen features are just the cherry top for me.

Keith

HTC Flyer with LeeDroid v1.0.0
[Galaxy Note GT-N7000 General] android_master:
What you{& others} fail to understand is what's the purpose of Google Nexus Series.

Google never ever launched these phones to compete with any other smartphones{hell N1 never came out of it's native region},Nexus S was launched in limited countries only.

But these smartphones offers you unskinned,pure,greatest & fastest updates.They compete with each other{consider them as Apple iphone}.

Nexus S was a definite improvement over N1{better camera,hardware,screen,NFC},,similarly Galaxy Nexus is a giant leap forward compare to N1 & Nexus S.

Galaxy Nexus is not launched with the intention to compete with S2/Note/Sensation series.....if you want unskinned version,you want stock you go for it.It's here to launch with ICS, introduce it,bring on HD resolution{it will be a norm from now on for high end droids}

If you are looking for best hardware on the market{although ICS with hardware acceleration will run like super smooth on Nexus}...wait for some time,,you can almost bet Samsung Galaxy 3 or HTC next supersmartphones will have better screen/processors/camera than it.

So this comparison is not worth.
[Galaxy Note GT-N7000 General] bbdj69:
It is hard to take your posts objectively when I see your signature.

Also, I was going to get the Nexus exactly for the reason that it was going to be the bleeding edge, and it just about was. It is a fair comparison.
[Galaxy Note GT-N7000 General] paulshields:
I've been umming and arring about a Galaxy Nexus or a Galaxy Note. In the end I plumped for the Note. I currently have a Nexus One, a Galaxy Tab (original 7 inch) and a Galaxy Tab 10.1. I like them all for different reasons, but do find that sometimes I'm using the N1 when I wished it was the Tab 7 inch, and sometimes using the 7 inch when I wished I had the 10.1 close by.

The Note I think will nicely replace the N1 and the Tab 7 in those circumstances. Also the fact that I can sell those two on (with accessories) and pretty much make up the cost of the Note also helped. I'm also lucky in that my company pays for my phone data, so I'm not interested in plans or suchlike.

It'll be sad to part with the Nexus One - the best smartphone I've owned. I love the huge community behind it. I was all set for the Galaxy Nexus, but for me I feel it's a bit limiting. 16GB-only for the UK it seems. No SD slot. The biggest selling point is that it'll be ICS out of the box, but software comes to all who wait...

As for my 7" Tab, recently I've reverted that to Froyo as it's actually better performing than Gingerbread in certain areas - BBC iplayer being the most significant improvement for me. I originally used it as a phone as well, but it was just too big to use natively, and a pain to always have a bluetooth device for hands-free calling.

ICS will get to all current devices very soon, but I'm confident that the Note runs Gingerbread very well from all the reviews I've seen. It seems like the perfect compromise (all devices are compromises) for heavy phone use and casual tablet use.
[HTC Amaze 4G] Trevorhimself:
hey,

is anyone aware of a method to remove SIM lock on an Amaze 4G without use of an Unlock code (basically I can't find any available at this time - phone was only released on the 4th on the Telus Network and I'm with Rogers).

if a method is possible with use of temp root please advise :)

thanks,

Trevor
[HTC Amaze 4G] Trevorhimself:
Thanks that's awesome! Success would make you my hero haha. I'm excited to call this great phone a phone ;)
[HTC Amaze 4G] Massiv99:
I am also hoping this comes through. Wife wanted this phone (telus) but she's on contract with Rogers. Would be nice to use the temproot to do sim unlock!

-massiv.
[HTC Amaze 4G] Binary100100:
Try something like this:

http://www.lightinthebox.com/i-Smar...Nokia-and-Most-Other-Cell-Phones_p120276.html
[HTC Amaze 4G] Trevorhimself:
Found an unlock code at Mobileincanada.com!
[HTC Amaze 4G] Massiv99:
THx chief - will check there.
[Galaxy S II Q&A, Help & Troubleshooting] asirigaya:
When I unlock my phone (by pressing power or home button) first I can see my home screen before the lock screen. Is this normal or is there a way to solve this problem?. My phone is rooted.
[Galaxy S II Q&A, Help & Troubleshooting] dikai_yang:
This should only happen the first time after boot. It shouldn't happen on the stock lockscreen. If you're using widgetlocker or jkay lockscreen, maybe you're using a governor that responds slower waking from sleep?
[Galaxy S II Q&A, Help & Troubleshooting] asirigaya:
No. I haven't installed any lock screen and I'm using stock lock screen. It always like this. Not just after reboot. When I press home button or power button to unlock the phone first I can see home screen (or the screen before I lock the phone) and then suddenly change to lock screen.
[Motorola Droid 3] jarzy00:
Need some help here. Basically im on the tweaked bootstrap( the one where it says bootstrap recovery and reboot recovery when the apk is clicked on) and im currently running the monster rom. Ive been recently interested in installing safestrap but i have no idea how to switch over. Ive been reading alot of different forums and people have been struggling trying to switch and i heard theres data confliction and it can be difficult. Soo im gonna throw some questions at you guys and it might be alot but its good info that i would like to know so... thanks in advance!!

1) Do i have to start from scratch. Meaning wipe data as my first step?

2) is it as simple as deleting the bootstrap and installing safestrap?

3) Can i flash a new rom with safestrap (lets say cm7 for example) over the monster rom even tho monster was installed using the tweaked bootstrap?

4) using safestrap, how does it actually work? Meaning do i still install a new rom the same or similliar way as the tweaked bootstap? ( ex: cwm recovery.. install from sd.. etc.)

5) and the 5th question is. Im sure im missing some important info so.. What am i missing that would be helpful to me?

THANK YOU GUYS
[Motorola Droid 3] jellydroid13:
you can just install safestrap but when you flash a rom now it will be flashed to your pre install partition leaving your original system (in this case with monster rom intact, though hash meant for you to keep the blur original system) intact. if you are leaving monster rom though i recommend just backing up with titanium backup and sbf ing back to stock then doing everything from safetsrap from now on
[Motorola Droid 3] Hashcode:
jellydroid13's answer is right on point.

However, I can answer your questions in more detail:

1. Installing Safestrap won't affect your primary system, as jellydroid13 says. It's meant to add a "2nd- system" where you're protected against bad flashes, etc. So there's no worry about /data for the 1st step.

2. Yes. Remove Koush's Bootstrap and Install Safestrap. Then open the app and use the "Install Recovery" button. The next time you reboot, you'll should see a splashscreen right after the Red "M" Logo. While that's being displayed you can enter Safestrap recovery by hitting the [ menu ] button.

3. No. Currently, there is no way for you to affect your MonsterROM /system from Safestrap. Be it flashing or otherwise. Now you can do a bunch of stuff with the data for your MonsterROM installation, via backup / restore, etc. But that's a bit more advanced.

4. Safestrap is basically a modified version of Clockwork Recovery. It has mostly the same menus for making backups, flashing ROMs, etc. If you're familiar with Koush's Clockwork Recovery, then you'll immediately know where everything is in Safestrap. For reference, Safestrap recovery is currently using CWRecovery 5.0.2.7 sources as it's base.

The biggest difference is that anywhere you see "/system" it's talking about a 2nd-system on your phone. SO, when you flash a ROM, you're flashing it to this 2nd area which you can now choose to boot from.

Added to the normal Clockwork Recovery menus is a Safestrap Menu, where you can set which system you want to boot from. When you "toggle" between the systems, Safestrap will stash your current data/cache files and save them and try to load any previously stashed data/cache for the system you're going to.

If you want your data from a previous ROM (or the Non-safe system) you'll need to advanced restore it from a backup file (data partition only). In many cases, data can cause a hung boot. If it does, then battery pull, go back into Safestrap recovery and wipe data/cache. You'll have to use a titanium backup instead once the OS is loaded.

5. Know that the /system backups you make in Safestrap are NOT compatible with Koush's Bootstrap(or the tweaked version of it). Safestrap expects to be loaded from the /preinstall partition. When you try and restore a Safe System to the main /system.. you will get a hung boot at the Red "M" Logo.

Don't do it... Bad.
[Motorola Droid 3] ryanmcdonald:
Just so I understand.....

Hashcode, can you tell me if the following is true?

The actual phone has only one "real" /data partition.

Each time you toggle between systems (which is done via toggleing safe mode on and off), safestrap tars up the contents of /data and copies the tar file to sd/emmc, then DELETES the contents to free up the only real /data partition. Then optionally restores the /data from the previously deactivated system from a previously created tar file.

Right now my phone is running CM4D3 from an activated safesystem. Can I assume the contents of my original /system partition still contains the stock blur rom, and my original stock /data has been DELETED (after having been tarred up and moved to SD/EMMC by the toggle process)?

Questions:

Is the /restore partition a real actual disk partition or is it a subdirectory somewhere?

If something goes terribly wrong, is there a working SBF method that works no matter what has happened?

Following your directions, I do a "wipe data/factory reset". During this process, safestrap says it's formatting sdcard-ext. This obviously scared the **** out of me. Turns out my external sdcard was NOT formatted. What actually happened?

Now that I have a orig system and cm4d3 system in my tars, do I need to wipe data/cache and format system each time I toggle? (Does the unzipping of the saved system info do a format or wipe first)?

Since I did a backup BEFORE activating safe system, this backup does contain my stock /system and stock /data correct? I was using safestrap 1.04.

When you release a new version of cm4d3, do I need to wipe data before installing if I'm running a previous version of cm4d3?

When I installed safestrap, did you resize any of my physical partitions?

So far, I love SafeStrap and CM4D3. What was bugging me about stock (openvpn and tether) is working great! Thanks for all your hard work. For me, the only thing I see so far are the known audio-volume and camera issues. Also, it seems youtube and cam360 both try to scale and position video into a small box rather than go fullscreen (or be where they should be). MoboPlayer in hardware decode mode gets it wrong too, but in software decode mode, works fine.
[Motorola Droid 3] Hashcode:
Hello ryanmcdonald,

These are very insightful questions. I'm probably going to put them up on my FAQ.

Answers:

- Yes, the phone (and Safestrap) currently manage the 1 /data partition. (It's 2Gig in size, I couldn't find a 2nd area to store Safestrap's data in)

- Yes, it's doing a /data swap between toggles from the original system to 2nd-system.

- Your original system still contains the stock blur ROM. And your original /data has been moved to the .tar in {internal storage}/safestra/orig (and deleted from the /data partition)

- The restore files are stored in a subdirectory on your internal storage: safestrap/orig and safestrap/safe

- YES, we have a full fastboot for 5.6.890 (It's somewhere around here in the forums)

- The message is "formatting sd-ext" but yeah it looks scary when you first see it. The sd-ext area is where apps go when you place them on the SD card.

- You do not need to wipe data/cache between toggles now, as long as you want the same ROM and apps when you go back to that system.

- YES, you did exactly what you should have done: make a full backup prior to entering Safe Mode which means you have a fall back of your entire stock system for Safestrap to restore from should anything unforseen happen.

- You will not need to wipe data for new versions of CM4D3 (unless I say so in the release notes, but I can't think of a reason offhand.)

- No, I didn't resize any partitions. SIDE NOTE: I was considering in the future placing the 2nd-system and a new 2nd-data partition on the external storage area -- which would require resizing the vfat partition to be smaller by about 2GIG. But, I'll talk about that if I move towards that direction. I need to confirm that running from the SD card is a stable option through testing.

And thanks!
[Motorola Droid 3] johnniekombat:
I had the Droid3Bootstrapper installed on my Droid3 with stock ROM. I uninstalled it and installed Safestrap apk.

I am getting the safestrap spalsh screen on boot up BUT when I hit the menu button I get a blank screen...I have to remove the battery to get it to reboot. Then it reboots to Blur with no problems...

I tried doing an factory reset within blur and still getting the same hang up after pushing the menu button on boot up...

Any suggestions on where I go from here?

Thank you!
[Motorola Droid 3] DoubleYouPee:
I had the same problem but hashcode never answered after asking multiple times :(. After 3rd time reinstalling safestrap and reinstall recovery my phone bootlooped on droid 3 screen and had to debrick with .890 SBF.

When I tried safestrap then it worked fine. I think there is a bug when removing the old boostrap.
[Motorola Droid 3] MrJudylicious:
I remember he said he had 3 people who had issues like you are describing. i believe uninstalling his bootstrap and then installing safestrap should do it. i thought part of the safestrap install was to remove the other hijacks. when in doubt, SBF, root with 1 click, safestrap and go go go

edit: i recently moved from tweaked bootstrap to safestrap and it worked find for me and its in his instructions per the thread in dev. DoubleYouPee I see where you actually quoted Hashcode saying that but i cant find where he said he knew of a couple people who had problems but i know he said he was looking into it. that couldve been a prior release too, not sure.
[Motorola Droid 3] Hashcode:
Which version of the Droid3Bootstrap were you running? I had made an original one back in Sept. (before Koush picked up support). And that hijack was slightly different than Koush's. It may be that there's an issue with Safestrap cleaning up the hijack files for that original version.. but I'd like to see what you were running.
[Motorola Droid 3] DoubleYouPee:
Well, in my case i was using your updated version of koush bootstrap. I succesfully used it to create 2 nandroids.

Then uninstalled, installed safestrap 1,04, installed recovery, reboot, touch menu, black screen. Retried a couple of times..on the 3rd time it bootlooped.

It works fine now though after SBF.
[Motorola Droid 3] RandomTaskMan:
Hello Hashcode,

I was wondering if the deodexing rom found on the rootzwiki is compatible with safestrap, I had tried it last night but got nothing but a black lit up screen anf had to battery pull after several minutes
[Motorola Droid 3] Hashcode:
I'm not sure but that ROM might still have the /system/etc/rootfs files in it which causes Safestrap to bomb out during boots.

You can try deleting that folder from the ROM. Then format your /system and re-flashing. Let me know if that fixes it.

---------- Post added at 04:30 PM ---------- Previous post was at 04:25 PM ----------

There may be some case I'm missing for the cleanup of the old bootstrap code, and I'm nearly certain you ended up with 2 bootstraps installed. I'll have to take a look and see if I did anything different in my tweaked version vs. his which is available in the Market. Sorry about that.

I'd also like to apologize for missing your posting on the other thread asking for help. At the time I was checking 4 different forums for Safestrap issues, and working on a new release of CM7 for the D3.

Unfortunately, I totally passed over your posting some how and it got lost in the mix.
[Motorola Droid 3] DoubleYouPee:
Ah I see, well no problem then :D I also think it didn't properly remove the older boostrap. But I'm sure I followed the right steps. Anyway the debrick was very easy with the 5min debrick and it works great now. Used it with maverom.

Goodluck with safestrap and CM7 etc!
[Motorola Droid 3] RandomTaskMan:
Worked like a charm! Thank you sir!
[Motorola Droid 3] johnniekombat:
WORKS like a charm. Thank you for your hard work. Your dedication to the development of these products is greatly appreciated.
[Motorola Droid 3] jimcarter:
Bootloop in safe system of Droid 3 XT862

I have a bootloop problem. (Thanks to Safestrap, it's recoverable :) ) I activate the "safe system". Format /system. Wipe data (and cache, sd-ext, .android-secure). I also tried anally retentive extra wipes; didn't help. I installed CM4D3-nightly-20111116-1445.zip with gapps-gb-20110828-signed.zip; also tried motoblur-5.7.894.zip with the same result. I tried an extra wipe at this point; didn't help. Reboot (also tried power cycling and a battery pull; didn't help). Motorola logo for 8 secs, Safestrap boot menu for 10 secs, gray screen (lamp on but all pixels black) for 22 secs; at this point the boot animation should start, but the screen goes black (lamp off) for 5 secs and the Motorola logo reappears, starting from the beginning. I've removed and re-installed safestrap-1.06, didn't help. Here are some versions, from About Phone in the unsafe (stock) system:

Model Number: DROID3

System Version: 5.5.959.XT862.Verizon.en.US

Baseband Version: N_03.18.16P

Safestrap version: 1.06
​

In another thread Hashcode asked for this info: ls -l /system/bin/log*

lrwxrwxrwx root shell 2011-06-13 00:10 log -> toolbox

-rwxr-xr-x root shell 13952 2011-06-12 23:57 logcat

-rwxr-xr-x root shell 6975 2011-12-12 10:49 logwrapper (By: Hashcode)

-rwxr-xr-x root root 9760 2011-12-09 21:59 logwrapper.bin

cat /proc/cmdline #list breaks inserted for readability

console=/dev/null rw mem=512M@0x80000000 vram=4M omapgpu.vram=0:4M

init=/init ip=off brdrev=P2A omap3_die_id androidboot.bootloader=0x0000

mmcparts=mmcblk1:p7(pds),p15(boot),p16(recovery),p17(cdrom),p18(misc),

p19(cid),p20(kpanic),p21(system),p22(cache),p23(preinstall),

p24(userdata),p25(emstorage)

(busybox) df

Filesystem Size Used Free Blksize

/dev 219M 76K 219M 4096

/mnt/asec 219M 0K 219M 4096

/mnt/obb 219M 0K 219M 4096

/system 320M 312M 8M 1024

/data 1G 472M 1G 4096

/cache 535M 16M 518M 4096

/data/tmp 2M 12K 1M 4096

/pds 3M 1M 2M 1024

/preinstall 464M 181M 283M 1024

/mnt/sdcard-ext 966M 460M 505M 4096

/mnt/sdcard-ext 966M 460M 505M 4096 (listed twice)

/mnt/sdcard 11G 1G 9G 8192

/mnt/secure/asec 11G 1G 9G 8192

/mnt/sdcard/.android_secure: Cross-device link

/mnt/sdcard 11G 1G 9G 8192 (listed twice)

Does anyone have a suggestion what I could try next, or what detail I might have omitted? Normally I would install safestrap-1.07 but I'll wait for responses before trying.
[Motorola Droid 3] eww245:
Looks like you never got the OTA for 5.6.890 install that first then try again.
[Motorola Droid 3] Hashcode:
I second the OTA install. In almost all cases, the ROMs are built from the 5.6.890 files (including kernel modules).