I am suspecting this is an issue with square and not the ROMs, since headphones work, but I am just wondering if anyone here who is using a 5.0/5.1 ROM has managed to get their square reader working?
Its driving me nuts... Everything else about aicp/cm12 are solid and I use aicp as my DD right now, but I hate having to carry a second phone with me just for square when I'm working.
Fadelight said:
I am suspecting this is an issue with square and not the ROMs, since headphones work, but I am just wondering if anyone here who is using a 5.0/5.1 ROM has managed to get their square reader working?
Click to expand...
Click to collapse
Square works for me on CM12. I haven't tried it yet on CM12.1 but will try in the next few days.
Until AICP in the past couple of days, I had been running CM12 for quite some time. It doesn't recognize the reader, but headphones work. If I am the only one having a problem, I am even more confused now than I was before.
Related
Hi. I run serendipity 5.1 on my Captivate and I recently purchased a basic 3.5mm to AV red white yellow cable. When I set the settings to NTSC, nothing works. The image is garbled and the sound is a super loud buzzing. Has anyone else attempted to use tv-out on their captivate running an i9000 based rom?
I read somewhere you have to switch the wires. Have you tried that yet? Like red in yellow and so on. I am waiting for my cables myself.
I've used it successfully on phoenix and firefly
Sent from my GT-I9000 using XDA App
Just curious if anyone has been able to get this feature working on Andromeda. I have had no success at all, even switching the connectors (red/yellow)...
I had the same problem. All I did was switch it to pal and once showing tv out, switched back to ntsc.
smokestack76 said:
I read somewhere you have to switch the wires. Have you tried that yet? Like red in yellow and so on. I am waiting for my cables myself.
Click to expand...
Click to collapse
When you get your cable can you try with an i9000 based ROM such as Serendipity?
Well I have attempted all combinations of Red White and Yellow in each slot. They all show garbled images, with certain combinations have different characteristic garbled images. I think the problem may just be the ROM here. I have seen youtube videos of this working on normal Captivate ROM's but i have never seen it done with an i9000-based rom (at least that i know of) I'm just trying to confirm if at least one person CAN get it to work on an i9000 based ROM (Like Serendipity).
I use di11i's roms and it works I have to switch red and yellow though.Now they just need to fix the wii controller app so I can play my retro games comfortably
I have the same issue abraham. buzzing audio and scrambed video. I can see the text 'tv-out' but everything else is black and white scrambed.
I'm on stock rogers 2.2 though in canada.
previously it worked.
please post if you find what is causing this.
I'll try switching to pal and back but I doubt that's it.
PAL is simply the tv mode in the uk. I don't think canada uses PAL im almost certain its NTSC. One if these days I will flash another rom and see if it works. Is di11i's rom based on normal or on i9000 rom's?
Sent from my SAMSUNG-SGH-I897 using XDA App
yes canada is ntsc, how backward you think we are? lol
but maybe switching pal back to ntsc may fix it.
dunno. i run phoenix 4.5 rom and have NO PROBLEM with vid out. my cables red is video yellow is right audio but.. meh...
Trusselo said:
i run phoenix 4.5 rom and have NO PROBLEM with vid out.
Click to expand...
Click to collapse
Yeah, phoenix 4.5 is not an i9000 ROM. I'll have to flash one of those to try it out then. I still would like to see if any other ROM's that are based on the i9000 work or don't work. Cause if all i9000 rom's do not support tv-out, then thats something they need to say in their ROM thread.
I'm running TD 9.1, and prior was on 8.0. Tried both stock kernel, and a few other ones with no luck. At first when the sounds starts playing, the left speaker works fine, then with in a sec, it will fad to almost nothing. Is this something someone else has encountered? For all I know it has been like this since day one.. But I don't believe so.
Edit: I have also tried clean installs. i have not tried other roms yet.
Double edit: My xda search is not working, but google did for me. Found one other person having somewhat the same issue, but it was never answered. I hate to bump an old tread like that, after i have posted mine already.
[Q] HTC One speaker problem - One speaker turning off / mono sound
vwmaniacx said:
I'm running TD 9.1, and prior was on 8.0. Tried both stock kernel, and a few other ones with no luck. At first when the sounds starts playing, the left speaker works fine, then with in a sec, it will fad to almost nothing. Is this something someone else has encountered? For all I know it has been like this since day one.. But I don't believe so.
Edit: I have also tried clean installs. i have not tried other roms yet.
Double edit: My xda search is not working, but google did for me. Found one other person having somewhat the same issue, but it was never answered. I hate to bump an old tread like that, after i have posted mine already.
[Q] HTC One speaker problem - One speaker turning off / mono sound
Click to expand...
Click to collapse
I have the exact same issue. Tried million ROMs, sound patches and tricks but nothing change. The easiest way to see the difference between the two speakers is to run the Audio Test using HTC Function Test by dialing *#*#3424#*#*
Finally, I managed to get S-Off and now I'm going to get back to 100% stock flashing RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.exe, I'll do the test again and update the post.
EDIT: I'm full stock and it didn't fix it I guess I have to send it back...
BTW, what did you do? Did you fixed yours?
Running Sinless 5.1.5 now with elemental, everything works 100%. I guess for some reason my phone just didn't like TD, we all know they have a personality of there own..
Sorry for the long wait before response, I don't pay attention very well.
Newbie here. I've been an avid WebOS fan since the first Palm Pilot. My TP just isn't being used anymore, so this week I used JS's Toolbox and installed Lollypop cm12 on my TP. It works pretty good and thanks to all who worked on the project. I have noticed however that the team is now working on Marshmallow. Does this mean that development on CM12 is coming to an end? (and that the camera may never work on CM12?)
I would ask in the development forum but as a newbie I can't post there yet.
Thanks again to all.
CM12 for touchpad was dead long time ago.
I am typing on my touchpad running marshmallow which runs better than lollipop.
Sent from my Touchpad using XDA Premium App
So everything was working on CM11 but CM 12 they never got it all to work so they moved on to Marshmallow? OK I guess I try and install Marshmallow and see how that goes. Lollipop is working fine but just has no camera so if there is no camera in Marshmallow then whats the difference.
Thanks for your reply.
Tracks650 said:
So everything was working on CM11 but CM 12 they never got it all to work so they moved on to Marshmallow? OK I guess I try and install Marshmallow and see how that goes. Lollipop is working fine but just has no camera so if there is no camera in Marshmallow then whats the difference.
Thanks for your reply.
Click to expand...
Click to collapse
Actually, camera does work on some lollipop roms for the the Touchpad. I have previously used flintmans Evervolv lollipop rom which has camera working. You could give this a try if camera is a priority for you, although the camera quality on the Touchpad is just not that great. There is only one marshmallow rom so far for the HP Touchpad and it is a Evervolv Rom not a CM rom. Even tough there are still some bugs, its solid for a alpha build. Its worth giving a try.
Do you happen to know which ROM the camera worked with?
Tx
Tracks650 said:
Do you happen to know which ROM the camera worked with?
Tx
Click to expand...
Click to collapse
The latest build for this rom has the camera working:
[ROM] Evervolv | 5.0.0p1 [AOSP Lollipop 5.1.1] [3.4 kernel] [TESTING] With DM
I used a cm ROM, that's why. It's working really well so I might just wait a week or so to see if Evervolv Marshmallow gets the camera working first, if not then I'll try the other one.
Tx for the reply.
WAS working well until....... I changed the keyboard color and turned off the sound for the keyboard typing. The very next time it went to sleep it bricked! Now how do I unbrick it?
Does Bluetooth load right
Sent from my TouchPad using XDA Free mobile app
Ohjustdale1963 said:
Does Bluetooth load right
On which Rom?
Click to expand...
Click to collapse
Tried a hard boot three times, nothing.
Tried a three button hard boot 5 times, nothing.
Plugged into PC, nothing.
Opened WebOS doctor, connected TP, nothing.
Started Doctor and did 2 more three button resets..... on the last one (obviously) the USB symbol showed up..... and WebOS Doctor Crashed.
Then the HP logo showed up, so I left it...... overnight and in the morning the HP logo was still on and hung.
Did another hard three button reset and the tablet booted normally into Lollipop, go figure.
Using cm-12 tenderloin
So it crashed again, went to sleep and wouldn't wake up with connecting it to a PC and doing the three button tango. Time to try Marshmallow.
Got it running again, went back to the default white keyboard and turned sound back on. Haven't had a crash since.
Interesting. I need to dust off my Touchpad and put some Marshmallow on it
Leaving it off the charger but asleep for 28 hours, battery is still at 94%. I think thats pretty good.
Tracks650 said:
WAS working well until....... I changed the keyboard color and turned off the sound for the keyboard typing. The very next time it went to sleep it bricked! Now how do I unbrick it?
Click to expand...
Click to collapse
tpdebrick will do the job.
edit:
-------------
If you have an original hp charger, put it away for emergencies. Get a 2-3 amp charger for regular use and hold that hp charger aside for emergencies. I've had an occasion when the hp charger was the only thing that would charge a bricked tp. If the battery is too far gone, the charging circuit won't work with a generic charger. However, generic chargers are fine the rest of the time.
If the tp is bricked, just plug it into the computer (with drivers, web doctor, and novacom), run tpdebrick, and follow the instructions. If the tp wasn't in USB mode, it'll tell you which buttons to press and even when to let go.
If it says there's no TP and you know the TP was previously recognized by that computer (indicating good software setup), then that's when you bring out the hp charger. Let it sit for a couple days and try tpdebrick again.
One final general note. The TP is real sensitive to power spikes, so be very careful when inserting or removing the power. If the USB connector shell gets deformed and allows the plug's pins to short across the connector's pins when plugging, it's 99% likely that the tp will brick.
You guys didn't read my last post, after connecting to the PC, hard three button boot attempts several times, got it booted up, restored to default keyboard, turned keyboard sound back on, and haven't had a crash since.
Nice to know about the HP charger. I don't use it but I have it. I have my TP docked on the TP touchstone charger.
This thread has seemed to get a bit off track. To address the question, TP on L versus M, I recent switched to Evervolv 6.0.1. There are a few glitches (ie. camera and BT not working), but otherwise its been smooth sailing, and the main improvement I have noticed is the battery life improvement (seems Doze works on the TP). I wouldn't use the camera (originally it was pretty bad anyway), and the only BT device I miss so far is the original HP BT keyboard. I have a hunch the dev's will sort out the BT issue eventually.
btw, pretty amazing that my first device running Android 6.0.1 would be an vendor-abandoned 4 year old tablet intended to run webOS.
With cm12....1110 I get awesome battery life, no crashes since I mentioned the above keyboard issue. but no camera. Haven't tried pairing bluetooth to anything yet but it runs. Only issue is wifi cuts in and out inconveniently. But I always had that with WebOS on this tablet too.
Tracks650 said:
With cm12....1110 I get awesome battery life, no crashes since I mentioned the above keyboard issue. but no camera. Haven't tried pairing bluetooth to anything yet but it runs. Only issue is wifi cuts in and out inconveniently. But I always had that with WebOS on this tablet too.
Click to expand...
Click to collapse
Camera works in jcsullins' Lollipop CM12.1 20151116, so I'm not sure if I understood your post correctly. I haven't had any WiFi trouble beyond the WiFi trouble that occasionally crops up in any of my WiFi devices, Android or otherwise.
I'm impressed with flintman's Marshmallow (still in Alpha testing, as of this writing). I think it holds great promise, but it doesn't have a working camera or Bluetooth, yet.
Hi all,
I had my One M7 Sprint for several years, i got an issue that it freeze while i'm using and reboot, then there is no longer appear the status bar. Beside that i got camera issue as well, open the camera app and it quit intermediately after that.
So strange that if i flash back to Jelly Bean or Kitkat, my phone worked again with no camera. The camera seem like cause by hardware issue. Sometime worked, sometime didn't.
Have anyone advise me about this issue?
Thank you!
boomlord said:
Hi all,
I had my One M7 Sprint for several years, i got an issue that it freeze while i'm using and reboot, then there is no longer appear the status bar. Beside that i got camera issue as well, open the camera app and it quit intermediately after that.
So strange that if i flash back to Jelly Bean or Kitkat, my phone worked again with no camera. The camera seem like cause by hardware issue. Sometime worked, sometime didn't.
Have anyone advise me about this issue?
Thank you!
Click to expand...
Click to collapse
Never heard of that, but if you want to really test the hardware, the best thing to do would be to run the RUU and then test it running pure stock. If you still have the issue, then I'd say it's most likely hardware, if not, then you'll be able to use the phone normally. Worth a shot I think.
Hey, no long ago, about 2 weaks or so, I had to replace my broken screen. Everything is fine now, my screen isn't that great tho, but that's okay. But I've noticed something, before I used to have customs roms (mostly mokee os), but when I sent my device to a store to fix it, I reinstalled stock, when I receive it back, everything was great. But then, I got bored of stock, and reflashed Mokee (notice: I tried with LOS 14, MOS 15, MIUI) and then I realized that at random power ups my vibrations stops working. To make it work again, I have to reboot the device a few times. Anyone ever had any issues like that? What should I do? Remember: vibrations works fine on stock, only have this issue with customs roms.
warutzu said:
Hey, no long ago, about 2 weaks or so, I had to replace my broken screen. Everything is fine now, my screen isn't that great tho, but that's okay. But I've noticed something, before I used to have customs roms (mostly mokee os), but when I sent my device to a store to fix it, I reinstalled stock, when I receive it back, everything was great. But then, I got bored of stock, and reflashed Mokee (notice: I tried with LOS 14, MOS 15, MIUI) and then I realized that at random power ups my vibrations stops working. To make it work again, I have to reboot the device a few times. Anyone ever had any issues like that? What should I do? Remember: vibrations works fine on stock, only have this issue with customs roms.
Click to expand...
Click to collapse
I have had a similar problem, the "Vibrate on tap" didn't work with the replaced LCD and custom rom.
vhcolombo said:
I have had a similar problem, the "Vibrate on tap" didn't work with the replaced LCD and custom rom.
Click to expand...
Click to collapse
Did you fixed it?