Related
Hi everyone. This is a weird thing - I haven't found anyone with a similar issue, either here or with Google-fu.
I successfully rooted my HTC Desire a while ago (S-Off) and was pretty happy with it, the LCARS bootanimation installation also went well. After trying out a lot of apps, finding the best configuration for the phone etc. I decided to format and set up the whole thing again on Monday, to have a clean installation and no more space issues.
Although I went for the CyanogenMod V7.1.0-RC1 this time 'round I somehow doubt that has something to do with it, but who knows. Okay, SD card was set up anew, custom mod got installed, everything went as smoothly as it possibly could. (cool story, bro)
However, after I moved the bootanimation.zip into the system\media folder and rebooted, the animation started, but only at half the size it usually has, in the middle of the screen. I tried another one and it was the same thing. The longer one of the two also broke off in the middle with a brief flash, as if I'd pressed the Power button, then stayed dark until I pressed the Power button twice (turn off/ back on), only then it would show me the pin number display.
Apart from that the phone works perfectly.
It's not an incredibly important issue, just something I find weird and would like to fix, if possible. Does anyone have an idea what could be the source of this?
Doesn't anyone have the slightest idea?
you try flash bootanimation over Android Flasher..
Hi majko11293 - first of all thanks for pointing me to this programm. I'd used it before (worked brilliant with my own custom splash screen), but somehow lost it again.
Anyway, even when flashing it with Android Flasher, the bootanimation stays at half size. The animation itself changes depending on which one I choose, but the size issue remains...
Hi All,
I have looked around for a similar problem but could not find anything.
I have a problem with my screen on my HTC Sensation. I was using Virtuous ROM but when this started happening, I wiped with superscript and switched to Insertcoin ROM and the problem actually became worse.
When I lock my phone with the Power button, instead of the screen turning black instantly, the bottom and top of the screen slide up and meet in the middle (like a transition that you put inbetween chapters in a home made movie).
The same happens when I unlock the phone.. and it's very annoying and of course very slow.
I can't work out if it's hardware or not. I just recently edited the build.prop file (only removed the '#' from the screen capture line- which worked, didn't touch anything else)... and now when I unlock, the font and app icons seem a little enlarged and blurry.. then once I slide between screens and back it goes to normal.
I'm a noobie and would appreciate the help.
Thanks
Ginox
I always thought is was on purpose
No, this is very exaggerated and slow. Usually the phones screen goes off reasonably quick when you lock the phone (and vice versa with unlocking).
It sounds like you are describing the CRT animation for locking and unlocking, like an old TV turning on/off. Some ROMs include this by default. If the phone is running slow/sluggish it can look poor and cause other issues like the funky looking icons.
~T.J.
Hmm, it doesn't seem like that kind of problem... my phone runs reasonable fast.
Here's a video of it:
twitvid.com/ZMWJA
Can't direct link, please copy and paste.
Yup, thats the CRT animation, that's what its supposed to do. It must have been included with a ROM you installed by default. Like I said, its meant to look like you are turning on or off and old tube type television or computer monitor. Someone might have a flashable file out there for you to remove it, I don't know. At least now you can search "remove CRT animation" or something and see what you can get.
~T.J.
Oh really, thats interesting as I was pretty sure it done something similar on the previous Virtuous Rom.
Does anyone else out there have this feature on their Insertcoin ROM? (I've only ever had stock, Virtuous and Insertcoin).
I will have a search but if anyone knows the fix, please let me know
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.
So I bought the BLUE Qiku 360 N5s and found how to Root it from GizChina.it BUT for some reason whenever I flash the root developer rom (TO ROOT PHONE) that they provided, my phones camera gets messed up. Now heres the weird thing, I bought my girlfriend the same phone but in BLACK and followed there instructions and her camera works fine. Only my phone for some unknown reason doesn't work the the freaking developer rom. Its frustrating because I want to get rid of all the CHINESE bloatware with the custom rom they provided (which works) BUT I need TWRP to flash it and I need to ROOT my phone before I can install TWRP. Some please send me some guidance cause I'm stressed and desperate!!!! THANK YOU
Verified Rootable
Hi there,
I recently bought the same phone, (Black version), and was finally able to root it after a month of struggling. Other than the camera not functioning, exactly what problems are you experiencing? You were able to fully root your GFs black version? Unlocked bootloader confirmed? Let me know. I'll give you whatever help I can.
Zyraelindir said:
Hi there,
I recently bought the same phone, (Black version), and was finally able to root it after a month of struggling. Other than the camera not functioning, exactly what problems are you experiencing? You were able to fully root your GFs black version? Unlocked bootloader confirmed? Let me know. I'll give you whatever help I can.
Click to expand...
Click to collapse
Can you please tell me what you used to root it? Thats the only problem, after flashing the devrom the rear camera stops working and the front camera works but is grainy and all the functions for the camera stops working (flash beauty etc), I'm able to press on them but it doesn't do anything. The camera is still able to take a picture though. When I press the button to change it to the rear camera it freezes and stops working. I've tried downloading a 3rd party camera app but it doesn''t fix it eithier. Camera is still grainy on the app and the camera flip function doesn't work as well. Also I can't login to snapchat with this phone. I think its because the phone has a built in screen recorder so snapchat won't let me login. Can you help me with that as well? Thank you!!!
raymondchiu said:
all the functions for the camera stops working (flash beauty etc), I'm able to press on them but it doesn't do anything. The camera is still able to take a picture though. When I press the button to change it to the rear camera it freezes and stops working. I've tried downloading a 3rd party camera app but it doesn''t fix it eithier. Camera is still grainy on the app and the camera flip function doesn't work as well.
Click to expand...
Click to collapse
I unlocked the bootloader via fastboot after flashing Giz China's dev-rom. The only real roadblock to rooting it is having the developer software to bypass 360's proprietary bootloader restrictions. Once the dev-rom is flashed, you should be able to utilize all of the adb and fastboot resources as you would for a non-Chinese phone.
Now that you've described your camera problems a bit more, I have to say that it sounds like a compatibility issue. I can't be certain without testing it, but the dev-rom has a lot less bells and whistles than the stock rom, so it's quite possible that the dev-rom is missing the necessary files for running all of the extra camera filters. The dev-rom is just a temporary fix to allow you to alter the bootloader, and isn't ideal for daily use.
I recommend you try reflashing it so that you can get root access, or if you already have root access then simply flash a custom rom to replace it, and then see if your camera is still having the same issues. Don't forget that you'll need to flash SuperSU or Magisk or whatever SU app you're familiar with after flashing the rom. Also, if you try reflashing the dev-rom with 360's software, I recommend doing so via a Windows7 installation. I initially tried it via multiple Windows 10 machines and it failed horribly in all of them. It worked in a matter of minutes in each Windows7 machine though. Go figure.
GizChina also has a custom rom for the 360 n5s, not sure if you're aware of it or not. You can find it here:
ttps://rom.gizchina.it/360-n5s/
You might need to utilize Google translate if you can't read Italian .
Let me know if that helps or if you have more questions.
Yeah oddly it doesn't work with the blue phones. Only the black phone worked. I have 3 N5s's 2 are blue and 1 is black. The black one is completely fine and the two blue phones camera stops working after flashing the DevRom. I don't think theres anything I can do.
raymondchiu said:
Yeah oddly it doesn't work with the blue phones. Only the black phone worked. I have 3 N5s's 2 are blue and 1 is black. The black one is completely fine and the two blue phones camera stops working after flashing the DevRom. I don't think theres anything I can do.
Click to expand...
Click to collapse
Have you tried flashing the custom ROM I suggested? There's no harm in trying. Just backup your files with TWRP, flash the custom ROM, if it works great, if not you can restore the Dev-rom and your old files.
Zyraelindir said:
Have you tried flashing the custom ROM I suggested? There's no harm in trying. Just backup your files with TWRP, flash the custom ROM, if it works great, if not you can restore the Dev-rom and your old files.
Click to expand...
Click to collapse
The DevRom works and roots my phone but messes up my camera on the blue phone. The custom rom also works but it doesn't fix the problem I have with the camera... Keep in mind that I did this with a black N5s and it worked perfectly fine. But when I try it with 2 different blue N5s's they both encounter the problem with the camera. Only the black phone works properly. I have also flashed the blue phones ROM back to the manufacturers and it fixed the problem that the DevRom created with the cameras.
raymondchiu said:
The DevRom works and roots my phone but messes up my camera on the blue phone. The custom rom also works but it doesn't fix the problem I have with the camera... Keep in mind that I did this with a black N5s and it worked perfectly fine. But when I try it with 2 different blue N5s's they both encounter the problem with the camera. Only the black phone works properly. I have also flashed the blue phones ROM back to the manufacturers and it fixed the problem that the DevRom created with the cameras.
Click to expand...
Click to collapse
If that's true and the custom rom has the exact same issues running the camera filters then the only thing it could be is a lack of support built into the roms for those camera functions, or those functions are dependent on an app that has been removed from the new roms, but exists in the stock rom.
In order for either of those to be true though, it means that your black phone and your blue phone should have different camera functions, because the roms aren't changing, the only difference is your phone model (blue or black), so either you've accidentally erased something needed, or there is a series of support files that you could try installing back into the blue phone.
I wouldn't know which files though lol, you'd have to do some research. I doubt you will find much guidance on it by searching online. Your best bet would be to compare the file differences between your black phone and your blue phone to see which camera app files are on the blue one but not the black one (on the stock rom) and then try reinstalling all of those files and their support trees once you flash the dev-rom/custom-rom.
That is what I would do next if it was my phone.
Okay what about the snapchat problem where it doesn't let you login because of the built in screen recording feature in the phone?
Zyraelindir said:
If that's true and the custom rom has the exact same issues running the camera filters then the only thing it could be is a lack of support built into the roms for those camera functions, or those functions are dependent on an app that has been removed from the new roms, but exists in the stock rom.
In order for either of those to be true though, it means that your black phone and your blue phone should have different camera functions, because the roms aren't changing, the only difference is your phone model (blue or black), so either you've accidentally erased something needed, or there is a series of support files that you could try installing back into the blue phone.
I wouldn't know which files though lol, you'd have to do some research. I doubt you will find much guidance on it by searching online. Your best bet would be to compare the file differences between your black phone and your blue phone to see which camera app files are on the blue one but not the black one (on the stock rom) and then try reinstalling all of those files and their support trees once you flash the dev-rom/custom-rom.
That is what I would do next if it was my phone.
Click to expand...
Click to collapse
I've also noticed that the black phones kernal version is 3.10.84 while the blue phones kernal version is 3.10.84-perf (also the snapchat problem on both blue and black n5s)
This preview of the Oreo build is updated with the March 2018 security patches. It is Android Oreo, version 8.1. If you want to use this, keep in mind that this is a development preview! It is not the final release. There are also a few things to note about using it.
It requires you to be bootloader unlocked (unlocking wipes your phone)
This update will wipe your phone even if you're already unlocked
You will not get any OTAs while on this build
VoLTE and WiFi Calling might not work
No CTS, so Android Pay/Pokemon Go may not work
May be some undocumented bugs
If you're fine with all of that, then the download link can be found on Razer's developer page about the update.
If you want to go back to the stock Nougat images, just follow the instructions here.
If anyone does this can they show us some videos
iStasis said:
If anyone does this can they show us some videos
Click to expand...
Click to collapse
Look up a video of Oreo on a Pixel. It looks exactly the same.
No default white theme like normal Oreo same default theme as nougat.
Screen now has a colour option which can be set to show more vibrant colours.
Double tap to sleep (only on lockscreen)
Speakers seem louder than before.
And all the normal Oreo stuff
Also Pokémon go does work.
Roxas598 said:
No default white theme like normal Oreo same default theme as nougat.
Screen now has a colour option which can be set to show more vibrant colours.
Double tap to sleep (only on lockscreen)
Speakers seem louder than before.
And all the normal Oreo stuff
Also Pokémon go does work.
Click to expand...
Click to collapse
Color options and more power for the speakers are both great news. Much excited.
I'm tinkering with GSIs and I've realised you can go into Download Mode by tapping the Power button several times as soon as the Razer logo pops up (before the orange 'tampered' message appears).
In case that helps someone ^
linuxct said:
I'm tinkering with GSIs and I've realised you can go into Download Mode by tapping the Power button several times as soon as the Razer logo pops up (before the orange 'tampered' message appears).
In case that helps someone ^
Click to expand...
Click to collapse
I wonder if there's a way of doing that with maybe the volume buttons to go directly into recovery as well ?
Roxas598 said:
No default white theme like normal Oreo same default theme as nougat.
Screen now has a colour option which can be set to show more vibrant colours.
Double tap to sleep (only on lockscreen)
Speakers seem louder than before.
And all the normal Oreo stuff
Also Pokémon go does work.
Click to expand...
Click to collapse
How would you rate the new colors, I've always felt the display was a tiny bit washed out
need help
im trying to update my phone, but when i run the flash_all command, its says waiting for device and stays there for ever, now it has more than 30 minutes with no sign of working
Horuhe93 said:
im trying to update my phone, but when i run the flash_all command, its says waiting for device and stays there for ever, now it has more than 30 minutes with no sign of working
Click to expand...
Click to collapse
Install Android USB driver
hello5629 said:
Install Android USB driver
Click to expand...
Click to collapse
ADB reboot bootloader then the flash all bat
i tested oreo and it looks very good,but until official release i reflashed the noughat stock img and now my sim wont recognise any help
please
parky169 said:
i tested oreo and it looks very good,but until official release i reflashed the noughat stock img and now my sim wont recognise any help
please
Click to expand...
Click to collapse
It did the same thing to me when I flashed stock nougat to fix boot loop. Remove and reinstall the Sim card. That worked for me.
Anyone having Bluetooth mic issues on this preview?
Just got a new BT headset with a built in mic and it ain't working. Just thought I'd check in here before returning it.
I went back to Nougat but did anyone else notice the screen colours go between vibrant and normal all the time? noticed it on the lockscreen, Keyboard and quick toggles but it only seemed to happen with colourful stuff. Default Razer wallpaper, Coloured keyboard and theme applied etc
Yes @Roxas598 I did notice the colors change from vibrant to normal a lot. And I've been watching Netflix on it lately as well and have been watching the second season of a series of unfortunate events and the whole show has been looking darker than it should, making it hard to watch even with brightness all the way up.
AwesomeFabe said:
Yes @Roxas598 I did notice the colors change from vibrant to normal a lot. And I've been watching Netflix on it lately as well and have been watching the second season of a series of unfortunate events and the whole show has been looking darker than it should, making it hard to watch even with brightness all the way up.
Click to expand...
Click to collapse
I already reported the issue but wanted to make sure it wasn't just me. Thanks!
My Fitbit is not being recognised at all, and my bluetooth mic on my new headphones doesn't work. So it looks like there are some issues with Bluetooth which I'll revert to stock to resolve. Not bad so far, but obviously being close to stock means it doesn't feel much different to 7.1, certainly not enough that you get that excited buzz we once got back when Android revisions were massively different.
Literally got everything working
joemossjr said:
Literally got everything working
Click to expand...
Click to collapse
How did you do this? I'd like to know since I'd like to use Netflix and Google Pay.