Database Info

A fix for POLA100, Haret and waiting for notbusy error

I think that this error needs no intorduction for POLA100 users who tried running latest Android kernels using Haret.
It also seems that this error is caused by the double vibration at the beginning of boot process and was solved once by paipo (see this post) by commenting out the vibration part and rebuilding. But those kernel is outdated and misses some latest features and fixes.
So I did the same as paipo but with the latest kernel from the git repository (as of 19.07.2010, revision d5d0a56fae6df779443a82e2d90b7ec8097cb332). zImage is attached to this post. I'll try to update the kernel from time to time.
Please, note that the attached kernel image is optimized for Eclair (CONFIG_ECLAIR=y in .config or System Type/Android Optimization is set to Eclair in make menuconfig).
And yes, you can do it yourself. Just follow the guide in the second post

Disabling the vibration and rebuilding the kernel yourself
So how do you do this?
First of all, follow the steps 1 to 4 of Building kernel For Vogue, Kaiser, and Polaris part from this guide to prepare your building environment.
Now you need to open the arch/arm/mach-msm/board-htcpolaris.c file in your favourite text editor.
Search for vibrate word (it was line 1019). You'll see something like this:
Code:
// vibrate
for (i=0; i<2; i++) {
while(msm_proc_comm(PCOM_VIBRA_ON,0)==-EAGAIN);
mdelay(150);
while(msm_proc_comm(PCOM_VIBRA_OFF,0)==-EAGAIN);
mdelay(75);
}
Remove this part or replace with the following:
Code:
// vibrate
// for (i=0; i<2; i++) {
// while(msm_proc_comm(PCOM_VIBRA_ON,0)==-EAGAIN);
// mdelay(150);
// while(msm_proc_comm(PCOM_VIBRA_OFF,0)==-EAGAIN);
// mdelay(75);
// }
As you can see, all lines now start with two slashes.
Now follow step 5 from the guide, mentioned above. You'll see a menu.
Go to System Type and select Android Optimization accroding to your needs. Then select Exit, than again Exit, then Yes.
Now follow step 6 from the guide. This will take some time. At the end you should see:
Code:
Kernel: arch/arm/boot/zImage is ready
Copy zImage from arch/arm/boot folder to \Storage Card\andboot folder on your device and use it

I update this option in the kernel.
Now double vibration is disable by default.

You are great !!!
leppa said:
I think that this error needs no intorduction for POLA100 users who tried running latest Android kernels using Haret.
...
Please, note that the attached kernel image is optimized for Eclair (CONFIG_ECLAIR=y in .config or System Type/Android Optimization is set to Eclair in make menuconfig).
And yes, you can do it yourself. Just follow the guide in the second post
Click to expand...
Click to collapse
YOU ARE GREAT !!!
THANKS A LOT A LOT A LOT !!!
THIS EVENING I WILL TRY SURELY !!!!!!!
Only a question: Optimized for Eclair is equal to Optimize to FROYO ?
Can I use your zImage to Froyo RLS 11 ?
Thanks in advance.
Bye

This flag now do nothing, so it's indifferent

GGGGGGGGGGGGGGRRRRRRRRRRRRRRRRRREEEEEEEEEEEEEEEEEAAAAAAAAATTTTTTT !!!!!!
I Have Just tested zImage in attached files.
Froyo seems better reactive, more smooth and rock stable.
Thanks a lot ...
When Video Playback will be solved... I will flash immediately Froyo to give a new life to my Cruise!!!
Thanks thanks thanks!

@foxct2005 : you can flash it month ago!
All these problems are only for haret!

l1q1d said:
I update this option in the kernel.
Now double vibration is disable by default.
Click to expand...
Click to collapse
This change isn't yet in the git repository, is it?
I was thinking about how to make this option available to any user without having to recompile the kernel. And came up with the idea of the new kernel parameter. So I added board-htcpolaris.no_boot_vibration parameter.
The attached kernel images work as they did before - with double vibration on boot and "waiting for notbusy" error. To disable the double vibration (and get rid of the error) add board-htcpolaris.no_boot_vibration=1 to default.txt so this line:
Code:
set cmdline "board-htcpolaris.panel_type=1 ppp.nostart=0 pm.sleep_mode=1 mddi.width=240 mddi.height=320 no_console_suspend clock-7x00.mddi=0xa51"
will look like this:
Code:
set cmdline "board-htcpolaris.panel_type=1 [COLOR="Red"]board-htcpolaris.no_boot_vibration=1[/COLOR] ppp.nostart=0 pm.sleep_mode=1 mddi.width=240 mddi.height=320 no_console_suspend clock-7x00.mddi=0xa51"
Adding this parameter is mandatory if you suffer from "waiting for notbusy" error.

big thanks for that patch!
I started a new try with android and my polaris yesterday but froyo doesn't work (with haret). Now with this patch it work and even booting and boot logo is much faster on my Pola200! Great! Thanks!

leppa said:
I was thinking about how to make this option available to any user without having to recompile the kernel. And came up with the idea of the new kernel parameter. So I added board-htcpolaris.no_boot_vibration parameter.
Click to expand...
Click to collapse
Good idea!
I have long think why developers not added it to the cmdline.

Thank you, thank you, thank you..
I almost sold my Polaris in despair that this problem will never get fixed..

DmK75 said:
Good idea!
I have long think why developers not added it to the cmdline.
Click to expand...
Click to collapse
I think, they have much more other, more serious, things to do
michasch said:
big thanks for that patch!
I started a new try with android and my polaris yesterday but froyo doesn't work (with haret). Now with this patch it work and even booting and boot logo is much faster on my Pola200! Great! Thanks!
Click to expand...
Click to collapse
nikiiv said:
Thank you, thank you, thank you..
I almost sold my Polaris in despair that this problem will never get fixed..
Click to expand...
Click to collapse
You're welcome
If this patch gets upstream, we will not need to rebuild the kernel every time a new build comes out. I already posted it in the Polaris Android Linux Kernel Development Project thread.

thanks leppa,
i tried the froyo one, but for me doesn't work. last days i used the last dzo one, it worked for 2 or 3 days, and now doesn't work again. the only zimage that works is the 29-04 one, but my battery doesn't like it so much

loscassapalle said:
thanks leppa,
i tried the froyo one, but for me doesn't work.
Click to expand...
Click to collapse
What do you mean by that? Do you still get "waiting for notbusy" error?
If yes, did you add the kernel parameter board-htcpolaris.no_boot_vibration=1?
If no, than I can't help, cause this is the only thing I changed in the kernel.

leppa said:
What do you mean by that? Do you still get "waiting for notbusy" error?
If yes, did you add the kernel parameter board-htcpolaris.no_boot_vibration=1?
If no, than I can't help, cause this is the only thing I changed in the kernel.
Click to expand...
Click to collapse
maybe is not my problem...i can't see an error string, the problem is the animation at the start that never end.

loscassapalle said:
maybe is not my problem...i can't see an error string, the problem is the animation at the start that never end.
Click to expand...
Click to collapse
Then this is some other problem. Cause "waiting for notbusy" error occurs almost at the very beginning of the boot process (while text is running, before even "Hold down Volume Up or DPad..." message).
How long do you wait? At first boot the animation may run for five and even more minutes. Try reinstalling from scratch (i.e., wiping system and data partitions).

leppa said:
Then this is some other problem. Cause "waiting for notbusy" error occurs almost at the very beginning of the boot process (while text is running, before even "Hold down Volume Up or DPad..." message).
How long do you wait? At first boot the animation may run for five and even more minutes. Try reinstalling from scratch (i.e., wiping system and data partitions).
Click to expand...
Click to collapse
i checked now, i also have this string that you said (now i'm using the froyo image you uploaded in 8# post).
the animation problem is strange. the zimage of 29-4 works, the animation ends in a few seconds, but the battery life is very short. the last dzo zimage worked for a couple of days, then i had the same problem after a softreset...and this one is the same...
EDIT: now it works... lol

loscassapalle said:
i checked now, i also have this string that you said (now i'm using the froyo image you uploaded in 8# post).
Click to expand...
Click to collapse
I didn't test the Froyo image, cause I'm playing with Eclair. Does it vibrate on start? It shouldn't or you forgot to put the kernel parameter.
loscassapalle said:
EDIT: now it works... lol
Click to expand...
Click to collapse
So, it started working?

leppa said:
I didn't test the Froyo image, cause I'm playing with Eclair. Does it vibrate on start? It shouldn't or you forgot to put the kernel parameter.
So, it started working?
Click to expand...
Click to collapse
i don't know how to edit the zimage...but now it works...i didn't change anything...

loscassapalle said:
i don't know how to edit the zimage...
Click to expand...
Click to collapse
You don't need to. I was talking about editing default.txt as I described in post 8.

Thumb Keyboard force closes

Hey all.
Had this issue for a while now and I have no idea what's causing this problem. It started a week or 2 after updating to the Modaco beta rom from v3 to v4. I assumed it was because I hadn't wiped but I tried a full wipe and tried Overcome but I have the same issue. It worked fine on the first boot, but after rebooting it kept force closing again
Anyone else having issues with it?
Sent from zombie infested Gingerbread.

GANJDROID said:
Hey all.
Had this issue for a while now and I have no idea what's causing this problem. It started a week or 2 after updating to the Modaco beta rom from v3 to v4. I assumed it was because I hadn't wiped but I tried a full wipe and tried Overcome but I have the same issue. It worked fine on the first boot, but after rebooting it kept force closing again
Anyone else having issues with it?
Sent from zombie infested Gingerbread.
Click to expand...
Click to collapse
You can trace the cause by inspecting the android log file. You can view the log file with adb or (more convenient) on the Tab itself with one of the log viewers on the market. I myself use catlog.
If you post the log, I can see what is going on, and if necessary update the keyboard.

No issues here, and I just updated to JMIv2 this past weekend.

Realised my mistakes. I think its because I changed the build.prop sdk number to 9 to fit in with my Gingerbread theme, but after a fresh wipe and not changing orbits fine. Strange thing is, it still force closed after I changed it back to 8.
Sent from my GT-P1000

GANJDROID said:
Realised my mistakes. I think its because I changed the build.prop sdk number to 9 to fit in with my Gingerbread theme, but after a fresh wipe and not changing orbits fine. Strange thing is, it still force closed after I changed it back to 8.
Sent from my GT-P1000
Click to expand...
Click to collapse
Which version do you have? Later versions are compatible with all current SDKs (also sdk 10: honeycomb)

appelflap said:
Which version do you have? Later versions are compatible with all current SDKs (also sdk 10: honeycomb)
Click to expand...
Click to collapse
2.9.2b?
The latest one Probably fc because I'm tricking it into thinking its 2.3?
Sent from my GT-P1000

GANJDROID said:
2.9.2b?
The latest one Probably fc because I'm tricking it into thinking its 2.3?
Sent from my GT-P1000
Click to expand...
Click to collapse
Yes! that certainly could be the case. It uses specific native libraries that differ across some android versions. If you tell it that it's running on sdk 9 it tries to load a native lib that is build for sdk 9. But weird that you still got an error on sdk 8.

appelflap said:
Yes! that certainly could be the case. It uses specific native libraries that differ across some android versions. If you tell it that it's running on sdk 9 it tries to load a native lib that is build for sdk 9. But weird that you still got an error on sdk 8.
Click to expand...
Click to collapse
Aha, my mistake
It is strange. I thought after a few reboots, uninstalling and reinstalling it'd have been fine, but it just wasn't working after that. All fine since I haven't changed the SDK number though
Sent from my GT-P1000

[GUIDE/DEV] Building AOSP 4.2 for the skyrocket

Im in the process of compiling android 4.2 for the skyrocket right now. i wanted to share the changes i needed to make to get it to keep compiling. i am not currently done with the compiling process right now but i have made a few changes that others can use to get them along the way as well. if you have any other changes i have not listed here PLEASE LET ME KNOW so i can add them to this google drive doc and always have it up to date. if there also is something you think should be in there PLEASE LET ME KNOW! i would like to collaborate with some people to get this built quick. we did an awesome job with jellybean and i have hope we can get this going quick.
Here is the google drive doc i have with the changes needed to get this compiling.
Google Drive Doc to build Android AOSP 4.2
if i come across any issues that i cannot solve i will be asking on this thread so please be checking back every once in a while if you are an experienced dev.

i have already made a few changes to the doc. im trying to make this as easy as possible to build.

i got it to completely build without any errors. http://d-h.st/Dvo
it does not boot though. and i dont know why. im going to need some help on this one.
im guessing maybe it has something to do with the ramdisk

sk8erwitskil said:
i got it to completely build without any errors. http://d-h.st/Dvo
it does not boot though. and i dont know why. im going to need some help on this one.
im guessing maybe it has something to do with the ramdisk
Click to expand...
Click to collapse
so i diff'd the init.rc of the skyrocket cm10 and the init.rc and of the stock nexus4 system image from the android website and theyre exactly the same. so im guessing its not the init.rc. i tried copying over adbd and init from the n4 ramdisk but it gets stuck at the samsung logo.
edit: ignore that. i was looking at the same file. lol. this is what comes from no sleep

sk8erwitskil said:
i got it to completely build without any errors. http://d-h.st/Dvo
it does not boot though. and i dont know why. im going to need some help on this one.
im guessing maybe it has something to do with the ramdisk
Click to expand...
Click to collapse
thanks for sharing your efforts, ill be downloading the source over night and tackling this in the morning, with this ill have a head start on it, appreciate sharing your work.

sk8erwitskil said:
so i diff'd the init.rc of the skyrocket cm10 and the init.rc and of the stock nexus4 system image from the android website and theyre exactly the same. so im guessing its not the init.rc. i tried copying over adbd and init from the n4 ramdisk but it gets stuck at the samsung logo.
edit: ignore that. i was looking at the same file. lol. this is what comes from no sleep
Click to expand...
Click to collapse
the issue is most definitely in the ramdisk. im 99% sure. so if anyone with ramdisk knowledge wants to help it would be very appreciated. i only know a little bit about what it should look like. the BOOTCLASSPATH needs to be changed and some permissions have been changed in 4.2 but besides that im lost. the init.rc that it builds is completely wrong. i think we would be best off taking the cm10 one and editing it.

sk8erwitskil said:
the issue is most definitely in the ramdisk. im 99% sure. so if anyone with ramdisk knowledge wants to help it would be very appreciated. i only know a little bit about what it should look like. the BOOTCLASSPATH needs to be changed and some permissions have been changed in 4.2 but besides that im lost. the init.rc that it builds is completely wrong. i think we would be best off taking the cm10 one and editing it.
Click to expand...
Click to collapse
which kernel modules did you use? since you added the kernel during the build?

gs2usr said:
which kernel modules did you use? since you added the kernel during the build?
Click to expand...
Click to collapse
i didnt manually add any modules. i thought those get added from the vendor/samsung/skyrocket folder.

sk8erwitskil said:
i didnt manually add any modules. i thought those get added from the vendor/samsung/skyrocket folder.
Click to expand...
Click to collapse
if the make file was not building you a kernel, then it shouldnt make you any modules, could you check if you have anything on dir system/lib/modules

gs2usr said:
if the make file was not building you a kernel, then it shouldnt make you any modules, could you check if you have anything on dir system/lib/modules
Click to expand...
Click to collapse
haha wow i totally missed that. it didnt add any modules. imma add the ones from cm10 to the zip and re-install and see if it works.

sk8erwitskil said:
haha wow i totally missed that. it didnt add any modules. imma add the ones from cm10 to the zip and re-install and see if it works.
Click to expand...
Click to collapse
added the modules and it still gets stuck in a boot loop

sk8erwitskil said:
haha wow i totally missed that. it didnt add any modules. imma add the ones from cm10 to the zip and re-install and see if it works.
Click to expand...
Click to collapse
Sounds good, keep us informed
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

just going through the overlays you removed. In the msm8660 overlays, you could keep
Code:
<string name="config_datause_iface">rmnet_sdio0</string>
as that is in the config.xml in AOSP, but is set to rmnet0 by default.
Also for the location provider, in AOSP, the default is:
Code:
[COLOR="RoyalBlue"]<!-- Package name(s) containing location provider support.
These packages can contain services implementing location providers,
such as the Geocode Provider, Network Location Provider, and
Fused Location Provider. They will each be searched for
service components implementing these providers.
It is strongly recommended that the packages explicitly named
below are on the system image, so that they will not map to
a 3rd party application.
The location framework also has support for installation
of new location providers at run-time. The new package does not
have to be explicitly listed here, however it must have a signature
that matches the signature of at least one package on this list.
-->[/COLOR]
<string-array name="config_locationProviderPackageNames" translatable="false">
[COLOR="RoyalBlue"]<!-- The standard AOSP fused location provider -->[/COLOR]
<item>com.android.location.fused</item>
but in CM10, it's this:
Code:
[COLOR="RoyalBlue"] <!-- Component name of the service providing network location support. -->[/COLOR]
<string name="config_networkLocationProvider">com.google.android.location.NetworkLocationProvider</string>
[COLOR="RoyalBlue"] <!-- Component name of the service providing geocoder API support. -->[/COLOR]
<string name="config_geocodeProvider">com.google.android.location.GeocodeProvider</string>
Also, in the celox-common overlays for Phone, all of those configs are in AOSP, so I'm not sure why they would need to be removed.
Doubt that any of this matters in terms of you not being able to boot, but I just thought I would make a note.

the fix for the kernel being added is here:
ifeq ($(TARGET_PREBUILT_KERNEL),)
LOCAL_KERNEL := device/samsung/skyrocket/kernel
else
LOCAL_KERNEL := $(TARGET_PREBUILT_KERNEL)
endif
PRODUCT_COPY_FILES += \
$(LOCAL_KERNEL):kernel
add to device.mk

sk8erwitskil said:
added the modules and it still gets stuck in a boot loop
Click to expand...
Click to collapse
Oh well, was worth a shot. Anyways should be added to the list, I probably wont be of much help until I have the source downloaded, but keep up the good work
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

gs2usr said:
Oh well, was worth a shot. Anyways should be added to the list, I probably wont be of much help until I have the source downloaded, but keep up the good work
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
i made some changes to device.mk to add the kernel to the out directory. hopefully it adds the modules as well. ill see once its done compiling again.

m4570d0n said:
just going through the overlays you removed. In the msm8660 overlays, you could keep
Code:
<string name="config_datause_iface">rmnet_sdio0</string>
as that is in the config.xml in AOSP, but is set to rmnet0 by default.
Also for the location provider, in AOSP, the default is:
Code:
[COLOR="RoyalBlue"]<!-- Package name(s) containing location provider support.
These packages can contain services implementing location providers,
such as the Geocode Provider, Network Location Provider, and
Fused Location Provider. They will each be searched for
service components implementing these providers.
It is strongly recommended that the packages explicitly named
below are on the system image, so that they will not map to
a 3rd party application.
The location framework also has support for installation
of new location providers at run-time. The new package does not
have to be explicitly listed here, however it must have a signature
that matches the signature of at least one package on this list.
-->[/COLOR]
<string-array name="config_locationProviderPackageNames" translatable="false">
[COLOR="RoyalBlue"]<!-- The standard AOSP fused location provider -->[/COLOR]
<item>com.android.location.fused</item>
but in CM10, it's this:
Code:
[COLOR="RoyalBlue"] <!-- Component name of the service providing network location support. -->[/COLOR]
<string name="config_networkLocationProvider">com.google.android.location.NetworkLocationProvider</string>
[COLOR="RoyalBlue"] <!-- Component name of the service providing geocoder API support. -->[/COLOR]
<string name="config_geocodeProvider">com.google.android.location.GeocodeProvider</string>
Also, in the celox-common overlays for Phone, all of those configs are in AOSP, so I'm not sure why they would need to be removed.
Doubt that any of this matters in terms of you not being able to boot, but I just thought I would make a note.
Click to expand...
Click to collapse
Thanks I'll add that to the doc tomorrow
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Hopefully you get this up &running. But you should soon, having Gs2 helping you out. Can't wait till this is complete so I can check it out. :good:

im trying to get aosp to compile the kernel like cm does. i added build/core/tasks/kernel.mk but it gets stuck on
Code:
out/target/product/skyrocket/obj/KERNEL_OBJ does not exist
when i check that folder does exist. for some reason its not recognizing it.

sk8erwitskil said:
im trying to get aosp to compile the kernel like cm does. i added build/core/tasks/kernel.mk but it gets stuck on
Code:
out/target/product/skyrocket/obj/KERNEL_OBJ does not exist
when i check that folder does exist. for some reason its not recognizing it.
Click to expand...
Click to collapse
if i just do that prebuilt kernel option then it doesnt add any modules. not sure how to fix that.

[Q] AOSP Building and Binaries

Hi All,
Ive been trying to building AOSP myself and every time i boot it has no gsm. (phone is reporting IMEI as Unknown). I must be missing a step but I cant work out what.
My N5 is currently running the latest developer release of Lollipop including bootloader and radio.
Heres what I did:
1. Repo init with no branch set (master branch)
2. repo sync
3. extracted the binaries from my N5 using a modified 'generate_packages' (essentially it adb pull's the files from the connected N5)
4. setup build environment
5. lunch with aosp_hammerhead
6. make
I'm confident that i've done everything (looking at guides) but it still has no radio

eskemo said:
Hi All,
Ive been trying to building AOSP myself and every time i boot it has no gsm. (phone is reporting IMEI as Unknown). I must be missing a step but I cant work out what.
My N5 is currently running the latest developer release of Lollipop including bootloader and radio.
Heres what I did:
1. Repo init with no branch set (master branch)
2. repo sync
3. extracted the binaries from my N5 using a modified 'generate_packages' (essentially it adb pull's the files from the connected N5)
4. setup build environment
5. lunch with aosp_hammerhead
6. make
I'm confident that i've done everything (looking at guides) but it still has no radio
Click to expand...
Click to collapse
I'm just trying to figure out what Binaries I need for L too. I used the CM extract-files.sh which is very similar to what I imagine you've used, but it will only create /vendor/lge. I'm trying to work out what I need for /vendor/qcom anf /vendor/broadcom as they're missing. They could affect Radio if you haven't got them too...

I just used:
[aosp_folder]/device/lge/hammerhead/self-extractors/generate-packages.sh
But changed line 247 to:
adb pull $FILEDIR/$ONE_FILE
Obviously I had my N5 ruining the latest Dev preview attached
Sent from my Nexus 5 using XDA Free mobile app

eskemo said:
I just used:
[aosp_folder]/device/lge/hammerhead/self-extractors/generate-packages.sh
But changed line 247 to:
adb pull $FILEDIR/$ONE_FILE
Obviously I had my N5 ruining the latest Dev preview attached
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Hmm didn't know that was there... Looks like it creates broadcom and qcom already
Edit, well that generate creates the same 3 shell scripts as I downlaoded here:
http://nosemaj.org/howto-build-android-kitkat-nexus-5
Do we know that qcom and broadcom are not version / branch specific? When I run the script, it creates KOT49H from source. What is that line 247 amendment actually doing?

The modification pulls the files from a connected device via and. So in my case it would pull the binaries for the developer preview and thus lollipop compatible drivers
Sent from my Nexus 5 using XDA Free mobile app

Search google "nexus binaries preview", try that
Sent from my Nexus 5 using Tapatalk

I tried those that's why I decided to extract from a device running the preview instead. Also I've read that the Google hosted binaries don't have all the files which is why extracting seems better.
Sent from my Nexus 5 using XDA Free mobile app

I used to use these for SlimRoms KK
<manifest>
<project name="TheLoonyBin/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="kk4.4" />
<project name="TheLoonyBin/proprietary_vendor_qcom" path="vendor/qcom" remote="github" revision="kk4.4" />
<project name="TheLoonyBin/proprietary_vendor_broadcom" path="vendor/broadcom" remote="github" revision="kk4.4" />
</manifest>
Apparently they have been updated to LP now, with the preview stuff, so if you pull from the correct branch, it should work. I'm going to try it.

I'll give it a go too. I may flash stock 4.4 first then my build. Maybe it's related to the radio version or bootloader
Sent from my Nexus 5 using XDA Free mobile app

eskemo said:
I'll give it a go too. I may flash stock 4.4 first then my build. Maybe it's related to the radio version or bootloader
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Shouldn't be if you flashed the preview.
I've still got my October 2013 Bootloader.... I flashed Preview via a zip with the radio. I guess as long as you have the latest radio, it cant be that...I've flashed AOSP builds (not by me) and they worked. Not sure where those guys are getting their binaries
Your build doesn't flash Cache does it?
Yeah on the loonybin just update the revision. Im at work now so probably wont get to do a good test until.. well weekend actually... I dont even know that my build env will work properly as I havent fully tested it since rebuild to Mint.

beekay201 said:
Search google "nexus binaries preview", try that
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks! Found this link:
https://developers.google.com/android/nexus/blobs-preview

I've been doing a flashall so it does flash boot, cache, user data, and system. Does that make a difference?
Sent from my Nexus 5 using XDA Free mobile app

eskemo said:
I've been doing a flashall so it does flash boot, cache, user data, and system. Does that make a difference?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
With your build?
Not in itself, however the IMEI etc symptoms you report in your OP have been seen regularly with a "bad" cache flash, so I suppose first thing to test is to take it back to a fully working state and flash just system and boot. If for no reason other than eliminating it as the cause.

I'll give that a go then. It seems quite likely by the sounds of things.
Sent from my Nexus 5 using XDA Free mobile app

[CM-AOSP]-KK Culcalkin Kernel-R1

The purpose of this kernel is to provide the new features of the community to an older version of android.
To see this old version of android in its maximum splendor, trust on me, its better use kk on your smartphone than another version of android
FEATURES
for now (i am working on add some features but something gone wrong, and i think re-made everything, so keep calm)
-Fix wifi issue on dual sim version thanks to @kaminari
-Reclaim ram from loggers
-Fixed some memory leaks
-Xperience Governor WIP
-OC/UC Bus
-OC/UC GPU 600 mhz-100mhz
-OC/UC/UV CPU up to 1.6ghz-96mhz
-Compiled With Sabermod 4.7
-Fix Screen Flickering and added ULPS
Click to expand...
Click to collapse
INSTALLATION
-Install a CM-AOSP KK rom (no works on GPE and Stock)
-Flash via TWRP or CWM.
-Enjoy
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------------------
| If something gone wrong.... you can follow a video tutorial from How-To Basic in YT to fix your device |
| Nah just a joke, give me a logs to see what can i do for you |
--------------------------------------------------------------------------------------------------------------------------------
DOWNLOADS
-----LINK----
FOLDER ON DRIVE
https://drive.google.com/folderview?id=0Bzhj4Q-XtM6RMkJjM19uT3hvQmc
Click to expand...
Click to collapse
BUGS
None for now
Click to expand...
Click to collapse
SOURCES
https://github.com/STR4NG3R/android_kernel_motorola_msm8226-1
Click to expand...
Click to collapse
Thanks to...
@hurtsky @BryanByteZ @TeamMex @h2o64 @kaminari @Slate21&MOTOG
-And all the real developers in this community.

Recomendations for best perfomance:
ROMS:
https://forum.xda-developers.com/moto-g/development/rom-cyanogenmod-11-4-4-kernel-fixed-t3431146
https://forum.xda-developers.com/moto-g/development/rom-speedmod-slimkat-based-lollipop-t3430480
TIPS:
Since the moto g have a partition thats isnt used for nothing(/cache partittion 600mb), , you can made a swapp file into it (with the apps ram expander from google play).
Click to expand...
Click to collapse

Wifi issue
Very nice Kernel. Better than others in all respect but one. Wifi cannot be turned on. I tried wiping cache, copying CM11 wifi module, persistence, etc... None worked. Any idea?
XT1033 dual sim here. Your kernel did fix the flickering issue and stopped random rebooting. But I am reluctant to use it due to the lack of wifi.

stonelight said:
Very nice Kernel. Better than others in all respect but one. Wifi cannot be turned on. I tried wiping cache, copying CM11 wifi module, persistence, etc... None worked. Any idea?
XT1033 dual sim here. Your kernel did fix the flickering issue and stopped random rebooting. But I am reluctant to use it due to the lack of wifi.
Click to expand...
Click to collapse
So weird ://// i dont know why

Is this rom based on Render? I checked the Render kernel website http://forum.xda-developers.com/showthread.php?t=2724016 and people were complaining about wifi not enabled on KK 4.4.4 and XT1033, which is exactly my phone. Unforetunately Render stopped developping in 2014.
Now I have an ugly workaround. Two kernels work to some extent:
Render or Culcalkin: I flash boot with pre_render_boot.img, all good except wifi.
Pink: I flash recovery with pre_pink_boot.img, has wifi, but suffers from random reboot, not able to wake up sometimes, and flickering screen at boot up.
So most of time I use boot image into Culcalkin. When I really need wifi, I reboot into recovery which is indeed pink kernel.
STR4NG3R-GUY said:
So weird ://// i dont know why
Click to expand...
Click to collapse

Does it work on gpe 5.1 bootloader?

stonelight said:
Is this rom based on Render? I checked the Render kernel website http://forum.xda-developers.com/showthread.php?t=2724016 and people were complaining about wifi not enabled on KK 4.4.4 and XT1033, which is exactly my phone. Unforetunately Render stopped developping in 2014.
Now I have an ugly workaround. Two kernels work to some extent:
Render or Culcalkin: I flash boot with pre_render_boot.img, all good except wifi.
Pink: I flash recovery with pre_pink_boot.img, has wifi, but suffers from random reboot, not able to wake up sometimes, and flickering screen at boot up.
So most of time I use boot image into Culcalkin. When I really need wifi, I reboot into recovery which is indeed pink kernel.
Click to expand...
Click to collapse
maybe are based in the same sources, tell me with which kernel's you dont have thats issues to make a EXP build for you
XMoDuLeSx said:
Does it work on gpe 5.1 bootloader?
Click to expand...
Click to collapse
yes it does.
im dead right now, never drink a lot X_X

I tried too many kernels and forgot where I got that boot image . The ROM that I used is http://forum.xda-developers.com/moto-g/development/4-4-4-rom-t2826944 and its buildin kernel works with wifi (but with the flickering issue etc.). And somehow I have a boot image called pre_pink_boot.img which also works with wifi.
Your kernel is the only CM11 kernel that does not have the flickering issue on my phone. All others suffer from a moving flickering line at bootup, until I turn off screen and turn it back on again.
I heard that CM12 and above does not have those issues but I like the compactness of CM11. And Xposed is much easier on CM11.
STR4NG3R-GUY said:
maybe are based in the same sources, tell me with which kernel's you dont have thats issues to make a EXP build for you
yes it does.
im dead right now, never drink a lot X_X
Click to expand...
Click to collapse

Next update will be in december i need to dedicate all my time to my college, i learn how to add a lot of features so its a promise... Next version version will be really featured

STR4NG3R-GUY said:
So weird ://// i dont know why
Click to expand...
Click to collapse
You need to put this in your Makefile:
Code:
LDFLAGS_MODULE = --strip-debug
Otherwise the wi-fi module will be over 30 MiB in size and it'll definitely not load (the proper size for the module is no more than 4 MiB). Both your defconfig and updater-script are fine, no need to change anything inside them.
*MiB: mebibyte or binary megabyte (1024² bytes).
Edit: This line is already present in the Makefile, but it's empty.
Code:
LDFLAGS_MODULE =
You need only replace this line with mine.

wifi issue
Kamin4ri, thanks. do you have a compiled working CM11 kernel that is stable and with WIFI? Mine suffers from random reboot on XT1033.
Kamin4ri said:
You need to put this in your Makefile:
Code:
LDFLAGS_MODULE = --strip-debug
Otherwise the wi-fi module will be over 30 MiB in size and it'll definitely not load (the proper size for the module is no more than 4 MiB). Both your defconfig and updater-script are fine, no need to change anything inside them.
*MiB: mebibyte or binary megabyte (1024² bytes).
Edit: This line is already present in the Makefile, but it's empty.
Code:
LDFLAGS_MODULE =
You need only replace this line with mine.
Click to expand...
Click to collapse

Updated

what is the decryption key?

stonelight said:
what is the decryption key?
Click to expand...
Click to collapse
Moved to G-Drive

Thank you!