yashsingh1/xdaforums huggingface dataset:
[Vibrant General] #Henkate:
Just found this thread, sorry for late reply :p

You can find the memos in Memo.db or Memo.db-journal in /data/data/com.sec.android.app.memo/databases .

I have tried Memo app and is working on my Galaxy J5 5.1.1 Lollipop touchwiz. Gonna try it on cm12 since thats why i have searched for an alternative (cm doesnt have memo app).

EDIT:

I forgot to tell you. You need some program to be able to read .db files (.db = database). Not sure which program, but i guess that you can find it on google.
[Galaxy S II Q&A, Help & Troubleshooting] Lach0:
Hello, I come from a Nokia 5800 and this behavior was common in CFWs, but I can't find anything similar on android yet. :(

What I mean is, android's behavior is something like this:

- 30 seconds go by and the screen dims.

- 5 seconds more and screen turns off.

- 2 seconds more and lockscreen kicks in.

- If you want to use the phone now, you must press power or home button.

In Nokia 5800, it was something like this, and what I'm looking on android:

- 30 seconds go by and screen dims.

- 5 seconds more and screen turns off.

- xx seconds more and lockscreen kicks in. Also (this is the important part!) if you tap the screen at this point while the screen is off, it turns on back again! Kinda like when its dim and you touch it and it lights up again. Same behavior but with screen off!

My question is, Is there some way to replicate this behavior on android?

Thanks. :)
[Nexus One General] lchiu7:
My N1 is having its power button replaced again but HTC (at least it's no charge) and while it's away I have been using a borrowed HTC Sensation.

I am finding I am not missing the trackball much since I really didn't take too much notice of the various colors the ball would flash and for editing the HTC Sensation SenseUI has an Apple like editing function that when you highlight an area with a long press, you are presented with a magnified image of that area that you can easily select the area you want to edit. (As an aside it's so similar to the IOS editor that I am surprised nobody has sued anyone yet over it!).

I find this editing function even better than the function on ICS so it makes me wonder why Google didn't ask HTC if they could borrow that functionality.
[Nexus One General] Jack_R1:
This functionality is present for a long time in Sense builds, since Froyo.

And while having a trackpad on MT4G, I only use it as a second wake-up button, and never use the text navigation functionality. Moreover, I don't miss the glowing trackball colors either. While good for showing off, they're not that useful - a small LED combined with Sense 3 lockscreen does all I need, one trackpad press and I know exactly what I missed.
[Nexus One General] plan3:
I love my trackball! I bought the phone just because of this feature.
[Nexus One General] XSafire:
I feel like I wouldn't miss the trackball much, since I rarely use it. But I would miss the customize-able color notifications. That's a deal breaker for me. Sometimes I'll set my phone aside, like while I'm driving or when I have my hands full, and knowing if the alert I just got is an urgent email or just a facebook notification without having to touch my phone is so useful.
[Nexus One General] blas4me:
I'm about to upgrade to the Evo 3D, and I'm truly going to miss trackball notifications, and the ability to get right to the space I want to edit. My nephew has the Sensation, I rooted it for him, and having no trackball made me hold on to my Nexus a bit longer. Time for change though:-)
[Nexus One General] lchiu7:
Well I thought I would miss the trackball and the ability to position the cursor but having use the (stock) Sensation, its magnifying glass feature works fine.

I have just bought a Galaxy Nexus which I presume will have the same editing features as my Xoom with ICS which I find okay but not great. I guess I will see how well I will cope with it.
[Nexus One General] genecor:
Nexus One user and I would think I would learn to live without the trackball, the colour notifications is nice and all, but not a game changer.

Granted on the Nexus One the trackball has been quite a good thing esp when the infamous inconsistency of the touchscreen starts manifesting.
[Asus  Eee Pad Transformer Prime] banvetor:
Hi all,

I just tried to install Qype on my TP, but the market says that it isn't compatible with my device!!!

Anyone else also seeing this? Is it an error or is it really incompatible? Why?

Thanks!
[Samsung Epic 4G Touch] kobridge:
It appears that Android market allows downloading apps without checking phone's lcd density any more.

Until yesterday, I couldn't download lots of Android apps because market did not allow me to download because of compatibility issue. To download, I had to change the density to default 240 and delete cache/data and reboot.

Starting from this morning, I can download any apps with density 200.

This means that Android market is not checking the device's resolution any more or they put the Epic4gt to their database with many other allowable densities?

Does anybody else notice that?

I hope this also work for you.

[Update] Please read if you want to know how to

OK. I tested it out a lot more after the above post.

My finding is, there was nothing changed from Android market. Possibly, each app could be changed for its supporting devices and resolutions. But, it's not my case here.

Definitely, Android market has some databases handling the devices and resolutions per each applications. So, first thing is, you need to find out the most commonly accepted resolutions for your device. After that,

1. Set or change your device resolution (density) from build.prop file in \system folder (Don't touch anything else except the ro.sf.lcd_density value). You can use many tools to edit this file.

example: In here 240 is the most commonly accepted LCD density for D710 from Android market

ro.sf.lcd_density=240

2. If Market app is open, then close it and be sure it's not running thru task manager. Go to the Application Manager and delete the cache and data.

3. Reboot and check if the app is downloadable.

4. Go back to build.prop file and change the resolution that you want to use.

example:

ro.sf.lcd_density=190

5. save the file and reboot the phone. Most important thing in here is, DON'T wipe the cache or data. Based on my test, market app uses the first successful configuration data instead of reloading it every time. So, if you wipe the data or cache by some reason, you need to this steps again.

6. Try the market download with the solution that you want to keep.

Bingo!

This steps are based on my test and it worked well on my system -ICS FB27. I don't know how it would work on different build or ROM but I think it would be quite common over most ROMs and build. Do it with your own RISK! :D
[Samsung Epic 4G Touch] phatmanxxl:
That.sucks I just bought the density modder pro app a few weeks ago.
[Samsung Epic 4G Touch] blackroseMD1:
It's quite a bit better for me, but I still get a few "device not compatible" messages for apps that I know are compatible, like quickpic, when running at 190.
[Samsung Epic 4G Touch] kobridge:
I just tested out quickpic with 190 and 200. 190 does not work but 200 works. I know that 200 was not working until yesterday. This means that A.droid market only added some commonly used densities for D710 or for all devices?
[Samsung Epic 4G Touch] JohnCorleone:
Correct me if I am wrong here...don't you have to be either 160, 200, or stock 240 or you will run into issues?
[Samsung Epic 4G Touch] phatmanxxl:
Native resolutions are/were 140, 160, 240.
[Samsung Epic 4G Touch] blackroseMD1:
I'd love to be able to run at 160, but it causes com.android.phone to force close.
[Samsung Epic 4G Touch] phatmanxxl:
Say wah? I run 160 all the time, but 200 is the sweet spot for me.
[Samsung Epic 4G Touch] JohnCorleone:
I think it depends on other variables. I just switched my Nexus to 160 to see if the dialer would be offset and apps would download and it works fine. It has same stock 240...On a stock setup dialer is offset at 160 so theme makes a difference too
[Samsung Epic 4G Touch] iSaint:
What is this resumolution you gents speak of :confused:
[Samsung Epic 4G Touch] JohnCorleone:
Inside ROM Toolbox...
[Samsung Epic 4G Touch] blackroseMD1:
Well, on other roms I can hit 160 just fine, but on CM9 it causes phone to FC.
[Samsung Epic 4G Touch] iSaint:
Haha I knew :p

Thanks for actually replying though :D
[Samsung Epic 4G Touch] kobridge:
Could you try it again with the method that I posted again in top thread?
[Samsung Epic 4G Touch] AVAH0LIC:
When you guys are changing your densitys'. What launcher are you using? TW sure does look stupid rockin 160 lol

Epic 4G Touch perfected by Calk!
[Samsung Epic 4G Touch] kobridge:
For me, I use Go Launcher EX. It still has lots of widgets and looks not bad on ICS and GB. For ICS only, some likes Nova launcher because it's better fit for ICS.

I do not use the Nova yet because it does not have widgets as much as Go Launcher.
[Samsung Epic 4G Touch] phatmanxxl:
ADW EX here, most of the launchers look fine at the lower DPI, use a third party dialer, calendar, and calculator app as well as the TW ones will also be borked.
[Samsung Epic 4G Touch] tenazrael:
Worked brilliantly!

Currently running Blazer ROM 4.1 w/ EL29 (Gingerbread).

1) Checked that the LCD density was set to 240 via build prop.

2) Opened task manager and check to make sure the Market app was not open.

3) Went to manage the Market App and took it a step further by uninstalling update, deleting cache and delete data.

4) Started the market app, and confirmed I could see the Holo Launcher as a downloadable item.

5) Went into build.prop (using ES File Explorer) and set lcd density to 200. Saved file.

6) Rebooted phone, and went into Market and sure enough, I could see holo launcher.

Awesome job OP!
[Samsung Epic 4G Touch] feyrune:
I use the clear cache/data and reboot method, but my market seems to reset.or something because the Movies tab disappears and apps say not compatible until i rinse and repeat.

I haven't seen a common factor between when it happens. It just seems random.

Has anyone else seen this?
[Samsung Epic 4G Touch] tenazrael:
Yes, I have. I'm experiencing this now. It seemed to work once and then a reboot of my phone seemed to undo it. Very very annoying.
[Epic 4G Q&A, Help & Troubleshooting] justlovejoy:
I gave my OG Epic to my StepDad, It's On CM9 alpha 4, He loves It but I sent it to him in the mail and now he cannot activate the phone through sprint[ he has to enter the **##XXXX##** thingy] whatever right. My StepDad just learned to text a month ago, w/e right, I want to remote control his laptop and just odin the sucker back to stock and I'll reupdate it to cm9 whatevers latest when i see him. Ignition is email based trial, so i can just do it that way but then the trial will run out and i may need to do the same thing or different for them shortly after the trial runs out. leading to my QUESTION:

1st. what else can i use to do the job?

2nd. is there a way that i can remotely flash cm9 after i get it odin'd to stock with root?

Thanks! I appreciate posts like idk over a falsehood, if you really dont know, it's okay, You're Awesome!
[Epic 4G Q&A, Help & Troubleshooting] KennyG123:
Teamviewer I believe.
[Epic 4G Q&A, Help & Troubleshooting] justlovejoy:
lol thats what i had in a tab on my browser!
[Epic 4G Q&A, Help & Troubleshooting] Djinn23:
I think I used a join.me thing lately that was a freebe. I was on,win7 x64

sent from a phone using an app
[Epic 4G Q&A, Help & Troubleshooting] LORDFIRE00:
U want to use teamviewer. Its free and u can install It on ur pc and phone.
[Epic 4G Q&A, Help & Troubleshooting] AOD_Corwin:
Logmein.com is free
[Epic 4G Q&A, Help & Troubleshooting] Shinydude100:
I also second / third teamviewer.
[Epic 4G Q&A, Help & Troubleshooting] justlovejoy:
Shinydude, yo what's up? haven't heard from you in a while. what's your latest work? Any ways add me to ur gtalk bro! Thanks every one it worked perfect and I loved the process. Mission: get DAD epic OG, has been successful. Thanks team.

Via Etouch 4g Cm9 & fueled by the NYGiants 2012 Champions!!!!!
[Samsung Galaxy Nexus] alphahere:
Just got a Galaxy Nexus GSM version. I have very noticeable static with voice phone calls using a headset connected to the headphone jack. Has anyone else noticed this?

I can hear faint static with the bluetooth, speaker phone and standard phone speaker.

My nexus s sounds perfect with headset with calls.

Is this normal for galaxy nexus? Anyway to reduce and correct the problem? I did search but could not find anything expect folks complaining static when playing music. I have faint static with playing music but with calls it is very loud.

Thanks
[Samsung Galaxy Nexus] dulllou:
Yes, suffering from the same problem here on both stock and 4.0.2. Not only phone calls, also during video / music playback. Static gone when screen off.
[Samsung Galaxy Nexus] alphahere:
Tried with screen on and screen off - absolutely no change in static level with headset when making calls. Static is very low with music or bluetooth, I have to concentrate to hear it. If anyone else out there with a headset, could you try using a headset and check for static when making calls. Thanks.

I guess I will send this unit back before my return windows closes. Should I get another unit?

Coming from a samsung nexus s, this static is not acceptable for me. With the nexus s and voodoo sound control the audio quality is amazing. I was hoping for better with galaxy nexus.

Thanks
[General Questions and Answers] himynameisgeoff:
A very straight forward question!

When I boot my Desire I get the splash, screen after that the screen begins to flash blue and white. I think it's something to do with the partitions but I can't be sure.

Anyway, in order to flash anything I need root access. Please help!

Thanks in advance

~G~

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

Solution: I was on stock Froyo so all I needed to do was flash the Gingerbread update.zip from HTCDev. That reset the partition table which was causing the problem in the first place.

Thanks for your suggestions guys!

~G~
[General Questions and Answers] matts95:
It should be possible using the old "goldcard" method, but i havent tested this.

First download "rooting tools":

if you have a bootloader version 0.75.xxxx or below AND a current ROM of 1.15.xxx.x or below – Desire Rooting Tools

OR

if you have a bootloader version 0.80.xxxx or below AND a current ROM of 1.21.xxx.x or below – Desire Rooting Tools

Next, begin

Step 1 - set up ADB & Fastboot

Step 2 - make a gold card

Note: you will need to format card as Fat32 on your computer as you cannot boot your phone, and if you can access ADB from recovery use

adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid

there. Your card will need to be in your phone for this.

Edit:

you may be able to get adb while in your boot loop if you cant get it from fastboot, bootloader or recovery

Step 3 - root

Step 4 - install ROM

BTW for the HTC Desire I would recomend choosing from the following ROMs:

4.0 Ice Cream Sandwich (experimental):

Sandvold's ROM (currently Evervolv prieview based)

CM9 for Desire (unofficial prieview, released by dk_zero-cool)

2.3 Gingerbread (stable):

Cyanogenmod 7.1

Oxygen
[General Questions and Answers] Hikari:
Dont think so

I dont think that you need root access for flashing using fastboot :)

EDIT: sorry I just saw the date :D
[General Questions and Answers] thomasvdalen90:
dont know if there are custom os?
[General Questions and Answers] himynameisgeoff:
I have hboot 1.02. And adb doesn't see the phone. Only fastboot usb and it's commands. I've also tried running the RUU and flashing it's update via fastboot usb. It flashes fine just still got the messed up screen
[General Questions and Answers] matts95:
Do you have an s-off boot? If so you should be able to re flash the partitions/hboot without faffing about rooting.

Otherwize you can extract imgs partitions to the computer using Fastboot, you may be able to get CID from these if you need it.
[General Questions and Answers] moose.splash1:
If you get the gingerbread update for the desire from the official HTC site (no root required) and install that then it automatically has fast boot installed

Hope this helped :)
[General Questions and Answers] matts95:
Does the stock froyo RUU (official HTC stable rom) have hboot/fastboot flash included?

Download links? Nice suggestions :)
[General Questions and Answers] moose.splash1:
I'm not sure but I don't think so... its normally only gingerbread onwards and you need sense obviously

Hope this helped :)
[General Questions and Answers] himynameisgeoff:
I have s-on which I think is the problem. How would I go about extracting to my computer?
[General Questions and Answers] matts95:
It seams I was mistaken in thinking you can back up from fastboot :( - it is only for flashing to partitions

You only real option is to find an RUU from HTC (singed correctly for your Desire) which contains a fastboot, a hboot and a rom, that way you will have a working device, and can root in the normal way/downgrade to o more favourable RUU version after.

For desire the updates were 2.2 and 2.3 (although 2.3 was considered unstable due to its size and therefore space consumption)

Try these, if one fixes your main problems, you can later work on others :) (assuming GSM not CDMA, see thread)

Gingerbread RUU

Froyo RUU (HTC WWE)

GSM HTC OTA:

WWE - HTC

UK - Vodaphone

UK - T-MOBILE (v1.15)

UK - T-MOBILE (v1.21)

DE - O2

GSM:

WWE:

RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4. 05.00.11_release_122704.exe

RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4. 06.00.02_2_release_126984_signed.exe

RUU_Bravo_Fastweb_IT_1.15.1600.5_Radio_32.30.00.28 U_4.05.00.11_rel_121996.exe

RUU_Bravo_H3G_UK_1.20.771.3_Radio_32.36.00.28U_4.0 6.00.02_2_release_124822.exe

RUU_Bravo_H3G_UK_1.22.771.1_Radio_32.36.00.28U_4.0 6.00.02_2_release_127568_signed.exe

RUU_Bravo_HTC_Europe_1.15.405.1_Radio_32.30.00.28U _4.05.00.11_release_121684.exe

RUU_Bravo_HTC_Europe_1.15.405.3_Radio_32.30.00.28U _4.05.00.11_release_121865.exe

RUU_Bravo_O2_UK_1.20.207.1_Radio_32.36.00.28U_4.06 .00.02_2_release_124865.exe

RUU_Bravo_SKT_KR_1.19.911.4_R_Radio_32.36.00.28U_4 .06.00.02_2_release_124410.exe

RUU_Bravo_SoftBank_JP_1.18.762.2_Radio_32.34.00.28 U_4.05.00.30_2_rel_123706.exe

RUU_Bravo_SoftBank_JP_1.18.762.7_Radio_32.34.00.28 U_4.05.00.30_2_release_128910_signed.exe

RUU_Bravo_TMO_UK_1.15.110.11_Radio_32.30.00.28U_4. 05.00.11_release_122755.exe

RUU_Bravo_TMO_UK_1.21.110.4_Radio_32.36.00.28U_4.0 6.00.02_2_release_127570_signed.exe

RUU_Bravo_Telstra_WWE_1.15.841.14_R4_Radio_32.30.0 0.28U_4.05.00.11_123851.exe

RUU_Bravo_Vodafone_FR_1.21.163.2_Radio_32.37.00.32 U_4.06.00.16_2_release_126985_signed.exe

RUU_Bravo_Vodafone_UK_1.19.161.5_Radio_32.36.00.28 U_4.06.00.02_2_release_126338_signed.exe

RUU_Bravo_hTC_Asia_India_1.21.720.4_Radio_32.36.00 .28U_4.06.00.02_2_release_127705_signed.exe

RUU_Bravo_hTC_Asia_WWE_1.19.707.7_Radio_32.36.00.2 8U_4.06.00.02_2_release_126179_signed.exe

RUU_Bravo_Virgin_Mobile_1.23.351.1_Radio_32.36.00. 28U_4.06.00.02_2_release_128941_signed.exe
[General Questions and Answers] lingeringhope:
whenever i turn my phone, i get an error that says the com.android.sdksetup application failed or something like that and when forced to close, it would just show up again.

as a result, i'm stuck in that infinite loop, i can only access recovery (3e) and the bootloader. I've tried a factory reset but that only erases user data. Since it runs on 3e recovery, I get signature verification errors when trying to flash to a different rom. I was wondering if there's any way I can access the system files through any of these two modes? the phone is the Gooapple 3g
[General Questions and Answers] matts95:
I dont know about your specific phone, but i managed to get a bit of info from a google search :)

I believe what yo want to be doing is flashing a recovery that allows you ADB write access to /system (if your recovery doesnt already - try 'adb remount' or 'adb shell mount -o remount,rw /system')

You may need the PdaNetA302.exe file from http://www.alcatel-mobilephones.com/...iew/full/25287 to use USB ADB

This thread may be useful: http://xdaforums.com/showthread.php?t=1252195

the clockworkmod recovery section may be useful as cwm allows read/write access to the /system partition via ADB:

INSTALL CLOCKWORK RECOVERY (orange lantern recovery)

Flashing custom recovery image:

{Non ADB method}

1) Download flash_image and place it on the root of your SD card: http://db.tt/flHRxiG

2) Download recovery.img to the root of your SD card: http://db.tt/uy56zhj

3) Open Terminal Emulator and issue these commands:

Code:

$ su

# cp /sdcard/flash_image /system/bin

# chmod 747 /system/bin/flash_image

# flash_image recovery /sdcard/recovery.img

4) If you see a bunch of successful on your screen then it has flashed properly.

{ADB method}

1) Open up command prompt and issue these commands:

Code:

C:\Users\Your_Name> cd ..

C:\Users> cd ..

2) Navigate to your installed Android SDK (Mine is under the Program Files (x86) folder):

Code:

C:\> cd Program Files (x86)

C:\Program Files (x86)> cd Android/android-sdk/platform-tools

3) Connect your device to your computer and make sure you have USB Debugging enabled on your phone.

4) Issue this command to verify that your computer recognizes your phone:

Code:

C:\Program Files (x86)\Android\android-sdk\platform-tools> adb devices

5) If you see your phones serial then it is connected.

6) Download flash_image and place it in the platform-tools folder: http://db.tt/flHRxiG

7) Download the recovery.img and place it on the root of your SD card: http://db.tt/uy56zhj

8) Issue these commands in command prompt:

Code:

C:\Program Files (x86)\Android\android-sdk\platform-tools> adb push flash_image /system/bin

C:\Program Files (x86)\Android\android-sdk\platform-tools> adb shell chmod 747 /system/bin/flash_image

C:\Program Files (x86)\Android\android-sdk\platform-tools> adb shell

# flash_image recovery /sdcard/recovery.img

9) If you see a bunch of successful on your screen then it has flashed properly.

boot into recovery, hold home whilst powering on, after 5 long seconds, let go of home and then push home again, you will need to put the volume/menu-back toggle to "volume" mode and according to deepakpitrola333, you need to cycle the list 3 times using volume to allow selection.

Video by mayiandjay;

http://www.youtube.com/watch?v=B_dX9Ruoljo
[Galaxy S II Q&A, Help & Troubleshooting] juDGEY2k10:
Hey i got the samsung galaxy s2 with SUPER AMOLED Plus but im looking at HTC One X with HD 720p...

Wot screen would be better?

Nub question i know but i just want to be sure.

Thanks
[Galaxy S II Q&A, Help & Troubleshooting] peachpuff:
You're comparing a phone that came out last year to a one that was just announced, of course the htc one x has the better screen due to its resolution but its blacks are nowhere near as good as samoled screens. I'd at least wait for the galaxy s3 and compare those side by side.
[Galaxy S II Q&A, Help & Troubleshooting] TH3-JUL10:
HTC One X with HD 720p screen will be better... is HD..... the screen of SGSII is not HD...in the last update of the APP YouTube, can play videos in HD (in compatible phones), but in the SGSII no :(
[Galaxy S II Q&A, Help & Troubleshooting] IINexusII:
because the screen resolution isnt HD on the S2 so whats the point in playing HD videos lol
[Galaxy S II Q&A, Help & Troubleshooting] Kailkti:
I dun get it...

Whilst I would love a 720p screen, I don't want just any 720p screen, it's gotta be samoled or ips+.

$1 gets you a reply
[Galaxy S II Q&A, Help & Troubleshooting] King Shady:
The One X has a 720p (non pentile) and uses LCD 2 technology. I've heard it looks amazing
[Galaxy S II Q&A, Help & Troubleshooting] xsaintzx:
720p screen would be better, some people don't like the saturated colors of AMOLED screen.
[Galaxy S II Q&A, Help & Troubleshooting] Erlanderterv:
I doubt that on a 4 inch screen you can tell whether its HD or not!
[Galaxy S II Q&A, Help & Troubleshooting] hedgepigdaniel:
Why don't you just go to a shop and look at them, with your eyes? You can't be sure which you will prefer by asking people here.