Database Info

[Q] HTC Desire, rooted, bootanimation display/size issue

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...

[Q] LG P920 3d Touch Screen strange behaviour

VERY strange touch screen behaviour
Device: LG P920 Australian Optus Model, was upgraded to 2.3.5 using LG tools, then rooted ( cant remember which guide I used but it installed a package and su, was not superone click, maybe VRoot? it was for 2.3.5 and it worked) .
- then updated to v28b- eur- xx ICS , 4.0.4, kernal 3.0.21 using guides from Drastic00 xda guide
I am a bit of a phone noob, just learning to root using old samsungs and did my first ics flash on the LG P920. All good so far and thanks to all the guide contributors.
So the problem I am having in that the touch screen has two dead sections, the bottom section exactly covering the area occupied by the phone , message ect icons, and half way up a similar size section right across the phone. I have searched every post and forum I can find and cant find any thing like this. The touch screen works, just not in those sections. To get around it I can some times flip the phone to access things on parts of the screen that work, but a lot of time not.
I believe this started after I rooted the phone, although its always had issues with touch lag. If I hadnt rooted the phone, and its was just some random section I would put it down to hardware, but using the developer touch screen tests i can see the dead parts are exactly rectangle over the main phone controls at the bottom, which seems to me to indicate software, and on the new ics home screen I have activated the touches to be visual, and there are quite often two touch points racing back and forth along the little white line just above the dialer, message ect icons. when this happen you cant activate anything else because it thinks you are using two touches on the screen already.
I have used the LG remote computer controls program and i can access all sections of the screen perfectly through it, so that rules out everything but the link between the screen and phone in terms of software/ hardware. Have pulled off the ribbon plug and reattached also. I was hoping after upgrade to ICS it would be resolved but no luck. Unfortunately I cant remember how I rooted it but it was working fine for a few days then i noticed the touch issue after I started killing bloatware with Titanium. Is it possible removing an app has somehow messed up the touch screen code and its somehow not being repaired by the ics upgrade? Anyone seen this type of thing before. Found one post with a dead section after removing an app, but wast the whole bottom section and no ghost touches running around. Possessed?

http://forum.xda-developers.com/showthread.php?t=2213727
actually this post is similar to my problem but no solution found, will contact poster to see if it was a screen failure or software. My screen is also periodically doing the flashing buttons, going beserk thing as described in this post.

[Completed] Nexus 5 BLACK SCREEN ( FASTBOOT ONLY)

I had my nexus 5 using multirom manager i had liquid smooth and paranoid android roms on it and i flashed ubuntu too the phone was working fine on all of the three roms.. the only issue i had was the microphone that wasn't working on phone calls but it worked only on speakers so i tried to change the mic piece and same the mic wasn't working. So i thought that it was something wrong with the software and i tried to flash a different kernel (Franko Kernel ) and i tried to flash couple GAPPS and nothing still with the mic problem and in the ROM i had a message that says com.play.services not responding so i tried to go on play store and upgrade the services and the play store wasn't working so i dowloaded some play services from chrome, after i installed the apt file i tried to reboot the phone and as soon as i did the reboot the screen had some rainbow an gray colored lines all over the screen horizontal and vertical lines, after that the screen was only black but i could see the backlight on it. I tried to restore stock with fast boot and still nothing i restored android 4.4.4,5.0,5.0.1 and nothing happen the screen was still black, the only thing was that the phone was able to be seen on fast boot and so i thought that the problem was the screen or the flex cable so i tried to buy a new screen i did ordered it from eBay and last night i changed the screen, but nothing worked I'm still having the black screen and the phone is still going on fast boot mode but I'm not able to use my phone... PLEASE HELPPP !!!!

Hi
Thanks for writing to us at XDA Assist. I had a quick search and found a great q&a thread for your device here:
[HELP THREAD] Nexus 5 | Ask any question
I'd suggest you ask your question there, that way it'll reach the most suitable people to answer your question.

Thread closed, thanks.

[Q] Camera and lamp won't open

Hi everyone, I've look everywhere and I'm kind of desperate now
So, I've had my nexus 5 since it came out here in Europe, never had an unsolvable issue (thanks to the internet), but right now I'm stuck
MY PROBLEM :
One day (just like this, I don't remember doing anything special with my phone), the camera completely stopped working, along with the lamp.
DETAILS ABOUT THE PROBLEM (The situation right now) :
1. Camera doesn't show up in the application drawers
2. It DOES show up in Settings/Applications, and in "My applications" tab from Google Play, but I cannot open it in any way. When I could, however, it would just crash away.
3. I am also unable to access the stock lamp from anywhere (quick settings, etc.)
THE INITIAL SITUATION AND THE EVOLUTION OF THE PROBLEM :
1. I was running CM12.1 (nightlies) on my Nexus 5, and I beieve it occured after an update, but I don't believe it really has much to do with it. When I tried to open the camera, it would show me "unable to get a link with the camera" (translation may not be exact) and the system lamp had disappeared
2. I tried to downgrade the phone, to an earlier nightly, but it didn't fix it.
3. I've donne every kind of wipes : Data, Dalvik, Cache, even Internal Storage
4. After a full Internal Storage Wipe, I reflashed fresh Marshmallow images from the official website, unrooted, reflashed stock recovery, relocked the bootloader and used the system factory reset again on my phone.
5. After this, the problem changed a little bit. The lamp is still impossible to find, but however this time the camera is too. What I mean is, on CM, it used to show up and crash, now I can't find it in the app drawer (See DETAILS ABOUT THE PROBLEM)
I think that's all, so yeah, this one is kind of a challenge.
If the solution is software... Well i really dont know what I could try else; if it's hardware, I'm not afraid to open up my phone. (however I'm a complete noob)
One last thing, I've contacted Google, but the phone they sent me back was in such a bad state that I'm keeping mine (or getting them to send me an other), because the power button was really used, and the lowest part of the screen really "white" (brighter than the rest, my guess was it had fallen)
Thank you very much !

Hi, looks like we have the same problem. Unfortunately I have no solution for you, either. I have ordered a new rear camera from ebay that should show up here end of January. I'll let you know if that fixed the problem.

As you can see from my recent post, I am also having the same problem. I have also order a replacement rear camera from ebay and I fitted it. It worked for one day and then it also stopped working. I am not sure whether it is worth repeating this experiment or I'd just be wasting money on replacement cameras. So annoying, because, apart from the camera (and the torch), the rest of the phone functionalities are still perfectly fine.

Has anyone tried to use a different camera or torch app?
Sent from my Nexus 5

ShapesBlue said:
Has anyone tried to use a different camera or torch app?
Sent from my Nexus 5
Click to expand...
Click to collapse
Of course.

maurimauri29 said:
Of course.
Click to expand...
Click to collapse
That's odd then. It seems like you've done nearly everything that should of been done. I'm at a loss for words here
Sent from my Nexus 5

Qiku 360 N5s ROOT/TWRP/Custom ROM

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)