Database Info

[Share][8-Sep-2011] Almost all fix for CM7 and MIUI, include some optimization v2

Just share all these with anyone.
All fix included:
New added in v2:
1. A more native fix to USB connection ( moto portal&tool is available now )
2. add imoseyon tweak script
3. improve GPS(add UK/brazil/CH+HK+TW/USA services info)
4. some adjustment on auto brightness
5. fix losing (gapps) icon issue (area related issue, redirect google services in hosts)
6. enable WIFI tethering
7. try to improve battery charging(replacing charge_only_mode)
8. try to improve touch sensitivity (build.prop)
9. clean some system apps/junks ( common/necessary gapps are reserved )
10.update moto IME from GB leak
11.improve network and voice (not sure)
12.fix sensor/GPS crash in 0906 version(replace 2nd-init with RC1.5)
Download Link: http://www.mirrorcreator.com/files/VMXNTP1B/All_in_One_Fix_for_CM7_and_MIUI_v2.0.7z_links
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1.bootmenu overclock
2./data formatting and restoring issue on CWM
3.CPU governors
4.light/gravity
5.keyboard mapping (QWERTY/Z)
6.GSM fix
7.keyboard backlight
8.camera upside down
9.dual way call recording
10.soft keyboard half size
11.random SD card mounting issue in CWM
12.charger light
13.compass
14.APN fix
15.share sd card / DATA function in bootmenu
16.300mhz fix
17.stock recovery fix
18.battery jumping
and also include tweaks and optimization：
1.enhanced sms and location info(ch)
2.moto IME
3.tweaks on framework and build.prop
4.optimized auto brightness
5.power profile
6.some scripts from wajk in /system/etc/init.d
7.full Gapps
Unsolved:
1.video decoding/encoding(720p recording)
2.enable 4-lv freq setting in bootmenu( a little edit in overclock.c)
3.share SD/data/system function in bootmenu are still buggy,sometimes is ok, sometimes not.
4.Alt-lock (I thinks we can ingore this)
5.battery charging(im not sure, but someone said the full voltage in stock 2.2 can reach 4200+ and down in 3100, in CM7 it only get 4160 and down in 3300)
Please use winrar3.50+ or latest 7zip to depack it.
Download link: http://www.mirrorcreator.com/files/IYOX37NY/fix-for-CM7_0.7z_links

Amazing share man!!! Thanks a lot!!!
The link does not work for me.
[Failed to open redirect file]

sahilarora911 said:
Amazing share man!!! Thanks a lot!!!
The link does not work for me.
[Failed to open redirect file]
Click to expand...
Click to collapse
My fault. I post the wrong link. I have updated a new one. Try again.

Endless7 said:
My fault. I post the wrong link. I have updated a new one. Try again.
Click to expand...
Click to collapse
Hey Endless, can you post what is missing/still needs fix?

r2beta0 said:
Hey Endless, can you post what is missing/still needs fix?
Click to expand...
Click to collapse
1.video decoding/encoding(720p recording)
2.enable 4-lv freq setting in bootmenu( a little edit in overclock.c)
3.share SD/data/system function in bootmenu are still buggy,sometimes is ok, sometimes not.
4.Alt-lock (I thinks we can ingore this)
5.battery charging(im not sure, but someone said the full voltage in stock 2.2 can reach 4200+ and down in 3100, in CM7 it only get 4160 and down in 3300)

Ah,for 720p recording. Jorixine send me a PM with a possible method. I try,but failed. But I still want to post here.
The fix is somewhere within media_profiles.xml and build.prop
media_profiles.xml can be edited as you please, even for making the HD videos to size lesser than normal
For it to work, in the build.prop you have to change the following:
ro.media.capture.maxres=5m
ro.media.capture.fast.fps=4
ro.media.capture.slow.fps=60
ro.media.enc.hprof.vid.width=1280
ro.media.enc.hprof.vid.height=720
ro.media.capture.flash=led
ro.media.capture.useDFR=1
ro.media.capture.flashIntensity=42
ro.media.capture.torchIntensity=42
ro.media.capture.classification=classE
ro.mot.setuptype=1
ro.media.enc.aud.fileformat=3gp
ro.media.enc.aud.codec=amrnb
ro.media.enc.aud.bps=12200
ro.media.enc.aud.ch=1
ro.media.enc.aud.hz=8000
ro.media.dec.jpeg.memcap=20000000
r,o.media.dec.aud.wma.enabled=1
ro.media.dec.vid.wmv.enabled=1
He insists, recording 720p is working, the thing is that the phone reboots by itself a lot and some of those reboots are even when it never finished loading the OS, its very annoying.
Seems like the key question is to keep playing with these values. Moreover where it says ClassE, because in GB that comes as ClassH, but he changed it.
Maybe somebody with more expertise can playaround with these two files, get the correct configuration and avoid the rebooting issue.
Click to expand...
Click to collapse

Endless7 said:
Ah,for 720p recording. Jorixine send me a PM with a possible. I try,but failed. But I still want to post here.
Click to expand...
Click to collapse
I think we can make it work with the original camera application.<
Hey im the onlyone getting "unsupported compression method" on 7z¿

WeeDv2 said:
I think we can make it work with the original camera application.<
Hey im the onlyone getting "unsupported compression method" on 7z¿
Click to expand...
Click to collapse
Use winrar3.50 or latest 7zip. Because I use highest compress level.

I think I have fix the battery charging issue. Now I am on 4167 at 92%. No jumping during charing.

What about USB not working as in Stock? any update on that? i think its the MotoUSB.apk, ill try replacing it with stock USB.apk from Arg Movistar 2.2.2
(and yeah i already edited MIUI framework-res.apk)
Endless, your framework-res.apk included is the CM7 one right? cuz the one of MIUI usually is about 7 to 8 MB and your is 4/5 MB

WeeDv2 said:
What about USB not working as in Stock? any update on that? i think its the MotoUSB.apk, ill try replacing it with stock USB.apk from Arg Movistar 2.2.2
(and yeah i already edited MIUI framework-res.apk)
Endless, your framework-res.apk included is the CM7 one right? cuz the one of MIUI usually is about 7 to 8 MB and your is 4/5 MB
Click to expand...
Click to collapse
It's CM7 one.
word patch.

Very nice share Endless7 Thanks

Endless7 said:
I think I have fix the battery charging issue. Now I am on 4167 at 92%. No jumping during charing.
Click to expand...
Click to collapse
I too get to somewhere around there while charging but at 100% I get 4169mV I guess, but if I keep charging it after that it drops to 4134 mV something.
And the link is fine now, thanks!!

Endless7 said:
1.video decoding/encoding(720p recording)
2.enable 4-lv freq setting in bootmenu( a little edit in overclock.c)
3.share SD/data/system function in bootmenu are still buggy,sometimes is ok, sometimes not.
4.Alt-lock (I thinks we can ingore this)
5.battery charging(im not sure, but someone said the full voltage in stock 2.2 can reach 4200+ and down in 3100, in CM7 it only get 4160 and down in 3300)
Click to expand...
Click to collapse
So, have media playback besides mp3/mp4 been fixed?

Is this a complete CM7?
Because decompressed its only ~83 MB....

As the title says, they are fixes for applying on a defy's cm7 or miui, to make it work on milestone 2.
It's not a complete ROM.

ah ok and install logically in cwm "apply update from zip" ?

r2beta0 said:
So, have media playback besides mp3/mp4 been fixed?
Click to expand...
Click to collapse
No,this issue is described in 1th point as video decoding.And i think this also cause the 720p problem.

mj084 said:
ah ok and install logically in cwm "apply update from zip" ?
Click to expand...
Click to collapse
No,but you can overwrite cm7 package with this.

overwrite cm7 package with this....how?

[MOD] MegaBassBeats by D3HUM4NIZ3D

Today I am glad to present you the MegaBassBeats audio mod by D3HUM4NIZ3D !
INSTRUCTIONS
1. Take all necessary backups (just in case something goes wrong)
2. Download the CWM flashable zip from one of the links below
3. Flash the zip via CWM
NOTES
1. There is no proper working DSP Manager until we have CM.
2. I have tested this package under XXLQ9 firmware and have encountered no problems at all.
DOWNLOAD
RAPIDGATOR.NET
1st build : http://j.gs/1S5F - NOT WORKING
2nd build with test updater-script : http://j.gs/1S6F - REQUIRES TESTING
3rd build with the sample cwm zip : http://j.gs/1S6I - REQUIRES TESTING
HOTFILE.COM : COMING SOON

Why this will not work:
- The libs and binaries are compiled for the NEON instruction set which we don't have. (This will be a problem maybe, I'm checking it now.)
EDIT:
I didn't check the first lines of the file. Sorry for misleading. The mentioned line '/dev/block/platform/omap/omap_hsmmc.0/by-name/system' is just unnecessary but doesn't cause any problems.

Adam77Root said:
Why this will not work:
- The updater-script is not changed. You cannot simply get one from another device (look at '/dev/block/platform/omap/omap_hsmmc.0/by-name/system'). This script cannot mount or system (the above specified path does not exist on our device).
- The libs and binaries are compiled for the NEON instruction set which we don't have.
Click to expand...
Click to collapse
I will forward that to the dev. However, there has been at least 1 other user which reported it as working. In the test build, DSP was installed and working but verry buggy.

downloading buddy & let you know after the same..
---------- Post added at 09:55 PM ---------- Previous post was at 09:54 PM ----------
Adam77Root said:
Why this will not work:
- The updater-script is not changed. You cannot simply get one from another device (look at '/dev/block/platform/omap/omap_hsmmc.0/by-name/system'). This script cannot mount or system (the above specified path does not exist on our device).
- The libs and binaries are compiled for the NEON instruction set which we don't have.
Click to expand...
Click to collapse
WTF..I just downloaded this one. But thanks a million buddy. Now I will flash it after your instruction received.:victory:

Adam77Root said:
Why this will not work:
- The updater-script is not changed. You cannot simply get one from another device (look at '/dev/block/platform/omap/omap_hsmmc.0/by-name/system'). This script cannot mount or system (the above specified path does not exist on our device).
- The libs and binaries are compiled for the NEON instruction set which we don't have.
Click to expand...
Click to collapse
Forwarded. Can you suggest a proper sound test method to check if it's somehow really working or is just an impression ?

Well, the original zip gave me 'status 6' error in CWM. (because of some bad formatting ('line 1 col 56: syntax error, unexpected BAD')). If anybody of you know what is the problem pls let us know.

Adam77Root said:
Well, the original zip gave me 'status 6' error in CWM. (because of some bad formatting ('line 1 col 56: syntax error, unexpected BAD')). If anybody of you know what is the problem pls let us know.
Click to expand...
Click to collapse
May be a bad End of Line Delimiter buddy. Will download and check

This one http://j.gs/1S6F has the test build updater-script. This one is another package done with the sample cwm zip : http://j.gs/1S6I - if anyone else can confirm as working I'll add to OP. These ones should at least give no errors in CWM. I cannot do much unless the dev joins this discussion.

Here is a modified version of the zip. Flash and let me know guys. I flashed and it went thru successfully. Could not check Megabassbeats features. Feeling sleepy. If working fine, ask the OP to update the post with this zip.

selva.simple said:
Here is a modified version of the zip. Flash and let me know guys. I flashed and it went thru successfully. Could not check Megabassbeats features. Feeling sleepy. If working fine, ask the OP to update the post with this zip.
Click to expand...
Click to collapse
Thanks. I cannot test this myself as I already have the files installed. If anyone can please compare the sound output before and after flashing to find out if it's actually working.

Here im reporting to the thread
Sent from my Galaxy Nexus using xda premium

D3HuM4NiZ3D said:
Here im reporting to the thread
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
We need someone to test the package on this post http://forum.xda-developers.com/showpost.php?p=32255374&postcount=10 - if it's OK I'll push it to the OP.

And no one wants to do it?
Sent from my Galaxy Nexus using XDA Premium HD app

selva.simple said:
Here is a modified version of the zip. Flash and let me know guys. I flashed and it went thru successfully. Could not check Megabassbeats features. Feeling sleepy. If working fine, ask the OP to update the post with this zip.
Click to expand...
Click to collapse
Looks like with a permissions' fix, your package works, however I need at least 1 more person to confirm before pushing it to the OP.

I've recently returned my phone to stock nordic ics + latest ardadat kernel and cannot notice any difference in sound quality. I'm pretty sure mbb is not working on our phone.

Important. For those who are using AOSP/AICP 7.0 ROM

1.Okay so, in this thread I'm going to post a fix for the infamous mobile data bug I.e mobile data which stubbornly refuses to turn on until restart
2. Substratum weird notification toasts after installing dark themes in which the lowercase y,g,q are incompletely rendered or else, in simple terms, they look weird because the lines don't seem to fit the toast
3. Only 2g bug
3. Overheating bug and battery drain
4. People who are sceptical about doze
5. No sim detected problem
6.Video recording bug
7. And if any more bugs, please mention. The above ones are all fixable although 5th and 1st require some workaround.
Important note. : to make sure that you don't encounter any sim card problem, clean flash this ROM only if you have flashed the official ROMs
Fixes :
1. Install any cm13 nightly. Dial *#*#4636#*#* and change the network type to WCDMA(3G) Preferred (or any G according to your choice). I recommend this step as a must because it hardwires the device to use all of types of desired networks and not enforce only 2g. Also, *please note to insert the data sim in the first slot only* in order to properly use this functionality.
If you are done with the above step, congrats, 80% of the work is already done. Open root explorer and go to /system/etc/apnconfig.XML (something related to APN and I'm sure it'll be the first file). Copy the file and save it somewhere in the internal or external memory.
Now flash android 7.0 and replace the same file in /system/etc/ and set the permission to read only I.e disable every right to write that file.
(This will work in most cases. If not then its a modem issue perhaps )
Edit : I found a new fix. Change the APN name to EE
and APN to everywhere
2. Go to display, change the display size to large and text size to small.
3. Flash the latest ROM of AOSP and disable clusterplug. There's already a tutorial on it in moto x play section. Please google it also govtuner is reportedly working.
4.doze works and phone goes to deep sleep. Observed via EX kernel manager
5.flash the stock ROM properly and then reflash this. Also possibly this is due to .70 volte update. So make sure you use the .52 update before flashing this ROM
6.use google camera and set the quality to 720p
7.you mention.
I'm no developer and I love to experiment. I'll make it a point to experiment on any other bugs if present
Thank you and please post your opinions.

Update : I disabled the aggressive doze in greenify and the data seems to work with the normal apn settings 'apparently'. Although this is the case with android n only. I didn't face this whole using cm13
Also I recommend periodic clearing of partition cache

This is definitely posted in the wrong section. What about this thread implies "Original Android Development" ?
Should be in the general discussion section.

Men thks for the post but, can you xplain how can i do the cluster plug off ? can you help me please

FanDroid09 said:
This is definitely posted in the wrong section. What about this thread implies "Original Android Development" ?
Should be in the general discussion section.
Click to expand...
Click to collapse
The whole point was, the ROM was included in this section. So people will automatically see this post if they are facing any problems. Please understand the logic behind this

anderson.laverde said:
Men thks for the post but, can you xplain how can i do the cluster plug off ? can you help me please
Click to expand...
Click to collapse
http://forum.xda-developers.com/mot...r-plug-enable-disable-stock-cm-t3422345/page4

kpamkar said:
The whole point was, the ROM was included in this section. So people will automatically see this post if they are facing any problems. Please understand the logic behind this
Click to expand...
Click to collapse
Still the wrong section

Why is this needed? Most workarounds are told already. And this should be in general not development

kpamkar said:
The whole point was, the ROM was included in this section. So people will automatically see this post if they are facing any problems. Please understand the logic behind this
Click to expand...
Click to collapse
It doesn't matter what your logic is. This section is for developers that are posting their original work.
The point is to keep the forums properly organized. Not to make it as easy as possible for users who can't search a thread for solutions that have already been talked about.

kpamkar said:
1.Okay so, in this thread I'm going to post a fix for the infamous mobile data bug I.e mobile data which stubbornly refuses to turn on until restart
2. Substratum weird notification toasts after installing dark themes in which the lowercase y,g,q are incompletely rendered or else, in simple terms, they look weird because the lines don't seem to fit the toast
3. Only 2g bug
3. Overheating bug and battery drain
4. People who are sceptical about doze
5. No sim detected problem
6.Video recording bug
7. And if any more bugs, please mention. The above ones are all fixable although 5th and 1st require some workaround.
Important note. : to make sure that you don't encounter any sim card problem, clean flash this ROM only if you have flashed the official ROMs
Fixes :
1. Install any cm13 nightly. Dial *#*#4636#*#* and change the network type to WCDMA(3G) Preferred (or any G according to your choice). I recommend this step as a must because it hardwires the device to use all of types of desired networks and not enforce only 2g. Also, *please note to insert the data sim in the first slot only* in order to properly use this functionality.
If you are done with the above step, congrats, 80% of the work is already done. Open root explorer and go to /system/etc/apnconfig.XML (something related to APN and I'm sure it'll be the first file). Copy the file and save it somewhere in the internal or external memory.
Now flash android 7.0 and replace the same file in /system/etc/ and set the permission to read only I.e disable every right to write that file.
(This will work in most cases. If not then its a modem issue perhaps )
2. Go to display, change the display size to large and text size to small.
3. Flash the latest ROM of AOSP and disable clusterplug. There's already a tutorial on it in moto x play section. Please google it also govtuner is reportedly working.
4.doze works and phone goes to deep sleep. Observed via EX kernel manager
5.flash the stock ROM properly and then reflash this. Also possibly this is due to .70 volte update. So make sure you use the .52 update before flashing this ROM
6.use google camera and set the quality to 720p
7.you mention.
I'm no developer and I love to experiment. I'll make it a point to experiment on any other bugs if present
Thank you and please post your opinions.
Click to expand...
Click to collapse
Moved out of the Development sections to here....

can you give the important parameters from: /etc/apnconfig.XML
thnx

New fix is mentioned. Please check

E:Unknown Command[log]
E:Unknown Command[log]
Error when flashing any nougat rom

PSxplay said:
E:Unknown Command[log]
E:Unknown Command[log]
Error when flashing any nougat rom
Click to expand...
Click to collapse
Not an error. Happens with everyone. Don't worry

I'm trying to go with RR5.7.4 / CM13 but AOSP / AICP N7.0.0. Returning to .52, install the kernel from axxx007xxxz / only for N, full wipe, wipe data. Does not help. "Insert SIM". When flashing an error in a previous post.

Rive188 said:
I'm trying to go with RR5.7.4 / CM13 but AOSP / AICP N7.0.0. Returning to .52, install the kernel from axxx007xxxz / only for N, full wipe, wipe data. Does not help. "Insert SIM". When flashing an error in a previous post.
Click to expand...
Click to collapse
Wait. Why are you flashing a different kernel other than what was given in the rom already ? Also you need to do a full flash which includes flashing of every single file in the retasia/reteu package

I need to go back through the fastboot on the stock?

Rive188 said:
I need to go back through the fastboot on the stock?
Click to expand...
Click to collapse
I guess so. It seems you messed up with the kernel settings. And please give me the exact details of the files you flashed

kpamkar said:
I guess so. It seems you messed up with the kernel settings. And please give me the exact details of the files you flashed
Click to expand...
Click to collapse
All files are taking on XDA. Now it sets RR 5.7.4. I tried to install AICP, AOSP.

Rive188 said:
All files are taking on XDA. Now it sets RR 5.7.4. I tried to install AICP, AOSP.
Click to expand...
Click to collapse
I'm sorry I didn't get you. Can you elaborate properly?

[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!

[ROM] [UNOFFICIAL] LineageOS 13 for Life One X2-Mini [Discontinued]

LineageOS 13 for Life One X2 Mini​
This Rom was ported from the Unofficial LineageOS 13 for the Yureka Black. First I need to give credit for all the hard work the developers put into their Rom, I only modified it to work on the Blu Life One X2 Mini.
Note: Please remember I'm doing this on my own time and using my own money to cover expenses.
What Works:
(please let me know)
Camera
Fingerprint
SIM
Data
GPS
Audio
Video Playback
Sensors
Led
Not Working Yet:
(Please let me know)
FM Radio
Bluetooth
Latest Build: https://drive.google.com/open?id=0BzMHnGbQH3bheWVUNlFDNjljcEE
Builds: https://drive.google.com/drive/folders/0BzMHnGbQH3bhRXNUWi1jaGhDR3M?usp=sharing (list view recommended)
TWRP: https://drive.google.com/file/d/0BzMHnGbQH3bhTERvcGxlSkZFa2M/view?usp=sharing
Kernel:
Gapps: http://opengapps.org

Screenshots:

Changelog

Troubleshooting
Encryption Unsuccessful Screen:
Boot into TWRP and format Data (not wipe)

reserved 4

OK--it installs correctly, but after reboot it starts optimization & then screens up with encryption unsuccessful & wants to reset phone-goes to an open script to reformat/reset in TWRP--executes it & then reboots to the same again---this repeats as long as you allow it to. I tried installing twice-- the second time I wiped the phone completely---same result.

debianmain1 said:
OK--it installs correctly, but after reboot it starts optimization & then screens up with encryption unsuccessful & wants to reset phone-goes to an open script to reformat/reset in TWRP--executes it & then reboots to the same again---this repeats as long as you allow it to. I tried installing twice-- the second time I wiped the phone completely---same result.
Click to expand...
Click to collapse
Boot into TWRP and format Data (not wipe)

srgrusso said:
Boot into TWRP and format Data (not wipe)
Click to expand...
Click to collapse
Better choice , imho, would be to unpack the boot.img and change fstab to remove "forceencript"
edit:
sorry spoke too soon.
Just looked at fstab.qcom in boot.img and it is not set to "forceencrypt"

mrmazak said:
Better choice , imho, would be to unpack the boot.img and change fstab to remove "forceencript"
Click to expand...
Click to collapse
this is the current entry:
Code:
/dev/block/bootdevice/by-name/userdata /data ext4 nosuid,nodev,noatime,noauto_da_alloc wait,formattable,check,encryptable=footer;length=-16384
If I wanted to do that what would I change it too?
Thanks

OK--everything loaded & the phone booted normally. Wi-Fi is not working (deal-breaker for me--I use cellular data as little as possible--I have Wi-Fi everywhere I normally go.) Camera works-looks normal (using Google Camera)--works normally. Bluetooth is also not working.. (notice that Bluetooth Share has stopped). Screen & touch work normally. Right now I don't have cell service (that's the reason I use Wi-Fi quite a bit--all cell service is spotty where we live) & can't check cell data. If You could get the Wi-Fi to work, I could check quite a bit more......
More about the Wi-Fi: the MAC address looks like giberish---02:00:00:00:00:00

srgrusso said:
this is the current entry:
Code:
/dev/block/bootdevice/by-name/userdata /data ext4 nosuid,nodev,noatime,noauto_da_alloc wait,formattable,check,encryptable=footer;length=-16384
If I wanted to do that what would I change it too?
Thanks
Click to expand...
Click to collapse
I added an edit to my earlier post.
The way it is looks ok.
It can be encrypted, (encryptable=footer) but not being forced to be. (forceencrypt=)
The length and location of the encryption key would be important to get right, if force is used.

debianmain1 said:
OK--everything loaded & the phone booted normally. Wi-Fi is not working (deal-breaker for me--I use cellular data as little as possible--I have Wi-Fi everywhere I normally go.) Camera works-looks normal (using Google Camera)--works normally. Bluetooth is also not working.. (notice that Bluetooth Share has stopped). Screen & touch work normally. Right now I don't have cell service (that's the reason I use Wi-Fi quite a bit--all cell service is spotty where we live) & can't check cell data. If You could get the Wi-Fi to work, I could check quite a bit more......
More about the Wi-Fi: the MAC address looks like giberish---02:00:00:00:00:00
Click to expand...
Click to collapse
if your ready to do some more testing I should be able to get wifi working.

debianmain1 said:
OK--everything loaded & the phone booted normally. Wi-Fi is not working (deal-breaker for me--I use cellular data as little as possible--I have Wi-Fi everywhere I normally go.) Camera works-looks normal (using Google Camera)--works normally. Bluetooth is also not working.. (notice that Bluetooth Share has stopped). Screen & touch work normally. Right now I don't have cell service (that's the reason I use Wi-Fi quite a bit--all cell service is spotty where we live) & can't check cell data. If You could get the Wi-Fi to work, I could check quite a bit more......
More about the Wi-Fi: the MAC address looks like giberish---02:00:00:00:00:00
Click to expand...
Click to collapse
That type of address could be sign of either a corrupted NVRAM or incorrect radio firmware.
What do you have on the about screen for "baseband version"
and also on the about device/ status / IMEI information (do not list your numbers, just wheather or not they are there)

mrmazak said:
That type of address could be sign of either a corrupted NVRAM or incorrect radio firmware.
What do you have on the about screen for "baseband version"
and also on the about device/ status / IMEI information (do not list your numbers, just wheather or not they are there)
Click to expand...
Click to collapse
The rom is missing the kernel modules from the base rom. should be an easy fix. I already been through all this porting the same rom to th X2.
I might need to edit the boot image and build a script in bin to automaticly load the modules. I don't have a mini but as far as I can tell there is not much diffference from the X2.

srgrusso said:
The rom is missing the kernel modules from the base rom. should be an easy fix. I already been through all this porting the same rom to th X2.
I might need to edit the boot image and build a script in etc to automaticly load the modules. I don't have a mini but as far as I can tell there is not much diffference from the X2.
Click to expand...
Click to collapse
Sounds good---I need the phone for tomorrow, so I'm restoring it right now---will be ready to do more testing tomorrow night. As soon as I get working Wi-Fi I can get logcat up + the normal app load I use....then I could really test it---It looks real good so far.

mrmazak said:
That type of address could be sign of either a corrupted NVRAM or incorrect radio firmware.
What do you have on the about screen for "baseband version"
and also on the about device/ status / IMEI information (do not list your numbers, just wheather or not they are there)
Click to expand...
Click to collapse
This phone's kernel uses external modules, instead of built in like most kernels, odd choice by manufacture. system/lib/modules is missing, once the modules are added, and loaded wifi should work, just fine.

vampirefo said:
This phone's kernel uses external modules, instead of built in like most kernels, odd choice by manufacture. system/lib/modules is missing, once the modules are added, and loaded wifi should work, just fine.
Click to expand...
Click to collapse
So I would guess that will close the Wi-Fi & Bluetooth issues at the same time.

debianmain1 said:
Sounds good---I need the phone for tomorrow, so I'm restoring it right now---will be ready to do more testing tomorrow night. As soon as I get working Wi-Fi I can get logcat up + the normal app load I use....then I could really test it---It looks real good so far.
Click to expand...
Click to collapse
I have a new rom uploading now. It will be waiting for you when you are ready. Since you are using the stock rom could you please post the result of "lsmod" it will help me. Also after you boot the new rom could you please put the output of "dmesg" in a text file and post me a link or else just post it in pastbin. In order to get the adb shell working you'll need to change "the usb used for" from charging to file transfer.
Thanks

srgrusso said:
I have a new rom uploading now. It will be waiting for you when you are ready. Since you are using the stock rom could you please post the result of "lsmod" it will help me. Also after you boot the new rom could you please put the output of "dmesg" in a text file and post me a link or else just post it in pastbin. In order to get the adb shell working you'll need to change "the usb used for" from charging to file transfer.
Thanks
Click to expand...
Click to collapse
No problem---I also contacted the other guy that is interested in helping---should hear from him soon. Will download the new one & be ready for tomorrow.

Here is the new build. Hopefully it fixes Wifi.
https://drive.google.com/file/d/0BzMHnGbQH3bhenZNVE5MeEttVFk/view?usp=sharing