Hello, been reading the forums for a while, new to posting in it. That said, I'm not allowed to post in the CyanogenMod 10.1 thread because it's in development, and I need more than 10 posts to post in there.
I have an issues with the screen resolution on my HTC One. It's the same problem as in the post below.
http://forum.xda-developers.com/showpost.php?p=41803030&postcount=1120
The buttons and text for certain apps become extremely, extremely small, as if I'm using a tablet. I'm running the latest CM nightly, and so far I've noticed this bug in Google Currents, Minecraft PE, FPSE, Broken Sword, and Canabalt HD. Is there any solution or workaround to this?
I've already read through all 190 or so pages of the CM10.1 thread, and tried changing the LCD density in build.prop. All to no avail. Help please?
So... nothin? No one had this problem? Or no one has a solution?
eHabaski said:
So... nothin? No one had this problem? Or no one has a solution?
Click to expand...
Click to collapse
I have this problem... (although on a Galaxy S2) I was using CM10.1 for a while, then recently tried a few other ROMs out and came back to a fresh clean install of CM10.1 latest release in the past few days and the fonts and the whole screen resolution is weird and fonts seem tiny, icons are smaller - it's just weird. I had flashed back to Samsung stock and that was bigger and more readable as I expected.... so what's changed I wonder?
Baronne
Related
I've got a Nook Color running CM7 nightly build 07202011 (I think that's 138) with LCD density set to 160 and the new market installed (though it's flaky) and Swype installed as my chosen keyboard. Don't know if any of this is relevant, but when I run the Google+ app and click on the pen icon at the top right to start a new post it FC's 100% of the time right away.
Anyone else see anything like this?
sprior said:
I've got a Nook Color running CM7 nightly build 07202011 (I think that's 138) with LCD density set to 160 and the new market installed (though it's flaky) and Swype installed as my chosen keyboard. Don't know if any of this is relevant, but when I run the Google+ app and click on the pen icon at the top right to start a new post it FC's 100% of the time right away.
Anyone else see anything like this?
Click to expand...
Click to collapse
Yes, the people in the Google+ Thread in the Apps section have mentioned this several times. See the thread there.
Wow, would never have thought of it being a GPS issue - Google Maps geolocates me right to my house, but G+ crashes instead - stupid.
I noticed the update yesterday fixed this issue.
Yes, the update has solved the problem. No more work arounds
Is it just me, or does the new Google Maps experience some odd graphical glitches?
I'm running schizoid 10.1.
Sent from my skz_tenderloin using Tapatalk 2
I feel ya, bro. Serious graphical glitches on my HTC vivid running Cyanogen Mod 10. The maps continuously skip and jitter, and any window overlaid over the map interface becomes transparent.
xmanfit0 said:
I feel ya, bro. Serious graphical glitches on my HTC vivid running Cyanogen Mod 10. The maps continuously skip and jitter, and any window overlaid over the map interface becomes transparent.
Click to expand...
Click to collapse
I really have no clue what the problem can be. I suppose the transparencies are causing some rendering issues. I hope Google fixes this soon!
Many people have reported this issue on different roms for the Desire HD. CodefireX, Jellytime and CM10.1 all suffer from it.
I hope Google fixes this soon cause Maps is unusable in its current state.
Largamelion said:
Many people have reported this issue on different roms for the Desire HD. CodefireX, Jellytime and CM10.1 all suffer from it.
I hope Google fixes this soon cause Maps is unusable in its current state.
Click to expand...
Click to collapse
Happens on my HTC Evo 3D too. The glitches are more severe when the phone is in portrait mode.
If it is Maps 7, then I think its Googles issue and not any of the ROMS or devices we are using them on... As this happens on my phone too..
Lister
BuffMcBigHuge said:
Is it just me, or does the new Google Maps experience some odd graphical glitches?
I'm running schizoid 10.1.
Sent from my skz_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
did you trying re-installing maps?
Is this issue mentioned anywhere else? I checked at http://productforums.google.com/forum/m/#!categories/maps/mobile-android but didn't find anything.
I am having the same problem, 'rjand' on this forum suggested for me to downgrade Maps to a previous version (version 6.*). I have done this, but have yet to test if the problem persists.
Downgrade Maps
Old thread, but this may help @xmanfit0 , @lokster and others like me who found this thread by searching for "Google Maps cyanogenmod glitch".
I had this problem on my HTC Vivid with CM10, but after downgrading to Google Maps 6 it works nicely.
The APK can be found here:
Maps-6.apk
I found the APK from the bottom of the second post in this thread.
This one: http://goo.gl/2vRQy
On my One running CM10.2 it doesn't display correctly, eg program details don't fit in the screen. It's also landscape only, and I think it should be portrait for handsets and landscape for tablets only.
https://www.dropbox.com/s/u7gvp61go1g1q97/2013-08-21 15.45.26.png?m
I believe the issue is down to the device properties in CM as I'm led to believe it runs fine on stock Sense roms. Any ideas? Anyone else have this issue?
Edit: Argh, sorry mods just realised this should be in the Q&A/Troubleshooting forum
Fine for me running stock, wondering if it's a CM issue?...
Possibly a combination of that and poor coding on Sky's part. Their apps seem to have a tendency to be on the rubbish side, Sky Go doesn't recognise the device either.
Just got my Nook HD+ 32GB today - very excited to put CM on it!
I'd like to hear opinions/recommendations on which version I should try first. I'm mostly interested in stability, but I also wish to have the latest'n'greatest.
CM-10.1.3-RC2 -or- CM-10.2-20130914-NIGHTLY ?
Try cm10.2. If you feel it unstable, try cm10.1.3.
Sounds like a good strategy. I'll give CM 10.2 a try first.
software_samurai said:
Sounds like a good strategy. I'll give CM 10.2 a try first.
Click to expand...
Click to collapse
If I remember correctly, I had trouble with Amazon Kindle on CM 10.1.3-RC2. It is working on CM 10.2.
dmullens said:
If I remember correctly, I had trouble with Amazon Kindle on CM 10.1.3-RC2. It is working on CM 10.2.
Click to expand...
Click to collapse
The dalvik dump tweak which allowed the Kindle App to work in 10.2 is in 10.1.3-RC2. Some are still reporting issues, but defiantly a minority.
Just a quick update:
I installed cm-10.2-20130915-NIGHTLY-ovation and the gapps, and so far it's been running very well for me. Chrome occasionally crashes, and I've experienced a few hiccups relating to WiFi, Bluetooth, and the nav menu button. But overall I'd say it's pretty stable.
software_samurai said:
Just a quick update:
I installed cm-10.2-20130915-NIGHTLY-ovation and the gapps, and so far it's been running very well for me. Chrome occasionally crashes, and I've experienced a few hiccups relating to WiFi, Bluetooth, and the nav menu button. But overall I'd say it's pretty stable.
Click to expand...
Click to collapse
Have you tried any other browsers to see if they crash as well?
I've used the default browser a few times now, and it hasn't crashed on me like Chrome.
I just installed 10.1.3 on a brand spanking new unit and the kindle app closes right away. The hdmi output also has black bars all around the picture. Going to try 10.2 tomorrow. Any recommendations on which build works best?
cutefuzzybunny said:
I just installed 10.1.3 on a brand spanking new unit and the kindle app closes right away. The hdmi output also has black bars all around the picture. Going to try 10.2 tomorrow. Any recommendations on which build works best?
Click to expand...
Click to collapse
The one you are running. There is an easy fix for Kindle. Just set the heap size to 384M in /system/build.prop.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
The one you are running. There is an easy fix for Kindle. Just set the heap size to 384M in /system/build.prop.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
What is the downside of increasing the heap size?
---------- Post added at 04:04 AM ---------- Previous post was at 03:49 AM ----------
software_samurai said:
I've used the default browser a few times now, and it hasn't crashed on me like Chrome.
Click to expand...
Click to collapse
The 2 apps that cause occasional crashes for me are Playstore, when updating apps and stock browser, with tab with video graphics. Chrome was a problem that I abandoned.
Crashes are spontaneous reboots. I also get rare incidents of screen having no sensitivity to touch but the hardware keys remain functional. I have to shutdown and restart when that happens. The browser is active when that happens too.
leapinlar said:
The one you are running. There is an easy fix for Kindle. Just set the heap size to 384M in /system/build.prop.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Guess I'll need to figure out how to edit that file. I know what it is and have edited other system files, but so far not that one! Are there any downsides to setting the heap size to that? If not, any reason you can think of why it isn't that way by default? Hasn't this been an issue for a while now?
I'm not doing well with this build. I put 3 apps on it. Kindle didn't run, my sons "my math app" (free in the play store) doesn't display properly. Its supposed to put two numbers and a plus/minus/multiply/divide symbol and a total line. Puts the two numbers way apart and the sign in the middle of them, and its either showing part of the same problem off the bottom of the screen or its the next problem...didn't really look at it that hard. And the nfl sunday ticket app gave me bars around the video and wouldn't go into full screen mode. When I tried full screen, I had to tap the icon about 30 times, it did get larger but not full screen, then when I tapped it again it went to quarter size and was very resistant to going back to sort-of-full-screen.
Been running the stable 10.1-10.3 on my old 7" nook tablet for a while now with great success. Surprised to find this a little less 'stable' than prior stable CM releases.
I don't think the hdtv adapter picture size is fixed until 10.2 and given my results with display issues with other apps, does it make sense to just plow ahead to those or are the bricking problems I've seen here and there still a concern with those nightlies? Is one considered particularly stable vs the others? I ran 10.1 nightlies on the old tab for a while without any major issues cropping up.
cutefuzzybunny said:
Guess I'll need to figure out how to edit that file. I know what it is and have edited other system files, but so far not that one! Are there any downsides to setting the heap size to that? If not, any reason you can think of why it isn't that way by default? Hasn't this been an issue for a while now?
Click to expand...
Click to collapse
The developer did just change the heap size to fix the Kindle problem. The problem now is Amazon keeps changing the app because other devices were having trouble too. My older version of Kindle works fine with the recently changed heap size, but the newest versions on Play Store don't work with it.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
The developer did just change the heap size to fix the Kindle problem. The problem now is Amazon keeps changing the app because other devices were having trouble too. My older version of Kindle works fine with the recently changed heap size, but the newest versions on Play Store don't work with it.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Thanks for the info. These things are always harder than they look.
leapinlar said:
The developer did just change the heap size to fix the Kindle problem. Kindle appThe problem now is Amazon keeps changing the app because other devices were having trouble too. My older version of Kindle works fine with the recently changed heap size, but the newest versions on Play Store don't work with it.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
It's a strange problem. The 0927 build has 402 heap. Kindle FC on my HD+. I increased to 480 and Kindle runs. I keep reading here that 384 works so I tried that. AND no FC.
Would build.prop in a folder, "storage/emulated/0/system/etc" work?
king200 said:
Would build.prop in a folder, "storage/emulated/0/system/etc" work?
Click to expand...
Click to collapse
No. But you could try putting just that heap size line in /data/local.prop. Local.prop gets loaded after build.prop and for some settings can override the build.prop setting.
EDIT: I just tried that and it works. You can put this line in local.prop and it will override the build.prop setting. That means it will survive the flashing of a new ROM with other settings:
dalvik.vm.heapsize=384M
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
... try putting just that heap size line in /data/local.prop. Local.prop gets loaded after build.prop and for some settings can override the build.prop setting.
EDIT: I just tried that and it works. You can put this line in local.prop and it will override the build.prop setting. That means it will survive the flashing of a new ROM with other settings:
dalvik.vm.heapsize=384M
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Handy tip for Nightly flasher.
As an FYI, I installed the 9/26 10.2 nightly since the info for the 9/27 and 9/28 wasn't particularly good. Kindle runs fine. NFL Sunday ticket works so far but I haven't tried it on a real game or tried the hdmi output yet to see if its formatted correctly. My Math App displays more correctly, with the numbers and signs showing up formatted correctly, although the seconds on the timer in the lower right corner are clipped off, you just see hours and minutes, but only part of the first two digits for seconds.
Didn't update gaaps, but everything that was on there was either updated or runs fine with what was on there. Tried chrome, play store, google search,etc. Everything ran but I didn't put them through an exhaustive test.
Just did the CM updater from 'about tablet' from 10.1.3 to the nightly and then told it to update. Thats it.
---------- Post added at 04:46 PM ---------- Previous post was at 03:51 PM ----------
Alright, weird. As I mentioned above I installed the 10.2 9/26 nightly and it made most of my problems go away. However, under 'about tablet' it says android version is 4.2.2 and cm version is 10.1.3. Same as it was when I installed cm 10.1.3, yet my apps work now and they didn't before I did the update. Hmmmmm....
---------- Post added at 05:24 PM ---------- Previous post was at 04:46 PM ----------
Alright...weird. I put the 9/26 nightly of 10.2 and the latest 10.2 gaaps on the sd card I made for the 10.1.3 install, booted into that, applied 10.2 and gaaps, everything looks good but kindle is back to FC'ing and the sunday ticket app still displays a 3/4 size image in the middle of the screen on the tv with the hdmi adapter just like 10.1.3 stable did. Thought that was supposed to be fixed in the later 10.2 releases. Doesn't appear to be, unless there's a magic trick. Full screen on the tablet, not on the tv.
Wondering what magical thing happened when I tried the in-place upgrade from 10.1.3 stable to 10.2 using cmupdate on the tablet, where it didn't actually go to 10.2 but the kindle app started working without editing anything or doing anything.
10.1-20130813-NIGHTLY-Ovation
cutefuzzybunny said:
I just installed 10.1.3 on a brand spanking new unit and the kindle app closes right away. The hdmi output also has black bars all around the picture. Going to try 10.2 tomorrow. Any recommendations on which build works best?
Click to expand...
Click to collapse
I'm running 10.1-20130813-NIGHTLY-Ovation on my Nook HD+ and I'm having very few issues. I had attempted to apply one of the 10.1.3 updates and it caused some apps to crash, so I switched back. I've not tried using HDMI out with it, though.
I have a Sandisk 32GB MicroSDHC Class 4 Memory Card that I have dedicated to holding the stable CM release (and accompanying CWM and GAPPS files) so I can always flash the HD+ to a known working state if something goes haywire. It also helped out when I bought an HD+ for the wife.
Cheers,
Dave\Esotic
Bluetooth issues on 10.2
Esotic said:
I'm running 10.1-20130813-NIGHTLY-Ovation on my Nook HD+ and I'm having very few issues. I had attempted to apply one of the 10.1.3 updates and it caused some apps to crash, so I switched back. I've not tried using HDMI out with it, though.
I have a Sandisk 32GB MicroSDHC Class 4 Memory Card that I have dedicated to holding the stable CM release (and accompanying CWM and GAPPS files) so I can always flash the HD+ to a known working state if something goes haywire. It also helped out when I bought an HD+ for the wife.
I had been running 10.1.something hybrid for the longest time on my Nook HD+, without any issues.
Yesterday I decided to go to 10.2.latest and now bluetooth is not working; I can not pair with Creative D-200 .....
Any ideas? (Apart from going back to 10.1.x ?)
Thanks,
A
Click to expand...
Click to collapse
Has anyone found a work around for the black browser screen in the 4.4 based roms? I see it in the evervolv and cyanogen 11 builds. I love 99% of kitkat on the touchpad, but with 2 step verification I can't do a clean install. HTML email is all black too.
Thanks to all the devs for their continued work on our orphaned touchpads. Your work is well appreciated.
If you have two android devices, you can use titanmium to backup and restores app from one device to the other device
jaltman said:
Has anyone found a work around for the black browser screen in the 4.4 based roms? I see it in the evervolv and cyanogen 11 builds. I love 99% of kitkat on the touchpad, but with 2 step verification I can't do a clean install. HTML email is all black too.
Thanks to all the devs for their continued work on our orphaned touchpads. Your work is well appreciated.
Click to expand...
Click to collapse
I to am having this exact issue, are you also having mediaprovider crash in the background? if not it may be unrelated. also are you using legacy display or media? are you getting overlay log spam? and if you are using legacy repos which ones?
Sorry if the questions seem random, but they may help me track down where this issue lies.
Also do you remember when you first experienced this issue?
Kits the current kernel. It will be fixed. Nothing as a user you can do. Let the developers have more time.
Moody66 said:
Kits the current kernel. It will be fixed. Nothing as a user you can do. Let the developers have more time.
Click to expand...
Click to collapse
I'm getting it working with Chrome browser.
jaltman said:
Has anyone found a work around for the black browser screen in the 4.4 based roms? I see it in the evervolv and cyanogen 11 builds. I love 99% of kitkat on the touchpad, but with 2 step verification I can't do a clean install. HTML email is all black too.
Thanks to all the devs for their continued work on our orphaned touchpads. Your work is well appreciated.
Click to expand...
Click to collapse
The latest opera browser works for me.:good:
I had not used Android since 2.2. Last night finally I decided to flash my TP. The first thing I tried after flashing was web browsing and saw the black screen. I thought I did something wrong and almost restarted the flashing process. Then I installed Chrome and it works fine.
Applies to Milaq's CM11 KK 4.4.2 and Evervolv/ASOP 4.4 update for the TouchPad (tenderloin). As others have reported the devs are still working updating 3.6 kernel. Reportedly the kernel changes will resolve the black box issue in default browser api.
So we need to live with the 2.6.35 kernel or a while longer. Until then apps utilizing default browser api in KitKat on the Touchpad are problematic. At least Chrome, Firefox and Opera are working.
Sorry for digging up an old thread but I am having this issue and not sure what to do. I reset my Google password. Since I have 2 step auth, it forces me through the browser to do the Google Signin, however the default browser has black screen. I have installed Chrome on the device, which works, but no matter what I do, I cannot make the signin go through Chrome, it always goes through the default browser with the black screen. So at the moment, I can't use my Google account with my TouchPad
Does anyone have a work around for this?
I am running the latest Evervolv nightly ev_tenderloin-nightly-2014.04.10.zip which was installed via the EV updater.