yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] superchilpil:
Go to settings>app> then choose the app you want to freeze and at the top it should say disable
[HTC Rezound] DbZ Gokuu:
I updated. Scott told me to, so I did. Lol.

Sent from my Ice Cream covered Rezound
[HTC Rezound] 1967ls2:
Waiting. There appears to be too many issues with the new leak not to mention battery drain issues. No thanks...waiting patiently
[HTC Rezound] jmichaels1982:
Not worth it

Here is why :

The process is extremely tricky for average users ( This is my second relock and un-lock and third android to root and custom rom and theme it ). Every thing that can go wrong will go wrong and unless you really know how to trouble shoot, dont expect too much help because there are tons of ppl in your shoes ( simple supply and demand ).

The update destroys your internal sd memory, this is where titanium likes to back up . Enjoy going through the pain of re-installing all your apps from scratch. ( for the love of god change where titanium backsup AND sync it to your drop box) Every thing in your download folder is also going to be vaporized.

The battery drain issue is very very real. It feels like i just downgraded back to the thunderbolt. Battery doesn't last 3 hours

Reception is exactly the same. Stability is exactly the same as earlier ics builds but in no way does the stability of ics matches gb. ICS is very lagy on our phones in comparison .

Please don't spend your time hating my comment or criticizing it. This is just my .02
[HTC Rezound] Marcismo55:
Not criticizing but merely pointing some misconceptions...

1. I don't really understand how it is trick to relock, rename the RUU to PH98IMG.zip, flash in bootloader (it kicks you out the first time and then you flash again) and you're golden. If you have been able to unlock your phone using htc.dev you should be able to flash this ICS leak.

2. If you go into settings in TB, you can change the backup location to your external SD card or copy the actual backup folder from internal storage to your Sd card (worst case scenario). Users should know by now that an RUU is meant to restore your phone to stock and in the process, wipes your internal storage.

3. For me, on the newest ICS Leaked RUU my battery life has been just as good if not better. I'm curious how you have your phone setup to only last 3 hours.

4. This leaked ICS in stock form was just as quick as GB. I was actually REALLY surprised because I didn't think it would work so well out of the box.

I just want to set some things straight because I do not want other users to be misinformed.
[HTC Rezound] DigiDave:
I'm waiting because I love our Rezound dev's so much that I completely trust in them to come out with a patch/something to help the process go smoothly :D. Con247 made the last OTA easy for me. If anything else, I will eventually do it when its official.

Thanks to all in this dev community!
[HTC Rezound] ericsignals:
I saw a post you made on bamf....what made you decide to flash..

..I have been holding off in the case the ota version won't overwrite the leak and something gets fixed. I doubt it would happen, bit you never know lol

I tried joelz and it seemed kernel was stuck at max like previous leak..was unsure if the oldfirmwarepeopleIMG he had for the old firmware was the old leak kernel or the new leak. So I figured I would hold.off longer.
[HTC Rezound] hgoldner:
No, but not because I like Gingerbread. I already have ICS via Nils' Business ICS 2.3, so I don't "need" the firmware update.

I went through the process of doing the OTA so I could assist in releasing the files to the devs, but I don't have the same impetus to do that with an unofficial "leak."

As others have said above, by the time the OTA is "official", the devs will have come up with easier methods of acquiring the firmware than the multi-step, easy to screw up process we face now. Yeah, I'm sure I could get it right over time, but then if the official OTA is different than the leak, we'll have to go through it all over again.

Of course, if we had S-Off.....
[HTC Rezound] andybones:
I updated because there didn't seem to be any issues with the new leak. It's running great now, I was having reboot issues, but I was having them on the old firmware, so then I updated and still got them, and me and Joel figured out it was the android.policy.jar for some reason, but once I replaced that haven't had a reboot since. It's running much faster, smoother, doesn't get as hot, and batt is better.

I also am able to go back to any GB ROM and it's just as if I didn't update. I went back to my old nandroid and it was just fine, ran it for a while to see how the batt responded as was just the same.

you need to flash one file to make the internal be seen on GB ROMs, very easy actually, it's the same process that joel uses for old firmware ppl to be able to use the new leak, but reversed lol.

Hope this helps.

the process to install the leak was as easy as pressing vol up, then power to reboot. Oh, and some patience. :D
[HTC Rezound] ericsignals:
Does the kernel scale.properly in the new leak or is it on 1.5 the whole time?
[HTC Rezound] a.mcdear:
I have not upgraded yet for a variety of reasons:

1) changed internal storage mappings. This isnt a huge deal, except that there isnt a recovery fully capable of accessing the internal storage yet.

2) don't want to update HBOOT yet. The only reason for this is in case an exploit comes out for S-OFF, which isn't likely

3) I'm already running ICS, based off a combination of the previous 4.0.1 and 4.0.3 leaked builds, and don't want to wipe and modify it for the new HBOOT yet

4) haven't had time yet

5) I'm lazy
[HTC Rezound] andybones:
theres a new recovery out.... fixed mounting points...
[HTC Rezound] a.mcdear:
Nope, not fully fixed yet. the latest 3.15 Amon Ra still can't back up or restore from internal storage correctly.... but I do expect it'll be fixed pretty fast now cause Drellisdee is aware of it now.
[HTC Rezound] johnwaynegacy:
No, I am not interested in going from sense to sense. I'm waiting for cm9
[HTC Rezound] mjh68:
I agree with Marcismo.. yes there was a little bit of learning curve of what to expect since it acted a little differently than the OTA leaked RUU did , along with the tampered label and thinking we had to get rid of it. Other than that it was easy enough. To broadly paint it so poorly is your experience most don't have those issues.

My battery is exactly the same on GB or this newest leak so must be your setup or something you have installed is wreaking havoc on your battery life.
[HTC Rezound] theGross1:
Nope, I too had an eris and took the early leak. That and I'm too lazy
[HTC Rezound] ericsignals:
Anyone know if the kernel functions properly on the new leak or does it get stuck at max like the previous leak
[HTC Rezound] putney1477:
I understand that people are hesitant, myself included. However, the devs do an awesome job on their own time, mostly for fun, developing, tweaking and modding roms for us.

Honestly, the leaks, are just that, leaks, but they have been tweaked to work on our phones, everything has some kind of bugs, even official OTAs ;)

I guess what I am trying to say is, the leaks aren't ****. The devs work their butts off for us. Its totally a personal option to root and flash or not :)

Sorry about ratteling on and on....just want the devs to know they are appreciated.
[Sony Ericsson Xperia Neo, Pro] ptitflo21:
First I'm sorry to creat a new thread, but even if I have more than 10 posted messages I haven't the right to post in development section. I don't understand why.

More over, there is no thread for discussion for the development of KA6 ice cream sony.

So, sorry for my english, I have a problem with the battery. in 4h i lose more than 40% of my battery without game or wifi... i dont do anythink special. juste 4 or 5 sms.

I see this on the development thread "Remove persist.rildenabled=1 line from build.prop, save it and restart phone" But, someone tell that is not enough, and he has some persist batery issue.

Maybe this problem will be fix in the next realese, that will be great.

Thank you very much krabappel2548 for your rom, it is almost perfect, when the battery issue will be fix, this will be the best one.:)
[Sony Ericsson Xperia Neo, Pro] Madfysh:
So have you tried to do that? :)
[Sony Ericsson Xperia Neo, Pro] ptitflo21:
yes I have do that this afternoon, but it's look not realy better. I will see tomorrow after a complete charge.
[Sony Ericsson Xperia Neo, Pro] ptitflo21:
every thing works perfectly now. thank you krabappel2548 for your rom.

But I don't understand why I can't whrite in development section.... :(
[Sony Ericsson Xperia Neo, Pro] Qwerty123 \m/:
You need to have a minimum of 10 posts

Go through the threads and reply to any post that you can help in
[Sony Ericsson Xperia Neo, Pro] Madfysh:
hm, but strange is that he already have 10 posts.. who knows, maybe a bug.

OP: contact moderator to check your account, to see where is problem.
[Sony Ericsson Xperia Neo, Pro] equlog:
I havent any battery drain issue so far.. and deepsleep works ok. Normally my battery last 1day and some hours(2/3h screen, some 3g data, wifi on and some calls).
[Sony Ericsson Xperia Neo, Pro] Bartske:
try to update to the newest update :)
[HTC Sensation XL] ali magdy:
Hello

I have been searching for beats audio skin for a while and I can't find one that can work on my sensation XL . Can someone tell me where I can find a free one that can work on sensation XL?
[HTC Sensation XL] voileuxcool:
Deviant art
[HTC Sensation XL] CoSaWa:
Or have a look around the Desire HD forums, they're a lot more active. :(
[Galaxy S II Q&A, Help & Troubleshooting] efebaris97:
hi all, I'm using I9100 and I search a rom, I want it drains battery slowest, can someone help me :) thanks

sorry for my bad english
[Galaxy S II Q&A, Help & Troubleshooting] MistahBungle:
There is no such thing as the "best battery rom". You have your phone setup differently to everyone else, you use your phone differently to everyone else and your phone came out of the factory slightly differently to everyone else's.

A rom that runs well for me might not run well for you.

I suggest you go the development sections of the forum & read the first few pages and the the last 10-20 pages of the particular threads devoted to different roms. That way you will get an idea of the features/pluses/minuses of each rom, and also see other users' experiences with that rom.

There's too many variables which determine battery life to be able to say 'This is a great rom for battery" (or performance, or anything else)

Then you can test different roms for yourself to find one that works best for you.
[Galaxy S II Q&A, Help & Troubleshooting] sandip.banik:
After Installing any ROM..make sure you freeze the apps that arent needed and uselessly hold wavelocks..and u will definitely find that suits you.. Search..Read..and Explore XDA, a lovely place for development
[Galaxy Tab 10.1v Android Development] ORiZorrie:
UPDATE !! The drivers for the front camera are found ! Check the latest CM9/CM10 ROM's and the drivers should be incorporated !

-----------

This topic is for devs and testers only. Please keep this topic as clean as possible. So only post if you have some new information to share.

The idea of this thread is to gather all the information we have regarding the 10.1v camera so that a developers can port the camera drivers to ICS.

What do we know already?

1. Back camera lens: Sony IMX-073 - CMOS : OV-8820 (technical specification)

2. Front camera lens: Samsung S5K5BBGX - CMOS : OV-9640

3. The Samsung Galaxy S II is using a IMX-105 lens and NOT an IMX-073 lens as we assumed. However, the CMOS chip is identical: OV-8820 in both devices. So in theory we should be able to use the same driver.

4. In HC 3.2 the device drivers are:

camera0=/dev/imx073,back,0,mono

camera1=/dev/os5k5bbgx,front,0,mono

There is a mention of IMX073 in this lib: \system\lib\libnvodm_imager.so

I guess the following files are impacted as well:\system\lib\libcamera.so

5. Honeycomb Sources for our Camera drivers (2.6 kernel):

- IMX073 & s5k5bbgx : https://github.com/cyanogen/galaxy-2636/tree/ics/drivers/media/video/tegra

- IMX073 : https://www.codeaurora.org/patches/quic/la/PATCH_MSM7x30_1969_Sony-IMX073-Driver_20100608.tar.gz

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

What needs to be done?

-> Many data structures have changed between HC & ICS. There are many fundamental changes in the way memory is shared for preview/pictures/video, so that will need to be addressed. This is a rather painful process, but it can be done. There is a chance when Samsung releases the ICS rom for the 10.1, that we can use it for the 10.1v. But probably this driver will not have proper support for our camera model. So we can only hope for the best!

UPDATE: The best option is that someone writes a HAL (Hardware Abstraction Lager) module for Tegra 2 SoC's. If my information is correct, that means that the hardware calls to the SoC need to be reverse engineered. Once we have this HAL module, developers can write a wrapper around the old (Gingerbread 2.6 kernel) camera driver. With this HAL module all Tegra 2 devices have a good chance of getting the camera to work. The good news is that there are a lot of Tegra 2 devices, so the community is big and there is a fair chance a skilled developer will develop a HAL for it.

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

Attempts to make it work so far

I've tried the Samsung Galaxy S II camera libs (same camera model) and the Motorola Xoom (same Tegra 2 chipset but different camera model) camera libs, but without success.

Error codes are visible in logcat:

- S II libs: signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 5b3804a2

- Xoom libs: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00010ef0

- Old HC libs: isimobile tried with the HC libs without success -> check here

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

If you have any information to share, please post in this topic.

Thanks
[Galaxy Tab 10.1v Android Development] ORiZorrie:
I've been doing some more digging and I've found this driver source for the IMX073.

Could it be of any use for us?
[Galaxy Tab 10.1v Android Development] vanhyfte.johnny:
Just a quick brainstorming:

If the module is the same as in the SII wouldn't it be possible to use the driver from the ICS update for the SII once that's out?
[Galaxy Tab 10.1v Android Development] ORiZorrie:
Update: the front camera is actually a 's5k5bbgx'

And the source code appears to be on github already (pushed by pershoot for the p5 device)

So I really think pershoot should take a look at this topic :eek:

https://github.com/cyanogen/galaxy-2636/tree/ics/drivers/media/video/tegra
[Galaxy Tab 10.1v Android Development] Psyloid:
already posted this in the isi ICS thread, but also suited here

In regards to make the camera working maybe pershoot, isimobile or another person with the knowledge on how to do it, XDA member twistedumbrella made the camera work for a lot of HTC devices under ICS. He had no source from HTC, he took the Gingerbread driver, decoded it and modified it so it would work with ICS. Maybe anybody can contact him to ask how he did it, so maybe we can do it too with our Honeycomb driver

Just a thought
[Galaxy Tab 10.1v Android Development] XaMaB:
I've asked this in the KANG thread already, but didn't receive an answer. Maybe here it may draw attention of the right ppl
[Galaxy Tab 10.1v Android Development] ORiZorrie:
I have sent him a mail. I hope he's open to that because he's not accepting private messages. In any case, I'm just trying to gather as much information as possible. We'll see if he replies or not....
[Galaxy Tab 10.1v Android Development] ORiZorrie:
Thanks. I have already looked into that code, but it's for Qualcomm SoC's, and not for Tegra 2. We would need a HAL (Hardware Abstraction Layer) module for Tegra 2 instead I guess...
[Galaxy Tab 10.1v Android Development] isimobile:
I have done some further testing:

I back ported tegra_camera.c from the nvidia 2639 kernel. tegra_camera.c is being called from imx073, in a couple of places. The driver seems to be loading ok and if I open the camera app, it does not FC anymore, but the device "hangs". I have to forcefully reboot it to get to work again.

What it looks like is that the problem is libnvodm_imager.so. That is what we found earlier that that library have hardcoded values for the camera. The lib we are using is looking for OV5640 camera which it the transformer (TF101) camera. So unless we can get a working libnvodm_imager.so. I think we are stuck. I tried to hexedit the values in the lib to imx073/s5k5bbgx, but did not make any difference.

Comments suggestions are welcome.

Here is a portion of the logcat:

D/NvOsDebugPrintf( 112): +NvOdmImagerOpen (202):ImagerGUID= (0), Handle=0x702134
D/NvOsDebugPrintf( 112): NvOdmImagerOpen (203):Compiled at Feb 21 2012 21:26:41
D/NvOsDebugPrintf( 112): NvOdmImagerOpen (205):prop: force.camera=Unknown
D/NvOsDebugPrintf( 112): NvOdmImagerOpen (251):ioctl failed!
D/dalvikvm( 1166): GC_FOR_ALLOC freed <1K, 7% free 8489K/9095K, paused 22ms
I/dalvikvm-heap( 1166): Grow heap (frag case) to 8.770MB for 331516-byte allocation
D/NvOsDebugPrintf( 112): +SensorYuv_Open (362):compiled at Feb 21 2012 21:26:41
D/NvOsDebugPrintf( 112): +check_project (31):
D/NvOsDebugPrintf( 112): check_project (33):prop: ro.epad.model=Unknown
D/NvOsDebugPrintf( 112): -check_project (42):undefined...!
D/NvOsDebugPrintf( 112): +ParsingCustomCap (156):
D/NvOsDebugPrintf( 112): -ParsingCustomCap (171):
D/NvOsDebugPrintf( 112): SensorYuv_Open (386):Custom Cap not found, use built-in one.
D/NvOsDebugPrintf( 112): -SensorYuv_Open (397):
D/NvOsDebugPrintf( 112): +SensorYuv_GetCapabilities (422):
D/NvOsDebugPrintf( 112): -SensorYuv_GetCapabilities (427):
D/NvOsDebugPrintf( 112): NvOdmImagerGetCapabilities (535):identifier:OV5640
[Galaxy Tab 10.1v Android Development] ORiZorrie:
https://github.com/cyanogen/galaxy-2636/blob/ics/drivers/media/video/tegra/imx073.c

If I look in the imx073.c file I don't see those references you mention apart from the header file reference 'media/tegra_camera.h'.

The photosensor for s5k5bbgx is OV9640 (see OP -> it's mentioned in the header of s5k5bbgx.c)

The photosensor for imx073 is OV8820 (see OP)

Simply hexediting the values in the lib won't work. Reverse engineering implies that you disassemle the code, edit it (assembled language) and then assemble it again.

What we need is a HAL module for Tegra 2 SoC's, When we have that HAL module porting the device driver should be more straightforward (at least if you're a C adept) because we can reuse the old driver.
[Galaxy Tab 10.1v Android Development] isimobile:
Have a look in camerafw_file_cmd_show: tegra_camera_enable_vi, tegra_camera_enable_csi

Send from my GT-P7100
[Galaxy Tab 10.1v Android Development] tyler79durdan:
Good job guys... keep up the great effort. Remember you're not making a thousand mistakes, just finding a thousand ways not to do it ;)
[Galaxy Tab 10.1v Android Development] PookiePrancer:
I say: drop all efforts to get a working rear camera on the Tab! I can live without that one. The front one, on the other hand, is crucial for everything from Skype, to Google Talk, to any number of other video chat apps which are way more practical on a tablet than using it as a huge camera. Front-facing first; rear-facing second :)

Great effort by all though; I love you guys! No homo
[Galaxy Tab 10.1v Android Development] GazaIan:
Just a quick note; If camera starts in the kernel, but doesn't start in Android itself, it's very likely that you will have to do some modifications to libcamera.so so that Android won't produce that error you have on the original post. I do not know exactly what the mods are, sadly, I wasn't fast enough on stalking the repositories :(
[Galaxy Tab 10.1v Android Development] ganiman:
QFT

The front camera is far more valuable than the rear. If I can find some time, I may start poking around with getting this working too. I hate the idea of rolling back to stock just to use Skype.
[Galaxy Tab 10.1v Android Development] insaneturbo13:
i hate to sound like a noob since i am not a dev at all, but has anyone tried the cm9 galaxy s 2 libs since they got the camera/camcorder working properly? this has just happened in the last few days. maybe something has changed since then.
[Galaxy Tab 10.1v Android Development] GazaIan:
Galaxy S II has both a different camera and SoC, so its not of much help.
[Galaxy Tab 10.1v Android Development] insaneturbo13:
well, the lens is different yes, but the cmos chips is the same, which is what counts, however the soc is is different... very different lol.
[Galaxy Tab 10.1v Android Development] ORiZorrie:
Yeah, and if what I understood from KANG is correct... before you can do ANYTHING driver related you need to be able to communicate with the SoC. So I'm afraid that is the biggest showstopper at this time.

About the front/rear camera I think that one might work once there is an ICS update for the GTab 10.1. Normally that cam should be very similar if not identical.
[Galaxy Tab 10.1v Android Development] GazaIan:
Question is, does Samsung love us enough to get us an update :(
[Galaxy Tab 7.7 General] Gaugerer:
I powered down my 7.7 and it automatically re-started in downloading mode. I've tried holding the power button down and that makes it disappear but then it comes back again. I recently did an OTA official upgrade to the firmware when it was offered and that might be causing the problem. It had worked fine for several days since I did the upgrade. My 7.7 was bought from Amazon UK.

Has anyone else experienced this problem or know how to fix it?

Thanks for your help
[Galaxy Tab 7.7 General] Gaugerer:
Here is an update of my previous post. I have contacted Amazon who are happy to send me a replacement on Monday but suggested that I phone Samsung technical support first to see if they can help. I was going to try replacing the official ROM using Odin but I don't have a suitable USB cable.

On my previous P1000 tablet I could use the charging lead to connect it to the laptop but on the 7.7 there is no USB connector. So my 7.7 is sitting with the green android and the message "Downloading" Do not switch off target. I've disconnected the power supply cable but it will probably take days for the battery to go flat. I should be able to get a USB cable tomorrow so that I can try connecting the 7.7 to my laptop.

Although holding the power button down for 10 seconds clears the downloading screen it re-appears almost immediately. I've tried pressing power+volume down and that shows a warning about installing custom ROMS, but when I select volume down to re-boot I just get back to the downloading screen. If I select volume up I also get the downloading screen and if I had a data cable then I could try re-flashing. This is one occasion where battery removal would be handy, but not an easy option with the 7.7.

Do you think it will harm the screen having the downloading screen on all the time? Also, do you think I should just return it to Amazon without trying to re-flash in case they accuse me of bricking it?
[Galaxy Tab 7.7 General] Gaugerer:
Update. My battery went flat overnight because of the stuck downloading screen and I was able to re-boot after re-charging. I'm going to keep the tablet on standby and avoid powering down until I get a USB cable which should allow me to re-flash the stock ROM if I get another problem.
[Galaxy Tab 7.7 General] Gaugerer:
Update: I received a USB data cable today so I tried shutting down the 7.7 and when I re-started it went into downloading mode again. I rang Samsung technical support and they said there was no need to shut down and that would avoid the problem and could not suggest any other solution. I felt the solution of never shutting down was not good enough so I re-flashed with LB3 and then tried KL3 but got the same problem each time

I would be most grateful for any help with this problem before I contact Amazon for a replacement.