[Q] Official AOKP users - Nexus 4 Q&A, Help & Troubleshooting

Hello,
Tried many custom roms but usually end up coming back to the offical AOKP rom for the N4. I like the options and speed of the rom, find it very stable and use the theme engine. I haven't tried their 4.3 roms as they are all nightlies and I am always led to believe these are a bit risky for using as a daily driver. I use my phone for work and important things.
I have stayed with 4.2, but the only issue I have found is that the camera flash does not work. I have tried the latest stable 4.2 release, but then under instruction by aokp him/herself flashed the last 4.2 nightly as I was told there was a camera fix for that release. This was a clean install, I wiped and flashed.
Unfortunately I still cannot get the camera flash to work. I know my phone is not faulty as the flash works fine in Beanstalk, CM and other roms.
Anyone else experienced this?

The nightly releases for AOKP 4.3.1 are stable. Just make s nandroid backup and install them.
sent via tapatalk

ThemeManager crash with Franco/Hells kernel
Hi,
Did anyone had issue with ThemeManager. It's crashing always while restarting phone. I tried Franco/Hells kernel and it happens on both. It's working correctly on standard kernel. I tried to set up stock theme/clean data in application. Nothing helps.

Related

HDCR Kernal forces Bluetooth Carkit reboot

Details :
Nokia CK-15w Bluetooth Car Kit
Any HDCR Kernel Based ROM
It seems that any HDCR Kernel based rom causes the Nkia car-kit to reboot when downloading contacts.
I was originally running WildPuzzleRom v8.0.11 FRF91 2.2 (kernel 2.6.32.21-g4b3e397 htc-kernal) which worked as expected and I could download the contacts to my Car-Kit.
I them swapped to CM7 RC1 (great work by the way) and contact download starts, but then causes the carkit to reboot. I tried the nightlies for a while but same issue and then tried RC2 but same issue.
I have tried different versions of the Kernel 4, 4.1 and 4.2 but that all cause the car kit to reboot when downloading contacts. I have tried a second Nokia CK-15w Car Kit and the same problem occurs.
I put CM6 on the phone, but same problem and have since tried a few HDCR kernel based roms but they all have the same problem. So I can only think something in the kernel is causing the issue.
Bluetooth connectivity works well, but contact download is the issue.
I quite like CM7 and would be very happy if I could resolve this issue, but so far I have been unable to. I also posted on the CM forum but have had no response.
So thought (i am new to this) I would ask here if anyone has any ideas? or if there is a Stock (non hdcr) rom i could use with either cm6 or cm7?
There is a new kernel in the latest nightlies (nFinity tuxbox by Arco), and, you can check that out. But, remember, some people are having other issues with that, like 3G not working, call drops when screen shuts off etc. There are fixes available in the CM thread here that solves it,but you will have to hunt a bit.
Either way, a Nandroid backup before trying it is essential.
3xeno said:
There is a new kernel in the latest nightlies (nFinity tuxbox by Arco), and, you can check that out. But, remember, some people are having other issues with that, like 3G not working, call drops when screen shuts off etc. There are fixes available in the CM thread here that solves it,but you will have to hunt a bit.
Either way, a Nandroid backup before trying it is essential.
Click to expand...
Click to collapse
its actually just nfinity.
Tuxbox is the name of Arco's host computer
Cheers, just downloaded CM7 nightly 30 so will at least be able to check to see if the contact downloads works. If its all good then will have something to look forward to once the other issues are resolved. I always take a nandroid backup lol Better safe than sorry.

[Q] Problem with Wifi (CM7.2)

Today I installed CM7.2 following the instructions in the thread. I came from stock froyo 2.2.1 and everything worked fine but had some random reboots.
Since I have CM7.2 installed my wifi doesn't work anymore. If I turn it 'on', it doesn't search for available networks. It disables itself after +-30sec. I also noticed I don't have a Mac-adress anymore.
Is it possible that the problem is caused by doing no 'remove caches'. It wasn't in the instructions so I didn't do it. Should doing that fix the problem?
reflashing always works hehe
Tried it and it worked.
Sorry for the useless thread...
I am having this same problem with the newest Aurora ICS, but reflashing didn't fix it.
If you want a stable GB rom forget about the official roms and use any custom GB with .32 kernel. These are the most stable ones. I use ezet's.

[Q] Major input lag on CM102 and newer

Hi everyone,
I've had my RAZR M for just over a year now and I've had several different custom ROMs on it. Several months ago I updated to a newer CM 10.1 nightly and noticed horrible input lag. Scrolling in menus was extremely slow and apps took way longer than usual to open. I tried several different ways of wiping, flashing and installing the ROM but failed to solve the problem. I also tried all kinds of options in the developer menu and the performance settings. No dice.
I fell back to a stable 10.1 ROM until a few days ago when I decided to try the same thing with CM 11. The CM 11 ROM suffers from the same horrible input lag as the older CM 10.1 nightlies. All ROMs after a certain point have the same behavior (I don't know the nightly it started on sadly). I'd really like to use a newer ROM but the ROM is unusable with the input lag.
Has anyone had similar problems? Thanks for any input. I'll provide any additional info that helps.
Additional info:
Using TWRP 2.6.3 from here here
Getting my ROMs from the official cyanogenmod release.
I've tried many combinations of wiping everything but external SD while installing. Recently tried mounting /system while wiping but that didn't help either.
I've tried googling the problem and I've found some similar problems but no one seems to have found a solution.
http://www.droidrzr.com/index.php/topic/30889-43-custom-roms-lag/
http://forum.cyanogenmod.com/topic/79209-major-lag-on-nightlies/
The lag also happens on Carbon ROM when I tried it a few months ago.
Stock is better. We will have to wait for official 4.4 for a fix.
Some say my version of pure perfomance helps, I have not tried the cm ver much. Go dev section. Jeeko is back & said he would make a newer.

GPS issues on custom roms.

I've recently moved to a new state and have been having to use my phone's GPS several times a week.
At the time I was using one of the Cyanogenmod 11 snapshot builds(sorry, I can't remember which one ). The GPS worked flawlessly. I would always update to the next snapshot build as they came out. One our two updates later my GPS couldn't seem to get a fix on my location. I tried wiping and doing a clean install of the ROM. Still had issues.
Eventually I got fed up with cyanogenmod and wiped my phone and installed Paranoid Android 4 beta 1. Had the same problem with the GPS. I tried several of the other beta releases as they came out to see if the problem was resolved. It wasn't.
So I restored my phone to stock using the Google factory images (4.4.2). The GPS worked beautifully. So I stuck with stock for a while and did the OTA update to 4.4.3.
After a while I started to miss the features and customizations that come with custom ROMs. So I wiped and flashed Paranoid Android 4.4 RC2. The GPS still can't seem to lock. On the rare occasion that it does it can't keep up with my car, especially if I turn onto another road.
Does anyone know what's up with the GPS? Didn't seen to have this issue at all on Jelly Bean custom ROMs. Is this an issue with Kitkat custom ROMs? Possibly a hardware issue? Any help would greatly appreciated.
Current setup:
Phone: Nexus 4(16gb)
ROM: Paranoid Android 4.4 RC2
Sent from my Nexus 4 using XDA Free mobile app
There appears to be an issue with KitKat and GPS. I'm running stock 4.4.4 and I can't get a GPS lock. I've tried everything I can, including a factory reset. I don't remember having the issue with 4.4.3, but I've seen issues reported going back to 4.4.2.
I don't know about you, but a reboot usually does it for me.

MoKee OS Official 5.1.1 Nightlies

For anyone who doesn't know; MoKee Nightlies are available for Thea, if anyone wants to try. It's pretty good.
http://download.mokeedev.com/?device=thea
Their original dev (and unkwon) must create a post for more detailed information...! But thanks for the advice.
Obviously. They haven't yet! Just telling people it's there.
It's pretty good, but at the moment Bluetooth is not working, can't connect to my Android Wear, so back to CM12 but I'll keep trying =)
hugoprh said:
It's pretty good, but at the moment Bluetooth is not working, can't connect to my Android Wear, so back to CM12 but I'll keep trying =)
Click to expand...
Click to collapse
Were you using a nightly or release build? Bluetooth is working fine for me. I'm on the latest release build. Smooth and stable.
mej0248 said:
Were you using a nightly or release build? Bluetooth is working fine for me. I'm on the latest release build. Smooth and stable.
Click to expand...
Click to collapse
Yep it was nightly 2015-05-23 , later I'll try the new nightly and if that does not work, then I will try the release build. Cheers for the info =)
How good is it? Is it better than CM?
I prefer it to CM. The release builds are great. No issues for me.
I4ve been on this ROM for a day now and it works like a charm. Mokee is really great. No buigs or FC for now
EDIT : GPS works for You ? I can't get a fix.... Did a clean flash of Mokee but still no GPS Fix
EDIT #2 : OK now it works, just have o erase modemst1 and modemst2 with fastboot
Hi everyone,
I've been enjoying Mokee for a week, flashed nightlys every two days and just discovered that their OTA system just download the changes from the rom installed to the new build. I tried to DL it and flash but I've an endless bootanimation after.
Is it the same for you too? Thanks
metalmoot said:
Hi everyone,
I've been enjoying Mokee for a week, flashed nightlys every two days and just discovered that their OTA system just download the changes from the rom installed to the new build. I tried to DL it and flash but I've an endless bootanimation after.
Is it the same for you too? Thanks
Click to expand...
Click to collapse
I don't use OTA.
I heard that it broke ever, then they fixed. I'll link to him.
Try using the Release builds instead. More stable and OTAs are every week or so.
Yes but releases are odexed and xposed does not work with odexed roms
Ok, I don't ever use Xposed with custom roms. Just stock.
Caution ! The 28/06 nightly doesn't work !
I will go back to CM because the 29/06 crashes when I use a theme.
Great rom but I honestly can't see the advantage over CM. Ota would be a plus but it fails.
Back on CM with Cyandelta for incremental updates
Another update on Mokee on Thea :
- OTA works great but you must not remove /system apps and modify build.prop however the phone will bootloop.
- OTA doesn't work with Xposed as well, bootloop
- Release versions (odexed ROM) are really smooth and seem to be more battery friendly than nightly releases...
- The ROM is bugfree, I've been using Mokke for two weeks now and no reboot, no freeze, perfect experience
metalmoot said:
flashed nightlys every two days and just discovered that their OTA system just download the changes from the rom installed to the new build. I tried to DL it and flash but I've an endless bootanimation after.
Click to expand...
Click to collapse
Same here, I'm really happy with Mokee (running release version), no bugs so far and smooth performance. However I tried as you did to download incremental update through Mokee Center and automatically flash through recovery (TWRP), but got endless boot animation, had to download full ROM and flash after wiping system/data/cache/dalvik.
Does anyone know if Mokee can be upgraded simply by flashing full ROM zip without wiping system and data?
Tried again updating through Mokee Center, this time downloading full ROM. Didn't get endless bootloop, but performance was really bad, moto g suddenly rebooted 2 times, very unstable. I decided to wipe all and reflash manually through TWRP. Working fine now... it seems that auto-update are not working very well. Anyone who didn't get those problems and successfully updated through Mokee Center?
I managed to have incremental updates working on release versions. You must not touch anything in /system (you can freeze apps however)
I've been updating like that for two releases and it works
Just a quick for OTA updates on nightly builds with Xposed.
Ota works if you uninstall xposed with the uninstaller zip before flashing OTA !

Categories

Resources