Related
If I try to search anything on Google Images, all I get is a blank page.
In single column view, I get everything except the pictures i.e. search field, page numbers, other little graphics etc.
In default view, I get a total blank page.
In desktop view I get a blank page again but I also a horizontal scrollbar with it.
The odd thing is that if I view the source of the results page, it's all there, it just doesn't load at all. I have checked by installing Opera and Google Images displays fine but I don't want to keep Opera.
Any ideas on what's causing this?
Thanks
Anyone have any ideas?
Sounds obvious but you have got PIE set to display images haven't you (Menu-View-Show Pictures).
Sorry if that sounds patronising but it usually is fogetting the obvious
Sounds to me like PIE is a bit screwed, either that or your registry settings are a bit fubared...
Personally I like to use both Opera and PIE, because PIE can load SWFs (provided you've installed the PPC Flash Player 7 cab, of course) so I can get my Weebl and Bob fix, but Opera is just so much better at rendering pages, and its download manager is far superior... And it feels less clunky... And it can do FTP... and... well, just use both side by side for a while and you'll realise it's not a bad investment
Weebl and bob on the phone, what a fantastic idea. <off to load Flash 7>
apologies for my previous post, when I wrote it my phone connection wasn't working so I couldn't try it out. I also am experiencing exactly the same problem as described. Would say it's most likely down to PIE not being able to interpret the script used by the Google Images page.
Yeah, i agree!
I also am experiencing exactly the same problem as described. Would say it's most likely down to PIE not being able to interpret the script used by the Google Images page.
Click to expand...
Click to collapse
But why on some devices and not others? I used to be able to browse perfectly on my JAM.
Anyway, I wanted to avoid a reset but it looks like the only way it might fix whatever's gone wrong.
Thanks
I was told in the main CM thread that starting a new thread about this issue specifically is more likely to get attention, so here it is.
In the last 4 version of CM on my Nexus One (5.0.5-5.0.5.3), the MMS app is not resizing the photos taken with the camera app. When I go to get details on a photo that MMS is trying to send, it shows that it's anywhere between 600kb and 1000kb, clearly too large to send through AT&T. When I flash back to the stock rom, the MMS app resizes these same photos and they go through every time.
I tried sending an MMS earlier today with no luck, I'm on 5.0.5.2
I thought it was something i was doing wrong :/
I have the same problem
I guess we'll have to wait for 5.0.5.4...
I have the same issue. The only workaround I found was to use Handscent SMS instead of the built-in messaging app.
mindfrost82 said:
I have the same issue. The only workaround I found was to use Handscent SMS instead of the built-in messaging app.
Click to expand...
Click to collapse
This is what I'm currently doing. Two things that suck about Handscent (from what I can tell). 1) It compresses the pictures to VERY small, so they actually look pretty lousy on a phone with a high resolution display. I think it compresses them down to 11kb. 2) Handscent doesn't send video.
This has been an issue with CM since the initial release. i switched to using Handcent as well.
Have you gone to the Settings menu in the Messaging App? From there go all the way to the bottom and Select Custom User Agent. Try selecting different ones and see if that changes anything.
importflip said:
Have you gone to the Settings menu in the Messaging App? From there go all the way to the bottom and Select Custom User Agent. Try selecting different ones and see if that changes anything.
Click to expand...
Click to collapse
I have tried all the user agents, none of these settings affect the size of the file being sent so it does nothing for this problem.
Any luck using chompsms?
i've had trouble with both reg message app and handcent....just reporting...HAHA
uh yep. same problem here. super annoying.
hopefully Steve has seen this and will look into it. I have played around with it a lot over last two days. It seems very random, works, then doesn't. I dunno....See if Steve mentions anything in next ROM update changelog, lets all hang tight, he's never let us down!!
chompsms has worked best in resizing mms and such
much prefer it to stock and handcent overall in use as well
I don't think this has anything to do with the CM ROM as I get the same on stock and from what I've read everyone seems to have the same issue.
There are other posts on here about this as well as on Googles Nexus help forum.
I struggled with the same issue. Firstly, as already pointed out, this is not an issue with Cyanogen, its the stock SMS app that is the culprit.
The solution is to edit your Mms.apk and hopefully Cyanogen will implement this fix in a new version.
Just use whatever binary editor on your OS to edit mms_config.xml which is in mms.apk. The limits are clearly visible as ASCII text in there. As the limit is 1048576, you need to make that 0307200 to be on the safe side. I also edited the resolution, 1024x768 would seem plenty for an MMS. The result is that out going messages here are around 100kb when resized and it never hits that 300KB limitation.
So start with unzipping the Mms.apk, then edit the file called mms_config.xml, and just zip it back up again.
Again, hopefully this fix can be implemented in the next Cyanogen version
cyanogen said that hes thinking about making the messaging app be configurable so we can choose which size the app does.
thanks for the tip Untouchab1e, but when i tried to unrar the file opened the xml file, edit with dreamweaver, changed the file size and the resolution (i did 800x600 though), but i rar it back up and rename to apk. Doesnt work. Am i doing something wrong?
EDIT
Well my current workaround for now is, download picsay (free) from the market, open picsay, tap get picture, open the picture you want, hit normal, hit menu button when the picutre is showing (menu on the 4 keys at the bottom) hit export, tap on save to sd card. after the picture has saved, open messaging app, attach a picture, open the picsay folder, select the picture and send. delete the picture from picsay if needed.
Any kind developers willing to recompile the Mms.apk with the edited xml file? I changed the file myself with the recommended settings, but I haven't the programming background to even begin to understand the process of putting the apk back together (everything I read about it gave me a headache).
Here's the zip file that contains everything, which technically just needs to be converted into an apk.
+1 here.
This is the biggest Problem for me with CM-Rom...
Its impossible to take a Picture and send it via MMS.
Iam 100% sure that the Picture-Resizing is working on Stock-Rom.
Please dont get me wrong, iam really happy with CM's Rom but iam wondering why Cyanogen didnt fixed this since the first release because its something like a "Basic-Feature" but it seems to be more important to have fancy color LED-Notifications...
Cyanogen, please fix this soon
It appears this is fixed in the upcoming 5.0.6 ROM, or at least it is in the test version.
You can also push the older 5.0.4.x version to get it working in 5.0.5.x, instructions are here.
I have a feeling that these settings only affect those using the Nexus One on AT&T, and since CM's ROM's are used by people in numerous countroes and various networks, it would make sense to keep it open for those carriers to allow larger pictures. That's just my guess though.
I tried 5.0.5.6 briefly just to test this and the results seemed to be the same. I'm going to try pushing the older version, but I don't want to lose the black background. I think it's slick.
Edit: Just reverted to the 5.0.5.4 MMS file as posted above without theme options and it's still not working. I also forgot that the old and stock version of this app have that inconsistent behavior when pressing the back button (sometimes you load all threads, sometimes you get kicked back to the home screen). Nandroid restoring now...
Sup, ppl?
Hey, I have a new X8 phone (3 weeks old) and I have a major issue with my camera from day 1!!! It's all glitchy and blurry, with wrong lighting and i can't take pictures at all. Sometimes when I repair the update with PC Companion or SEUS it gets to work again, but after using the phone for some time, it bugs again, especially after playing Angry Birds (even for just once!!!). I have never rooted my phone, it's all original.
I had it repaired by the service center, they said they just ran a software update (and I had the latest version) and I don't know how all my apps were still on the phone (I never manage to do this, everytime I repair the update I lose all my apps, how can I keep them?). I searched the web for several hours and haven't found anyone with my problem. I have posted question on SE support forums and on their Facebook page, but no one seems to help me. I think I'm having this unit replaced.
Another thing is that I formatted my SD card, and I thought I could get the original content again, but I was wrong. I had the "music" folder backed up, but I don't have the "media" folder. I lost some of the alarms (like the "multi alarm" one) and the notifications. Can someone upload the media folder for me please?
Thanks for all the help.
Felipe MacLeod said:
Sup, ppl?
I have a major issue with my camera from day 1!!! It's all glitchy and blurry, with wrong lighting and i can't take pictures at all.
Click to expand...
Click to collapse
What did u mean blurry? Maybe this phone does no come with an auto focus camera that why when you take picture will blur. Correct me if i'm wrong.
It's not exactly blurry, but it look horrible. For example if you edit a picture and you start messing with hue, saturation or color balance. The more you mess, the worse it gets. The display shows an bad colored looking picture and taking pictures does not work. Tried searching everywhere but can't find anyone with similar problem.
Can you post some photos? The best would be if you could put the phone fg on a table and take a photo without moving it at all. Cause to me it looks like either the camera itself is the issue or something wrong with software, if you're saying that when you mess with settings it gets even worse.
owiec said:
Can you post some photos? The best would be if you could put the phone fg on a table and take a photo without moving it at all. Cause to me it looks like either the camera itself is the issue or something wrong with software, if you're saying that when you mess with settings it gets even worse.
Click to expand...
Click to collapse
It's not that I can mess with the settings, the camera app doesn't have ANY settings to mess. The messing with settings exampled I used was about using a photo editor and try messing with the color levels or hue/saturation of any picture. My camera is displaying a screwed up image as if there was some color filter applied to it, someting that would react really poorly to lighting. Just like if you picked up a 16 million color picture with many gray colors (variant colors) and you converted it to like 256 colors, it would look really poor. That's the image my camera shows.
And did you try others apps for camera? Maybe there's something wrong with it. If not - go for warranty
owiec said:
And did you try others apps for camera? Maybe there's something wrong with it. If not - go for warranty
Click to expand...
Click to collapse
It happens to any camera app.
I'm an IT guy and I know sometimes unexplainable things happen with hardware/software. Today when I woke up, when I was going to put the phone in the pocket for leaving home, it slipped and fell to the ground scattering parts all over (cover and battery). After rassembling it i thought: "Wtf? I'll try the camera!". And believe or not: it was working PERFECTLY. And is perfect to this very moment. Some problems just don't have a reasonable explanation.
Original SD Content
Now the only missing piece is the original SD content, which I happened to wipe out unadvertedly. I tried some undelete tools, but none found the data, and I probably already overwrote all the data with many backups that I made.
So, if anyone could be very kind to post me the media folder contents (with the alarms and everything) and also the pictures that came in the images folder I guess?
Thanks, ppl.
-snip-
shutup-----
Hey All, I've had my TF for about a month now, and while I do love the device. the one thing that is constantly annoying me is in the browser. I have the agent string set to "Desktop" and it displays almost all websites without a problem. The annoying thing is when I open up Facebook and click on a picture someone has posted, it loads the picture up at a large size (almost full screen) with flash, but when I try to scroll to the comments the picture stays up blocking the picture. Has anyone else had this problem or know a workaround for it? The closest that I have come is keeping Dolphin also installed on the TF with the agent string on that set to Phone so I can view without Flash freaking out. Thanks!
Wow over 40 views and no thoughts. Am I the only having this issue, or the only one too dumb to know how to fix it?
sorry i cant offer a solution, but i can agree with what youve described. Picture blows up, and ive noticed the most horrible lag during that time. I try closing the picture and it takes a good 3-4 seconds to close..
havent tried on any other browsers
For those who are looking for a good emulator for their PC and genymotion/andy doesn't quite cut it for you, check out Amiduos from http://amiduos.com/ I am working on some tutorials on how to root/debloat/xposed the emulator, I have them posted up on my blog: http://talesfromtheandroid.blogspot.com/2015/09/amiduos.html I am almost finished with the 2.0 part, but it is not hard to manually root.
Happy rooting!
Amazing! Great job, and thanks a lot for this. I was using bluestacks, but ya, that's a piece of crap compared to this. Amiduos is a lot faster. Everything went well following the instructions on your blog for the 2.0 version. I only have one problem, and I know that it's because snapchat is the most piece of crap app ever created in the existence of mankind. Seriously, I have never seen a more problematic app across so many devices. Anyway, ya, it crashes on Amiduos 2.0 .. It seems like it does the exact same thing as what happens on my old-school Galaxy Tab 10.1 WiFi (GT-P7510). You can install it and open it to the login/signup screen just fine, but once you login and it attempts to go the main snapchat UI (where it shows the camera open), it crashes to home screen. I can understand it happening on the Tab 10.1 because it's such an old tablet with old architecture, and I've actually confirmed that it is just the Tab's capabilities itself because I've confirmed with a few other users with the exact same Tab that they have the same issue with snapchat, but you would think it would work fine with Amiduos. This doesn't happen on bluestacks, but my issues with bluestacks were a whole other deal. First off, it's slow compared to Amiduos, but aside from that, I was able to root and get Xposed installed on the latest version. Snapchat actually opens and runs fine on it, but when attempting to use snapprefs (xposed module), it basically doesn't work. It's strange because it was actually working on the first try on the 0.8.11.3116 version of Bluestacks, but snapchat had an issue where if I logged out and then tried logging back in, it gave me some BS login error, and I had to essentially just create a new account. I ended up screwing a few things up in my attempt to solve the issue by clearing data and cache on a number of apps including the xposed framework, and ya, I basically had to reinstall bluestacks, root, install xposed, etc. At that point it wasn't working anymore lol. Snapchat will just crash when attempting to share a photo into snapprefs (that's how you get a photo from gallery into the snapchat editing UI), or it would just show a black screen in the snapchat UI. I'm not sure if I want to try genymotion/andy for my snapchat/snapprefs needs. I might just have to use my old-school jailbroken iPhone 4 to run a tweak that basically does the same thing as snapprefs. The only reason I liked snapprefs better (when it was working on bluestacks) is because it didn't affect the quality of videos that I shared from gallery to send through snapchat. Phantom for snapchat (jailbroken iPhone tweak) seems to do that. Would you happen to know what the issue might be, and how to get snapchat working on Amiduos?
AmiDuos 2.0 Root Solved !
Previous Post:
http://forum.xda-developers.com/showpost.php?p=66391966&postcount=32