Dear you guys,
I don't know what has happened to my d850 but I can't use any MM ROMs. [emoji30] .
I have tried a three ROMs, including Resurrection, unofficial CM, and AICP. The flashing itself all went fine (or so they seemed) and boot animation started. During this process, I could here small sound coming from the Camera area (I can't say for sure it was the Can, just the top area of the phone). Then the optimizing process. The phone wouldn't pass "Starting Apps" message. And that sound, which came at regular intervals, was still heard.
The phone is now running CM12.1, rather smoothly. Camera would crash if I switched to front cam.
Anybody in the same situation? Any work around?
[emoji37]
Related
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.
Camera stopped working on AOSP roms. Flashed a new version of PacMan which I've been running for weeks, and camera suddenly stops. Won't work on any AOSP rom. Flashed back to TW momentarily, and it works fine however.
I've tried:
Numerous clean installs
Fixing permissions
Clearing gallery data
Re-installed newest baseband
Half the time I get a "Cannot Connect to Camera" error, and half the time I can appear to take one picture and then the device goes black and/or freezes.
Any ideas for a fix???? I've got a 1 year old, so the camera is not really optional for me at this time. Never had so many problems on a phone that couldn't be resolved with a clean flash, making me miss my trusty Gnex and almost starting to regret this phone. Thanks in advance!
Fixed... Odin back to stock and re-rooted.
When lollipop builds were first released for the one, there were tons of bugs. Since then much of them have been cleaned up. I've had two consistent problems, through at least 4 different roms.
1) recording video, and you hit stop. It doesnt stop, it just hangs and keeps recording until you force close and lose your recording. It doesnt appear to be happening in this rom however. So this is solved.
2) The current issue I'm having is that no matter which lollipop rom I use, if I try and take video using the built in camera, it shows heavy people static and can't take the video. I have multirom recovery installed, but I'm only using the primary rom. And I've now switched to AK kernel thinking maybe it was a kernel issue... But to no avail.
Anyone have any tips? I'm at wits end. Only happens with instagram.
Currently running a fresh install of darkobass, with ak kernel...
But it's also happened on CR droid, 2 of the first cm12 daily builds that released, blisspop, and on paranoid android that I just tried before darko.
I just want to let you know I finally made the ROM jump from MaximusHD to CyanogenMod 12.1 and it went superb!
Before starting this I thought I would be busy the whole evening (or more than one) so I prepared for the worst. I still use this phone on a daily basis. I got another HTC oldy as a backup just in case. My HTC One S isn't recognized on my PCs anymore since jumping in the swimming pool with it last summer so I had an extra handicap not being able to upload from PC to device.
I updated TWRP to the latest. Cleared storage. Rebooted in MaximusHD again ignoring the setup wizard as much as possible. Once booted I opened the web browser and downloaded the CM12.1 05DEC Unofficial ROM and TK GApps mini directly to my device. (All links available in the specific thread here on XDA) Booted in recovery again and flashed CM12.1 and TK GApps. All my apps and settings were uploaded/installed when the device booted CM12.1.
After boot all I had to do is change my Mobile 3G APN setting.
After one hour of work I couldn't believe it went so quick! And easy! The experience of CM12.1 on this 3 year old phone is unbelievable. I thought I would experience more lag and slow responses but... none of that. I can't notice any difference in speed comparing with the MaximusHD ROM.
I hope this stimulates others to make the update.
bakmanhans said:
I just want to let you know I finally made the ROM jump from MaximusHD to CyanogenMod 12.1 and it went superb!
Before starting this I thought I would be busy the whole evening (or more than one) so I prepared for the worst. I still use this phone on a daily basis. I got another HTC oldy as a backup just in case. My HTC One S isn't recognized on my PCs anymore since jumping in the swimming pool with it last summer so I had an extra handicap not being able to upload from PC to device.
I updated TWRP to the latest. Cleared storage. Rebooted in MaximusHD again ignoring the setup wizard as much as possible. Once booted I opened the web browser and downloaded the CM12.1 05DEC Unofficial ROM and TK GApps mini directly to my device. (All links available in the specific thread here on XDA) Booted in recovery again and flashed CM12.1 and TK GApps. All my apps and settings were uploaded/installed when the device booted CM12.2.
After boot all I had to do is change my Mobile 3G APN setting.
After one hour of work I couldn't believe it went so quick! And easy! The experience of CM12.1 on this 3 year old phone is unbelievable. I thought I would experience more lag and slow responses but... none of that. I can't notice any difference in speed comparing with the MaximusHD ROM.
I hope this stimulates others to make the update.
Click to expand...
Click to collapse
I've been tempted by the idea of jumping the MaximusHD rom ship for a while too. Are you happy with the camera performance? One of the reasons I'm reluctant to go the non-Sense rom way is the lack of the full hardware access to the camera on those roms.
I just jumped the ship three days ago. I didn't use the camera besides taking 3 pictures for test purposes. I'm a long time Camera ZOOM FX user so the app installed itself again. I replaced the CM12 camera app in the drawer with it.
I need more user experience time with the camera to tell you it lacks in any way.
What, besides performance (speed) issues, will affect the camera not being able to have full hardware access?
bakmanhans said:
What, besides performance (speed) issues, will affect the camera not being able to have full hardware access?
Click to expand...
Click to collapse
A couple of things I remember were missing from non-Sense camera apps are the ability to shoot slow motion video (lower res but higher fps) and the HDR mode for photos.
Not that these two produced any usable results though .
I believe the other parameters like photo/video resolution are adjustable with the stock CM camera and ZOOM FX apps, right?
twotimer said:
A couple of things I remember were missing from non-Sense camera apps are the ability to shoot slow motion video (lower res but higher fps) and the HDR mode for photos.
Not that these two produced any usable results though .
Click to expand...
Click to collapse
I can't find slow motion video. I never saw it in the MaximusHD ROM either. ZOOM FX cam does have the HDR option, just like with MaximusHD. But seriously, it's nothing more than a gimmick. Do you ever use it?
twotimer said:
I believe the other parameters like photo/video resolution are adjustable with the stock CM camera and ZOOM FX apps, right?
Click to expand...
Click to collapse
With stock CM camera I don't see these options. This cam app is really minimal. Some say you need to set resolution by entering the hamburger menu upper-left but I don't have the menu. App version is 2.0.002.
With ZOOM FX Premium all resolutions settings are there.
When booting my phone this morning I noticed that there is still one MaximusHD ROM leftover. I guess it's not really part of the ROM. It's the boot screen. The first screen you see when cold booting your phone. It's a screen with HTC logo and the development warning text in red underneath it. Can I easily get rid of it?
bakmanhans said:
When booting my phone this morning I noticed that there is still one MaximusHD ROM leftover. I guess it's not really part of the ROM. It's the boot screen. The first screen you see when cold booting your phone. It's a screen with HTC logo and the development warning text in red underneath it. Can I easily get rid of it?
Click to expand...
Click to collapse
It's not part of the ROM, it's rather a part of the bootloader itself. You can change it by flashing a modified bootloader version:
http://forum.xda-developers.com/showthread.php?p=38387544#post38387544
Just read the thread on how to do that and find the one that fits your HBOOT version.
Coming from MaximusHD my hboot is at version 2.16... I don't see any download for that.
I've been using 20151223 UNOFFICIAL for some time now without the camera/flashlight issue. I've been using the camera more than once during the holidays.
Only trouble I have is getting cellular (3G) back online after flight modus. It's not possible. I have to restart the device every time. Anybody else experiencing this?
No, working great here on 2015-12-23 Unofficial HBOOT 2.16 from Flyer. When going out of plane mode, it takes around 15 seconds to get H icon (for HSDPA, 3G if you prefer). It may be a problem with the SIM card or advanced operator settings.
This is my first time installing custom ROM's on my otherwise stock Sprint Motorola photon 4G LTE. After successfully flashing CM13 (2016_08_20 snapshot release), I tried to make a call, and upon hitting "call" from the dialer, the screen goes black and stays that way. The only recourse is to hold down power button long enough to reboot. While the screen is black, there is no sound from the ear piece (i.e. it does not appear that the call is connected). Finally, while the screen is black, the phone does exhibit some reactions: it vibrates sometimes if I hit the power button, in other words, the device is still 'on" until I have to reboot it.
After this happened, I gave up on CM13 and flashed CM-12 (the latest snapshot release, from 2015) , and experienced the same behavior.
The call apparently was completed, because the other party received a missed call. However, there was no sound on my end (although there was side-tone, when I breathed on it)
I googled for about an hour, and saw examples of the same behavior on other devices claiming to be related to the proximity sensor (though in those cases, there apparently was audio in the ear piece-- ie. the call completed, and was in progress while the screen was black). This behavior was not observed a few minutes before under stock ROM in the same device (so doubt it's a strictly hardware issue, so doubt I need to open the device and clean the sensor, per some of the suggestions out there).
I suspect the answer is very basic, because I found no similar threads searching XDA.
Please let me know any ideas. I did not do anything about updating my baseband version from stock before flashing the CM ROMs., but don't know if I have to I'm a noob at custom Rom's and just remembered that you had to worry about the baseband / radio version back on the HTC Evo 8 years ago, which was my last time flashing. Again, the ROM itself worked fine-- wifi and 3G/LTE connectivity was a success.
Let me know any ideas.
thanks
After restoring to stock, dialing worked again on the phone, but the behavior on the device was different from two other photons I tested next to it.
In the stock ROM, the call connected, but the screen turned off immediately upon hitting "call" (even when the phone was on the desk). You could get the screen back (in stock only) by hitting the power button.
In my other two photons, the black screen does not kick-in immediately. So it does appear it could be something having to do with the proximity sensor (i.e. it's always engaged). I don't have the skills to confirm. I am writing-off this phone for now, and have a different device (so not a high-priority thread at this point), but let me know if anyone has any ideas. Thx.
There's a way to validate if the prox sensor is working - zDeviceTest in the Play Store will test all of the hardware, and it will also show the metrics each piece of hardware is receiving - the prox sensor being fairly simple, it just identifies if an object is "near" or "far".
I always recommend making sure everything works in the stock ROM before flashing anything custom - as you need to validate everything works before making tweaks.
My advice is the same as arrrghhhs. (This name really looks like it was typed with a Photon Q with some characters repeated by the device >.>)
I noticed that my proximity sensor sometimes "stuck" to near (I use some different app [SatStat] so it shows 3 cm or 100 cm instead of near/far). Winking a little above the sensor helps sometimes. But your problem sounds like a defect.