yashsingh1/xdaforums huggingface dataset:
[Galaxy S II General] karendar:
Can you please do the following: "First of all please check your existing camera firmware version by typing *#34971539# and then press Phone/CAM FW Ver Check."

And post what shows up on the screen?

Thanks!
[Galaxy S II General] androidkid311:
Pretty sure sammy havent fixed anything, as some one said ur lucky as am i lol. My phone has no screen issues. Just the usual getting hot problem, so i dropped cpu to 1000mhz and undervolted, much better. If the new GS3 has a quad core processor it will be a sweet portable heater. ;-)

looks like an iphone but powered by android baby!!!!
[Galaxy S II General] karendar:
I pretty much lucked out on every front. Camera works perfect, screen is perfect, heats up very rarely...
[Galaxy S II General] androidkid311:
You my friend...should clone that S2 lol. :-P :-P

looks like an iphone but powered by android baby!!!!
[Galaxy S II General] karendar:
The person who gets it when I sell it will be veeery happy
[Galaxy S II General] kingofthebraves:
Your code doesnt work buddy :)
[Galaxy S II General] radkor:
This code works only on stock Samsung ROMs. It runs CameraFirmware.apk
[Galaxy S II General] karendar:
Yeah, forgot to mention that... I just wanna know what camera firmware you have considering it's a brand new phone... I'll post a walkthrough to get it running if you're willing to help.

What ROM are you running??

Sent from my GT-I9100turbobit.net/gf3fywnc5s1n.html download this file, copy it in /system/app, change permissions to 644 and then reboot phone... then try code again. ;)
[Galaxy S II General] Ankit Tulsian:
Even i never had screen issue nor the overheating issue.Mine is International version.
[Kindle Fire Themes and Apps] jerry247:
Does anyone have insight to make this work? It says not compatible but I can sign in and browse videos. When the video tries to load it freezes and then fc's to the home page.
[Kindle Fire Themes and Apps] Hellcat6:
Try doing a search, I know someone else posted on this. Have wifi turned off when you start the app, then when the app tells you it failed connection, start up your wifi and it will work. Weird but it works
[Samsung Galaxy Nexus] Joshaldo:
Does anyone here use haxsync? I have pictures downloaded from Facebook for my people app but they don't all match the contacts in my phone book. Is there any way to manually match them up at all?
[Samsung Galaxy Nexus] EddyOS:
Edit the contact, then go to Menu>Join and manually select the name

Tends to be those that have a different name on your phone as opposed to Facebook that have to be manually linked
[Android Q&A, Help & Troubleshooting] realgpp:
Is it possible to set for a contact with 2 number 2 different default action?

A i have a contact with 2 numbers and when I call him I want use a number while I want to text to the other number. Is there any app I could use?

I have the stock rom on my S2.
[Nook Color Q&A, Help & Troubleshooting] iakovl:
right now i use the CM7.2 KANG on my NC, works great... and as the saying goes... if it works, don't touch it

i need to do a repartition right now for the nook so i can go 1/5 (or 2/4) instead of 5/1 on the memory

i want to keep the CM7 becouse it works great for me so far

but i also want to try the CM9, going to get a bigger SD in few hours

so i'd like to know how to open a boot select menu between the CM7 and CM9 (also... the recovery would be a nice touch)
[G2 and Desire Z Q&A, Help & Troubleshooting] roadrash7:
hi all I just put andomadus v10 on my wife's g2 and camera will not work it says sorry unfortunately camera has stopped.

Came from cyanogenmod7 . Put supewipe and rom on SD ran super wipe installed rom tried camera, no go. Installed GApps still no go. Any help is appreciated. She needs a camera and I wanna play with ics cause I'm still waiting for it on my sgs2 : )
[G2 and Desire Z Q&A, Help & Troubleshooting] adamz667:
Install lgCamera app from Market or try to flash GApps for Andromadus v7.
[G2 and Desire Z Q&A, Help & Troubleshooting] roadrash7:
Lg camera kinda worked but its very glitchy. I'd like to get stock camera working. Trying a reflash.
[G2 and Desire Z Q&A, Help & Troubleshooting] roadrash7:
Still no go on camera. Worked fine on CM7. What's the deal. Op of andromadus thread says it works
[G2 and Desire Z Q&A, Help & Troubleshooting] adamz667:
Camera is still work in progress, so you can expect some distorsions, glitches etc.
[G2 and Desire Z Q&A, Help & Troubleshooting] gee one:
Try clearing camera data - settings/manage apps/all/...

This is still an alpha build, so it's not expected to be perfect. I still get weird distortions with the gapps v7 camera, although bar code scanner works perfectly.
[G2 and Desire Z Q&A, Help & Troubleshooting] Kéno40:
It work better for me with the Camera360 app.

But not perfect yet...
[G2 and Desire Z Q&A, Help & Troubleshooting] Spastic909:
Well when the list of working and not working shows as "camera(kind of)" I wouldn't expect it to be anything like cm7 considering when CM does release it will be CM9.
[G2 and Desire Z Q&A, Help & Troubleshooting] roadrash7:
Well it wasn't working at all at first but I finally got it working thanks for the help all
[G2 and Desire Z Q&A, Help & Troubleshooting] csolanol:
If you flash the Alpha10 and then you flash gapps your stock cam isn't the right one. Gapps have a Camera.apk. You can remove the CameraGoogle.apk from gapps zip before flash it or remove CameraGoogle.apk from /system/app/ and push the one in Alpha10's zip
[G2 and Desire Z Q&A, Help & Troubleshooting] Barry://:
Ics camera worked on CM7?
[G2 and Desire Z Q&A, Help & Troubleshooting] Kéno40:
I use FXcamera and it works well for me.

But no zoom inside this app...

Can anyone confirm this?
[G2 and Desire Z Q&A, Help & Troubleshooting] drakh_sk:
As written in developer forums for quattro or andromadus roms. Camcorder is still not working. Camera is working but still glitchy, and best solution to remove glitches is to set the camera to VGA resolution. yes for someone VGA resolution may be not the solution but, the camera in g2 is really not so good and if you want to take higher quality pictures i think it is better to use "real" camera not camera embed into phone.

---------- Post added at 05:26 PM ---------- Previous post was at 04:57 PM ----------

and why to use zoom - our device is not supporting "real" zoom. just SW zoom, what means, software will crop, and then upsample the image from camera. This process will just make your "zoomed" pictures look much worser in the end of the process.
[Kindle Fire Android Development] csholmq:
Thanks to jamez70's, we now know where the serial pins are.

Here is where the UART pins sits on the back of the motherboard.

(Courtesy of ifixit photo and jamez70's illustration)

The pins from 1-4 are:

RX TX GND GND (where #4 is marked)

From probing, we can detect the 1V8 level signal and the baud rate of 115200.

(Courtesy of jamez70)

If you want to hook this up, I suggest you solder on some wires to the pads and run the wires to the front, making life easier to re-assemble the KF.

I suggest you get something like the Breakout Board for FT232RL USB to Serial for hooking this up. Note that the KF is 1V8, so when you want to connect this unit (default 3V3), you may want to use a level shifter, or simply find the VCC on the KF and loop that back that through the VCCIO on the Sparkfun-converter. Sending 3V3 directly into the KF could possibly seriously hurt it!

If you want to construct a simple voltage divider, simply get two resistors and get your soldering gun out. According to Vout = Vin * Rb/(Ra+Rb)

Voltage divider circuit (courtesy of calculatoredge.com)

Vin: 3V3

Vout: 1V8

Ra: 10 kOhm

Rb: 12 kOhm

If you need more UART details, here are some tips:

Baud: 115200

Bits: 8

Parity: None

Stop Bits: 1

In the work to get a booting 3.0 kernel on the KF we need some low level access to debug since the USB initializes way later in the kernel sequence. I did some research on the OMAP4430 (the CPU in our dear KF) to try and find out where the UART interface might be accessed.

Looking at the datasheet we get a feeling of all the ball points ("pins") on the CPU. (Observe that this is seen from under the CPU)

OMAP4430 ball bottom layout

By then looking at the UART table TX pin numbers I try to get a feel where they might be located on the chip.

UART 1, 2, 3, 4 table

Finally, I cross referenced the UART table with TX pin and physical position on the board. The colors represent UART 1 TX, UART 2 TX and UART 4 TX. UART 3 doesn't seem likely to be mapped.

UART 1, 2 and 4 TX pin guesses

Observe that these are all estimates, but should narrow the search down (unless they're mapped somewhere way outside of the CPU area that is). I haven't had a chance of testing any of my guesses yet, but I thought I'd at least post my thoughts to get the ball running.
[Kindle Fire Android Development] pokey9000:
I'd put money on the four solder pads near the edge on the back (lcd facing) side.
[Kindle Fire Android Development] csholmq:
Where exactly? Could you describe more in detail? If you're referring to the ones on the right, I'm pretty sure they are for the two speakers.

Courtesy of iFixit.net

I opened my attempted to probe my KF one more time today. It was a close call where I tried finding the TX amongst the bigger solder pads and a spark went off. Luckily, an unplug/plug of the battery connector booted it right up again. My probes on my multimeter are waaay to big for all the small dots. Hopefully, somebody has some more fitting equipment for the task.
[Kindle Fire Android Development] Buffet_of_Lies:
I'd be willing to shave my pet poodle that he means the four solder pads in the middle on the right side of your image.
[Kindle Fire Android Development] csholmq:
Yeah, I just realised that I had been flipping it the wrong way in my head :) The pads on that side looks very promising! I'm not sure how I'm gonna test out the pads without disconnecting everything from the board. Our best bet is probably to solder some wires and test directly on them. Won't do that on my KF atm though. Too dependant on it for my lecture slides :)
[Kindle Fire Android Development] Buffet_of_Lies:
Yeah. I don't blame you. I'm a big fan of circuit-bending but you usually use old junky electronics, not a brand new state-of-the-art device like this. Not really willing to go near this thing with my soldering iron at this point. But something else I noticed is that on a photo of the OTHER side of that board... there's a serialnumber/MAC address sticker right smack on top of where those four solder pads are. Totally screaming in an attempt to hide where the traces are going!

Something else of interest is the closeup photo of the wifi/bt chip:

What I've long suspected is that the bluetooth isn't wired onto the motherboard. Looking at the image you posted above it's on the upper left side and darned if I don't see some empty component spaces!
[Kindle Fire Android Development] csholmq:
I'm no kernel dev. But for those who are, it would certainly be worth looking under the sticker! Assuming the UART is TTL, I recommend getting Teensy USB dev board or something similar. Certainly helps with the debugging. I have one and it works great (it's compatible with the Arduino IDE).
[Kindle Fire Android Development] pokey9000:
The Teensy's great, and would probably work if you're running it at 3.3V. The serial port on the Fire should be 1.8V, and the ATMEGA32U4 at 3.3V should have a suitable input threshold. I recommend though getting an FT232R breakout board from Sparkfun if you're going to be hacking serial ports onto modern embedded gadgets. I've heard that the Bus Pirate works too, but I thought the buffer doesn't go down that low.

As for missing components and bluetooth, there are only a couple of no-pop discretes, and some that look like a pull-up/pull-down select. I wouldn't count BT out just yet.
[Kindle Fire Android Development] UberDuper:
There's a lot of busted lcd kindles on ebay for cheap. Probably a good place to start.
[Kindle Fire Android Development] csholmq:
Sure, but the Teensy has analog inputs aswell. So as long as it's below 5 V you should be able to use it to read serial. Even though the KF is just at 1.8 V.

Edit: Actually, it looks like it reads high signal in above 0.7*Vcc, which makes 3.3V a no go - as with the Teensy :/ At least with proper serial communication.
[Kindle Fire Android Development] Buffet_of_Lies:
In the interest of clarity, the KF is 5 VOLTS at 1.8 AMPS not 1.8 Volts..
[Kindle Fire Android Development] csholmq:
What? But the battery is just 3.7 V.
[Kindle Fire Android Development] Buffet_of_Lies:
I stand corrected.
[Kindle Fire Android Development] csholmq:
I see. I read your post in the other thread now. You referred to your USB charger? Yeah, that sounds about right. The KF is 1.8 Volts though.

When you talk about Amps (current) you almost always talk about "max current". I.e maximum discharge current from the battery or maximum load current from charger adaptor.

Btw, I found a great piece of looking breakout board. UART to USB micro for basically no money at all! It can be driven on either 3V3 (standard with jumper), 5V (from USB) or Vcc directly from device (1.8, 3.3 etc etc).

Now I just need to find a KF motherboard. All the broken screen units gets hogged on Ebay...
[Kindle Fire Android Development] pokey9000:
That's exactly the one I was referring to. I've used mine on a Nook Color and Nook Tablet (both 1.8V I/O) and it works great.
[Kindle Fire Android Development] csholmq:
Chatted some with Hashcode on IRC. He found lines suggesting UART 3.

11:55 <@Hashcode> if ((up2->pdev->id == CONSOLE_UART)
11:55 <@Hashcode> #define CONSOLE_UART UART3

As I didn't find any dots likely to be mapped next to the CPU, this might suggest that they are actually mapped somewhere else. Easy to access maybe?

So our best bet atm are the 4 pads on the right middle back ("under" the touch controller). I would love to have a look under the MAC sticker on the top. To see if it hides something interesting.

UART 3 (serial) pads estimates. TX/RX/GND/VCC (not in order)
[Kindle Fire Android Development] csholmq:
Chatted some more, this time with UberDuper. He gave me some hands on proof that all 4 UART are defined and UART2 is actually up and running!

I was afraid that if everything was disabled, it would severely obstruct finding the port. I'll try to get my hands on some tech as soon as I can to have a look.

# cat /proc/interrupt

102:	0	0	GIC serial idle
103:	0	0	GIC hsi_dma_mpu
104:	0	0	GIC serial idle
105:	0	0	GIC serial idle
106:	16	0	GIC serial idle, OMAP UART2

# dmesg

<6>[0.201904] omap-hsuart.0: ttyO0 at MMIO 0x4806a000 (irq = 104) is a OMAP UART0
<6>[0.202148] omap-hsuart.1: ttyO1 at MMIO 0x4806c000 (irq = 105) is a OMAP UART1
<6>[0.202362] omap-hsuart.2: ttyO2 at MMIO 0x48020000 (irq = 106) is a OMAP UART2
<6>[1.437225] console [ttyO2] enabled
<6>[1.441101] omap-hsuart.3: ttyO3 at MMIO 0x4806e000 (irq = 102) is a OMAP UART3
[Kindle Fire Android Development] UrticantOwl:
A thread popped up yesterday that seemed to be relevant to this one.

KF Serial Port

Apparently you all were right about it being at the 4 pads on the right side... but what next?
[Kindle Fire Android Development] ttabbal:
Now we need kernel devs to connect up to it and get the 3.x Android kennel booting. Hashcode said he's getting the gear for it. I've got some stuff that should work, so I might get into it as well. I'm pretty busy though, so not sure how much I can contribute...

What's the voltage level this CPU uses for serial? 1.8? If it can take 3.3 on those pins, I'm good to go. If not, I might need to toss a level shifter in there...
[Kindle Fire Android Development] death2all110:
OP in the thread link UrticantOwl posted said 3.3v and I plan on getting the gear soon. Probably from sparkfun or something.
[Kindle Fire Android Development] csholmq:
I updated the OP with new details. I would be careful with 3V3 as the KF is 1V8. You don't want to wreck it!
[Kindle Fire Android Development] Houndog101:
The charger says it is 5 Volts at 1.8 amps, and on your pinout, which pin is 5 volts in ? You spec pins 3 and 4 as ground, one has to be 5 volts in..
[Kindle Fire Android Development] csholmq:
What? USB has nothing to do with this.

The charging current of 1.8 Amps is not in any way the same as the KF operating voltage of 1.8 Volts.
[Kindle Fire Android Development] Houndog101:
Reread my post,, The CHARGER is rated at 5 volts, 1.8 amps. That means one pin of the micro-usb plug gets 5 volts....:rolleyes:
[Kindle Fire Android Development] csholmq:
I'm not following. How is 5 V relevant to the UART?

Check out my post in another thread for info about the USB connector. I don't quite understand what you're getting at.
[Kindle Fire Android Development] Houndog101:
Its not, I'm referring to the other 2 pins that supply charging voltage, pins 3 and 4. Which one gets the 5 volt charge, 3 or 4 ? Thanks for your reply tho..
[Kindle Fire Android Development] csholmq:
Those are ground (GND). No 5 V on either of those.
[Kindle Fire Android Development] Houndog101:
My bad, I'm referring to the micro-usb port pinouts..:o
[Kindle Fire Android Development] riverzhou:
any news about 3.0 kernel?
[Kindle Fire Android Development] Hashcode:
My spark fun device should be here in a day or so. Fun times!
[Kindle Fire Android Development] jamez70:
Would you like me to probe these pins and do a scope capture if they are uart pins?
[Kindle Fire Android Development] Hashcode:
I think thats a great idea if its not too much of a hassle.
[Kindle Fire Android Development] jamez70:
Well I did this in busybox on the board:

echo hello > /dev/ttyO0;echo hello > /dev/ttyO1;echo hello > /dev/ttyO3

and probed every pin/pad you had and more... no dice. One was spitting out 23MHz. I may look under the BT chip if I can flip the board over when its on.

---------- Post added 21st February 2012 at 12:56 AM ---------- Previous post was 20th February 2012 at 11:56 PM ----------

I did discover something in the kernel though..

#define BLUETOOTH_UART_DEV_NAME "/dev/ttyO1"

/* wl128x BT, FM, GPS connectivity chip */

struct ti_st_plat_data wilink_pdata = {

.nshutdown_gpio = 55,

.dev_name = BLUETOOTH_UART_DEV_NAME,

.flow_cntrl = 1,

.baud_rate = 3000000,

.suspend = plat_kim_suspend,

.resume = plat_kim_resume,

};
[Kindle Fire Android Development] death2all110:
Jamez70

See my post in the other thread...we found the same thing...

http://xdaforums.com/showpost.php?p=22777384&postcount=19

also: http://gitorious.org/pandroid/gingerbread/commit/07a1ec73727e1faff43b0f35220476b708068ca9
[Kindle Fire Android Development] Hashcode:
In the kernel source both BT and the serial port are not set / commented out.

I can set both to active and build a test kernel if you want to do some probing.
[Kindle Fire Android Development] death2all110:
Sure build a test kernel. shoot me a zip with the zimage and ill test her out.
[Kindle Fire Android Development] riverzhou:
I will build a 3.0 kernel for kindle fire. Can you test it for me?

I need the boot output.
[Kindle Fire Android Development] death2all110:
i havent ordered the stuff from spark fun yet, so i cant probe the UART ports
[Kindle Fire Android Development] jamez70:
I am unfortunately tied up working tonight but I can tomorrow evening. Is that ok?
[Kindle Fire Android Development] riverzhou:
OK. Thanks a lot.
[Kindle Fire Android Development] jamez70:
What command line? The kernel didn't have any console output

console=ttyO2,115200n8 is what I have
[Kindle Fire Android Development] riverzhou:
Command line of the kernel is "console=ttyO2,115200n8 mem=463M@0x80000000 init=/init vram=5M omapfb.vram=0:5M" .

I change it to yours and set"Always use the default kernel command string" and build again.
[Kindle Fire Android Development] riverzhou:
If it's no output totally , I think the problem is the boot.img . The kernel not be started at all.
[Kindle Fire Android Development] csholmq:
I think he got output from the boot loader. He posted it in his post the other day. Maybe you could just switch out the kernel in a know-to-work boot.img?
[Kindle Fire Android Development] death2all110:
Depends on the rom. He needs to use the cm7 ramdisk if using cm7 and the cm9 ramdisk if using cm9
[Kindle Fire Android Development] csholmq:
What I meant was, he should take a boot.img from an ICS build that is known to work. And then replace the kernel in it. But if the boot loader is already giving output, then there's really no issue here.
[Kindle Fire Android Development] death2all110:
He isn't getting output from the bootloader. At least not with the 3.0+ kernel. Look at the output he posted in that post:

...

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.35.7+ (ubuntu@ip-10-174-42-153) (gcc version 4.4.1 (Sourcery G++ Lite 2010q1-202) ) #1 SMP PREEMPT Tue Jan 10 06:22:28 UTC 2012

...

The output he posted was from before trying the 3.0 kernel.
[Kindle Fire Android Development] csholmq:
One messed up battery pin and a freshly built kernel later.

:)
[Kindle Fire Android Development] Hashcode:
Let the games begin:

http://pastebin.com/6tEB3PBr
[Kindle Fire Android Development] fattire:
Congrats.. nice soldering, tex!
[Kindle Fire Android Development] riverzhou:
wow....

Nice news.
[Kindle Fire Android Development] Veritass:
I'm not sure what any of this means o.o
[Kindle Fire Android Development] jmcoffey:
It means the uart is working. So now we can finally get a working 3.X kernel
[Kindle Fire Android Development] xzjn9p:
very impressive
[Kindle Fire Android Development] animefun135:
Linux version 2.6.35.7+ (hashcode@SCOTTML-UNN)

where is 3.0 kernel? just 2.6.35
[Kindle Fire Android Development] jearl75:
Give it time, this all just happened like 5 hours ago. Have patience
[Kindle Fire Android Development] kraftwerk2020:
Awesome!!!
[Kindle Fire Android Development] intersectRaven:
This is great news! I feel I won't even get a chance to test my backport before a 3.0 kernel is released! :)
[Kindle Fire Android Development] csholmq:
It was 2.30 am local time for Hashcode when he tried it. He needs to build the 3.0 with enabled U-boot, UART etc before debugging.
[Kindle Fire Android Development] lovejoy777:
awsome work guys.

wish I could help, the only way i can is if you need something testing, I'm willing to try anything risky.

thanks for your work, you guys sound like wizards.:-)
[Kindle Fire Android Development] Hashcode:
But, you'll still be able to do your magic to any new kernel I can put out. :)

My skills are still pretty rough.
[Kindle Fire Android Development] Veritass:
What's the difference of a 2.X kernel and a 3.X ?
[Kindle Fire Android Development] uoY_redruM:
Full on HWA for one :D (if I'm not mistaken)
[Kindle Fire Android Development] jmcoffey:
Its like the difference between Windows XP and 7. A bunch of asthetic upgrades and a lot of different code. And yes, hopefully full HWA. :)
[Kindle Fire Android Development] treUse:
It's a kernel upgrade, not a OS upgrade, everything changed is under the hood, so to speak.
[Kindle Fire Android Development] AlexDeGruven:
Wow... Just wow.

Anyway, ****post aside. This is great stuff.

I think I'm going to have to pick up a broken Fire and repair it so I can play with all of this without messing up my stock Fire.
[Kindle Fire Android Development] death2all110:
Exactly what I was planning on doing. xD
[Kindle Fire Android Development] csholmq:
I update the OP with a simple voltage divider circuit. There was one mentioned earlier in the thread, but my calculations indicated it was way off.
[Kindle Fire Android Development] Peowraaku:
The FT232 datasheet advises against connecting VCCIO to a supply originating from a different source than VCC. They probably don't want you to have VCCIO powered while VCC isn't. I'd suggest using the voltage divider (or an actual regulator) to drop USB5V down to 1.8V for VCCIO.

I also dug through the OMAP4430 datasheet expecting to find an absolute max rating that would make all this seem frivolous. Unfortunately it is not clearly stated. It seems the inputs are tolerant of 3.80V, but most pins say 2.1V.