Related
Extreme kudos and awesomeness and gratitude to jcsullins and all the folks involved with developing CM10/Android for the TP. Thank you.
I had been watching the forums to figure out a good time to "jump in" and yesterday I took the moments to install CM10.1 (4/18/13) on my TP. I was amazed at how seamless and flawless the installation was. It seemed it took less time to do the install than it did to download CM10 (download was ~100kb (kB?)/s). CM10 came up running without any problems.
Of course, it wasn't without some issues After confirming CM10 was functional (along w/Wi-Fi, etc.) I installed gapps and that's where the problems began. I first tried gapps-jb-20130409-signed (which did not get installed with CM10). After it was installed, I lost the keyboard app (kept getting messages about the keyboard no longer working). I tried suggestions of default/reset and clearing both caches. Didn't fix the problem. Wasn't sure how to uninstall gapps, so I did a complete CM10 reinstall and tried gapps-jb-20130409-signed again. Still no good. I thought maybe it was a compatibility issue (I could never be absolutely clear which gapps would work with which CM version). So, I went with gapps-jb-20130301-signed. Same problems. I then came across gapps-jb-4.2-Gapps-And-Extras-Signed (I changed the name to be sure it would work with ClockWorksMod) mentioned in a posting. This seemed to do the trick. Keyboard remains fully functional.
I'm curious if there are any log files kept on the TP from the install. Each time I installed CM10, I noticed in the messages rolling up the screen that certain directories couldn't be found. And I think a few of them were related to gapps installation. I'd be interested to see what that was about.
The only problem I've noticed in the short time I've played with it is that the Wi-Fi went inactive (and not temporarily). I went into settings and tried to turn it off and then back on. Once I turned it off, I wasn't allowed to turn it on. There are prob'ly 1/2 a dozen or more Wi-Fi sites nearby, but the TP couldn't see any of them. I ended up doing a power down/reboot and that brought back Wi-Fi.
Anyway, I am very pleased with the new OS. And happy to be independent from WebOS, since its future is unknown.
Cheers....Steph
A two years old device with the latest Android, yeah, its definitively a great work!
Log files are saved in the back up and/or in /cache/recovery/last_log . Also do you have the "Keep Wi-Fi on during sleep" setting set to Never? That might be why your wifi is having issues, because I had the same issue when mine was set to Never. Now I usually keep mine set to Always and it hasn't had that issue and doesnt seem to use the battery too much.
Surge1223
Im curious, were you testing CM10 or CM10.1?
Go and read a guide again, you're installing the wrong gapps. The ones it specifically says not to use.
You need this one:
http://goo.im/gapps/gapps-jb-20121011-signed.zip
Hello everybody,
I have been waiting a bit until posting this issue to see if future nightly builds of Cyanogenmod solved the problem but to no avail, I already posted on their forums but so far no one has been able to figure out the problem... not that they tried.
I'm using an international Galaxy note (n7000) and these issues have been popping up since last month.
The main problem comes up when using the android keyboard and listening to music at the same time, the phone just seem to struggle a lot, music begins to stutter and usually the phone just becomes unresponsive and I have to force reboot the whole thing. A pain in the neck. Lately the phone just hangs whenever it feels like it and I have to reboot it, it usually happens twice a day.
Sometimes you're able to come back to normal after a few minutes but rarely.
The problem was even worse while using SwiftKey, now I'm back to just using the normal android keyboard but still the issue pops up almost every day. I already did a wipe data/factory reset, no avail.
Any thoughts on this?
Thank you in advance.
Post a log. Which ROM where you on before flashing CM.
sounds like a memory leak, try newer versions or trace down the issue. Check which apps consume most and cpu when it occurs.
Check as previous poster said logfiles
Sent from my GT-N7000 using Tapatalk 2
CM 10.1.3-N7000 bluetooth issues
Hello,
I'm using CM 10.1.3-N7000 and I really love it, but I'm forced to use another ROM, just because of the carkit compatibility via bluetooth. The sound is extremely bad.
Does anyone know if it's fixed in later versions or earlier versions?
Are there other ROM's, ot based on CM without the bluetooth problem?
I'm really searching since two days now to find a bluetoothfix, but can't find it.
Pairing and so on is no problem at all, it's just the soundquality that is terrible. (it was not the case with my stockROM)
thank you for giving me some advice!
I switched to Omnirom and I think the problem has been solved now.
If I see that the same problem is back as it was with CM, I will come back to that.
According to the thread on the Official Sony Support Community by Lemon and updated by me, Here a thread trying to list all troubles on the 4.2.2 Official Update.
If you're using a custom ROM do not list your problem here because that can be specifically a problem on your ROM.
Gracenote Update
I had approxamitely 3200 songs in my library. I attempted to update the artwork and music info using the integrated 'Download music info' option (powered by Gracenote). This repeatedly fails and crashes, and somehow managed to wipe approximitely 40 artists from my library of 150 artists. I now only have 108 artists, and have lost a lot of music, which I had paid for or ripped from CDs. I now have to do rip these all over again, and I've also wasted a considerable amount of money on MP3s which have now been wiped by shoddy software!!! I just tried to update some more files, just this moment, and while it managed to update beyond 82/800 tracks, it then failed and gave me a 'Network Error' and advised that 2 tracks had been updated - despite that it had already attempted to update more than 82 tracks!!! It's massively buggy. Not going to use it anymore in fear that it wipes more of my library.
Walkman App
Sometimes shows '-1' artists in library. When tapping into the Artist list and coming back out again, this updates and shows the correct number of artists. Why would it EVER show that I have '-1' artists in my library?!?
Android Become Slow
I've had it after the update, if you feel that your android is very slow since the update, just go to the settings, select applications and "desactivate" some useless app that eats memory, be carefull what you're desactivating, you don't need to be rooted for doing that, that helped in my case.
Earpods/Headphones Compatibility
My previous handset was the 2011 'flagship' Xperia Arc. The stock headphones which came with this handset are of a much better build quality (and tangle a lot less easily) than the stock headphones which came with the Xperia Z. However, upon connecting the Xperia Arc headphones to the Xperia Z, I get a message saying 'Headset not supported. Use another headset or visit the Sony Mobile support site for more information'.
Many earpods/headphone seems to not be supported anymore under this update, Sony needs to fix that quickly that's really annoying.
XDA Threads : http://forum.xda-developers.com/showthread.php?t=2340877
http://forum.xda-developers.com/showthread.php?t=2355500
MBS-100
Everytime I connect over Bluetooth to my MBS-100 (first generation) my WiFi crashes after about 4 minutes. Every time. This does NOT happen with my MBS-200. Seems Sony haven't put enough effort in testing support for their older devices/products, this is clearly also the case above with the stock Xperia Arc headphones.
SD Card bug surfacing
The Sony Xperia Z is suffering from a persistent hardware failure, which is inserted SD cards unusable. Most of time we need to reformat/restore it and in worst cases the SDCard is dead and you need to buy a new one.
I have this as well that asks me many times to check and verify my SDCARD when i use the MSC connection, if i don't do it i can't copy files on it.
XDA thread : http://forum.xda-developers.com/showthread.php?t=2352245
Photo Album uploading with Facebook for Xperia
Tried uploading 31 pictures using the integrated share to Facebook for Xperia feature last night, on a FAST connection (Download Speed: 44.9MBPS / Upload Speed: 7.4MBPS) - 1 picture uploaded, service failed. Tried again, 2 pictures uploaded, service failed. Tried again, notification said 'Uploading pictures for about 18 minutes, before timing out and failing without uploading any pictures. Any pictures that did upload, did not upload in order either. After repeatedly attempting this about 30/40 times, I managed to upload about 17 of the 31 pictures, and had to connect by USB in order to do the rest. Seems like this feature was slapped on without any REAL testing by Sony.
Lockscreen Bypass
It is possible to bypass the lockscreen by typing '*#*#7378423#*#*' and doing an NFC test in the Service Tests menu (http://www.youtube.com/watch?v=LLq1gxIt5YQ) - this renders the handset COMPLETELY UNSECURE.
XDA Thread http://forum.xda-developers.com/showthread.php?t=2206033
Socialife
Never updates automatically. Sometimes updates manually. Sometimes doesn't. Just tested manually refreshing this moment, today being March 26th, and nothing is showing beyond the afternoon of March 25th.
Stamina Mode / Battery Life
When first experiencing issues with my handset, a Repair was advised by support staff on the forum here, and official Sony Customer Support Staff. Following this repair, by battery life at 100% showed 4 DAYS AND 12 HOURS. A week later, on 100%, my battery life dropped to 2 DAYS AND 8 HOURS. Another week later, on 100%, my battery life is now showing 1 DAY AND 1 HOUR. All of these figures are with Stamina mode turned on. I haven't added anything to the handset to affect performance, it's simply degrading of it's own accord. Which makes me wonder why the support staff repeatedly assure us on these forums that 'the battery life will improve after a few charging cycles' - this is not the case, and there is CLEARLY a Power Management issue, which needs to be resolved.
LED Notification
Fortunately, I am not experiencing the LED issue that others have been. But it should be listed as others have been experiencing it.
Sleep of Death
Fortunately, I am not experiencing this issue. But it should be listed as others have been experiencing it, special mention for people who hard-bricked their phone, do not include that problem.
WiFi Signal Issues
Fortunately again, I am not experiencing any major WiFi issues. However, when uploading photos using Facebook for Xperia last night, it knocked off my WiFi twice for no reason. And I've also documented my WiFi issues in combination with Bluetooth to MBS-100 above.
Accessories
The 2011 flagship Xperia Arc came with quality headphones, a charger, and a mini-HDMI to HDMI cable for outputting to HDTVs. The 2013 flagship Xperia Z came with cheaper headphones, a charger and NO cable for outputting to my HDTV. I expected this to be included in the package, given the lofty pricetag, but now I realise I must go and buy an 'MHL Cable' - something I didn't even know existed until after I purchased the device. Thank you for not including this cable Sony.
If anyone has any further legitimate bugs/issues to add to the list above, let me know and I'll keep the OP updated.
If you know a fix i'll add a green comment.
Severity color :
Low
Medium
Critical
Fixed
Hi.
I'm on .423 and I don't seem to have the lockscreen bug.
In fact, I cannot dial any MMI codes using the emergency dialer.
On a side note, why is this tagged as [HELP THREAD]? There's already the help thread that I've started under stickies in the Q&A Section.
kgs1992 said:
Hi.
I'm on .423 and I don't seem to have the lockscreen bug.
In fact, I cannot dial any MMI codes using the emergency dialer.
On a side note, why is this tagged as [HELP THREAD]? There's already the help thread that I've started under stickies in the Q&A Section.
Click to expand...
Click to collapse
You're lucky, anyway that's interesting, what kind of ROM do you use?
For the thread i've edited with [BUGS LIST] it was just for being easily found for people, if you have a better idea for my thread i'm open to any suggestions.
QualQuek said:
You're lucky, anyway that's interesting, what kind of ROM do you use?
For the thread i've edited with [BUGS LIST] it was just for being easily found for people, if you have a better idea for my thread i'm open to any suggestions.
Click to expand...
Click to collapse
Stock ROM for C6603 from here.
[BUGS LIST] seems appropriate enough?
EDIT: There's also this SD Card bug surfacing. I have this problem too.
A bit short on patience right now, so haven't tried fixing it yet. You could add this to the list.
Thanks a lot, SDCard bug surfacing added to the list with critical severity.
musick oluarb
I'm Lemon, and these bugs have nothing to do with 4.2.2
I posted this in March, about 10 day's after the handset was launched, listing all the issues I found in the original 4.1 firmware, it's been updated a few times since.
With 4.2.2 I've only noticed a weird support issue where the software completely wiped me sd card of its own accord. I've lost ****loads of stuff as a result. It's only happened once though.
Still noticing the Walkman skipping during playback...
Some Home screen stuttering, nothing out of the ordinary for Sony.
Otherwise, 4.2.2 is much improved.
how are the lack of accessories, notably a mhl cable part of the bugs/issues with 4.2.2 ?
I don't know how to describe it wxactly but since the update (2 days ago), my phone has became super slow.
On 4.1 it was great never experienced any lag.. but now it feels like I'm holding my tired old phone again..
It goes from opening apps, through unsmoothly scrolling and floating around, to the lockscreen it self which can take about 3-8 seconds to show up image from black after pressinv power button to wake him up..
Also for unlocking, sliding up to move from lock screen to home screen can be laggy, stucky, and takes time...
Furthermore, WiFi signal (or atleast the icon showing) is poor and barely reaching my router when I'm 3 meters away..
As for not getting anything exciting from the update, or any changes, cool features from stock 4.2 (hmm som1 said notification toggles?) , I'm pretty disappointed, I would return back if that possible
Sent from my C6603 using xda premium
mcjordan92 said:
I don't know how to describe it wxactly but since the update (2 days ago), my phone has became super slow.
On 4.1 it was great never experienced any lag.. but now it feels like I'm holding my tired old phone again..
It goes from opening apps, through unsmoothly scrolling and floating around, to the lockscreen it self which can take about 3-8 seconds to show up image from black after pressinv power button to wake him up..
Also for unlocking, sliding up to move from lock screen to home screen can be laggy, stucky, and takes time...
Furthermore, WiFi signal (or atleast the icon showing) is poor and barely reaching my router when I'm 3 meters away..
As for not getting anything exciting from the update, or any changes, cool features from stock 4.2 (hmm som1 said notification toggles?) , I'm pretty disappointed, I would return back if that possible
Sent from my C6603 using xda premium
Click to expand...
Click to collapse
Yep i've seen many people complaigning about that too, btw you can disable some useless app on settings => applications, select one and choose "desactivate" that's helepd so much for me.
what in the world.. and .423 just came to my phone updates and it's now stuck in the notification bar but seeing all these makes me doesn't want to update it anymore ._.
From last night i am facing a problem where when I connect my headset (samsung) to my xperia z1 it displays the error *Headset not supported. Use another headset or visit the Sony Mobile support site for more information.*
I used to use this headset everyday but unfortunately it had stopped working.
Further, if i use any other headset, it displays the same message.
I have not updated my phone nor have i installed any mod or app.
Can anyone tell me the fix please?
Thank you!!
Hi guys,
Thought I would start a thread for users of CyanogenMod 12 for HTC One Mini 2 (memul).
I have installed a nightly dated 24th February 2015. It seems to be working great, my only issues have been:
After phone restart, the first time you call someone you cant hear them. Call them again, the problem is fixed and doesnt seeem to come back for that contact. (will happen again for other contacts the first time you call them though).
Camera is very laggy and doesnt respond well at all...the viewfinder is super stuttery and laggy and when you hit the take a picture button it can take a second or two to respond. I dont use the camera much so it doesnt bother me.
Have had some problems with the music player not outputting music to the headphones after a while, but taking the headphones out, pressing play so it plays out the speaker, then putting the headphones back in fixes this. Again,
not a big issue.
Official TWRP stops working after going through setup, but factory reset from within CM12 fixes it if you do have to re-flash or something.
So I recommend CM12 latest nightly for our phone, its better than CM11 and actually had less problems than the Release channel rom for our device (CM11). Although that ROM says it has no known issues, there are known issues that have not been noted on the wiki.
Hey thanks for doing this, I am considering CM12 on my phone too. i use the loud speaker and the camera a lot, does this impact the sound quality? i really enjoy the boom sound on this phone.
ECEng said:
Hey thanks for doing this, I am considering CM12 on my phone too. i use the loud speaker and the camera a lot, does this impact the sound quality? i really enjoy the boom sound on this phone.
Click to expand...
Click to collapse
Loud speaker works fine, and one of the great things about cyanogenmod is the built in system level equalizer, so boom sound equivalent is built in. Camera, on the basis of the build i am using from mid Feb, is not so good...actually the pictures are not so bad but the actual viewfinder is very laggy and pressing the take shot button is slow to respond. It could be fixed in newer nightlies, I have been away from home for over a month but when i get back ill flash a new nightly.
snorglamp said:
Loud speaker works fine, and one of the great things about cyanogenmod is the built in system level equalizer, so boom sound equivalent is built in. Camera, on the basis of the build i am using from mid Feb, is not so good...actually the pictures are not so bad but the actual viewfinder is very laggy and pressing the take shot button is slow to respond. It could be fixed in newer nightlies, I have been away from home for over a month but when i get back ill flash a new nightly.
Click to expand...
Click to collapse
Thanks for the advice, I installed march 25th build last night.
From your first post, only problem i experienced was the camera, its still very laggy, and the picture quality dose not compare well to the original. I have tired third party camera app but no joy, similar issues. Other than that, happy to say every thing else is working fine, i will update regularly to see if camera improves.
Hi all,
I'm using CM12 since 2 weeks. In some case, the phone is very laggy. For example, with Chrome or also when opening new apps, of when i switch from app to other.
Maybe i'm not using the correct boot or recovery or radio.
Can you tell me which one is recommended with the CM12 ROM ?
Thanks.
mlhamdi said:
Hi all,
I'm using CM12 since 2 weeks. In some case, the phone is very laggy. For example, with Chrome or also when opening new apps, of when i switch from app to other.
Maybe i'm not using the correct boot or recovery or radio.
Can you tell me which one is recommended with the CM12 ROM ?
Thanks.
Click to expand...
Click to collapse
Hi there,
I have been flashing the latest nightly. I think we need to log a JIRA issue for the camera, but I havent checked if someone already did. It doesnt seem to be getting better does it?
Dont use chrome...if you dont like the cyanogen browser, try firefox XD
The best recovery is TWRP, see the other posts in our part of the forum about this. Make sure your get the U-RA version of TWRP as the official TWRP page doesnt list our device for latest versions.
Also I should note that the calendar doesnt work in this ROM in offline mode, which is true for all Cyanogen ROMs i believe. But the solution is to install from DroidForge the offline calendar account, and then you can enter items in the calendar without google calendar, or sync USB with outlook etc (latter requires purchase of sync program separately to go on your PC).
Bad news for CM12 on memul: the only developer u-ra has stopped working with our device. So there are no new nightlies anymore since 04/11 and we don't know when it will be going on.
Look here: http://forum.xda-developers.com/showthread.php?p=60126091
corbeau56 said:
Bad news for CM12 on memul: the only developer u-ra has stopped working with our device. So there are no new nightlies anymore since 04/11 and we don't know when it will be going on.
Look here: http://forum.xda-developers.com/showthread.php?p=60126091
Click to expand...
Click to collapse
That is bad news alright, Is there any way for me to get back to stock rom and wait for official lollipop release? I am quiet new to this.
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.