yashsingh1/xdaforums huggingface dataset:
[EVO 4G General] reekotubbs:
One thing that I have noticed is that PRI 1.34 does not have a checksum value.

Just checked my tp2 and it has PRI 1.42_003 with a checksum of 9EF8EFD3.

Those with stock evo's what is your checksum for PRI 1.40?
[EVO 4G General] sgt. slaughter:
Maybe we or someone can get cracking back on the PRI issue? Maybe a bounty thread is in need to get it done?
[EVO 4G General] snandlal:
Someone Doing the NAND unlock process coming from stock with 1.40..PRI should modify the eng-PC36IMG to NOT include the rcdata.img file (so it won't write over the Newer PRI) and see what results you get....Doing the whole unlock NAND process without flashing the older 1.34 PRI...maybe?
[EVO 4G General] DeathBySnuggles:
I'm posting this here at the request of sgt. slaughter. This was being discussed in the Ava 2.2 ROM thread. I am currently running Ava's V3rA froyo ROM with netarchy's latest kernel. Someone asked about PRI and PRL versions. I posted that I'm running 60669 PRL and 1.40_003 PRI. It was brought to my attention that it's impossible to have 1.40_003 on a fully rooted phone. Well here I am. I promise you the screenshot is not faked, and I had no idea this was an anomaly when I first posted. So here's the back story of my device.

Out of the box I did the 2 OTA updates. I've been an iPhone user for the previous 3 generations. This is my first Android phone so I'm learning as I go, reading threads and experimenting on my device. I did the unrevoked 3 method so I could use Wireless Tether. I then decided I wanted to flash a ROM. I did the simpleroot process. Admittedly, during the simpleroot process, my experience was not verbatim as per the instructions. The prompts that I was expecting to get, I did not. However, when all was said and done, I was able to flash Fresh 1.0.1. I then got into flashing different themes. When the Froyo releases came out, I used ROM manager and flashed Ava's V3. Shortly there after I flash his rev A on top of it. I flashed ketarchy's 3.7.6c kernel, and now the newest. I am running Manup's theme. The phone works great, everything works. I'm taking 8mp pictures, 4G works. If anyone would like me to look into anything on my phone to help explain why I'm running this PRI, let me know.
[EVO 4G General] sgt. slaughter:
Also they stated the following below in the other thread if it makes a difference.
[EVO 4G General] lwarranty:
What are the thoughts on this - retaining 1.4 pri?

Looks like a glitch in the rooting process and/or mix of images, regardless - the bootloader doesn't indicate it's found the PC36IMG.zip???

Interesting it's retained the PRI and still flashes with no apparent issues....
[EVO 4G General] sgt. slaughter:
So since the post http://xdaforums.com/showthread.php?t=747319 has the RUU with the nv.img file seperated in it does it mean that we can now fix the PRI issue?
[EVO 4G General] lwarranty:
Good question!

Another interesting post...

http://xdaforums.com/showpost.php?p=6880100&postcount=25

I extracted that link and all dates are 7/26-31ish/2010 with the exception of the nv.img it was 4/1/2010...

Just wondering how the combination of flashing the fellow wound up with 1.4...
[EVO 4G General] DeathBySnuggles:
RESULTS REPLICATED!!

I just followed the same process on my wife's Evo and she is now running Ava's V3rA themed with PRI 1.40_003.

Exact process:

1. phone was stock with the 2 previous OTA's installed.

2. Rooted with Unrevoked 3 (not 3.1)

3. Installed wireless tether, titanium, rom manager. Superuser = super good

4. Ran simpleroot .2 ALL steps

5. After each step I checked and the PRI was still 1.40_003 each time

6. Ran ROM manager and flashed Ava's V3

7. Ran ROM manager and flashed V3rA

8. Ran ROM manager and flashed themes and radio updates.
[EVO 4G General] joeykrim:
first thing which pops into my mind, the userdebug RUU was loaded and not the eng RUU. i actually ran that setup for a long while.

when you reboot bootloader, or pwr + vol down, can you type up all the information, verbatim for the first 2-3 lines of that white screen? that will help us determine which hboot (subsequently the type of RUU) has been loaded.
[EVO 4G General] l33tlinuxh4x0r:
Can you dump the PRI on the rooted 1.40_003 phone?? maybe a nandroid backup
[EVO 4G General] Geniusdog254:
A nandroid won't return anything. The only thing I can think of would be using the "fastboot oem saveprt2sd" command to save the RCDATA & NV partitions to your sd as raw data, then flashing them thru fastboot to another phone.

BUT: the problem with that is, without the full NAND unlock, you can't access the whole arsenal of fastboot oem commands, which you have to have to use "saveprt2sd" And to get the NAND unlock to use that command, you roll back your PRI.

Catch 22...
[EVO 4G General] sgt. slaughter:
yes but If it is slightly possible DeathBySnuggles tripped over having full root and still 1.4pri then we could get the info needed.
[EVO 4G General] l33tlinuxh4x0r:
I have found out how to have FULL root NAND access without downgrading the PRI what you need to do is take the PC36IMG.zip and delete rcdata.img from it before flashing it. This will then bypass the PRI update and still unlock the NAND!!! Hopefully someone can dump the PRI now :)
[EVO 4G General] davidlightle:
I had just tried to get in touch with Toast over this, in IRC and PM here, about removing the rcdata.img from the eng PC36IMG in Step 3 of Root Part 2. So interestingly we're coming to the same conclusion from different angles.

So yes, the thing now is to take a stock phone that is rootable with unrevoked 3.1, gain root, gain eng HBOOT with this process without downgrading PRI, fastboot to pull off the rcdata partition, and hopefully we can flash it on others.
[EVO 4G General] chumba8:
wow i hope this works
[EVO 4G General] sgt. slaughter:
Going to require someone willing to possibly brick there fully stock phone that has never been rooted in order to test it out...
[EVO 4G General] Geniusdog254:
Thats true. It depends if it'll let us dump those partitions anyway. Some of them show as a size of 0 & won't let you flash or dump them.

One thing that could easily fix it if we get the new RCDATA & NV (we have the NV, but no RCDATA, correct me if I'm wrong) is to create a PC3600.zip image with just those images. You'd have to switch the the SuperCID to flash it, since otherwise it'll check a signature though
[EVO 4G General] davejet:
I am ready to try

I have non rooted stock phone

Firmware 2.1 update 1

build 1.47

PRI 1.40_003

I have cdma workshop

I have a windows 7 64bit

I am willing to do this if someone guides me.
[EVO 4G General] l33tlinuxh4x0r:
GREAT!!! I will help you do you have IRC?

First get http://dl.google.com/android/android-sdk_r06-windows.zip extract it somewhere like your desktop. Then open command line and cd to Desktop/android-sdk-*/tools

On your phone enable USB debugging. Then on your computer in command line type this:

adb shell rm /data/local/rights/mid.txt

adb shell ln -s /dev/mtd/mtd1 /data/local/rights/mid.txt

adb reboot

That should get you root. Next you need to do the nand unlock so we can dump the PRI. let me know when you get this far.
[EVO 4G General] davejet:
I just downloaded and installed mirc
[EVO 4G General] l33tlinuxh4x0r:
connect to irc.freenode.net and join the channel #HTC-EVO irc://irc.freenode.net/#HTC-EVO <-- that link should connect you.
[EVO 4G General] ilostchild:
failaure to unlock NAND flash

hello

i have htc desire running 2.2 with this unrevoked not work for this version yet? if so can you email me at lilbush81@gmail.com with fixes thanks for your time
[EVO 4G General] :
This is the EVO 4G forum. Go ask in your forum. I'm sure you'll find something.
[Touch Pro, Fuze General] heyi'm here:
hey guys, i've been using my Touch Pro for 1 year lately and i'm quite happy about it :), and now after only 12 months that so many things happen (new phones come out, new OS, new Software that only fits newer phones,...) just make me wondering that, should i replace my Touch Pro and upgrade to a newer phone (such as Touch Pro 2, because you know i love qwerty keyboard phone :)) or should i just keep my old lovely also my best buddy and wait for a couple few year to see how things work out :), please guys, if you have any idea, comment or useful advise, just help me out so i could make the right decision :D
[Touch Pro, Fuze General] mputtr:
personally, I think i would say no....

the touch pro 2 is barely different from the tp1... If I want to upgrade, I want to have (at the minimum) a processor upgrade not the same freaking processor..-_-
[Touch Pro, Fuze General] linktron05:
I'd have to agree, plus the touch pro 2 does not even have a LED light on the back. No one likes to be left in the dark
[Touch Pro, Fuze General] g1user101:
i have to recomend hd2? touch2, its not touch pro 2. its newer version of touch. i think thats it
[Touch Pro, Fuze General] Cassetti:
I heard that AT&T insurance is offering a Touch Pro 2 as a replacement to my phone. Called them and did an insurance claim on my Fuze (fault touch screen - had a minor dead zone that bothered me only a little bit over the past year).

They initially tried to give me a Pure but i wanted a keyboard, they are sending me a replacement refurb touch pro 2 instead.

I will miss the fuze's led light (used it often when installing sound systems). But want the larger screen.

There is really no change between the touch pro and the touch pro 2 aside from screen size. You get no better camera, no faster processor, and no additional buttons (from what i understand).

Id say if you must have a larger screen - and you can get a touch pro 2 for $50, it might be worth it. (key word is might)
[Touch Pro, Fuze General] Captain_Throwback:
Having just moved on from the Fuze (Raphael/Touch Pro) to the Tilt 2 (Rhodium/Touch Pro 2), I would say that it's not worth upgrading unless your TP isn't working right and you can get a replacement for $50. I also got mine device as an insurance replacement, and I must say, the screen is

beautiful

. Very large, and clear. And from a chef's perspective, it's really nice not to have to wait for packages to be ported - to have a device that's still (relatively) supported, and for which new ROMs are still coming out (infrequently, but still).

But I do miss the flashlight on my old device. I also miss the ability to get TMC updates for OnCourse Navigator using the HyperGPS driver. And I dislike that AVRCP doesn't work right, because the Bluetooth stack is completely different (I can't use it with anything other than WMP/Sense, like the old days on the Raph). I also miss the D-Pad (I know, it was a poorly designed D-pad, but it was SOMETHING). I also prefer the Raph Smart Touch wheel over the Zoom bar that the Rhodium has (whose idea was that?).

Overall, I feel that the Raphael actually has more/better features than the Rhodium - the only thing the Rhodium has over the Raphael, IMO, is the screen (resolution, tilt - if you think that's a feature). But that is just one man's opinion . . . :rolleyes:
[Touch Pro, Fuze General] braini86:
yes right, tp2 is just a screen upgrade...

i want a desire with qwertz keyboard! :)

who else? ^^

please htc make a desire pro or something like that :D would be great.
[Touch Pro, Fuze General] Farmer Ted:
I'd suggest trying out the new Resco 6.00 beta keyboard and see if you like it. If you do, then go for the HD2 (keeping in mind that the keyboard will be bigger and better on the larger screen). The rhodium never seemed all that great to me, but I guess since all the new devices are wvga, like Cptn said, there are more packages available for it nowadays.

I'm using my fuze til it dies.
[Touch Pro, Fuze General] neptune:
on point... got a free tp2 from my dad but gave it back cuz the size of the screen is not worth the features you lose.
[Upgrading, Modifying and Unlocking] omar_ramon:
My T5358+ was working fine except for the digitizer. So I order a replacement from China (I'm on Peru, at the other side) but the digitizer was not exactly of the same size.

Device works well but the original digitizer was slightly larger to support the zoom bar (swipe left and right actions). The new one doesn't cover this area.

So when I try to use Windows everything works fine, except I can not touch bottom bar commands because the zoom bar area is apparently "over" the bottom bar. If I use the image viewer I can make zoom dragging over the bottom bar.

If I rotate the screen, the bottom bar works fine because it's moved to another place not below the zoom bar.

So I want to disable the zoom bar to let windows use the entire touch area. I 've spent some hours looking at the registry for some value, but no luck for me.

Thanks for your help.

Omar :)

Lima - Peru.
[Upgrading, Modifying and Unlocking] Spiaatie:
I don't think that you can change anything in here.

You should get proper touchscreen.

:)
[Android Q&A, Help & Troubleshooting] joernsn:
As i understand it, android.permission.DEVICE_POWER is a protected permission and only allowed for apps signed as system apps.

There's probably some way to gain this permission on my rooted n1, but I have no idea how to do it. When installing android says:

W/PackageManager( 4819): Not granting permission android.permission.DEVICE_POWER to package casablanca.locknow (protectionLevel=2 flags=0x7e45)

(and yes, I ask for it in manifest)

Tried installing as a system app

adb remount
adb push locknow.apk /system/app

but i get the same logcat message (is this the correct way of installing a system app?)

I am trying to access the PowerManager's goToSleep() method:

PowerManager pm = (PowerManager) getSystemService(Context.POWER_SERVICE);
pm.goToSleep(0);

My questions are:

How can I install/sign the apk so that it is granted android.permission.DEVICE_POWER?

Can I do a lower level call using su to put the device to sleep?

-- Is there any other apps that can do this for me? (my power button is broken, so i want to sleep through software)

-- Is this the right forum for this question?

This is the API I'm accessing

http://developer.android.com/reference/android/os/PowerManager.html
[Android Q&A, Help & Troubleshooting] Steffest:
hi,

I found myself in the same situation as you with a defective power button and took all the same steps your describe.

Couldn't get it to work as I also couldn't get the android.permission.DEVICE_POWER permission.

I ended up writing a full screen app that displays a dummy "lockscreen" and sets the screen-timeout to 15 seconds.

Not a solution but rather a workaround that makes my phone usable again.
[Android Q&A, Help & Troubleshooting] joernsn:
Would you consider sharing your app in any way? market/apk/src?

Or, i can make it myself :)

and, i if you don't already know, here's how you power on without the power button:

- connect charger (wait for light)

- remove battery

- quickly insert battery again (before the light starts flashing)

Now, with CM, trackball-wake and a reboot app, we don't need the power button at all
[Android Q&A, Help & Troubleshooting] joernsn:
Soo, i wrote it myself. If anyone else want it, here you go:

http://while1.no/files/Lock3.apk

What it does:

Fullscreen, black

Sets screen timeout to 15 secs

Waits until phone is asleep

Sets screen timeout to 60 secs

Commits suicide

If you press the trackball within the 15 seconds, you return to home screen. If you press anything else, it pretends to be asleep.

(And yes, all values are hardcoded)

I'll post the source if anyone wants it (it's so ugly I'm embarrassed)

I'm still searching for a way to access gotToSleep(), binding it to trackball longpress would be perfect :)
[Android Q&A, Help & Troubleshooting] jrw7:
I tried your application, and would like to see the source. My use case: prevent the keyboard slider from turning on the phone. My phone slides out in my pocket and then turns on, sometimes trying to make emergency calls, etc. I have all tho code in place to receive the event when the keyborad slides out, and would like to send the phone back to sleep right away. The code snipped for setting the screen timeout would do.
[Android Q&A, Help & Troubleshooting] joernsn:
The complete eclipse project can be downloaded here:

http://while1.no/files/Lock3.tgz

It's ugly as hell, but it works. There's also a lot of dead, unused code. Watch logcat to see what's going on.

When it thinks the device is off, it also commits a hard suicide :p

The timeout is set to 15 secs, but i think you can set it to 5 as well. Let me know if you make any improvements :)
[Android Q&A, Help & Troubleshooting] joernsn:
The DEVICE_ADMIN permission of Android 2.2 solves everything.

I've created an app that locks your device (properly, no hacks!) if you either:

- Click an invisible widget on your home screen

- Long press search key

Name: "Invisible lock widget"

Market link:
[Android Q&A, Help & Troubleshooting] sekhuat:
Hi Joernsn,

Is it possible for you to release your source code? I am trying to develop application also need the "administrative right". Thank you.
[Android Q&A, Help & Troubleshooting] da1duc:
Anyone have any progess on doing something like this? There seems to be a lot of "Sleep apps" but no true power off apk.

Thanks,

D
[Android Q&A, Help & Troubleshooting] sekhuat:
Dear All,

I had managed to develop a utility that turn the device screen off and on by flipping the device itself. This app also came with a widget that allow you to turn off the device screen. The application is called JustFlip and you should be able to search it in Android Market under the tool section.

The application is design for Android ver 2.2 and the device must have orientation sensor. Currently the application only tested on Samsung Galaxy Tab and therefore not sure is it working fine for other device.
[Android Q&A, Help & Troubleshooting] Fr4gg0r:
You can sign the .apk with the system signature - impossible if it's not a custom rom.

Maybe it also works if you edit the packages.xml (as root): set sharedUserId to 1000 (system) to your package.
[Android Q&A, Help & Troubleshooting] Akshay (Aky):
Well, Thanks for your app.

Can, you please tell me how do you unlock the phone ??

Just, the code for unlocking.

Thanks in advance mate.
[XPERIA X1 General] eiben_robert:
Hello,

I have since 2 weeks a Xperia X1 which I run with an NRG Sense Rom. This, as most cooked Sense ROMs has 2 camera/camcorder apps:

- Sense (HTC) app which as a camcorder can film up to CIF (352x280) resolution in mpeg4 format

- Xperia R3AA camera app which can film up to VGA resolution in 3gp (I think H263) format

The movies made with the Sense camcorder seem relatively ok but they are lower resolution.

The movies made with Xperia camera app in VGA are quite bad: skipped frames and a lot of compression artefacts

The following tweak can be applied to SENSE camcorder app (if it's cooked in your rom)

Unlock Additional Video Recording Formats

Go to [HKLM\Software\HTC\Camera\P2 and replace the EncodeFormat value with 2147483647

This will unlock all modes/resolutions listed below:

H263(3gp): CIF 352x288 \ M 176x144

MPEG4: L 320x240 \ CIF 352x288

3GPP2: S 128x96 \ M 176x144 \ L 320x240 \ CIF 352x288 \ VGA 640x480

MOTION JPEG: S 128x96 \ M 176x144 \ L 320x240 \ CIF 352x288

H264: L 320x240 \ CIF 352x288

Conclusion: the best results I got with sense camcorder CIF (352x280) resolution in mpeg4 format.

any other advice on how you managed to get decent movies out of xperia is welcomed :)

Thanks

Robert
[XPERIA X1 General] ring-bearer:
It's a good question and unfortunately I don't think I can be much help. I have tried messing with the registry settings for the video recorder: I'm fairly confident there's no registry setting for what format to record in. I also messed with settings for frame rate and resolution etc, but could never tell much difference. Then again, I didn't have a scientific way to determine if there were changes.

I think the registry place is HKCU/software/sony ericsson/camera or something.
[XPERIA X1 General] Ethermind:
no

it is not right place

when i made attempt to port x2 camera app i learned some coding related places.

it place is absolutely unrelated
[XPERIA X1 General] eiben_robert:
I found a tip from itje

Unlock Additional Video Recording Formats

Go to [HKLM\Software\HTC\Camera\P2 and replace the EncodeFormat value with 2147483647

This will unlock all modes/resolutions listed below:

H263(3gp): CIF 352x288 \ M 176x144

MPEG4: L 320x240 \ CIF 352x288 \ VGA 640x480

3GPP2: S 128x96 \ M 176x144 \ L 320x240 \ CIF 352x288 \ VGA 640x480

MOTION JPEG: S 128x96 \ M 176x144 \ L 320x240 \ CIF 352x288 \ VGA 640x480

H264: L 320x240 \ CIF 352x288

However the value 2147483647 is too large for that field (hex or dec).

Anybody had luck with this?
[XPERIA X1 General] Ethermind:
where i can download htc camera software ?
[XPERIA X1 General] Ethermind:
All ok for me. But still need ported htc camera.
[XPERIA X1 General] wphoenix:
Yeah, me too, i'm looking for a htc camera app in CAB format for my X1 ^^
[XPERIA X1 General] NEO130:
Why don`t you do a search in the X1 Tread for "HTC camera" and look yourself first ?:)
[XPERIA X1 General] wphoenix:
Found 1 :

http://xdaforums.com/showpost.php?p=3630728&postcount=176

but this one doesn't work on X1

I really need a HTC Camera cab file which doesn't affect X1 OEM camera app, someone please help!!
[XPERIA X1 General] ring-bearer:
NRG and Williyung cook them into their ROMs. Contact them.
[XPERIA X1 General] wphoenix:
I haven't contact them yet, but I think they want it make their ROMs become special ^^ That's why they don't release a stand alone cab up until now
[XPERIA X1 General] NEO130:
[30.12.09] [GER] H.V Extendir (16.01.10-Package Update)

In this Rom-Tread is a download "Base packages". Is about ca. 131 MB great and in the folder multimedia you find the cab. I make this search for you. :)
[XPERIA X1 General] Ethermind:
Give me a link on a ROM.

I'll extract standalone CAB.
[XPERIA X1 General] NEO130:
ii

Hä, it`s here in the xperia rom dev, look yourself, I`m not your bimbo.:)
[XPERIA X1 General] Ethermind:
seems the tweak doesn't work
[XPERIA X1 General] Ethermind:
Hacked Version 352x288 --> 640x480

I've done some fixes in hex, so i've changed 352x288 to 640x480.

http://www.multiupload.com/BBJRFQSTC9

But seems all useless - all video is LQ.

I think that problem is in variable bitrate and framerate.

Also we have 5 (five) resolutions:

S 128x96 \ M 176x144 \ L 320x240 \ CIF 352x288 \ VGA 640x480

But in the same time we have 4 encoding related reg entries:

CodecSmall

CodecMedium

CodecLarge

CodecVGA

Unlocking tweak give us only new formats, not new resolutions.
[XPERIA X1 General] wphoenix:
I'm downloading, thanks for your hint. I installed it. It works but doesn't display any text for configurate >.< and quite slow, the auto focus work not correctly :(

All 'Energy' ROMs got HTC Camera cooked in. He uses HTC Camera v6.16 and I heard that there is newer version (v6.18) but only for chief. Don't know if any chief cooked it into their ROM. If you can create a stand alone English CAB then go ahead ^^ Hope to hear from you soon. I really love HTC Camera

Ah, and I'm using ur 1% battery decrease cab :D really cool and helpful!!
[XPERIA X1 General] Ethermind:
I downloaded camera from Extendir Package, but it is 6.6 version.

So give me a link to 6.16 or 6.18.

edited:

looks like exist 6.29

http://www.mediafire.com/?omywgbxhmt0
[XPERIA X1 General] ultrashot:
Ethermind, http://www.multiupload.com/ZPXLC6XDIV

camera package (6.16) from rhodium + patch to save photos to 100XPRIA instead of 100MEDIA
[XPERIA X1 General] wphoenix:
This file doens't work :(

Sorry but i don't know what's the difference between those version ^^!
[XPERIA X1 General] Ethermind:
yes. 6.29 doesn't work.

and i heard about existence of 6.30

now works 6.22 vga version, but and there nothing about 640x480 too.
[XPERIA X1 General] wphoenix:
Have you got any stand alone cab? I use it to capture image only ^^ 6.16 or above is ok for me. If you have it, please share ^^ Thanks alot
[XPERIA X1 General] Ethermind:
Since 6.22 for vga, it has big hole about ~100px from right : )