Related
Ok, so there's a few problems I've had with my phone and ether have gotten recently/haven't bothered to fix.
The first problem is the calibration on the touch screen, normally it's just fine, but if I plug it into the wall charger it gets a bit shaky if I do something like drag my finger and hold it on the screen afterwards without taking my finger off. But as I said before it only happens when I use the AC charger, if I plug it into the USB port of my computer the calibration is just fine.
Another problem that I could live with but would rather fix is the slow startup time of my phone. I run Froyo with a 1.25 GHz overclocked kernal (the one with the wifi fix), and when using this kernal my phone seems to take a very long to boot. The Droid logo will take a long time to appear and transition into the H.A.L. 9000 lookalike eye. After I boot it up and SetCPU starts it's just fine though, is there anyway I can fix this? There is also a question I would like to ask, does anyone know a good program for to-do lists (one with notifications, maybe a widget, etc.), I've looked around on the market and I can't seem to find one that works well enough. Also does anyone know a good program to use the dual camera LED's as a flashlight, I havn't been able to find one that works with Froyo (I used to use Droidlight but because of the fact the camera flash can stay on during videos in Froyo (at least I think that was the problem, I saw it on a forum at one point iirc) it just force closes when I try to open it.
I would appreciate help with these problems if possible, thank you.
I have an HTC pure, running Energy Rom, SPB mobile shell 3.5.5, and XDAndroid.
Here are my questions.
1. XD Android keyboard is t9 and in japanese. I dwnld'd gineger bread keyboard, which didnt change the look at all. (yes, I am sure i had it installed and set up in settings correctly.) So what IME can I use to replace annoying japanese keyboard? Which also has no option to close keyboard (hard key back button works, but will often close app im using)
2. I can make calls, and recieve them, but THERES NO SOUND! no in call volume, period, adjusted every setting I can find. checked my startup .txt file, added suggested controll lines, no change.
3. Sleep button (remapped to end key) works about 10% of the time, only when turning screen off is it 100%, getting screen back on, is a crap shoot. why is this? buttons light up, dim in and out, but no screen response, have to hit it a bajillion times, to get a response, and sometimes the old on/off/power button (top) will turn screen on... and my LED is going nuts, back and forth from yellow to orange, constantly.. I read nearly 25+ pages of the XD android thread, no help there...
4. No droid on boot, Seems I have to boot android from the haret.exe starter, everytime I want droid running, why doesn't it boot with phone?
5. No SD card, I have on in, and its got all my droid related files on the root, but no app 2 sd b/c it doesn't read the card as being mounted.
6. live backgrounds, animated backgrounds arent working either? could be just the device, but idk anything about this..
7. what is the processor speed on a pure, and what is overclocking, what does it do, and should i pursue this with spb, windos 6.5 etc running..?
8. If I can get froyo on my winmo pure, why cant I get it on my aria? and what can you do to an aria? seems like nothing... stupid att?
9. is there a way to speed up android on my pure? should I wipe my phone clean, flash a low ram using rom, and then re install droid?
10. every so often when in market, phone reverts to flying droids spelling xdandroid, and gets looped there. wtf.
It's a big set of issues, hope help is on the way, also, I have searched, ad searched, so please, if you have nothing relavent to offer me in response to my questions, just leave.
Okay, fixed they keyboard issue, but it wont set a keyboard other than the stock one to default, I have to change it every time I type, or select a text box.
Annoying but an improvement.
Still not recognizing my SD card, and the camera isnt working period, been through multiple kernels, fx03 fx02, tried several command lins in my image text.
Still nothing.
Call issue seems to beback and forth, had my g/f call me sitting on the couch, and the call had sound, went through perfect. Went outside, and nothing, n o ring, no nothing, and went to voicemail on her end. visa versa, when I her phone rang, and connected, still no sound. seems to have a 1 in 5-8 sucess rate..
and still having issues with turning on the screen, once off, it takes several try's and multiple button clicks to get any response. Just led flickering and lots of dimming/lighting buttons.
all in all however, the look on my ATT store rep. when i whipped out my PURE, set it next to my aria, and said, "pure has froyo, aria is eclair" he about ****.. "how do you have froyo on a winmo phone??"
Magic
Thanks XDA, you guys are awesome! (plus with my windows rom running i have tehering for wi-fi router, and ability to side load apps into android on here makes it about 10X cooler than my aria, now if only stability, performance, and a better touchscreen, were factors..
Lastly, what can I do about the hardware issues, I realise the Pure must not have a very fast CPU, and WTF is over clocking and what are it's pro's cons'?
Seriously,o one can say anything about this after over one hundred views... wow guys, just wow.
I am right there with you. :/
If you've found any progress with this or a better build, email/add me:
[email protected]
**This could be used as a bump.**
Normally I don't have a problem locating this kind of info, but for TP CM9 it eludes me. I found the link with the tech speak generated list. But I need the info to be a bit more plain english. And couldn't find a known issues list. I would like to check this info to see if I would like to try it out on my TP.
Thanks much.
StoneRyno said:
Normally I don't have a problem locating this kind of info, but for TP CM9 it eludes me. I found the link with the tech speak generated list. But I need the info to be a bit more plain english. And couldn't find a known issues list. I would like to check this info to see if I would like to try it out on my TP.
Thanks much.
Click to expand...
Click to collapse
Known issues are basically the camera and mic don't work, some folks have wifi issues and some don't... and some have issues with the audio acting up when waking from sleep... I myself am happy to say I don't have wifi or audio issues... but camera and mic are driver issues that may never get to work. All in all very stable though
Sent from my cm_tenderloin using Tapatalk 2
If camera and mic are the only problems then I see no reason not to give it a shot. I don't know if I would ever use them.I was concerned that it was missing core functionality making it something one wouldn't use as a daily OS and only switch over to it for test scenarios and then switch back. I have cm9 on my Samsung epic (the one with hw kb). Would the current latest nightly be the one to go with?
Just curious, why are the camera and mic drivers so difficult? I would have thought having them running on WebOS was at least some of the work. I guess porting said work to Android is a completely different ballgame.
I wonder if the wifi/audio issues are still being worked on tho? Or are those of us with those stuck with em forever?
The big thing for me was hardware video decoding. Alpha 1 fixed that for YouTube, and alpha 2 finished the fix for Netflix and others.
If you haven't already, check out the thread at rootzwiki.
I was using webOS by choice until CM9 came out. I switched to CM9, and have been using it as my daily driver since the very first Alpha. I never video chat, but if I wanted to I know I can just boot webOS.
Don't let people here tell you CM9 (or the Kangs thereof) are unstable. Some people continue to spew that we don't have a stable version of android purely because its called an alpha. I don't think it will graduate past alpha without camera/mic support, and that may never happen. Right now, without trying, I am sitting at 587 hours of up time on my TouchPad. I can't think of a better word to use than "stable."
Sent from my Galaxy S II (i777)
Known Issues that I can think of. I know some were mentioned above, but all in one place is good.
Broken, NO FIX:
1) No Microphone
2) No Camera
Partial Workarounds:
1) Audio gets noisy with screen off. Kinda workaround: Turn volume down, only happens at higher volume levels. Or set screen timeout longer/always on while playing audio. No complete fix.
2) Wi-Fi dies or doesn't reconnect. Some people never have a problem, others do. Workarounds: First, set WiFi to always on so it doesn't turn off with the screen. Second, try changing the channel on your router, or if you have 2.4ghz/5ghz switchable, try using the other. If Wi-Fi still dies, toggle it off and back on.
3) Some people report that if the TouchPad fully discharges to 0% they have trouble getting Android to charge properly. Others report that if you reboot the device with it plugged in, sometimes it won't charge. I've experienced neither problem, but the best advice is, charge before the device shuts off fully, and unplug the charger/usb while booting.
Broken, but Completely Fixable:
1) Random crashes. Install CPU Master and raise minimum CPU speed to 384 or 416 depending on which works for you, and crashes go away. Also, don't overclock too much.
Setup Issues:
1) DPI is at 160dpi stock. This works for most things, except a few tablet apps and games will not work properly. Setting DPI to 120dpi fixes everything, but the display quality is not ideal. 132dpi is ideal, but breaks the market after a day or two. Most people use 160dpi or 120dpi.
2) The default launcher, Trebuchet, is NOT compatible with the 4:3 aspect ratio of the TouchPad's screen if you use any DPI other than 160. Why something so easily fixable has not been fixed escapes me, but you will quickly find you need a new launcher. Go Launcher HD is one of a few that are very friendly to the TouchPad.
App Issues (not really issues but you probably want to know)
1) A few apps really, really, really are picky about the screen size and just won't scale right. (see Trebuchet notes above). One example is Politico HD - it forces 16:9 aspect ratio and thus gets cut off. Some apps simply refuse to run. Contacting the developers rarely works. This is probably less than 1% of the apps on the market, however.
2) Some developers simply are too strict on app compatibility on the market, and whitelist only select devices. Getting compatibility from these guys is a longshot. Best option is to install on another device, grab the APK or use Titanium Backup to move the app to the TouchPad.
3) Some games (notably Gameloft is the worst) enforce device compatibility checks within the program itself and it will refuse to run unless you masquerade as an approved device by hacking your build.prop... which is not normally recommended.
Did I miss anything anyone?
Hello, I am having some touchscreen problems with CM9 and 10, but not with webOS. Namely, I think that the tablet is detecting double or even triple taps when none are present.
In CM9, when I execute a longpress (to move an app for example), the tablet just kind of... spazzes out, and in general nothing happens. In CM10 it also does this, and almost everytime, it starts whatever app I was pressing on.
Also, when I try to type in the CM10 keyboard, 2-4 characters are being entered at a time, unless I touch incredibly lightly, and even then, I will often get two.
There are other symptoms along these lines, like trying to pull up the notifications, etc. This does not appear to be isolated to any one portion of the screen, it is happening everywhere I could check it.
This CM9 versions I have tried are the nightly 0715, and whatever the latest nightly was about a week ago. The CM10 version I am using is jcsullins' 12/16.
As stated, I have zero issues in webOS.
Is there any way to change the touch sensitivity? Am I a moron and doing something wrong?
Thank you for your help/advice.
To clarify, I think this might be two separate issues...
I'm not as concerned with the CM9 issue, as it is only a mild annoyance and everything else is outstanding. CM10 is virtually unusable, however, so I'm hoping someone can help me out there.
thatdumbguy said:
Hello, I am having some touchscreen problems with CM9 and 10, but not with webOS. Namely, I think that the tablet is detecting double or even triple taps when none are present.
In CM9, when I execute a longpress (to move an app for example), the tablet just kind of... spazzes out, and in general nothing happens. In CM10 it also does this, and almost everytime, it starts whatever app I was pressing on.
Also, when I try to type in the CM10 keyboard, 2-4 characters are being entered at a time, unless I touch incredibly lightly, and even then, I will often get two.
There are other symptoms along these lines, like trying to pull up the notifications, etc. This does not appear to be isolated to any one portion of the screen, it is happening everywhere I could check it.
This CM9 versions I have tried are the nightly 0715, and whatever the latest nightly was about a week ago. The CM10 version I am using is jcsullins' 12/16.
As stated, I have zero issues in webOS.
Is there any way to change the touch sensitivity? Am I a moron and doing something wrong?
Thank you for your help/advice.
Click to expand...
Click to collapse
I've not had this issue, but this might help. Go here : http://goo.im/devs/jcsullins/cmtouchpad/testing
Download the touch pressure utility (should be the last one) and flash it. Hope it helps.
Good luck.
As an update, after shelving the touchpad for a few months, I have revisited it, and, after doing a clean install of jcsullins' CM10.1 w/BT Fix (20130808), the same issues as above still persist. I've done the following, although I didn't really expect most of them to work:
Switching to stylus mode (no difference)
Changing the accessibility settings for touch & hold delay
Even went so far as to install another launcher (nova) to ensure it wasn't trebuchet (not that I think it was)
Same for the keyboard
This has never been an issue I've seen in webOS... additionally, I don't remember ever having any issues in CM7 either. I did play with webOS for some time today to make sure it wasn't some kind of hardware failure between now and the last time I used it frequently, but I failed to reproduce the problem there.
Is there any light someone can shed on the subject? Thanks!
Thanks for that Chicle_11... I don't know why I failed to mention it, but I did also try the patches with CM9, but it is to my understanding that they were rolled into cm9 nightlies at some point?
I wonder if I could be having a minor hardware issue that just isn't severe enough to display in webOS, because I can't seem to find anything else about this, especially the keyboard problem with CM10. Its bizaar for sure.
Started experiencing the same issues after upgrading from cm9
I recently upgraded from cm9 to cm10.2 and immediately noticed this issue. There were no such issues with cm9. When swyping on the keyboard (any - Google, Swype, etc.), the system registers that I lifted my finger, and so garbage gets typed - you can also see the effect in the trace. When typing instead, letters sometimes double-up for a single press. When playing games like PvZ2, dragging a plant results in a release of the plant before I've lifted my finger, and sometimes the plant gets planted across the screen from where my finger is pressing.
** Work-In-Progress: Ubuntu Touch Preview is just that.. a PREVIEW. Do not complain about missing features, etc. The OS isn't nearly ready for primetime. **
Curious as to how the Ubuntu Touch Preview looks? Why not load it on your Droid 3 and see for yourself.
Instructions:
1. Make a Titanium Backup and/or backup in recovery of your current Android (or just keep it on a different slot). This preview is fun to play with but not a replacement for something as developed as CM 10.1
2. Download the Droid 3 Mini-Android base for Ubuntu Touch and place it on your device:
[03/01] http://goo.im/devs/Hashcode/solana/ubuntu-phablet/ (use the newest one)
3. Download the latest Ubuntu Touch Preview Filesystem .zip from Ubuntu:
http://cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/quantal-preinstalled-phablet-armhf.zip
If the above link is broken, use this link for a full listing of the current build files (download the quantal-preinstalled-phablet-armhf.zip .. soon to be raring-preinstalled-phablet-armhf.zip):
http://cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/
4. Reboot into Safestrap. Create a NEW 2GB ROM in the #4 slot.
IMPORTANT:
4a. Install the quantal-preinstalled-phablet-armhf.zip FIRST, and then the phablet-2013xxxx.zip SECOND.
5. Reboot and Enjoy
FIRST BOOT TAKES A LONG TIME. AND THERE'S NO BOOT ANIMATION. BE PATIENT (MAYBE 3-4 MINUTES).
WHAT WORKS:
Display
Touch screen
Wifi
Audio
WHAT DOESN'T WORK:
There's so much that is still being implemented into the Touch version of Ubuntu, that this list could get pretty long.
Due to memory issues, the device gets VERY laggy after just a little while of use. This means the swap mem is full. I hope they work on the amount of memory used and how it's freed over time.
Barely any sensors other than touchscreen work. IE: no rotation, etc. Ubuntu WIP issue.
No HD codecs (still being worked on) Ubuntu WIP issue.
No screen timeout / auto blank -- becareful when walking away from the device. Need to press the power button to turn the screen off. Ubuntu WIP issue.
RELATED UBUNTU TOUCH LINKS:
(Some of these describe how to install it on devices -- you can ignore those instructions and follow the above)
Ubuntu Touch Wiki: https://wiki.ubuntu.com/Touch/
Release Notes: https://wiki.ubuntu.com/Touch/ReleaseNotes
IRC Channel on freenode.net: #ubuntu-touch
Re: [ROM] Ubuntu Touch Preview [02/28: Alpha Update #1]
Neat. I had to battery pull to get it to boot, bootlooped until I did. It feels like unity, for my phone. It'll be interesting to see how it performs on our device when it's complete
Sent from my XT860 using xda premium
Fine!, downloading and booting in moments! i was wondering about this in the forums, some days ago! Hash, you're the best!
Glad to see an alternative for our devices...who knows...maybe this could lead to a fully functional rom...
EDIT: Sadly, it doesn't boot at all...same issues as latest CM10.1, but after a while of black lit screen, the phone turns off...trying later something else
Re: [ROM] Ubuntu Touch Preview [02/28: Alpha Update #1]
FrankieDedo said:
Fine!, downloading and booting in moments! i was wondering about this in the forums, some days ago! Hash, you're the best!
Glad to see an alternative for our devices...who knows...maybe this could lead to a fully functional rom...
EDIT: Sadly, it doesn't boot at all...same issues as latest CM10.1, but after a while of black lit screen, the phone turns off...trying later something else
Click to expand...
Click to collapse
I had the same until I battery pulled
Sent from my DROID3 using xda premium
Looks pretty cool. I think I could get used to that interface pretty quickly. I did have a little trouble getting back into SafeStrap to boot into the stock ROM (or CM10.1 in slot1).
I used both the power button and battery pull to restart, I got the SafeStrap menu, chose boot to recovery, and in a few minutes I get the Ubuntu screen back. I finally got into SafeStrap by holding VolUp & VolDown while powering on and choosing BP Tools (bottom option).
I'll have to go back through the flash process and test a few things. Sorry that it's messing w/ some of your devices.
3/1/13 Build worked fine for me but I do have one of the older CPU's since all the kexec builds have worked for me, first boot time was only like 20 seconds and it still worked pretty quickly (but I only used it for about 10 minutes), seeing something different was refreshing and it took me about a minute to realize there was no lockscreen, most definitely a developer preview but it looks promising.Thanks Hashcode for the preview build and all the work you do, I'll keep testing them when they come out.
oh yeah the safestrap problem persisted for me as well had to hold the volume buttons to get back to Rom selection. No biggie
Hi
I tried phablet-20130301-cm_solana.zip and it worked better than I expected, I could even make calls.
The experience is quite nice and it seems Ubuntu Phone OS is very promising!
Thanks
taksan said:
Hi
I tried phablet-20130301-cm_solana.zip and it worked better than I expected, I could even make calls.
The experience is quite nice and it seems Ubuntu Phone OS is very promising!
Thanks
Click to expand...
Click to collapse
Are you on GSM?
Sent from my DROID RAZR HD using Tapatalk 2
I didn't even try calling. I didn't expect it to work
Sent from my XT860 using xda premium
Right now phone function is only implemented for GSM. The GSM RAZR has working voice calls. I didnt think D3 would work either but in theory it could.
(I occasionally activate a 3g SIM for testing, but didnt for the preview.)
Sent from my DROID RAZR HD using Tapatalk 2
taksan said:
Hi
I tried phablet-20130301-cm_solana.zip and it worked better than I expected, I could even make calls.
The experience is quite nice and it seems Ubuntu Phone OS is very promising!
Thanks
Click to expand...
Click to collapse
I tried dialing one call to one of our office lines while I was booted into Ubuntu . It dialed and rang ok but I couldn't hear the receptionist when she answered and she couldn't hear me.
Sent from my Nexus 7 using Tapatalk HD
Yes, I'm on GSM. I didn't expect it to work either, but I just thought I'd try.
The problem is that it usually doesn't boot and keeps "boot looping". The first time I pulled the battery and it worked, but now it is not working anymore.
I'm trying a reinstallation.
Even though it is quite crude, it worked better than CM10 (the droid 3 version), because the CM10 phone service crashed on start and I couldn't make
calls and neither connect to WiFi
I got it working once again, but after a while it froze. I tried rebooting the phone and it isn't booting anymore.
Ok, booted and tried, it works really well for an early alpha, who knows...this could be the base for a fully functional rom? i'm a dreamer...
Anyway i'm on GSM and calls are lagging of 1-2 rings, and voice seems to be broken, anyway, good work! as usual
Very nice! Works great for being so new. Could not do much as it would not connect to my work WiFi but expected with such an early build. Looking forward to future updates.
Being based on the CM kernel is it safe to assume we will not see any camera function for this unless it first gets worked out in the CM 10 builds?
thanks yet again Hash !
Installed as per the first post.
First boot - no longer than one min I reckon.
Wifi works, got on to FB with browser and even posted
Today showing work mate, dialled his number (without any hint of cell network / settings) and to my amazement not only did it dial, upon answering we could hear each other fine, maybe a tad lagged half a second or so but honestly worked fine!!
May have imagined things but it also appeared to get faster again after 5-10mins of being powered on, reboots no issue.
Just no idea how to power off correctly lol, seems like holding power button puts it in sleep (saw today image very dark but certainly there), then could not wake (happened yesterday also the can not wake part), so I just battery pull, again reboots no issue
Cheers
Ok man im trying to install this on my droid 3 to see how it works and then i was going to try and port ubuntu to the k1 tablet but on part 3 when installing it it will get almost done and by then my phone is very hot as well and any way it will get almost done installing and the phone will go black and i will have to pull the battery to even get the phone to do any thing so im asking what am i not doing right? I will like to get this booted on the droid 3 to get a fill of how this works befor i port to the k1 tablet.
Sent from my K1 using xda app-developers app
---------- Post added at 08:10 PM ---------- Previous post was at 07:16 PM ----------
leerpsp said:
Ok man im trying to install this on my droid 3 to see how it works and then i was going to try and port ubuntu to the k1 tablet but on part 3 when installing it it will get almost done and by then my phone is very hot as well and any way it will get almost done installing and the phone will go black and i will have to pull the battery to even get the phone to do any thing so im asking what am i not doing right? I will like to get this booted on the droid 3 to get a fill of how this works befor i port to the k1 tablet.
Sent from my K1 using xda app-developers app
Click to expand...
Click to collapse
I got it installed i had to install in slot 2 not 4 to get it all the way installed i dont know y this matters but o will any way i tested it in the other slots and it will not work in them ony 2
Sent from my K1 using xda app-developers app
Just got it from Ubuntu:
Known Issues
Power Consumption
Currently the devices can not be shutdown from within the UI or by pressing the power button. Even if you use the power button long press your battery will be drained.
To shutdown a device completely there are two options:
Remove the battery and replace it. (Not an option if battery is not removable)
Stop it from the adb shell by executing the following commands:
adb root
adb shell reboot -p
Memory Usage
Memory usage has not yet been optimized for the devices. It is possible to experience application crashes due to having too many applications open at the same time. A workaround is to close apps that are not being used.
Timezone
The timezone needs to be manually set from the command line. Valid values for timezones can be found in the /usr/share/zoneinfo/zone.tab file. Run the following commands ( specifying your own time zone choice ) with root permission to set your timezone:
Access your device through SSH
Then on the terminal connected to your device run:
echo "America/New_York" | sudo tee -a /etc/timezone
sudo dpkg-reconfigure --frontend noninteractive tzdata
Networking
The Developer Preview has support for Wi-Fi networking via the new network indicator, which supports basic Wi-Fi connections (Open, WEP and WPA Personal). It is possible to configure more advanced settings, however at this time this requires working directly with Network Manager system connection files.
The following network features are not yet included in the Developer Preview:
Airplane Mode/Wi-Fi Power Control
Advanced Settings (e.g. Hidden SSIDs, Manual IP, VPN…)
Bluetooth
Hot Spot/Tethering
Telephony
The Developer Preview currently only supports limited voice and SMS over GSM.
The following Radio technologies are not yet included in the Developer Preview:
CDMA
LTE
Airplane Mode
Settings ( eg. APN choice, 2G only, … )
Mobile data is not supported, data is available via Wi-Fi only.
These Call features are not yet supported:
Emergency Call Support ( ie. ability to dial emergency numbers without a valid SIM card ).
PIN/PUK support for locked SIMs
No SIM filesystem support
Speakerphone
These SMS features are not yet implemented:
MMS
Send error handling
Delivery Reports
leerpsp said:
Ok man im trying to install this on my droid 3 to see how it works and then i was going to try and port ubuntu to the k1 tablet but on part 3 when installing it it will get almost done and by then my phone is very hot as well and any way it will get almost done installing and the phone will go black and i will have to pull the battery to even get the phone to do any thing so im asking what am i not doing right? I will like to get this booted on the droid 3 to get a fill of how this works befor i port to the k1 tablet.
Sent from my K1 using xda app-developers app
---------- Post added at 08:10 PM ---------- Previous post was at 07:16 PM ----------
I got it installed i had to install in slot 2 not 4 to get it all the way installed i dont know y this matters but o will any way i tested it in the other slots and it will not work in them ony 2
Sent from my K1 using xda app-developers app
Click to expand...
Click to collapse
Got it working it tuck 20 m of living the phone on lmao
Sent from my K1 using xda app-developers app