yashsingh1/xdaforums huggingface dataset:
[Barnes & Noble Nook Tablet] zmobie:
It sounds like the cover is badly made or too flimsy - I would return it and get another, to be honest, if you can. If not, add some sort of small rubber or foam object to the area where the cover touched the bezel (like the things used for eyeglasses, etc). The cover shouldn't do this and that's the real issue. I haven't seen a mod changing what wakes the nook up, just a program that changes what the N button does when the nook is already awake. Might want to ask in the dev forum :)
[myTouch 4G Themes and Apps] mrmytouch:
If anyone wants cm9 bootanimation on mt4g get it here. Thanks to Marutian

It works fine on htc glacier im using it now. Flash at your own risk.
[myTouch 4G Themes and Apps] invasion2:
I can't flash it. I get CWM errors...
[myTouch 4G Themes and Apps] mrmytouch:
Did you change the file name to PD15IMG and flash in bootloader? Or you can try an app called bootanimation utility and import the zip.
[myTouch 4G Themes and Apps] RyanBoyGenius:
Pretty cool, thanks for this.
[myTouch 4G Themes and Apps] The Archangel:
Just use root explorer, it's simple right?

If I helped, give thanks, if you please.

........Death before dishonor........
[myTouch 4G Themes and Apps] mulletcutter:
Not every zip is flashable. /system/media for cm7, miui /data/system/theme/boots
[myTouch 4G Themes and Apps] saranhai:
system/customize/resource for Sense roms
[Galaxy S Plus I9001 Android Development] imans12:
shade of galaxy is a dangerous file and brikded your phone with 2.3.6 kps
[Galaxy S Plus I9001 Android Development] budakmaran:
do you mean port theme shade of galaxy thread??

most people get a bootloop..me too

but you should read a whole thread before trying it..

already be mentioned by several user that there is a bootloop..
[Galaxy S Plus I9001 Android Development] broodplank1337:
It's not bricked.. it's just in a bootloop probably, just flash it with Odin
[Galaxy S Plus I9001 Android Development] crisdorya:
After installing the theme, my phone is stuck at Samsung animation, so useless.

The developer knows and he is trying to fix the problem ASAP.
[Galaxy S Plus I9001 Android Development] sakindia123:
what the heck does the guy mean by sayin its fake
[Galaxy S Plus I9001 Android Development] nikagl:
Looks like he used a bad translation engine :)
[Galaxy S Plus I9001 Android Development] budakmaran:
[offtopic] sakindia, i already pm you (governet in ur test kernel with screenshot)..

sorry..just to made sure my pm arrive to sakindia..my internet connection is little bit mess now..
[Galaxy S Plus I9001 Android Development] sakindia123:
yup ,it arrived

posted it in cranium rom thread

thanks
[Samsung Galaxy Nexus] tonyph33r:
Hi does this phone supposed 4g lte for att?
[Samsung Galaxy Nexus] martonikaj:
No it doen't.

How many times do people have to ask this....
[Samsung Galaxy Nexus] Zepius:
11ty billion
[Samsung Galaxy Nexus] bennettm89:
Man, this is a hell of a title for this thread.
[LG Optimus 3D] winb87:
Never seen any one post this tip so here is mine. The improvement was very noticeable. Discovered by me.

1. Use a different launcher that allows activites. (Launcher Pro) install.

2. Long press on homescreen click shortcut then goto activites.

3. Expand com.lge.hiddenmenu then click hiddenmenu, it should now be on homescreen.

4. Run hiddenmenu goto connectivity test. Uncheck power save. Lol.

Simple i know. But enjoy longer range and more power.
[LG Optimus 3D] winb87:
Let me know if it also works for u guys? REPLY
[LG Optimus 3D] RubenGM:
I changed it, went back to the setting and it's checked again.

LG Optimus 3D running stock rooted V21a.
[LG Optimus 3D] winb87:
Hmm maybe software im running old v10c. Mines still unchecked. Sorry mate THX for the reply.

Btw. I unchecked, hit home button. Killed the process. Maybe it helps.
[LG Optimus 3D] hefonthefjords:
This doesnt do anything.
[LG Optimus 3D] winb87:
Seems it does not work for everyone. Some one else with a 925 check this please other then v10c. Thx
[LG Optimus 3D] DrGomez:
why would you need more WIFI range? And why do you think it's called "power save" ? ;)

Data might have been more interesting.
[LG Optimus 3D] mtvtitan:
Its one of the feature in acuras' rom -- the data transfer :cool:
[HD2 General] nileshkhedlekar:
Hi everybody..

This is my first thread on xda..

I am using unlocked o2 512 hd2 with windows mobile 6.5 in india

my problem is my usb connection port for data has been damaged. So i am not able to connect to pc useing usb. I have shown my device to service centre and they are saying to replace the motherboard which is very costly in india (around 200 usd).

So could anybody guild me how to install hspl4 ad bootloader on my hd2 without using usb cable.. Or should i need to chage my motherboard.

Thanks in advance

nilesh khedlekar
[HD2 General] samsamuel:
no usb - no hspl. Sorry.
[HD2 General] singh_60:
same boat

im in the same boat except i reverted back to stock and sent to HTC for warranty only to be told it's not covered and have the USB totally broken and returned. great service
[HD2 Android NAND Development] zivan56:
Due to the change in ICS that requires moving the camera driver from libcamera to libhardware (like GPS and other devices for Gingerbread), a new driver has to be written.

The problem with this is that many data structures have changed. I couldn't get a single one to compile with the ICS SDK. There are many fundamental changes in the way memory is shared for preview/pictures/video, so that will need to be addressed. I have addressed picture only functionality in the skeleton driver, which will show how to transfer a picture back to the HAL.

ICS Camera Driver Overview

The driver seems to be very generic to most Qualcomm SoCs, so either approach should work for many other devices.

New Driver

See CameraHal_Module.cpp from the ICS source code to see what functions needs to be implemented. It needs to be placed in /system/lib/hw/camera.<target_name_in_build.prop>.so and have the struct "camera_module_t HAL_MODULE_INFO_SYM" inside the code, which the HAL looks for before loading. Once it is loaded, you must implement a few dozen functions to get it to work.

Old Driver

The old drivers primary interface with Android is through libcamera. This loads liboemcamera, which sends commands to the camera kernel driver and the Snapdragon DSP. Liboemcamera is a propriatary library with no documentation apart from the source for QualcommCameraHardware.cpp (which compiles to libcamera.so). The actual Linux kernel module is just a simple I2C bridge to control the camera, and provides no real interface.

Current code/skeleton driver available:

http://xdaforums.com/showpost.php?p=20281617&postcount=17

Please do not comment in this thread unless you are able to contribute to the actual development process.
[HD2 Android NAND Development] KrewsialNL:
Please keep this DEV only!

Thank you.
[HD2 Android NAND Development] blarfiejandro:
If you're having a problem with the autolocks not releasing when needed, just do the locking manually. It's definitely tedious, but doable. I would guess, however, it's going to be easier in the long run to just implement a proper CameraHal module. If structures that you're relying on have changed... it's almost certainly better to rewrite from scratch.
[HD2 Android NAND Development] zivan56:
Unfortunately, I cannot recompile it with the current ICS source, as the structures the module uses have changed significantly. I could get the 2.3 source and compile against that, but then I might as well just re-write it as you have suggested.

Re-writing it based off of QualcommCameraHardware.cpp will involve the exact same hurdles. The previous driver (libcamera.so, which is compiled from QualcommCameraHardware.cpp) supplied only some functionality to Android, and passed numerous others to liboemcamera.so (completely closed source) via the same dlsym's. So there still wouldn't be a proper driver, just one less layer wrapper.

Ultimately, the only solution looks to be just to use the very core initialization methods from libcamera and find the proper ioctl calls to /dev/msm_camera/control0

I have tried to do that earlier, but liboemcamera.so has callbacks to libcamera.so (which may be passed back again to libcameraservice in Android), so its going to take some reverse engineering to figure out out.

I have been working on a skeleton camera HAL driver, but all callbacks to Android cause libcameraservice to crash (like autofocus finished event). Perhaps its an issue of the libcameraservice.so being distributed with the roms here, I will try it on an emulator.
[HD2 Android NAND Development] blarfiejandro:
With the Optimus V, at least, there's a lot of logic in liboemcamera such that any IOCTLs you call on the device will more or less get ignored unless they're what liboemcamera is expecting. I wouldn't spend a lot of time trying to preserve the 2.3 shim.
[HD2 Android NAND Development] zivan56:
So that pretty much only leaves direct calls to liboemcamera basically. I don't see any easy way duplicate liboemcameras functionality, as it does lots of non-camera related hardware setup having to do with the DSP.

It might be easier to backport the old camera library instead to ICS if liboemcamera cannot be used.
[HD2 Android NAND Development] Visentinel:
Is it an option to simply port the gingerbread camera related AOSP code into use for ICS that way there is no trouble with the camera.
[HD2 Android NAND Development] zivan56:
Its an option. The camera API presented to apps themselves doesn't appear to have changed, so it shouldn't affect the functionality of them. Hopefully only libcameraservice needs to be changed.

I will be giving calling liboemcamera a go again before trying that.
[HD2 Android NAND Development] zivan56:
Just a small update (no progress on the HD2 itself)

I have a partially complete skeleton HAL driver written dealing with taking images (not panorama or video). I figured out how to deal with the various callbacks, and now have most major events handled (auto focus, take picture, transfer picture to Android)...it even returns a fake image to test memory operations. Will post it later if anybody is interested.
[HD2 Android NAND Development] zivan56:
update: managed to get the camera HAL to negotiate the settings with the camera app and HD2 (i.e picture size, saturation, etc) and init the hardware. Now I am struggling with the preview stuff.

Seeing this error:

E/mm-camera 8x vfe( 69): vfe_util_updaterollofftbl: sensor doesn't support rolloff correction by VFE

When it tries to register memory for the camera to put images into. I will have to look through the kernel source and see what its tripping up on.
[HD2 Android NAND Development] zivan56:
Next issue is I need /dev/pmem_smipool . Only some kernels provide this, so I will have to look for one that supports it.
[HD2 Android NAND Development] kylew1212:
Great work! I know this is developer only thread but I want to help. I do not know how to code however I can test.
[HD2 Android NAND Development] zivan56:
I'm afraid unless you know how the pmem stuff works, you can't really.

The main problem now is that the driver (based off QualcommCameraHardware.cpp) and the kernel don't agree on where the shared memory is located (one of MSM_PMEM_OUTPUT1, MSM_PMEM_OUTPUT2 or MSM_PMEM_RAW_MAINIMG, MSM_PMEM_PREVIEW).

Now this depends on the 720p option being enabled/disabled in the kernel (which strangely enough, doesn't actually give 720p support for the HD2).

This is where it errors out:

E/mm-camera 8x-vfe snapshot( 69): vfe_snapshot_raw_axi_init: failed

(message comes from liboemcamera.so)

Kernel reports this:

msm_frame_axi_cfg 1293: pmem region lookup error

So it never transfers the picture/video/preview frames to the shared memory region

Likewise, the QSD8250 CPU has some very unique settings that other MSM devices do not. For example, its preview mode is just video capture mode. Whereas others have a dedicated preview mode.

So far what works:

- Init sensor, set effects, zoom, contrast, etc (and adjust on the fly)

- Take JPEG picture process and transfer to camera app (but only returns solid green due to the kernel not copying the picture into the proper pmem)

- Set video mode
[HD2 Android NAND Development] kylew1212:
Would it be possible to physically assign a memory address for these variables within the kernal? I understand theirs probably not much I can do, but I'm more than happy to if something comes up I can do. (I can't wait to take programming in school soon)
[HD2 Android NAND Development] Stickman89:
If your finding yourself getting stuck at any point the best person I can recommend from past knowledge would be XDA member DZO (Martin) who had done alot of sensational work on porting android to nand onto a number of QVGA WinMo devices i.e. Kaiser, vogue, polaris... rewriting many of the drivers himself from scratch.

I hope he is still active here on XDA, his work will be greatly remembered, even more so for myself as I used to own a HTC Kaiser in the past...

If your interested here's a bit about him from an XDA Interview: http://www.xda-developers.com/android/developer-interview-dzo/

XDA Member Profile: http://xdaforums.com/member.php?u=917443

(Looks like he's still active too xD)

Best Regards,

ST1Cl<^^aN
[HD2 Android NAND Development] zivan56:
Unfortunately, it doesn't look possible. The kernel driver (msm_camera.c) needs a special type of memory that the DSP can write to. The userspace driver tells the kernel to set up the memory and passes the details back to the kernel driver which tells the hardware to write to this special shared memory. I can copy the data from this buffer to the camera HAL, that works fine...but there is no data in the memory obviously.

Thanks for the contact. As long as they are Qualcomm MSM/QSD devices, it should be really similar.
[HD2 Android NAND Development] zivan56:
Since there were a number of requests for the current code, I am releasing the code for two things:

1. Skeleton.zip - A skeleton HAL which shows you how to do simple image transfers back to the HAL/setting negotiation. This should help with developing drivers for any device or if someone wants to start the HD2 driver from scratch. It will also complete the process of picture transfer back to the camera HAL (with a fixed picture of course)

2. libcamera3.zip - Progress so far on the HD2 driver. It will init the sensor, change/negotiate settings with the HAL.

It also implements notify/data callbacks which have changed significantly with ICS. There are scripts in there to help with getting the driver to the HD2 and chmod the devices so you dont have permission issues.

I used tytung's latest ICS build and the HD2 AOSP dev environment (http://xdaforums.com/showthread.php?t=1361859) see post #3 how to set it up. You may need to pull binaries from the ICS build to the prebuilt folders in the SDK in order to link the driver properly.

The scripts assume the git repository above is in ~/ICS/ and the Android SDK (with adb) is in ~/android-sdk-linux/

Documentation is nonexistant, but it should be easy to figure out. I cannot help anyone with what QualcommCameraHardware.cpp does, I did not change it much apart from implementing the new callbacks and the ICS HAL wrapper.

I wont have much time to work on it, so hopefully someone else can get the ball rolling on getting the shared memory stuff to work properly. Likewise, set up a git repo somewhere for others to contribute.
[HD2 Android NAND Development] BoneMo:
thx

thanks for effort and work

how does the development continue ?
[HD2 Android NAND Development] zivan56:
I am sure someone will pick it up. Its in the interest of owners of the Nexus One and a bunch of other Qualcomm Snapdragon based phone owners who want the camera working in ICS. If someone fixes the driver I was working on, it should support at least a couple more devices with very small changes in the code (or perhaps 1 driver that works on all of them by detecting the phone).
[HD2 Android NAND Development] vua777:
from ankuch ICS sd build: http://xdaforums.com/showpost.php?p=20305195&postcount=677

Edit: Sorry not a dev post
[HD2 Android NAND Development] davibs:
Sorry if not a dev post but today it's 22 December, and last post was 15...

No news?

Sorry Again, but i'm really interested at this Ics.

Really need working Camera, for photos.
[HD2 Android NAND Development] CR5N:
Don't apologise, just give the devs a break and wait paitently. Or, you could learn to code and contribute something useful...
[HD2 Android NAND Development] 2n3906:
Helping with the coding.

I'd like to contribute to the coding of this effort but have no idea of the language and/or tools used. I'm a java/c#/vb.net developer. How should I go about getting started? Thx in advance.
[HD2 Android NAND Development] twistedumbrella:
Are you guys just working with the AOSP "generic" version of the camera code and modifying that?
[HD2 Android NAND Development] zivan56:
The skeleton driver follows the API required to get a camera working on AOSP ICS. Likewise, the modified libcamera driver (which supports a bunch of Qualcomm Snapdragon SoC and associated camera sensors) has been mostly modified to support this new API.

I have a feeling Qualcomm will have to release a driver soon, as there will be Qualcomm MSM/Snapdragon devices running ICS. Since the code supports multiple devices, presumably you can take their driver and put it in /system/lib/hw and it will just work.

As I said, I have no more time to work on this. Anyone is welcome to pick it up...
[HD2 Android NAND Development] twistedumbrella:
Thanks. I will have to check this one out. Much more realistic than the version that released some prebuilt files for one device profile in terms of compatibility.
[HD2 Android NAND Development] twistedumbrella:
One thing I am confused about is the libcamera3 replaces hardware/msm7k/libcamera and then the libcamera proprietary is the one from GB and this just builds the HAL to use it correct?

I started expanding on this, but I was making sure I had the right ideas about the actual function of it all.
[HD2 Android NAND Development] zivan56:
The driver included in ICS under hardware/msm7k/libcamera doesn't even compile, it is a very simple version of this driver (with very few features). It's not even modified to use the new structures and/or messages. I don't even see why it was included.

This driver includes that plus and extra features that were included for CM and other tweaks to bypass liboemcamera.so (proprietary binary) as much as possible. None of that was written by me, it was written for Gingerbread by various people. It doesn't replace that actual file (libcamera.so), but is in the new format expected by ICS for camera hardware (libhardware in ICS).

So it does use some liboemcamera functions, but does lots of direct ioctl calls to the kernel camera driver.
[HD2 Android NAND Development] twistedumbrella:
Let me attempt to word my question better. When building this code as a replacement for the current libcamera, what proprietary files should be deleted?
[HD2 Android NAND Development] zivan56:
libcamera.so

This should then be put in /system/lib/hw/camera.<product name>.so where product name is whatever is in build.prop (usually htcleo).
[HD2 Android NAND Development] twistedumbrella:
That's unusual because until I put libcamera back I couldn't get it to build. Looks like I need to sit down and review where I went wrong.

Edit nevermind, I just realized I have libcamera going into system/lib instead of lib/hw after it is used to build. Makes sense.
[HD2 Android NAND Development] masterex567:
http://developer.android.com/reference/android/hardware/Camera.html

The site above should help.
[HD2 Android NAND Development] carlosivan3:
Sorry if this is a too noob suggestion.

After a lot of googling I've seen this guy working seriously in Qualcomm camera issues for ICS:

h t t p s : / / g i t h u b . c o m/yjwong/android_hardware_qcom_camera

Maybe he could be of help if contacted.

Thre is also a group coding android specifically for Qualcomm chipsets:

h t t p s : / / w w w . c o d e a u r o r a . o r g /contribute/projects/qaep/

Hope it helps and sorry if it doesn't :D

Thx to all
[HD2 Android NAND Development] lagloose:
Hey folks,

i know this is not Galaxy Ace Thread but meanwhile i'm a little frustrated and have no idea how to go on, so i decided to ask here if someone has an idea what i can do or try. I have camera working on Galaxy ACE with no preview. Camera seems to be initialized correctly. I can shoot pictures with stock camera but no preview...

IMO preview can't be shown because of this SIGFPE in libc which is obviously thrown through calling 'initDefaultParameters'

...

V/QualcommCameraHardware( 145): startCamera picture_sizes 0xa7758430 PICTURE_SIZE_COUNT 7

V/QualcommCameraHardware( 145): startCamera preview_sizes 0xa7758468 previewSizeCount 5

V/QualcommCameraHardware( 145): startCamera X

I/QualcommCameraHardware( 145): initDefaultParameters E

F/libc ( 145): Fatal signal 8 (SIGFPE) at 0x00000091 (code=0)

I/Process ( 309): Sending signal. PID: 1421 SIG: 3

I/dalvikvm( 1421): threadid=3: reacting to signal 3

I/dalvikvm( 1421): Wrote stack traces to '/data/anr/traces.txt'

I/Process ( 309): Sending signal. PID: 1421 SIG: 3

I/dalvikvm( 1421): threadid=3: reacting to signal 3

...

This gives followup errors so that preview is not shown. Due to the fact that i've used proprietary libcamera.so from a stock ROM i've only limited possibilities to debug... I've attached a complete logcat from starting camera app through shooting a picture and ending camera app.

Anyone who can help ? if the answer is not of general interest, reply via PM to avoid flooding this thread.
[Nexus S Q&A, Help & Troubleshooting] DangerZone1223:
Hey, guys.

Since there's a 10 cent sale, I can't pass it up. There's 2 apps I got on the Amazon Appstore for free, but they're on the market for 10 cents. Might as well pay the 10 cents and get better support and updates through the Android Market. :)

However, the Android Market shows I have those 2 apps... but I can't download them because it keeps coming up that I haven't paid for them. Duh! It won't let me purchase them either. It keeps coming up "Error - The download was declined because you haven't purchased it."

There's no buy button. Just install. I Force Closed Market, cleared cache, and cleared defaults. Still the same problem. What can I do?
[Nexus S Q&A, Help & Troubleshooting] Rblacula:
Have you tried from a computer?
[Nexus S Q&A, Help & Troubleshooting] DangerZone1223:
No luck there.
[Nexus S Q&A, Help & Troubleshooting] DangerZone1223:
It's solved. Google says their payment system is updating. It's on their end. Didn't get an ETA for when it'll be fixed. Probably later tonight is my guess.
[Nexus S Q&A, Help & Troubleshooting] Rblacula:
I'm now having the same problem for swiftkey... did it ever get resolved for you?
[Nexus S Q&A, Help & Troubleshooting] albundy2010:
Uninstall the Amazon version of the app.

Purchase it from the android market.

Have a nice day.
[Nexus S Q&A, Help & Troubleshooting] 2t0m:
I have the same problem and even if I uninstall the app from Amazon Appstore, Android Market continues telling "install" instead of "buy".

If I try to install : Market tells me I didn't purchase it... :(
[Nexus S Q&A, Help & Troubleshooting] BlackJack313:
I'm in the same boat, I have uninstalled the other version, tried unlinking it with TB and I still can't buy some apps :(
[Nexus S Q&A, Help & Troubleshooting] drpele:
I have the same problem. I couldn't even manage to buy with (old) Market version 2.2.11. :mad:
[Nexus S Q&A, Help & Troubleshooting] 2t0m:
I remember an option to "buy the app anyway" after the screen "you haven't purchased it", when I was using old Market.

I'l try to downgrade the Market to see if the option is still available...
[Nexus S Q&A, Help & Troubleshooting] drache713:
just chiming in to say i'm having the same problems as everyone else, I can't find a work around. :(
[Nexus S Q&A, Help & Troubleshooting] drpele:
The old market says the credit cards I attached to Google checkout are invalid. It is very strange because they are usable on Market 3.3.11...