Hi all,
Just flashed my first ever rom on my desire S.
Id already S-Offed.
Downloaded Rom manager full version.
Backed up my standard setup.
Downloaded the latest miuius.
and flashed it.
All through Rom manager, I recommend the app its very well written.
I couldnt believe how easy it was.
Very impressed with miuius rom.
Seems faster as its mildly overclocked.
cpu scaling is supported.
Fixed my wifi, battery was much better.
All the usual google stuff is there and market works perfectly.
Only a couple of small problems I could find:
No sound or mic on making calls sometimes, but fix available and applied.
Auto Screen brightness sometimes breaks, I think when a message screen comes down from the top.
Haptic/vibration on keyboard not working, not that fussed but would like it.
If you havnt done it yet I recommend you dive in.
Its not nearly as painful as it used to be.
Gordon
Related
Hi,
I have a very strange problem... I have a german MDA Vario IV (Raphael) and I recently flashed ROMEOS 1.12, then HTC StockROM and after a couple of days it first happened, that my camera viewfinder is completely black. The camera, however, works, i.e. it takes pictures which I can view in the album.
When I tap the screen in camera mode, I see the 3 symbols, but when I tap the preferences-wheel, nothing happens.
When Romeos 1.40 (German) came out, I flashed it - and I still have the problem. I don't quite understand it, as it worked first with the HTC Rom and after about 14days it stopped working.
Do you have any help?
I just had the same problem. Fixed by doing a hard reset...
did you flash a new radio?
I just registered to report this same issue.
I just picked up my fuze today, and was going through the steps in the noob guide before I decided to stop and just let the phone install the regular software so I could at least activate it before a new bill kicked in before the account got cancelled.
Right before I stopped going through the noob guide, I got as far as doing a soft reset right before the installing ATT bloatware and was removing some options in the guide and restarting. Then, since I just wanted to activate the phone (I had no SD card to safely try out all the steps in the noob guide, and wanted to wait for it), I did a hard reset.
After I activated my phone, I've been trying out my camera and it just shows a black screen. If I touch the screen the three buttons show up and clicking on the buttons don't do anything. Though, if I hold the enter key it clicks and takes a picture which shows up in my album.
I'm going to wait till my SD card comes in before I do another hard reset to do the install again. Hopefully the hard reset fixes the issue.
Still no one else with this issue? I have flashed NATF 4.5 as well as energy 2.0 . I have changed to two different radios and this problem has persisted. Everything works fine at first, but then within a couple of days it goes black. Everything is exactly as others have reported. Pictures take, the touch screen menus work ( selecting any setting ).... its just the viewfinder that is acting goofy. Soft resetting it will occasionally make it work again. It makes me feel as though some of us have some software somewhere that isnt acting as it should. I googled the issue to no avail.
Any gurus able to shed some light on this matter?
Currently running:
HardSpl 1.9
EnergyRom 2.0
Radio 1.02.25.32
I am running Shep's 3.0 rom with the new 1.12.25.19 radio and I have just recently had this viewfinder problem arise as well. I am about to flash Shep's new 3F and will check the camera after hard reset.
Is anyone running additional programs when this arises? I had thought there was a conflict with freecaddie as I was on the golf course when I noticed the problem but maybe this is more widespread?
KSS said:
I am running Shep's 3.0 rom with the new 1.12.25.19 radio and I have just recently had this viewfinder problem arise as well. I am about to flash Shep's new 3F and will check the camera after hard reset.
Is anyone running additional programs when this arises? I had thought there was a conflict with freecaddie as I was on the golf course when I noticed the problem but maybe this is more widespread?
Click to expand...
Click to collapse
It must be as I dont play freecaddy. I can post all of the addons I have used...maybe theres something in common?
Ok heres the list
Ageye G-Alarm ( Which isnt working correctly anyway as it plays the WM alarm and not my MP3 )
Coreplayer
WMWifiRouter
MS Livesearch ( Preinstalled )
ShapeServices IM +
Skyfire
Skype
TomTom7
Any of these similar ?
pyraxiate said:
It must be as I dont play freecaddy. I can post all of the addons I have used...maybe theres something in common?
Ok heres the list
Ageye G-Alarm ( Which isnt working correctly anyway as it plays the WM alarm and not my MP3 )
Coreplayer
WMWifiRouter
MS Livesearch ( Preinstalled )
ShapeServices IM +
Skyfire
Skype
TomTom7
Any of these similar ?
Click to expand...
Click to collapse
Of the programs you listed, Skyfire is the only one I am also running. I just completed my flash and turned the camera on prior to installing any apps, cabs, etc... and the viewfinder worked fine.
I am in the process of adding my customizations back on, doing a PIM restore, and installing cabs and will edit my post later to report whether it continues to function correctly.
After setting things up the way I like them and a full day of use, the viewfinder still works fine. I am baffled as to the cause but as long as its works I won't complain.
To those still having the problem, I would recommend a hard reset at a minimum or perhaps try a new rom.
KSS said:
After setting things up the way I like them and a full day of use, the viewfinder still works fine. I am baffled as to the cause but as long as its works I won't complain.
To those still having the problem, I would recommend a hard reset at a minimum or perhaps try a new rom.
Click to expand...
Click to collapse
This was an issue with RRE's roms a while back. Not sure what he did to fix it but I know he tweaked a flashed new versions about 100 times in one day! I would post the question in your respective rom's threads and see if the cooks have a better idea. I would bet that there is a file or setting common to all of the roms listed here that is causing the problem.
Im running the stock rom in a 1 1/2 month old Fuze
The Black screen happens to me, if too much sunlight gets thru on superfine settings. (i hold it facing directly into the sun) It seems to blow out the picture (goes all white) -then theres no display at all (black) unless i exit camera and restart.
Camera viewfinder is black
Hi,
there is a fix for this on the htc asia site, if you go to the support tab and look at the downloads for touchpro, I am not sure its for all phone as it asked for my serial number and told me it was not for my phone, on this site at least it seemed to be for hong kong, singapore & china, Perhaps check the htc site for your location.
Good Luck
A|C
First, I want to thank everyone on this forum for being so active and dedicated! I can say without doubt that you guys are the main reason I chose the Fuze as my new smartphone.
I just got my Fuze yesterday, and it was working great (if a bit laggy) on the stock rom. I then installed hardSPL and ' ROMeOS conFUZEd AT&T edition' without any problems. But shortly after that, I noticed that the colors started acting strangely. It almost looks like when you're running windows in 256 bit color mode. There are no smooth gradients. But even more strangely, these color 'bands' rapidly shift around, making most of my screen appear as though it's flickering.
I tried Da_G's latest rom, then went back to the stock rom and stock SPL. But this didn't fix it. I tried taking a screenshot of it with CapScrUtil, but when I view the images on my computer they look fine.
This all leads me to believe it's a hardware problem and I should take it back, but it is kind of suspicious that it started after flashing the rom. Just checking if you guys have any suggestions.
Thanks!
Can anyone who has installed a custom android type rom let me know if the touchscreen is better once rooted and reflashed. I am talking about sensitivity at the store two different ones now both units are just bad when trying to select something I occasionally had to hit the selection more than 2 times.
I am also interested in if this changes. I read that its hit or miss whether or not thr screen works as intended or has problems, leaving me to believe its a production consistancy issue.
Some love it and some hate it.
Does this sound accurate?
Obsolete X said:
I am also interested in if this changes. I read that its hit or miss whether or not thr screen works as intended or has problems, leaving me to believe its a production consistancy issue.
Some love it and some hate it.
Does this sound accurate?
Click to expand...
Click to collapse
Sounds like it.
There's another thread about this which has a youtube video of one of the ones who said their's was bad and it certainly looked to be the case. In the video on the "home" "page" of the launcher when he swiped in the top half of the screen nothing happened most of the time, while it worked as expected in the bottom half. Mine behaves as expected wherever I swipe...
I'm not going to let on that it will be perfect, but when I moved to TnT Lite (I'm now on 2.2.1), I installed LauncherPro. Within LauncherPro, you can adjust the sensitivity and scroll settings that covers all the launched actions. Also, there's an entry you can add to the local.prop [go into adb shell and type: echo ro.HOME_APP_ADJ=1 >> /data/local.prop ] (requires r/w permissions to update). This change made it smoother (and quicker) to go from screen to screen.
There are still times where I press an icon and nothing happens for a second or so, but it rarely happens anymore with all the improvements that have been added to TnT Lite over the last couple of weeks.
I have had no touchscreen sensitivity issues to speak of with ZPad ROM. I am now running the VEGAn ROM which has really come together nicely in the last few days, and again the touchscreen is as sensitive in all places as I would expect it to be.
Any slowness/lag issues were resolved with the updated drivers that were discovered a week or two ago.
The stock TNT ROM has lots of software issues that are totally unrelated to the hardware. This is most likely one of them. I can't say for sure, since I wiped my unit within 5 minutes of opening the box and installed ZPad.
The touchscreen is still not as good with multitouch as it should be, which I believe is a driver issue, so pinch and zoom and similar multitouch action is not as smooth as it ought to be. But in general use, typing, swiping, scrolling, etc. I am just single-touching and everything works as smoothly and well as it does on my Nexus One phone.
Hello everyone,
I've been having quite an interesting issue on my NS4G. I'm currently running the latest available CM7 nightlies/gapps, as well with Pete Alfonso's kernel. The underlying system in the phone (radio/etc) is all running the current latest available from Sprint as well.
Now the issue in question, I've been having an issue that seems to be occurring more and more frequently on my phone. Now because I am already running a custom ROM and not just stock, this makes me unsure if the issue is coming from the software, or if there is an actual hardware issue with my phone.
Occasionally (I would say as infrequently as once every 2 days or so) when I unlock my phone with the power button, for a split second after the CRT animation I see my phones screen as all green (with a hint of purple), almost the color you associate artifacting with. Now I am not overclocked, but I am running this custom kernel. But the thing is, I'm not 100% on this, but If I remember correctly I do remember seeing this issue on other kernels as well before (I've been running Pete's for some time now).
I also occasionally experience issues with lets say finishing up a phone call, and my phone may lock up with that green screen w/ purple, and then CM7 will automatically reboot the phone for me. I've also experienced my phone rebooting into "Safe Mode".
Essentially what I am wondering is if anyone can shed some light, are these just software bugs that I am running into that other users are experiencing as well, or is this an issue with my phone?
Thanks everyone!
boktai1000 said:
Hello everyone,
I've been having quite an interesting issue on my NS4G. I'm currently running the latest available CM7 nightlies/gapps, as well with Pete Alfonso's kernel. The underlying system in the phone (radio/etc) is all running the current latest available from Sprint as well.
Now the issue in question, I've been having an issue that seems to be occurring more and more frequently on my phone. Now because I am already running a custom ROM and not just stock, this makes me unsure if the issue is coming from the software, or if there is an actual hardware issue with my phone.
Occasionally (I would say as infrequently as once every 2 days or so) when I unlock my phone with the power button, for a split second after the CRT animation I see my phones screen as all green (with a hint of purple), almost the color you associate artifacting with. Now I am not overclocked, but I am running this custom kernel. But the thing is, I'm not 100% on this, but If I remember correctly I do remember seeing this issue on other kernels as well before (I've been running Pete's for some time now).
I also occasionally experience issues with lets say finishing up a phone call, and my phone may lock up with that green screen w/ purple, and then CM7 will automatically reboot the phone for me. I've also experienced my phone rebooting into "Safe Mode".
Essentially what I am wondering is if anyone can shed some light, are these just software bugs that I am running into that other users are experiencing as well, or is this an issue with my phone?
Thanks everyone!
Click to expand...
Click to collapse
go to the main settings, cyanogenmod settings, display.. turn on the screen off animation. then go back to cyanogenmod settings, lockscreen, delay and timeout, turn both screen timeout delay and screen turned off delay to immediately. that should fix the green screen.
Just noticed this:
update-cm-7.2.0-RC2-smb_a1002-signed.zip
http://download.cyanogenmod.com/?device=smb_a1002&type=RC
Anybody try it yet?
I'm still on a 1.1 Recovery, but that should not be a problem for this ROM right?
Post if you install and the success you have please. Thanks - Dan
CM7
I am running CM7.1.0.1 i am afraid to change roms due to lack of success with past flashes. I am pretty much outdated on my rom but it doesn't seem like developers are producing a lot of this particular tablet....or maybe its just me. Are any of you guys rocking a must have ROM for the tablet. I am also running into issues where i'll have to reset my tablet to access wifi. It'll freeze between screens when I enter my wireless settings. If you want me to i'll back everthing up using TB and Nandroid and try this new one if no one wants to take the plunge!
OK, I've installed it. Here's my review:
Upgrade Details:
Viewsonic G-Tablet - 1.1 Bootloader
Clockwork Recovery newly from latest ROM Manager (5.0.0.6)
Previous ROM - Official CyanogenMod 7.1.0.1
Method:
Reboot into Recovery - Wiped/Deleted/Formatted/Erased/Reset to Factory Defaults - Everything I could.
Re-partitioned 2048/0, even though I think it was that way already.
Wiped/Deleted/Formatted/Erased/Reset to Factory Defaults - Everything I could - again - and then again - a few more times, and then once again.
In case you are not comprehending the subtly of the above, let me clarify: I was trying to do a clean install.
Installed 7.2.0 RC2 from link in first post of thread.
Did NOT install Gapps, Sound Fix, Camera Fix or do any Market fix.
Observations:
- The 7.1.0.1 Bug of not having WiFi turned on upon reboot is fixed.
- WiFi Seems to connect more quickly/reliably than 7.1.0.1 - Probably (should) has DHCP bug fixed.
- Seems to have it's own audio fix. Multimedia Volume appears momentarily after boot, and sound seems to work (mostly) fine.
- DPI is set low for me -- I'll have to mess with build.prop
- Camera Works - Orientation seems correct, Snapped picture was clear, and there are more camera settings.
- There is no DSP Manager.
- In CyangenMod settings -- if you enable Screen-off Animation (Twilight Zone effect), it won't wake from a manual sleep.
- Still has problem of dockbar (not notification bar) disappearing, and I do not know how to get it back. Have to place an open/close app draw Icon on the home screens.
- Web Browser stability/speed seems better than 7.1.0.1 - This may be as much because of the wipe as anything else.
- I installed the Google Apps via the run-once market fetcher. This worked well with the exception of Google Maps:
- Current Google Maps causes almost immediate *bad* crash back to the Cyanogen Spinning arrow, and it stays there. I have to force a full reboot by power cycling. Will need to downgrade to a Maps 5.x.x I have on an SD Card someplace.
- Not sure whats up with Google Talk - Camera works for an instant, but seems to freeze, no audio. Google Talk does not seem to be in the Market, This Google Talk was in the ROM.
- Market Updated to Play automatically. Works fine. Most apps seem to be there.
- Some YouTube HQ videos still only play with HQ off. While messing with this, at some point I lost audio, and had to do the headphones in-out to get speaker audio back.
- 3D Tegra optimized game worked well with good frame rates. (Ground Effect XHD)
Look:
Definitely good ole' Gingerbread - Very few cosmetic changes from 7.1.0.1 - No CM9/Honeycomb look/icons or wallpapers. A few new Cyanogen wall papers that were not in 7.1.0.1
Skype
Just curious if you have tried Skype and the results.
Just curious if you have tried Skype and the results.
Click to expand...
Click to collapse
Sorry, but I do not use Skype.
I'll try a standard SIP client, and report back.
Now, with a Little more time on it, I can report that it is a perfectly useable ROM. I have not seen anything that would be a show stopper, or prevent this from being a release.
WiFi is definitely improved, and I would recommend it as an upgrade from 7.1.0.1.
Now an official CM9 would be better, but until then, 7.2 will keep me from feeling like I need to buy a new tablet for a while.
RC 3 out
I came over from Flashlight. CM7.2 rc3 works very well. Only issue I have is some video resolutions act like there is no sync, just get wavy lines.
Looking at the changes, which can be found here:
https://github.com/CyanogenMod/android_device_malata_smb_a1002
It does not look like much has changed from RC2 to RC3. (Which is a good thing, since by RC3, we should be getting pretty close to a release). Just some build stuff which probably does not effect the packaged ROM at all.
So I have not upgraded from RC2 to RC3.
I also get the diagonal lines in Youtube videos for some settings.
Only the fairly low resolutions seem to work at all.