Database Users

Video added: camera flash sync problem! frustrated

i recently received a new nexus one because of dust under the screen. today i noticed my camera flash is not working properly.
everytime i take a picture with the flash enabled the flash fires once (for exposure metering i assume) but the second flash never comes. so the images are flashless and super dark.
i tried "factory resetting" and the roblem continues. anyone else have this problem. seems like a software issue? any ideas on how to fix this?
im on stock ere27 2.1 update-1. ALSO this problem effects aftermarket apps as well because its part of the firmware.
Update: recorded a short video to demonstrate my problem.
http://www.youtube.com/watch?v=RVKlSe0UiDY

Called HTC, they had no idea what they where talking about. Transfered me to Google support. They had no idea what was causing this problem and suggested a "swap"
... this phone is a SWAP... its 2 days old.
I'm getting sick of this.

Is there anywhere to download the full stock ROM that is flashable without root? I tried the "manual update" patch from 2.1 to 2.1 Update-1 but that didnt fix it either.
Maybe my firmware has a glitch that is causing this flash problem. Anyone know where I could find the full flashable ROM?

Recorded a short video to further explain whats happening.
http://www.youtube.com/watch?v=RVKlSe0UiDY
please let me know what you think.

dills84 said:
Is there anywhere to download the full stock ROM that is flashable without root? I tried the "manual update" patch from 2.1 to 2.1 Update-1 but that didnt fix it either.
Maybe my firmware has a glitch that is causing this flash problem. Anyone know where I could find the full flashable ROM?
Click to expand...
Click to collapse
It's definately a odd problem, I haven't seen this myself, but if you have already reset your phone to stock and have done the updates and are still experiencing problems. Sadly, your best bet is to have Google warrenty your phone. Don't root to see if its going to fix the problem, you'll be in a much deeper hole if it doesn't fix your problem.
TL;DR
Let Google replace your phone.

Is there a way to re-flash the stock firmware from a ZIP without having the bootloader unlocked?

dills84 said:
Is there a way to re-flash the stock firmware from a ZIP without having the bootloader unlocked?
Click to expand...
Click to collapse
You might want to take a look here.
It has a complete list of all the stock roms and images. (With download links.)

You need to warranty your phone. Don't waste your time trying come up with a solution. I'm sure it's a hassle, but it will be worth it in the long run.

prettyboy85712 said:
You need to warranty your phone. Don't waste your time trying come up with a solution. I'm sure it's a hassle, but it will be worth it in the long run.
Click to expand...
Click to collapse
Just trying to come up with an easy alternative since this is kind of a minor issue?
Also this phone is my second nexus one, First one had tons of dust under the screen. This one is real clean so I was hoping I could hang onto it!

why did the picture without any flash at all have a brighter resolution than the one with the flash on?
EDIT - Have you tried one of the other free camera apps from the market? It might be an error or problem with the stock Camera.apk

palosjr said:
why did the picture without any flash at all have a brighter resolution than the one with the flash on?
EDIT - Have you tried one of the other free camera apps from the market? It might be an error or problem with the stock Camera.apk
Click to expand...
Click to collapse
As stated, this is the problem. The first flash is for "exposure" the second flash is for the actual picture. So the camera is exposing thinking there is a flash coming from the camera. But there is no flash happening during the picture, only before hand.
And yes this is a firmware problem. so any app that uses the camera has the same problem with the flash. I've tried a bunch.

Does anyone know the actual hardware innards of the nexus? If this is just some kind software glitch I may just unlock my bootloarder and fire up CM. Maybe that'll fix it?
I'd hate to return another one... this ones screen is perrrfect.

[Q] In call audio problem

So I convinced my aunt to get the nexus 4 a while back. Unfortunatly its now not able to make calls correctly. Everything works on the phone without an issue just that There is no sound incoming or outgoing without having to put it on speaker mode (while in a call). This is a already know issue but there is not true way to fix it. We got around it by install the aplication called soundabout and unchecking something about the headphones. That got It to work... for a while. Now it is not working and am going to have to have to downgrade it back to 4.2.1? I read that was the only way. But I wanted to find a real solution. Or at least a reason as to why it happens to maybe figure out a solution?

Are you on 4.2.2? If so, you need your radio baseband upgraded to .48.
If that's not the case, then it could be a hardware issue.
Sent from my Nexus 4 using Tapatalk 2

cmacia06 said:
So I convinced my aunt to get the nexus 4 a while back. Unfortunatly its now not able to make calls correctly. Everything works on the phone without an issue just that There is no sound incoming or outgoing without having to put it on speaker mode (while in a call). This is a already know issue but there is not true way to fix it. We got around it by install the aplication called soundabout and unchecking something about the headphones. That got It to work... for a while. Now it is not working and am going to have to have to downgrade it back to 4.2.1? I read that was the only way. But I wanted to find a real solution. Or at least a reason as to why it happens to maybe figure out a solution?
Click to expand...
Click to collapse
there are a few ways to fix this. technically its not broken, they want you to use the newest baseband/radio, since it disables lte. easiest way is to flash the .48 radio, which was already stated. there is also a method that involves editing a certain file(found in the original dev threads).

simms22 said:
there are a few ways to fix this. technically its not broken, they want you to use the newest baseband/radio, since it disables lte. easiest way is to flash the .48 radio, which was already stated. there is also a method that involves editing a certain file(found in the original dev threads).
Click to expand...
Click to collapse
When she brings me the phone ill have a look at it. Thank you for the replies. Ill probably upgrade her baseband seeing as how she doesnt need lte. I flashed the 4.2.2 images available on the google developers website. All of them. Do those images comes with the baseband that is needed? It came with the radio, recovery, and a few other things... I forgot.

cmacia06 said:
When she brings me the phone ill have a look at it. Thank you for the replies. Ill probably upgrade her baseband seeing as how she doesnt need lte. I flashed the 4.2.2 images available on the google developers website. All of them. Do those images comes with the baseband that is needed? It came with the radio, recovery, and a few other things... I forgot.
Click to expand...
Click to collapse
Where can I get the 4.2.1 Images seeing as how it was taken down from the google website. And so the .48 boot loader image
I Found this http://www.randomphantasmagoria.com/firmware/nexus-4/occam/ but i am not sure what version to download? are they all compatible?

Downgrading from JB to ICS

-STILL HAS SIGNAL PROBLEMS-
Hi guys. Im not exactly new but i think this is my first post, cos usually i don't have anything interesting to post.
Bit of backstory:
Had a razr i for a few months. Upgraded to JB, hated the removal of sleep mode and the pervasive fuzziness to it all (ics just seems much more crisp to me) and so decided to downgrade. Assumed peoples of xda had it figured out, ended up with complete refusal to connect to any mobile networks about an hour after boot, which meant i had to restart a lot, which meant crappy batt life. Tried to upgrade back to JB, bricked and dead. Is now a useful and attractive paperweight.
Bought another, fully intending to keep it on ics. Experienced some issues with software bugs, figured they would be sorted in JB, which they were. However, missed ICS. Searched youtube for a decent way to downgrade, found a video describing how to downgrade with a different method than i have seen anywhere on xda - editing xml file in the fastboot files, and then using rsd lite. Looked safe, tried, now rocking fully working ics exactly as it was when i bought it, save for now having an unlocked bootloader.
Title of video is Downgrade RAZR I XT890 do JB (4.1.2) para ICS (4.0.4)
(cannot link, technically new member lol)
Some instructions, because the video goes on unnecessarily :
Get the fastboot files (it says and links to brazil in vid, but i used GB Orange, which my phone came with, and it worked fine)
Extract
Edit xml with notepad++ as follows
Delete line with getvar max-download (My rom didnt have this line anyway)
Delete line that mentions flashing gpt
delete line that mentions flashing motoboot
save file
(Guy turns back into zip, but is unneeded)
Open xml with RSD lite
Install in fastboot
HUZZAH ICS
Try at your own risk, can only say that this suggests only gpt and/or motoboot are the files that affect the service required code corrupt message (which i got on my first razr i, with and without using the unbrick files on xda)
I dont understand any of what the guy is saying, but if you need to see it in action, the vid is on youtube, shows it very well and gets points clearly across
This is just about the only place i can post this so yeah
glhf, i take no credit or responsibility, i am but a wandering do-gooder and whatnot

have you tried it?

antkalaitzakis96 said:
have you tried it?
Click to expand...
Click to collapse
Yup, thought that was clear from the post worse writer than i thought
Currently posting this from my downgraded ics razr i. Hasnt even had a hiccup, good sign

FullXion said:
Yup, thought that was clear from the post worse writer than i thought
Currently posting this from my downgraded ics razr i. Hasnt even had a hiccup, good sign
Click to expand...
Click to collapse
keep me informed cause I want to downgrade too but I am afraid of all those bricked devices

Is it still working great?

any news ?
any news on this ?

Bad news
While everything worked fine for a few days, the signal problems cropped up again, so i had to flash jellybean again in order to get a fully functioning phone. Absolutely stumped as to why these problems happen, looks like ics is off limits as far as i can see.

FullXion said:
Bad news
While everything worked fine for a few days, the signal problems cropped up again, so i had to flash jellybean again in order to get a fully functioning phone. Absolutely stumped as to why these problems happen, looks like ics is off limits as far as i can see.
Click to expand...
Click to collapse
well, that means no ics for me

Many problems with 4.4.2 on Nexus 4

Hey guys, I've been having A LOT of issues with the new updates. First the 4.4 and then the 4.4.2 that didn't solve a thing. I've installed them via OTA but after that i've already did:
- factory reset
- installed via fastboot 4.3, then updated via OTA to 4.4.2
- installed via fastboot 4.4, then updated via OTA to 4.4.2
- factory reset AGAIN - installed via fastboot 4.4.2.
I don't know what do to anymore! I can't take pictures because nexus just turns off the moment i take one. I can't install facebook, twitter or instagram and another random apps... And btw, is it normal that in 10 minutes the battery charges to 1% to 50%? i think i never noticed that...
BUT WHAT DO I DO? PLEASE HELP!
UPDATE:
This problem is solved, it was the battery. I've changed the screen recently and it needed a new battery too. Thanks to everyone that tried to help me

just flash the factory images for 4.4.2 via fastboot
Sent from my Nexus 4 using XDA Premium 4 mobile app

saifulh2304 said:
just flash the factory images for 4.4.2 via fastboot
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
how do I do that? sorry but I'm a little noob.

maznex said:
how do I do that? sorry but I'm a little noob.
Click to expand...
Click to collapse
follow the guide here: http://rirozizo.blogspot.com/2013/11/guide-how-to-flash-factory-images-from.html

maznex said:
how do I do that? sorry but I'm a little noob.
Click to expand...
Click to collapse
If you don't know how to use fastboot, use the Wugfresh toolkit, makes life very easy. It has the drivers, downloads recoveries, root files and the factory images. Really is easy with that.

Riro Zizo said:
follow the guide here: rirozizo.blogspot.com/2013/11/guide-how-to-flash-factory-images-from.html
Click to expand...
Click to collapse
maritimesbob said:
If you don't know how to use fastboot, use the Wugfresh toolkit, makes life very easy. It has the drivers, downloads recoveries, root files and the factory images. Really is easy with that.
Click to expand...
Click to collapse
Guys, like I said I used fastboot to install 4.4.2, it still didn't work. I followed this guide googlenexusforum.com/forum/nexus-4-roms/4046-guide-flash-stock-option-using-android-sdk-tools.html

Hey, guys, I haven't updated it to 4.4.2 yet cause my phone is rooted so I'm asking is it worth to go through all the process again? And if yes can anyone state the new features? ☺ thx a lot!
Sent from my Nexus 4 using XDA Premium 4 mobile app

Looks like a hardware issue to me. Probably your battery is faulty... Could explain the shut downs and trying to use the camera usually drains more battery so again that could it be. Could you be more specific about the other errors that you get?
Sent from my Nexus 4 using xda app-developers app

evdrmr said:
Looks like a hardware issue to me. Probably your battery is faulty... Could explain the shut downs and trying to use the camera usually drains more battery so again that could it be. Could you be more specific about the other errors that you get?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Hardware? It started to happen only when I updated the first time via OTA to 4.4.
I open the camera, I try to take a picture, the flash goes on and then the phone goes off. Sometimes I can turn it on and the battery it's the same, sometimes I can't turn it on without connecting to the charger because it goes off when I go to insert the PIN.
Well, after I understood that the problem was that apps, when I turned the WI-FI on, the phone immediately turned off after that I unistalled that apps and when I turned the WI-FI on I could go on Chrome and Play Store, and installed some apps (like n7 player) and everything was OK.
One time I installed Twitter and I used it for a bit and everything seemed fine but then I installed Facebook and the phone crashed again so I unistalled both. Same with Instagram.
I don't know how much more specific I can be... I really need help :s

it's not hardware. anyone who had this phone running pre 4.3 aosp will remember the camera issues and the clicking noises that went along with the focusing and then the reboots. the battery charging is also a widely experienced issue as well as going from a full charge to 50% in a few minutes. I'm getting the camera bug again on 4.4.2 hope a .3 build pops up soon to deal with it. I'm also 100% stock no root

aaronrw said:
it's not hardware. anyone who had this phone running pre 4.3 aosp will remember the camera issues and the clicking noises that went along with the focusing and then the reboots. the battery charging is also a widely experienced issue as well as going from a full charge to 50% in a few minutes. I'm getting the camera bug again on 4.4.2 hope a .3 build pops up soon to deal with it. I'm also 100% stock no root
Click to expand...
Click to collapse
exactly this is happening but on 4.4.2
BTW, when I'm charging the phone, none of this problems happens. I can install and use all apps and use the camera.

maznex said:
exactly this is happening but on 4.4.2
BTW, when I'm charging the phone, none of this problems happens. I can install and use all apps and use the camera.
Click to expand...
Click to collapse
if I were having all those issues I'd try installing the Factory Image again or maybe try 4.4.1 and then use the OTA to update. BUT there is definitely some bugs in the latest KK release

aaronrw said:
if I were having all those issues I'd try installing the Factory Image again or maybe try 4.4.1 and then use the OTA to update. BUT there is definitely some bugs in the latest KK release
Click to expand...
Click to collapse
I did all of that as I refered in the beggining... I will try to install 4.4.1 though, that was the only thing I didn't do, but I doubt it's gonna work, because installing 4.4 and 4.4.2 didn't solve a thing

sorry about the double post but there isn't the factory image for 4.4.1 here... https://developers.google.com/android/nexus/images#occamkot49h .
I tried to flash 4.4.2 following this guide http://rirozizo.blogspot.pt/2013/11/guide-how-to-flash-factory-images-from.html and when I turned it on I had no signal.. what does that mean? I guess it didn't worked..

maznex said:
sorry about the double post but there isn't the factory image for 4.4.1 here... https://developers.google.com/android/nexus/images#occamkot49h .
I tried to flash 4.4.1 following this guide http://rirozizo.blogspot.pt/2013/11/guide-how-to-flash-factory-images-from.html and when I turned it on I had no signal.. what does that mean? I guess it didn't worked..
Click to expand...
Click to collapse
The latest factory images are 4.4.2, that's why you didn't see 4.4.1 on Google's server. When you flash factory images, your radio will also be updated. When you flash a custom ROM, your radio doesn't get updated, that's why you had problem with cell signal. Or flash the appropriate radio for the ROM.

taodan said:
The latest factory images are 4.4.2, that's why you didn't see 4.4.1 on Google's server. When you flash factory images, your radio will also be updated. When you flash a custom ROM, your radio doesn't get updated, that's why you had problem with cell signal. Or flash the appropriate radio for the ROM.
Click to expand...
Click to collapse
The phone asked me to insert PIN and then I had cell signal again.. Should I flash 4.4.2 again flashing the radio too? Because I have the feeling that this will not solve my problem. Like I said in the beggining I followed another guide to flash my phone, and in that guide it said to flash radio and "bootloader-mako..." (not sure what that is) and the cell signal problem still happened and then I couldnt install Facebook or Twitter or had my location on or using the camera without the phone turning off or rebooting...
EDIT: The phone just turned off when updating Google apps, so yeah... Didn't work :s

maznex said:
The phone asked me to insert PIN and then I had cell signal again.. Should I flash 4.4.2 again flashing the radio too? Because I have the feeling that this will not solve my problem. Like I said in the beggining I followed another guide to flash my phone, and in that guide it said to flash radio and "bootloader-mako..." (not sure what that is) and the cell signal problem still happened and then I couldnt install Facebook or Twitter or had my location on or using the camera without the phone turning off or rebooting...
EDIT: The phone just turned off when updating Google apps, so yeah... Didn't work :s
Click to expand...
Click to collapse
You said that when a PIN is input, the phone has signal again which means it's not a radio issue. Did you set up a PIN in the security section in your phone?

taodan said:
You said that when a PIN is input, the phone has signal again which means it's not a radio issue. Did you set up a PIN in the security section in your phone?
Click to expand...
Click to collapse
No this is just something that started to happen along with the other problems... Sometimes the phone loses signal for no reason and goes to the PIN input screen.

maznex said:
No this is just something that started to happen along with the other problems... Sometimes the phone loses signal for no reason and goes to the PIN input screen.
Click to expand...
Click to collapse
Which radio are you using? It should be .98 if you are on KitKat 4.4.2. You can flash a standalone radio zip file in recovery.

taodan said:
Which radio are you using? It should be .98 if you are on KitKat 4.4.2. You can flash a standalone radio zip file in recovery.
Click to expand...
Click to collapse
I don't know I will check later because now I'm not home. But when can I find that zip file and if I flash that it will only solve the cell signal thing right?

FXZ for Kit Kat released!

Are you bricked after the OTA? Here's how to unbrick it, locked or unlocked.
One other note: this is NOT an official 183 FXZ, so if this doesn't work, it won't make things worse, but you'll just have to wait for the "official" 183 FXZ.
Thanks go to stras1234 for providing a KK FXZ for those that needed it to unbrick their phone.
Another big thanks goes to SamuriHL for providing a tool to use the FXZ provided by stras1234 to make your job easier to unbrick your phone and get you running with KK.
Go here to get the FXZ and tool to help you profit in the glory that is Kit Kat on the XT926 Droid RAZR HD -> http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-to-kitkat-ota/
I have removed all my instructions as they are useless and no longer necessary with the FXZ being released.

Recommended strictly for unlocked bootloaders? Or would those of us with locked bootloaders be safe attempting as well providing we're on stock 9.30?

hi @iBolski i just want you to know that i share your post on the kk tracking post!

cmchance said:
Recommended strictly for unlocked bootloaders? Or would those of us with locked bootloaders be safe attempting as well providing we're on stock 9.30?
Click to expand...
Click to collapse
If you're already on stock 9.30, then it should work. I think the hang-ups for many who are manually loading it themselves via taking the OTA directly, were where if you were pushed the OTA and immediately accepted it and allowed it to go through and update it, it might have worked as long as you were unrooted on stock 9.30.
However, I chose to save the OTA off to the side (from the /cache directory) and hence, booted into the recovery manually, not realising that it installs a newer stock recovery and that's where I got hung up at. I thought the install failed, when in reality, I had to go back into the recovery and install it again. Of course, I tried using vol-down + vol-up and it wouldn't work.
If you currently have root though under 9.30, you might want to hold off until someone verifies if root can be obtained again. Because, without an unlocked boot loader, you will more than likely lose your access to root, especially if the latest "exploit" for 9.30 doesn't work under KK.
Your mileage may vary, but I don't have a locked bootloader phone to test this out on, so please, I do not accept any responsibility for what may happen if you try it, whether you have a locked or unlocked bootloader.
Thanks!

Just what I was needing to hear! I am currently rooted so I'll probably hold off. I've got a used Moto X on order though, should get it in today. After I test it out and verify that I can tolerate it and the smaller battery, then I might do some experimenting with the xt926 model I have and report back. Though, as anticipated as this update is, I'm sure someone will have already beat me to all the testing within a few hours from now lol

I'm on 9.30 with locked bootloader. I've tried your method but can't get pass signature verification. It just won't be installed on 9.30 firmware. There must be anything can be mess in updater script to avoid error signature.
Sent from my DROID RAZR HD using XDA Premium 4 mobile app

Hi! Can you please share "Blur_Version.9.30.1XT926.Verizon.en.US.zip" on dropbox gdocs or smth like that?

Sabissimo said:
Hi! Can you please share "Blur_Version.9.30.1XT926.Verizon.en.US.zip" on dropbox gdocs or smth like that?
Click to expand...
Click to collapse
I can't share the file, but if you look in the KitKat Tracking thread, you should find it there somewhere.
As an official soak tester, I'm not supposed to share the update. Technically, I'm not supposed to share ANY info, but I wanted to share this with other users who were having the same issue as I.
Thanks!

I do not believe the KK update for 9.30 has been shared anywhere.

No where that I can find. I've been scouring and following the forums waiting to find one myself.
sent from my ? and rooted XT1080 that thinks it's an XT1060

There you go, found it:
https://drive.google.com/file/d/0B8pGrRdP0CpyckJnd2JoQklHSjQ/
But I have another problem now: It says "Not a valid aboot" and aborts

I'm not worried about it right now, Moto Verizon just posted saying they approved the soak test and updates would be rolling out.
sent from my ? and rooted XT1080 that thinks it's an XT1060 using Tapatalk pro
---------- Post added at 03:16 PM ---------- Previous post was at 03:13 PM ----------
http://www.droid-life.com/2014/05/1...id-razr-hd-and-razr-m-on-verizon/#more-139933
sent from my ? and rooted XT1080 that thinks it's an XT1060 using Tapatalk pro

Sabissimo said:
There you go, found it:
https://drive . google.com/file/d/0B8pGrRdP0CpyckJnd2JoQklHSjQ/
But I have another problem now: It says "Not a valid aboot" and aborts
Click to expand...
Click to collapse
did your phone actually ota to 9.30 or did you use a sbf/utility and flashed it to 9.30?
the problem some people are having is, they flashed to 9.30 but the correct version they should be on is 9.18 and this post http://www.droidrzr.com/index.php/topic/44920-xt926-update-1824610-update/?p=431391 explains why thats a problem.

Sabissimo said:
There you go, found it:
https://drive.google.com/file/d/0B8pGrRdP0CpyckJnd2JoQklHSjQ/
But I have another problem now: It says "Not a valid aboot" and aborts
Click to expand...
Click to collapse
I got it! I used this link 'below' to finally get it to update while using this thread for advice. Thank so much!
http://sbf.droid-developers.org/phone.php?device=5
Now to try saferoot...???

For all my 9.30.1 people, I love you guys too.http://pan.baidu.com/s/1eQimdea
Enjoy that official KK ota for 9.30.1 over that slow ass chinese server and stop trying to get the 9.18.94 to work.

bweN diorD said:
did your phone actually ota to 9.30 or did you use a sbf/utility and flashed it to 9.30?
the problem some people are having is, they flashed to 9.30 but the correct version they should be on is 9.18 and this post http://www.droidrzr.com/index.php/topic/44920-xt926-update-1824610-update/?p=431391 explains why thats a problem.
Click to expand...
Click to collapse
I flashed to 9.30. When I received the OTA from the soak push, I saved the OTA off to the side and didn't apply it immediately. Then, when I attempted to apply it (after using House of Moto to fastboot it back to 9.30 stock), it rebooted after it started applying and then went back to the recovery screen, but at that point, they had changed how you get into it. It's now volume-up + power, not volume-down + volume-up.
In any case, that second step needs to happen where you go back and re-apply the OTA.
I'm thinking if I would have taken the OTA automatically right after it downloaded, it was probably automated. That, or maybe Motorola/Verizon decided to make it a game and see if people could figure it out? :silly:

Safe root for me was a no go. But kitkat is pretty nice!
Sent from my DROID RAZR HD using Tapatalk

Thanks for all the info. Got KK up and running
I used these instructions - http://forum.xda-developers.com/showpost.php?p=52602576&postcount=1
and I used this file - http://forum.xda-developers.com/showpost.php?p=52610188&postcount=11
All last night I tried using the leaked file someone put up from that "slow ass Chinese server" haha. Long story short, it didn't work at all.
This morning I tried again, and nothing. So I tried this file (the one I linked up top) and it worked like a charm. I installed it via recovery, phone rebooted, used vol up + power to get into new KK recovery, applied leaked file again, and boom I got KK.
As someone in another thread said, during the update it does say "Phase 1 possibly complete". WTF is that all about?

I've flashed my Razr Maxx HD to Kitkat using that slow Chinese server. I'm so happy it runs much smoother than JB. Everything seems fast and smooth. The new aosp lockscreen is much better than blur lockscreen. The aosp messaging is also nice. I can live without root for a while coz I already have a Photon Q modding to max. The only thing I dislike is the stock launcher which is not transparent anymore. So,I replace it with Nova Launcher Prime. It looks better now. Btw,I'm using GSM network and I notice signal is better than previous JB.

huatz84 said:
I've flashed my Razr Maxx HD to Kitkat using that slow Chinese server. I'm so happy it runs much smoother than JB. Everything seems fast and smooth. The new aosp lockscreen is much better than blur lockscreen. The aosp messaging is also nice. I can live without root for a while coz I already have a Photon Q modding to max. The only thing I dislike is the stock launcher which is not transparent anymore. So,I replace it with Nova Launcher Prime. It looks better now. Btw,I'm using GSM network and I notice signal is better than previous JB.
Click to expand...
Click to collapse
Glad it's all working for you now. It definitely performs better than JB ever did.