CyanogenMod 10.1 UNOFFICIAL for LG Optimus L9 p769
This is unofficial build. Use at your own risk. I am not responsible for anything that may happen to your phone.
Only for P769 version of the phone. Do not attempt to flash on any other device.
The phone bootloader has to be unlocked and correct recovery installed.
Please avoid discussing general unlocking, rooting, and other unrelated to development issues in this thread.
Watch for bugs. Report with logcat and dmesg.
Features
- Mostly based on p760 device tree.
- No emulated internal storage. Single external SD card configuration. (Read note in the 2nd post)
- Apps 2 SD support
- BLN support (limited, read note the the 2nd post)
- Analog amplifier gain control with Voodoo Sound support (read note in the 2nd post)
- Microphone preamplifier gain adjustments
- Performance kernel with OC/UV
- Advanced Settings to control kernel clocks
Kernel
- Compiled with Linaro 4.7
- Extended frequency table with 200MHz, 1200MHz, 1350MHz (overclocking doesn't work on some phones)
- Slightly undervolted
- Userspace voltage control. Use SetCPU, VoltageControl, or similar. Warning: Save a recovery script with either of these programs before playing with voltages!
- GPU is extended with 384MHz, IVA with 430 MHz
- Selectable screen-off maximum frequency
- Included SmartassV2 governor, SIO scheduler.
- Few performance tweaks.
- Kernel without performance tweaks available here
Bugs
- No 1080p in camcorder
- Usual p760 CM10.1 issues, if any
Installation
- If going from non-CM10.1 ROM, backup your data and do full reset. If updating from CM10.1 it is usually not necessary.
- Copy to SD and flash with CWM.
- Flash correct version of Gapps
Download
cm-10.1-20131018-UNOFFICIAL-p769.zip (Mega)
cm-10.1-20131018-UNOFFICIAL-p769.zip (Dropbox)
Sources
Github
History
Upstream merges
10/18/2013
- Reduced call microphone volumes even more
10/07/2013
cm-10.1-20131007-UNOFFICIAL-p769.zip
- Reduced call microphone volumes
09/07/2013
cm-10.1-20130927-UNOFFICIAL-p769.zip
- CM 10.1.3
09/07/2013
cm-10.1-20130907-UNOFFICIAL-p769.zip
- CM 10.1.3 RC2
8/30/2013
cm-10.1-20130830-UNOFFICIAL-p769.zip
- CyanogenMod 10.1.3 RC1
- updated radio blobs to LG v20f
- fixed vibrator tuning in Advanced settings
- minor tweaks
8/23/2013
cm-10.1-20130823-UNOFFICIAL-p769.zip
- adjusted power profile
- reduced in-call Bluetooth microphone volume
- some upstream picks and minor tweaks
08/19/2013
cm-10.1-20130819-UNOFFICIAL-p769.zip
- added BLN settings to Parts
- added vibrator intensity to Parts
- run ADB as root by default
- few tweaks
---- project split to CM10.2 here ----
08/13/2013
cm-10.1-20130813-UNOFFICIAL-p769.zip
- kernel with BLN support
- added BLN blinking adjustments to Advanced Settings
- added microphone preamp gain control to the kernel, adjustable from Advanced Settings
- changes to some audio volumes
08/08/2013
cm-10.1-20130808-UNOFFICIAL-p769.zip
- added option to disable touch LEDs
- fixed USB mass storage
- Interactive governor updated to 3.4
08/05/2013
cm-10.1-20130805-UNOFFICIAL-p769.zip
- fixed in-call headset volume control
- reduced headset volume
- added analog amplifier gain control with Voodoo Sound support
08/01/2013
cm-10.1-20130801-UNOFFICIAL-p769.zip
- IVA (Image Video Accelerator) overclocking
- GPU underclocking
- maximum screen-off frequency
- user settings to control the clocks (Settings->Device->Advanced)
- minor improvements to overclocking
07/29/2013
cm-10.1-20130729-UNOFFICIAL-p769.zip
- switched board to p769
- increased microphone volume
- fixed bluetooth call audio
07/26/2013
cm-10.1-20130726-UNOFFICIAL-p769.zip
- kernel: fixed excessive WiFi power consumption
07/22/2013
cm-10.1-20130722-UNOFFICIAL-p769.zip
- disabled internal sdcard emulation
- kernel is back to using omap4 audio codec
07/19/2013
cm-10.1-20130719-UNOFFICIAL-p769.zip
- fixed proximity sensor
07/17/2013
- Some changes to device, including another audio fix picked from p760
- Kernel:
--- Now using twl6040 audio drivers from LG source drop
--- SIO and SmartassV2
--- Entropy tweak
--- Force volume mounts with noatime
--- Picked a merge with common android kernel, version is bumped to 3.0.31
--- Compiled with Linaro 4.7
07/12/2013
cm-10.1-20130712-UNOFFICIAL-p769.zip
- Kernel with OC/UV
- Ported commit from p760 device to fix call echo and low speaker volume
- Repo synced
07/09/2013
cm-10.1-20130709-UNOFFICIAL-p769.zip
Notes
Storage
Originally our phone has very awkward, confusing, and often misunderstood configuration for external storage. Why all these strange emulated directories with cryptic numbers? Well, the numbers are needed for multiuser environment but we don't care about it as on phones it's not enabled. It appears that there is internal /sdcard (or /storage/sdcard0 which is the same) and everybody is welcome to store data on it. Truth of the matter is - there is no dedicated internal sdcard on our phone. There in no separate microchip, no separate partition, the internal sdcard does not exist. It is emulated by FUSE inside /data partition. The original location of files is /data/media/0 and /sdcard just simulates a drive from this directory. It means that every time you save anything to /sdcard, the space will be taken away from /data. Even worse, all apps think that /sdcard is real external storage and will dump data there. Very soon you will find that you've run out of space in /data and cannot install apps anymore. This configuration would have worked fine if we had big internal MMC card but unfortunately ours is quite small. So the best practice is not to use /sdcard at all and keep it as empty as possible. But if it's better not to use it, why even have it?
This ROM completely removes emulation of internal sdcard. There is only single /sdcard0 now and it is mounted to your real external SD. Android and all apps see it properly as external storage. There are no problems anymore with space hungry apps like big games. All downloads will go to the external SD as expected. Apps2SD works seamlessly because storage not emulated. The whole configuration is much more straightforward and easier to work with.
If you have files previously stored on /sdcard0, they are still accessible from /data/media/0, but it is better to move them from there to free space in /data.
If you have installed RemountSD or similar, uninstall it, you don't need it anymore.
If after updating to not-emulated ROM you find that the Camera does not store pictures, just clear its data in Android Settings->Apps->All->Gallery (yes, Camera is part of Gallery.)
Audio Amplifier Analog Gain
Controlling amplifier gain allows to play music both louder (+12dB) at high volumes and clearer at low volumes. The gain adjustment can be found in Android Advanced settings.
The included twl6040 kernel driver also simulates Wolfson wm8994 Voodoo Sound extension for headset amplifier. If Voodoo Sound is installed and Smart Amplifier is enabled, the amplifier gain will be controlled together with the volume. This maintains optimal Signal-to-Noise ratio at low volumes.
Voodoo Sound app shows incorrect range of levels: -57dB..+5dB. In fact our amplifier range is -30dB..0dB in 2dB steps. This discrepancy does not affect the functionality.
The amplifier returns to default gain upon a call or any other microphone activity. After the microphone activity is finished the gain control is re-enabled.
The kernel also supports controlling microphone preamplifier gains. The gain can be adjusted for certain scenarios, for example lowered to capture loud audio during concerts. Camera is using SUB microphone.
BLN
BLN will consume some battery when a notification is in progress. For the the touch LEDs to be lit our phone has to be awake, otherwise the power to the controller goes down and the LEDs turn off. In order to conserve the battery the kernel implements only blinking notifications. The kernel will hold a wakelock only during the short LEDs-On phase and release it when LEDs are Off letting the phone go back to sleep. Native BLN blinking is disabled.
BLN can be enabled either with neldar's app (his paid version supports scheduling) or in the Advanced Settings.
MMS is working for me, but I am on straight talk (tmobile)
I suggest anyone having issues, switch apn to tmo lte settings and see if it makes a difference.
If that fails try setting up a fresh apn with the following details
[source] http://forum.xda-developers.com/showthread.php?t=2240233
bertscookie said:
The KB from T-Mobile:
http://support.t-mobile.com/docs/DOC-1979
Code:
APN settings laid out in the KB:
Name: T-Mobile
APN: epc.tmobile.com or fast.tmobile.com (for LTE devices)
Proxy: <Not set>
Port: <Not set>
Username: <Not set>
Password: <Not set>
Server: <Not set>
MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc
MMS proxy: <Not set>
MMS port: <Not set>
MMS protocol: WAP 2.0
MCC: 310
MNC: 260
Authentication type: <Not set>
APN type: <Not Set> OR Internet+MMS (depending on software version)
If you find yourself not able to send MMS messages it is most likely because the proxy,port,username,password fields are not <Not Set>. Just tap these values and delete any information in them. I always restart but not always necessary.
Some people enter 216.155.165.50 for the MMS Proxy and 8080 for MMS Port I have never had to and am not exactly why these values might be needed but try them if the T-Mobile settings don't work.
Click to expand...
Click to collapse
auto-rotate is not functioning properly for me. i set it to full rotation for launcher and system. when taking a picture in portrait mode, it saves in landscape. attached logcat.
I wonder if the Google Voice via SMS app feature is included
Sent from my LG-P769 using Tapatalk 2
Sources posted.
Bad bug - sensors don't work. Can't look until tomorrow, forgot my hard drive with Ubuntu VM in the office. (Upd: fixed)
leolawliet: Not sure, accordingly to Koush post CM has to be Jul 1st or later (I synced and recompiled today), but he's talking about some middleware patches but from his words it's a little unclear are they already merged or not.
AntonX said:
Sources posted.
Bad bug - sensors don't work. Can't look until tomorrow, forgot my hard drive with Ubuntu VM in the office.
leolawliet: Not sure, accordingly to Koush post CM has to be Jul 1st or later (I synced and recompiled today), but he's talking about some middleware patches but from his words it's a little unclear are they already merged or not.
Click to expand...
Click to collapse
From what he said it looks like it's been merged since July 1st.
Sent from my LG-P769 using Tapatalk 2
I think I know why sensors don't work. Will recompile and post tomorrow morning. In fact I have already made them work on my phone.
leolawliet: So it should work. You can try or wait until tomorrow when I post ROM with fixed sensors.
Interesting observation. Looks like the ROM boots to not-mirrored screen now because of the compiled HWComposer. If I try to replace it with the old prebuilt one, it boots to a mirrored screen.
AntonX said:
I think I know why sensors don't work. Will recompile and post tomorrow morning. In fact I have already made them work on my phone.
leolawliet: So it should work. You can try or wait until tomorrow when I post ROM with fixed sensors.
Interesting observation. Looks like the ROM boots to not-mirrored screen now because of the compiled HWComposer. If I try to replace it with the old prebuilt one, it boots to a mirrored screen.
Click to expand...
Click to collapse
I think you're onto something and hopefully your findings grants our device some official CM support
I guess I'll wait a bit, still tweaking PACrom JB to my liking in the meantime
Awesome work!
Updated build with fixed sensors.
Will do something to the kernel next.
Question: Has anybody really tried running this thing at 1400 MHz? Should I include it or stop at 1300? Also, is pinyoto's undervolting stable, nobody had troubles with it? Sudden reboots, kernel panics, etc.?
AntonX said:
Updated build with fixed sensors.
Will do something to the kernel next.
Question: Has anybody really tried running this thing at 1400 MHz? Should I include it or stop at 1300? Also, is pinyoto's undervolting stable, nobody had troubles with it? Sudden reboots, kernel panics, etc.?
Click to expand...
Click to collapse
i usually oc to 1300, from what i've read 1400 brings too many cons than pros.
i've been running test on a new jellybam port that i'm working on and i get sudden reboots when i use bluetooth stereo headset/speakers or capture pictures/videos.
AntonX said:
Updated build with fixed sensors.
Will do something to the kernel next.
Question: Has anybody really tried running this thing at 1400 MHz? Should I include it or stop at 1300? Also, is pinyoto's undervolting stable, nobody had troubles with it? Sudden reboots, kernel panics, etc.?
Click to expand...
Click to collapse
Undervolt caused reboots and stack dumps on my P769.
Thread Moved from Original Development to Development.
Thanks
The-Hulk
The-Hulk said:
Thread Moved from Original Development to Development.
Thanks
The-Hulk
Click to expand...
Click to collapse
are all "original dev" threads being moved? also from this point on if we start a new thread should it be done in "dev" only now? thanks!
*edit* @AntonX sorry for going off topic
@AntonX
Do you think you will keep codename p760 or have plans to change it to p769 ?
Lelus said:
@AntonX
Do you think you will keep codename p760 or have plans to change it to p769 ?
Click to expand...
Click to collapse
When I tried changing the device from P760 to P769 in the build.prop on PACrom JB it borked my sound, it's better to leave it alone for now.
Sent from my LG-P769 running PACrom JB using Tapatalk 2
Lelus said:
@AntonX
Do you think you will keep codename p760 or have plans to change it to p769 ?
Click to expand...
Click to collapse
I left only the board (TARGET_BOOTLOADER_BOARD_NAME) as p760, everything else is p769. I actually tried changing it and some related files but the phone didn't boot. So I decided not to mess with it for now. If you can figure out why it didn't boot I can change it. Or I may try later again.
leolawliet: There is library someplace called by the board name, like audio.primary.p760, so you probably need to rename it. HWComposer is also like this.
Only issue I have so far is the low audio.
Sent from my LG-P769 using Tapatalk 4 Beta
AntonX said:
I think I know why sensors don't work. Will recompile and post tomorrow morning. In fact I have already made them work on my phone.
leolawliet: So it should work. You can try or wait until tomorrow when I post ROM with fixed sensors.
Interesting observation. Looks like the ROM boots to not-mirrored screen now because of the compiled HWComposer. If I try to replace it with the old prebuilt one, it boots to a mirrored screen.
Click to expand...
Click to collapse
So no mirrored/inverted screen funny business? That would motivate me to unlock the bootloader lol.
Related
mattc Leo + Froyo w/Sense 1.8
Quick Changes:
New EVO kernel
Wifi tethering now works
Light sensor works
PPP reliability improved dramatically
No more hard freezes switching from Wifi to mobile data
MMS size fixed for T-Mobile US
Touch screen and G-Sensor freezes practically eliminated
Green line in YouTube HQ is gone, picture quality is improved
Based on the official HTC Desire Froyo update.
READ THIS!! You will see a strange screen at boot. It may have different images or lines in black/white and will appear to be frozen. This is normal, just be patient and it will move past this. Also, there is no RMNET - not even an option - for this build. PPP is stable and no longer freezes.
Random notes on the build:
Kernel is not overclockable. You can always replace with an overclockable kernel if you wish.
On PPP build, make sure all of your APN settings are correct. It may not work if they are not.
Instructions:
Download zip file.
Extract contents of zip file into a folder on your SD card named 'Android'.
Using a file explorer in Windows Mobile, inside the 'Android' folder run CLRCAD.exe. Don't worry, it will appear to do nothing, that is normal.
Run Haret.exe.
Enjoy Android.
Known problems:
It is easier to list what I know doesn't work.
Certain apps from the market won't install. Neocore is one for example. You have 2 options to get them to work. A) Copy the .apk to your SD card then run it from your phone or B) Unmount your SD card first (Settings > SD Card > Unmount SD Card).
Notification LEDs are flaky, sometimes work, sometimes not
Camera flashes prematurely.
Some items you may want that are indeed WORKING!
Bluetooth - Works completely on my Ford Sync system. A2DP, streaming audio, answering and ending calls, etc. BT Keyboards don't work yet.
Camera
3G. I get ~1000kbps down in Ft Worth. My EDGE speeds have increased in RC1.4.
WIFI. Confirmed working with WEP and WPA.
GPS. Takes some time to pickup on first use, works great.
SIM contacts are working. (edit: some people have had issues, I have not).
I have included Automount (a free app) to mount your SD Card. Simply open Automount, set it to mount, then plug in your USB cable.
FM Radio
Camcorder!
Change log:
1.8:
New EVO kernel
Wifi tethering now works
Light sensor works
PPP reliability improved dramatically
No more hard freezes switching from Wifi to mobile data
MMS size fixed for T-Mobile US
Touch screen and G-Sensor freezes practically eliminated
Green line in YouTube HQ is gone, picture quality is improved
1.7:
Added EVO and Nexus cam interfaces. User can choose which to use.
Default sense wallpaper now works. Live and static.
Voice dialer added, works over bluetooth.
New base for better app/market stability.
PPP and RMNET versions will be available without having to patch anything.
More default APN some corrected including TMOUS.
Root file system will allow easier updating in the future.
Switched to kernel from git. No overclocking. You can install any other kernel you wish.
Improved WIFI performance.
1.6b:
Bluetooth is working again.
Apps requiring SU are now working again. SetCPU and Titanium have both been tested.
Overclocking and underclocking work now.
Battery life has been improved.
Media folder added for missing ringtones and notifications.
Added Adobe Flash 10.1.92.8.
Random freezes should be fixed. You may get a hard freeze on first boot.
PPP reliability improved.
1.6
Flashlight now works on all 3 levels. No need for market flashlight app.
Switched from RMNET to PPP data. Results are more reliable connection and faster upload speeds.
1GB data store. This rootfs.img is *NOT* compatible with any others.
USB connections are now recognized as usb. You should get a usb menu upon plug-in.
5MP camera with standard def camcorder. Camera app has improved picture quality and flash over previous build.
1.5b:
Using new kernel that overclocks and has full ram.
Added support for LED keypad lights.
Amber charging and notification lights work occasionally but don't count on them.
1.5:
Speed increased dramatically with new kernel.
Added EVO camcorder and camera app, allows pictures and recording via onscreen button.
RC1.4:
Used official OTA Froyo update for Desire. This added a speed increase.
Added Cotulla's 03-08 kernel.
a. Fixed issues with sharp panel
b. Increased stability of I2C
c. increased touch screen ratio
d. Fixed volume level
e. Volume can be changed during call
f. Some work under removing apt voice during calls
g. Program soft reset should work now
Added USB Automount program to easily mount SD card within Android.
Data.img increased to 512MB for added app storage.
Market speed is increased significantly.
Bluetooth support adjusted, may add more support. Need testers. (Not keyboard support).
RC1.3:
Fix for proximity sensor killing phone issue.
Updated Bluetooth. This may fix some issues.
Added Froyo default keyboard w/voice input. To activate, long press in any text input field, choose 'Input Method', choose 'Android keyboard'. You will see a microphone button, push it to use voice input. This keyboard also has the "swipe up" feature standard in Froyo.
Added Voice Dialer and Voice Search apps. They work great.
RC1.2:
Added Cotulla's and dan1j3l's GPS fix. I don't think it has been tested 100% so just know it is experimental right now. Thanks to the devs for getting us that!
Cleaned some unnecessary files to (hopefully) improve speed a little.
Testing improved stability of the filesystem. If you transfer files to your device (music, etc.) as a USB device, make sure to safely eject the device before removing the USB cable. If you improperly remove the device, you may experience some strange issues.
RC 1.1:
First Build.
1.8 Download link: http://www.multiupload.com/Y4ZQOJ1YWO
1.7 Download link (ppp): http://www.multiupload.com/0HXQF8OAO9
Mirror (Germany): http://www.meinmedienportal.de/download-page/?category=30
Download for RMNET version(only use if you are having internet or hard freeze problems with PPP version, this is not a patch but a full version): http://www.multiupload.com/542ASB67OI
I have removed all previous downloads to clean up the post. PM me if you would like a link.
Kernel Sources:
The latest zImages can always be found here:
http://oe.netripper.com/files/htcleo_autobuild_evo_tree/
Git: http://www.gitorious.com/linux-on-wince-htc/linux_on_wince_htc
note: you do not need to download those, they are included.
Thanks!!!
Matt
I have had several people ask where they can donate. If you want to donate, click the 'Donate' button here:
Credits for help on the build:
ElBartoME - Amazing help with PPP
michyprima - for compiling a kernel so I don't have to
huanyu - for his overclocking skills
darkstone
shu8i
dan1j3l
cotulla
And beta testers:
Refuge
mega
Microang
EdangeL
I appreciate all feedback. We can't improve without criticism.
hahaha thx
Ok let's try this. (with sense )
I keep you updated.
Thats what i've been waiting for! darkstone's froyo with a sense skin ..
Wonderful! thank you
I just wanna know one completely un-related thing. does anybody know how to add more screens to sense?
Welcome mate.
Will give your rom a try as I try all the roms always even in WinMo. Thats how you find some really talent chefs.
I like the idea of bluetooth in -calls working
Can share the other download link? Megaupload doesn't support on my area. Thanks.
Great mod but was unable to get the bluetooth headset working with my jawbone icon. The A2DP worked for music, but not the phone audio. Will try on my Lexus to see if the phone headset works in there, will report back.
chiu1110 said:
Can share the other download link? Megaupload doesn't support on my area. Thanks.
Click to expand...
Click to collapse
what site can you access? I'll try to upload it for you.
Was waiting for a Sense build with Froyo, thanks.
taifuller said:
what site can you access? I'll try to upload it for you.
Click to expand...
Click to collapse
Thanks so much. Most of the site I can access except Megaupload. Example:rapidshare...
thank you. will try tonight
thanx mate! I'll give a try,and feedback as well
em what what is the rom are you guys run?
Hey i just got my HTC like 2week ago, right now running HTC rom (original t-mobile htc hd2) idk
but this is the point, I got a robot voice while calling with this Froyo version, plus the music won play at all.... SO any idea? plzzz
smithvilly said:
Hey i just got my HTC like 2week ago, right now running HTC rom (original t-mobile htc hd2) idk
but this is the point, I got a robot voice while calling with this Froyo version, plus the music won play at all.... SO any idea? plzzz
Click to expand...
Click to collapse
Thats the android (robot) speaking to you hahaha
try flashing a different radio and see if it helps...
all i can say is i'll keep this build for now great job mate waking up the phone is smoother than ever no SOD thanks and conrat
phone call doesnt work, anyone know why? other than that, excellent build!
thanks man.
lude219 said:
phone call doesnt work, anyone know why? other than that, excellent build!
Click to expand...
Click to collapse
Probably you didn't run CLRCAD befor HARET.
n e way i'm trying to run this build right now, 2 tries without luck i keep getting the green screen. any idea?
pandahboyz said:
Probably you didn't run CLRCAD befor HARET.
n e way i'm trying to run this build right now, 2 tries without luck i keep getting the green screen. any idea?
Click to expand...
Click to collapse
If you get green screen of death, it means that you are waiting too much to start android. Either boot with jmz loader or try one of the wm loaders and start it as soon as you can start something on your windows side.
hi guys
For those that haven't heard of or seen an Sleep of Death (SoD) in action , it is where your phone does not respond to any user input whilst it's in sleep mode thus making the phone unusable since you are unable to wake the phone. The only way to recover is to either force reboot the phone, receive a call or call yourself from another phone.
I have encountered SoD four times til now, on KE2, KE7 and Now KF2 .
I don't think its got anything to do with the ROM, this has happened for me on Cognition, VillainRom , CF-root on stock Roms.
looking around the web it seems it might be a kernel/driver issue and remains unfixed (not sure)?
Anyone knows workarounds? Any Devs that are working on this?
Thanks
I haven't encountered this yet and I've also tried a bunch of different ROMs. Are you by chance overclocking or underclovking/UVing at all? If so, that could be the culprit. If not, then its hardto say what may be causing it other than an app the phone may not respond well with.
I had this happen once. I tried many ways to wake it up even charging, the charging sound comes up but the screen wont wake. Had to reboot.
Havent happened again though.
I haven't under/over clocked the CPU at all but from what I understand it has nothing to do with CPU frequency but more so a bug in kernel or in one of the drivers.
Its not easy to reproduce but its definitely there, I'm hoping it'll be addressed in cyanogen rom when its out given the fixed SoD somewhere in 7.0rc I think.
Sent from my GT-I9100 using XDA Premium App
ke3pup said:
I haven't under/over clocked the CPU at all but from what I understand it has nothing to do with CPU frequency but more so a bug in kernel or in one of the drivers.
Its not easy to reproduce but its definitely there, I'm hoping it'll be addressed in cyanogen rom when its out given the fixed SoD somewhere in 7.0rc I think.
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
On my ace this issue occured when the wifi was on. The phone goes into "sleep mode" and needs a reboot (press the power key for 10 seconds).
I was not able to find the exact conditions but it was more promient when 3g was also switched on.
Does your issue occur only when the wifi is on?
This has happened 4-5 to me
as well. I have found that a putting the phone on charge can free it. But its a real pain if it happens out and about, I had to take the battery out to get it to work
i got it 2-3 times while using "Green Power" app.
Again this has nothing to do with an app/rom..etc. you may think a certain app you installed its causing it but in case of SoD that's highly unlikely. The source of problem is else where.
"@cyanogen: @Bradart @1000hams try a nightly build if you are on 7.0. Google fixed bugs for 2.3.4 that can cause that (7.0 is 2.3.3)."
Click to expand...
Click to collapse
The above is a quote in response to SoD question (don't know which device, but android < 2.3.4) which to me suggests another bug in 2.3.3 that has been fixed in 2.3.4.
http://forum.xda-developers.com/showthread.php?t=1238478
Here's the solution I hope it helps... it worked for me
Bug Report - SGS2 (Sleep of Death)
Please use this link to report the bug:
code.google.com/p/android/issues/detail?id=21607&thanks=21607&ts=1320690472
I think I found a way to avoid SoD (Sleep of Death)
I'm new on the forum And that SoD problem annoyed me for so long and I kept searching.... But I think I finally found why we kept getting SoD.
Ok so I'M NOT SURE, but Try following those steps and be sure of every single thing and then tell me if you guys keep getting SoDs..
1- "Do not use two governors as screen-on & screen-off govs, if they both have an upper frequency limit for screen-off state." - droidphile
2- I think some of us don't do "clean flash of our ROM", so you guys need to follow those exact steps from that link
http://forum.xda-developers.com/showpost.php?p=28395322&postcount=3
Or I will just write them again...
1- Reboot into recovery (Turn off your phone then press and hold the keys: Volume Up + Power + Home)
2- Wipe Data / Factory Reset
3- Install the Main ROM file
4- In AROMA installer select "Custom Installation"
5- Choose depending of your taste
6- When AROMA installer finish untick the "Reboot Now" option
7- When you're back on the recovery go to Advanced
8- Wipe Dalvik Cache
9- Fix Permissions
10- Wipe Cache Partition
11- Reboot
12- When you get the step for add your Google Account, if you don't have a WiFi enabled or you can' add it, skip it
13- When you boot into the system, it's probably that you don't have data enabled (3g, H+) just reboot the phone
14- When you boot again into the system, the data will be enabled and you can do the configuration of Google Account (if you don't do this step before)
This is the moment for install all the extras like themes, mods, fixes, kernels, etc.
3- ok and NOW After your "CLEAN Flash of ROM" When you use Titanium backup Root application to restore your applications, DONT restore the things with RED text color. Restore ONLY the things with green text color.
In other words, restore only apps with their data and NOT all system data.
4- Ok and Once you did that. About the Governor you use, I think we push the limits of the CPU and the phone just can't resist the tweaks we did and a SoD appears. So try these settings if you have Siyah Kernel
Minimum CPU frequency: 200 Mhz
Maximum Frequency: 1000 Mhz
Governor: luzactive
Default I/O sheduler: SIO
So try THAT and tell me if you guys keep getting SoD ...
lol I didn't get SoD since 2 days And I hope it could help. Because installing Wake My Android Pro, or WakeLock or Load Monitor just DIDN'T work for me -__-
i stumble upon this problem whenever i use too harsh UV settings(depends from kernel to kernel). also my device SoDs whenever i use 100mhz as the lowest step- again with some kernels it tolerates it. my guess is: every phone is slighty different, so you just have to experiment with yours and find the best settings for your specific hardware (you dont say xD)
screenager said:
i stumble upon this problem whenever i use too harsh UV settings(depends from kernel to kernel). also my device SoDs whenever i use 100mhz as the lowest step- again with some kernels it tolerates it. my guess is: every phone is slighty different, so you just have to experiment with yours and find the best settings for your specific hardware (you dont say xD)
Click to expand...
Click to collapse
I understand your point of view, but by the way, I read a lot of that forum, and putting minimum frequency at 100Mhz might be Bad for your phone for 4 reasons:
1) When you receive a call, the call might lag because it needs absolutely a minimum of 200Mhz, so setting your CPU minimum frequency at 100Mhz might cause probs for phone calls.. ( i read that somewhere on XDA but dont remember where...)
2) Moreover, "It seems 100 mhz uses more power than 200 mhz. According to tests, 100 mhz accounted to 1 W / GHz and 200 mhz to 0.7 W / GHz, when both the cores were online."
3) "200 mhz can finish same task faster compared 100 mhz and thus hit deep idle soon."
4) "200 mhz is the 'sweet spot' of frequency in SGS II. ie, the frequency used in the calculations based on the optimal energy to run (Ex: In Milestone it's 550 MHz). So , 'energetically efficient' frequency for our CPU is 200 mhz."
Those 3 last reasons came from droidphile I'm not the author of this, but minimum frequency should stay at 200Mhz
i want reactivate this thread, because I think there are some users who still have this problem like me.
As far as I recognized there seems to be more reasons for SoD.
All seems to have begun with Android 4.1.2 and just keeps on until now.
I have tried some kernels and runs now Dori 9.33 and see how it works.
It seems that there are some kernel issues as well as some apps and some constellations of SD-cards.
But no one has a real solution.
I read about a "indish kernel" for the i9100g models, but also some who reported SoDs with this kernel.
But I found no real solution for our i9100.
I have attached a logfile (catched with Catlog) which I recorded until my last SoD.
In my case, I can also call my phone and the caller hears it ringing, but my phone stays black without sound and unresponible.
The only thing is to hold the power button for 10 seconds and reboot it.
just to tell:
nearly 24h without a SoD with my combination
BUT: I have not used my camera so far! And I think camera & media scanning has something to do with it.
If everything is running until tonight, I will try my camera and see the result.
after nearly 2 days
:good: nearly 48h working, so I will keep my combination.
But it is interesting, that nobody has any problems although you can read a lot about this problem.
after more than 2 days:
and here we go. SoD :crying: but 48h is better than nothing
a lot of things might come from corrupt files.
There are 2 scripts which will clean your partitions and try to fix broken files
1. GS2ROMclean made by hawkerpaul
2. Fix_Partitions_v1.0.2.zip made by Computoncio
you can run out of CWM and install as a zip.
So far it is recommended to run 1. GS2ROMClean, reboot, then 2. Fix Partitions to ensure you have clean partitions
Be patient! 2. runs very long, up to 2 hours and the phone becomes very hot. So I think power connection is absolutely recommended
BUT NOT TESTED COMPLETELY BY ME
what I do not know is, how often these scripts shall be used
You could run the ROM clean as often as you want. If the other doesn't fix it after one time, no point running it again. In saying that, I'm not sure if there would be any benefit from running the first one more than once anyway.
Sent from a galaxy far, far away
lavemetoo said:
a lot of things might come from corrupt files.
There are 2 scripts which will clean your partitions and try to fix broken files
1. GS2ROMclean made by hawkerpaul
2. Fix_Partitions_v1.0.2.zip made by Computoncio
Click to expand...
Click to collapse
1. runs very fast, took round about 10 seconds. Reboot was successful afterwards. All was working.
Now I run 2. - info will follow - would be great, if there were a kind of progress bar or a kind of information. So you don not know if it hangs or not.
script 2. ended after 1h with a warning. Now run again?
Code:
/dev/block/mmcblk0p10: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p10: ********** WARNING: Filesystem still has errors **********
/dev/block/mmcblk0p10: 11854/131072 files (5.4% non-contiguous), 524288/524288 blocks
Checking preload partition:
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
/lost+found not found. Create? yes
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p12: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p12: 544/32768 files (0.0% non-contiguous), 29992/131072 blocks
Automatic Fix Partitions finished at 30-07-2013 14:10:33
attached is the complete logfile
ATTENTION: My phone was connected to USB and lost 10% battery during this script operation!
Hi
I prepared short review for SlimKat 3.4 unofficial build for XT910 UMTS.
I use it for a last few days and my general impression is positive.
But lets start from beginning...
1. Instalation
I use SafeStrap, so installation process is very easy: create slot, install software and gapps, clean cache and Dalvik cache. That's all.
After booting of phone there is sort setup and phone is ready to work. ALMOST...
After next restart phone stops connecting to network and to fix that problem it is necessary manually delete CellBroadcastReceiver.apk what is very easy because SlimKat is delivered with SlimCenter containing SlimSizer when user can delete any app.
So, delete it, reboot and forget about network connection problems. Why this app is delivered with most of KitKat ROMs for XT910 UMTS I do no understand. All of them have the same problem after rebooting.
2. Daily usage
I use it as my daily driver last days and it worked really good. I noticed just one crash when I used Any.do app but I cannot reproduce it so far.
Battery life is good for me - see BatteryLife.jpg attached. On the other hand I was totally surprised when I charged battery to 102% - see Battery102.jpg - really strange.
I turned system to use ART instead of Dalvik and I haven't noticed any problem so far. Every app I used worked properly. Of course app installation time is a bit longer now, but good information is that apps starts faster.
Call/receive calls - not problem. Sound is clean.
WiFi - I haven't noticed any problem with connection/disconnecting WiFi networks. Everything worked good.
GPS gets position really fat, I was very surprised with that.
SMS sending works properly but I still cannot send any MMS message. Nevermind data transmission is enabled. I does not work. To receive MMS data transmission must be enabled. This is the biggest bug I noticed.
Flip actions to dismiss call or alarm also don't work what confuses me. It worked perfectly in CARBON 4.2.2 version I used for long time.
It looks very strange in action: flip down - no action performed, flip up - phone seems to be blocked for some time and after a few seconds you can finally dismiss alarm or call.
Memory usage is much better than in 4.2.2 ROMs. After boot there is used 434MB and free 405MB of RAM with all of my services and widgets started. Great result.
Bleutooth I didn't test. I use it very seldom and it is not much important to me.
What was new for me - used apps display. It is changed in SlimKat - nice right side panel is displayed with list of used application.
Generally I must say that I like SlimKat. It has all options I really need to use it every day. I'm happy with Real dark option which turns system and most important apps into black theme, performance good enough without replacing kernel, ART support without problems and smoothness of GUI.
I hope that strange battery behavior and MMS sending problems will be fixed in next releases
And maybe XT910 will be officially supported by SlimKat team?
98236896 45
rys1908 said:
Hi
I prepared short review for SlimKat 3.4 unofficial build for XT910 UMTS.
I use it for a last few days and my general impression is positive.
But lets start from beginning...
1. Instalation
I use SafeStrap, so installation process is very easy: create slot, install software and gapps, clean cache and Dalvik cache. That's all.
After booting of phone there is sort setup and phone is ready to work. ALMOST...
After next restart phone stops connecting to network and to fix that problem it is necessary manually delete CellBroadcastReceiver.apk what is very easy because SlimKat is delivered with SlimCenter containing SlimSizer when user can delete any app.
So, delete it, reboot and forget about network connection problems. Why this app is delivered with most of KitKat ROMs for XT910 UMTS I do no understand. All of them have the same problem after rebooting.
2. Daily usage
I use it as my daily driver last days and it worked really good. I noticed just one crash when I used Any.do app but I cannot reproduce it so far.
Battery life is good for me - see BatteryLife.jpg attached. On the other hand I was totally surprised when I charged battery to 102% - see Battery102.jpg - really strange.
I turned system to use ART instead of Dalvik and I haven't noticed any problem so far. Every app I used worked properly. Of course app installation time is a bit longer now, but good information is that apps starts faster.
Call/receive calls - not problem. Sound is clean.
WiFi - I haven't noticed any problem with connection/disconnecting WiFi networks. Everything worked good.
GPS gets position really fat, I was very surprised with that.
SMS sending works properly but I still cannot send any MMS message. Nevermind data transmission is enabled. I does not work. To receive MMS data transmission must be enabled. This is the biggest bug I noticed.
Flip actions to dismiss call or alarm also don't work what confuses me. It worked perfectly in CARBON 4.2.2 version I used for long time.
It looks very strange in action: flip down - no action performed, flip up - phone seems to be blocked for some time and after a few seconds you can finally dismiss alarm or call.
Memory usage is much better than in 4.2.2 ROMs. After boot there is used 434MB and free 405MB of RAM with all of my services and widgets started. Great result.
Bleutooth I didn't test. I use it very seldom and it is not much important to me.
What was new for me - used apps display. It is changed in SlimKat - nice right side panel is displayed with list of used application.
Generally I must say that I like SlimKat. It has all options I really need to use it every day. I'm happy with Real dark option which turns system and most important apps into black theme, performance good enough without replacing kernel, ART support without problems and smoothness of GUI.
I hope that strange battery behavior and MMS sending problems will be fixed in next releases
And maybe XT910 will be officially supported by SlimKat team?
Click to expand...
Click to collapse
Small update:
MMS issue: installing 8sms application solves problem. Probably Messaging app does not resize image and whole MMS message is declined by network as too big.
SlimKat umts_spyder build 3.6 2014-03-09
I performed dirty flash of SlimKat 3.6 over SlimKat 3.4 - no problems.
Everything works as it worked before. I haven't noticed any new problems.
I'm still not happy with bad flip actions support but that this problem exists in every of tested KK ROMs - looks it is general malfunction.
Waiting for new version...
bluetooth
Hi I would be curious to know if the bluetooth works, in particular in the car. also if the bluetooth has any problems pairing and keeping the pair when you change from flight mode to normal, if you have to pair again or not . thanks for the review
Hi
I have tested bluetooth with other phone and headset and haven't noticed any problems. You do not have to pair devices again after going off flight mode.
SlimKat 3.8 upgrade
Hi
I performed dirty flash to SlimKat 3.8 without problems. CellBroadcastReceiver.apk is still delivered so you have to delete it manually to get rid of cell connection problems
After that device works good. Still great memory management
I noticed that problems with flip actions seems to be almost resolved and now I can dismiss call and alarm flipping down my phone.
For calls it works immediately but for alarms I need to perform flip down - flip up - flip down and after some delay alarm is dismissed.
What I'd like to see in SlimKat are Performance options in settings. Of course I can install some app to manipulate processor settings and governors but I think this should be part of system delivery.
And, of course, XT910 is still not supported officially, so forget OTA.
How about slim 4,any surprised？
I used SlimKat for a while and I found it REALLY FAST AND SMOOTH! I reccommend it!
Now I'm installing the 4.0 build and we'll see how it works
the only problem I experienced: when discharging completely to "0%"...my phone resets itself, quite strange/frustrating...
I'm still on 3.8. Yesterday I dischrged battery to 0% and phone shot down correctly , not restarted automatically.
Abou 4.0 - I'm a bit confused. SlimRoms.net does not mention that so far but in changelog we can find 3.10 version: http://slimroms.net/index.php/changelog.
I'll wait a bit
hello
I installed 4.4.2 build 4 and I got the network problem and after i deleted the cellbroadcast.. it worked!! but now i have a problem with the hotspot ;( my brother tried to connect but he couldn't ;( do you know what to do to solve this little problem?
I havent tried wifi tethering before (no need) but it looks problem exists. I also cannot connect to established hotspot (I still on 3.8). I remember that there was tethering problem on beginning of work on kitkat custom roms for Razr device but it was fixed long time ago.
rys1908 said:
I havent tried wifi tethering before (no need) but it looks problem exists. I also cannot connect to established hotspot (I still on 3.8). I remember that there was tethering problem on beginning of work on kitkat custom roms for Razr device but it was fixed long time ago.
Click to expand...
Click to collapse
Hello, 1st post here I LOVE Slimkat for our Razr, I've been running the latest updates in slot 1 for months and for the last few days I've run the latest build in the stock slot and love it even more.
But I have to agree that AP / hotspot / wifi tether is not working anymore. It was working fine for a while there -- here are notes in the update log:
29DEC2013 - CM's netd code "hopefully fixes wifi tether" [I think it started working around here for the 1st time]
09FEB2014 - "mobile hotspot fixed" [might have broke again along the line ? ]
In the last 2 builds (20MAR2014 first then tried 27MAR2014 both as dirty flash and then fresh in slot 1), I can create a hotspot but nothing can join. Too bad because I really make use of it, hope it gets fixed again soon
And thx to original poster for posting a quality review of what is one of the best ROMs for our classic spyder.
After a week on SlimKat 4.0 i have to say that it is really solid and stable. Wifi tethering is known problem (reported to dev forum). I also noticed that my favourite governor "hotplug" is no longer supported and battery usage over night is now 4% instead of 2% I used to. I'm not sure hotplugging is supported by interactive or ondemand governors. I think I'll try to use JBX kernel with SlimKat and see how good it is. If you have any experiences, plz share with me.
Whew this guy figured out that the CM11 WiFi AP fix still also works for us:
http://forum.xda-developers.com/showpost.php?p=51713472&postcount=1592
just installed and it's working.
Finally I tested SlimKat with JBX kernel (only battery saver enabled) and I havent noticed any better bsttery life. There was even worse than without it: 5-6% over night consumption when phone did nothing. I also played with governors enabled in JBX what almost every time caused system hanging.
So, finally I resign of JBX and made decision to give another chsnce to Carbon Rom that was my daily driver for months (release 4.2.2).
I must say I'm surprised how good is Carbon now - I remember first 4.4 releases. Everything seems to work properly including tethering. What is quite important for UMTS razor users we can disable CellBroadcastReceiver in settings - no need to delete it and restart phone.
There is one feature I love especially: lockscreen notifications. This is killer feature for me.
What is also important for me, Hotplug governor is enabled in kernel and again I have overnight usage 2-3%.
I must say I'm currently very satisfied with Carbon Rom. Looks it became my daily driver again.
rys1908 said:
Hi
I prepared short review for SlimKat 3.4 unofficial build for XT910 UMTS.
I use it for a last few days and my general impression is positive.
But lets start from beginning...
1. Instalation
I use SafeStrap, so installation process is very easy: create slot, install software and gapps, clean cache and Dalvik cache. That's all.
After booting of phone there is sort setup and phone is ready to work. ALMOST...
After next restart phone stops connecting to network and to fix that problem it is necessary manually delete CellBroadcastReceiver.apk what is very easy because SlimKat is delivered with SlimCenter containing SlimSizer when user can delete any app.
So, delete it, reboot and forget about network connection problems. Why this app is delivered with most of KitKat ROMs for XT910 UMTS I do no understand. All of them have the same problem after rebooting.
2. Daily usage
I use it as my daily driver last days and it worked really good. I noticed just one crash when I used Any.do app but I cannot reproduce it so far.
Battery life is good for me - see BatteryLife.jpg attached. On the other hand I was totally surprised when I charged battery to 102% - see Battery102.jpg - really strange.
I turned system to use ART instead of Dalvik and I haven't noticed any problem so far. Every app I used worked properly. Of course app installation time is a bit longer now, but good information is that apps starts faster.
Call/receive calls - not problem. Sound is clean.
WiFi - I haven't noticed any problem with connection/disconnecting WiFi networks. Everything worked good.
GPS gets position really fat, I was very surprised with that.
SMS sending works properly but I still cannot send any MMS message. Nevermind data transmission is enabled. I does not work. To receive MMS data transmission must be enabled. This is the biggest bug I noticed.
Flip actions to dismiss call or alarm also don't work what confuses me. It worked perfectly in CARBON 4.2.2 version I used for long time.
It looks very strange in action: flip down - no action performed, flip up - phone seems to be blocked for some time and after a few seconds you can finally dismiss alarm or call.
Memory usage is much better than in 4.2.2 ROMs. After boot there is used 434MB and free 405MB of RAM with all of my services and widgets started. Great result.
Bleutooth I didn't test. I use it very seldom and it is not much important to me.
What was new for me - used apps display. It is changed in SlimKat - nice right side panel is displayed with list of used application.
Generally I must say that I like SlimKat. It has all options I really need to use it every day. I'm happy with Real dark option which turns system and most important apps into black theme, performance good enough without replacing kernel, ART support without problems and smoothness of GUI.
I hope that strange battery behavior and MMS sending problems will be fixed in next releases
And maybe XT910 will be officially supported by SlimKat team?
Click to expand...
Click to collapse
Hi!
I installed Slimkat version 7.0 stable and my cell phone (S3 I9300) lost network connection randomly. Duration of connection is 1 - 2 seconds max. If I delete CellBroadcastReceiver.apk as you say, network connection will be stable, without disconnect randomly?
Thanks!
please dont quote the op!! just mention me
im going to attempt to keep a running list of bugs, per rom, for easy reference. good luck to me lol
THIS IS NOT A PLACE FOR ANY DISCUSSION ABOUT THE BUGS, OR ANY QUESTIONS ABOUT WHAT IS WORKING AND WHATS NOT!
below, i will list all available roms, and any bugs YOU REPORT IN THIS THREAD. there will be no debate, i will consider all reports and list accordingly.
please also notify me if something on the list gets fixed, so i can adjust the report.
as i cant test every rom, i will need your help. simple :reports please: 1. what rom exactly, 2. the problem/bug
any post not related to me making this list should be ignored.
if i have to dig through a pile of chit chat, to find the reports, ill just abandon the thread.
(im not including locked or dead rom threads)
please only report the bugs
(or what has been fixed) from the most current version of the rom, to try and keep this as accurate as possible. thanks
unofficial CM 12
- hotspot: not working
- data: spotty issues
- default messaging: spotty issues
- blue-tooth: not working for calls fixed 11/27/14
- ringtones: dont stick through reboot when on sd card
- location icon: appears randomly
- charging animation: intermittent fixed 11/27/14
- wireless charging: not working
- temperature: some reports of it running warm fixed 11/27/14
- airplaine mode: battery drain
- mms: works sporadically + general odd behavior on all messaging
- settings/private calls: see this post for issue details
official pac KK
- wifi: sporadic phone app crashes and screen re-sizing, see this post for details
-
-
validus
- wireless charging: not working
- text messages: default app not working
- blue-tooth: calls not working
jasmine
-
-
-
mahdi
- contact sync: not working
- hotspot: causes kernel crash
- wireless charging: not working
- blue-tooth: not working for calls
official CM 11
- wireless charging: not working
- blue-tooth: partially working (people cant hear you) fixed 11/27/14
- battery stats: not re-setting properly
- hotspot: occasional kernel crash, notification reports "0" connections even when connected.
- wifi: sporadic phone app crashes and screen re-sizing, see this post for details
official OSE
- screen: random freezing, seems to only effect some people
- wireless charging: not working
- blue-tooth: not working for calls
official vanir
- blue-tooth: calls not working properly
- proximity sensor: doesnt turn on the screen during calls when required seems to be fine for some, and not others)
- wireless charging: not working
- tap to wake: sporadic
- sms: possible issues with stock app
- pandora: sporadic playback issues (seems to be fine for some, and not others)
- screen: occasional freeze
official liquid smooth
- blue-tooth: call issues
- tap to wake: sporadic issues
-
unofficial beanstalk
- blue-tooth: calls not working
- tap to wake: sporatic
- display and lights: FC
unofficial slim kat
- wireless charging: not working
- blue-tooth: not working for calls
-
beanstown stock 11c
-
-
-
unofficial bliss stalk
- settings: Security/Notification Access, ticking "key test" causes soft brick.
-
-
paranoid android
- facebook: contact sync option missing reportedly, not a rom feature
- screen: random freezing after calls and sporadic in general fixed 11/28/14
- wifi: sporadic phone app crashes and screen re-sizing, see this post for details fixed 11/28/14
- system ui: infrequent crashing info
- charging: no animation/confirmation
reserved
let the reporting begin!!
i work during the day, so any reports then, likely wont get updated until im home.
PS. if you want to include a logcat, for an issue thats great. just post it and ill link it by he issue.
#bweN diorD ose has a issue with the screen not responding at random times would have to pull the battery Mahdi ROM for me wasn't letting me sync contacts also trying to use hotspot would crash the kernel
Sent from my LG-VS985 using Tapatalk
Also I'm running validus and I'm not able to send text messages
Sent from my LG-VS985 using Tapatalk
Unofficial CM12
1. BT calls not working, media is fine.
2. Ringtones don't stick, on reboot.
3. Location icon shows up in status bar intermittently. Not sure if it's running, or not.
4. Doesn't always show as charging, when plugged in. Not sure if it's charging, or not.
5. Wireless charging not working. Says it is, but it's not. Just had my phone on my charging pad, for an hour, and it lost a percent.
bostonbassman78 said:
Also I'm running validus and I'm not able to send text messages
Sent from my LG-VS985 using Tapatalk
Click to expand...
Click to collapse
i'm able to send text messages on Validus (using Evolve).
i just flashed Validus, and am wondering if BT calling works? I know it's a known issue with AOSP roms.
Vanir: 1. BT calling doesn't work.
2. something with proximity sensor - screen doesn't turn back on when call ends or when move phone away from face.
3. wireless charging doesn't work yet (shows as "charging" but doesn't actually charge).
Vanir was just a quick release, and they are working on 5.0 rom now.
EDIT: wireless charging seems to not be working with Validus, either (Tylt charger).
huskerkate said:
i'm able to send text messages on Validus (using Evolve).
i just flashed Validus, and am wondering if BT calling works? I know it's a known issue with AOSP roms.
Vanir: 1. BT calling doesn't work.
2. something with proximity sensor - screen doesn't turn back on when call ends or when move phone away from face.
3. wireless charging doesn't work yet (shows as "charging" but doesn't actually charge).
Vanir was just a quick release, and they are working on 5.0 rom now.
EDIT: wireless charging seems to not be working with Validus, either (Tylt charger).
Click to expand...
Click to collapse
Ya I have no idea didn't matter what messaging app I used they all failed I have for now resorted to my backup of beans deodexed
Sent from my VS985 4G using Tapatalk
Thanks for the reports!!
OP updated
@Bwen droiD thanks for the comprehensive bug list! This will be a great resource as more ROMs and updates are released.
As for Official Liquid Smooth
- BT audio is working, but BT calling is not fully functional (caller on other end cannot hear you, similar to pretty much all vs985 AOSP based ROMs I believe)
- dt2w has sporadic issues
Thanks for the report!!
OP updated
Unofficial cm12
All cell connections lost after reboot
Phone almost always is about 100 degrees
Standby battery drain on airplane mode
Thanks for the reports!!
OP updated.
Unofficial CM12
MMS sporadically works (constantly I'm "downloading" phase
---------- Post added at 01:59 AM ---------- Previous post was at 01:55 AM ----------
Edit: messenger is just acting weird... Messages having difficult sending and receiving... MMS especially
I'm now on aospa paranoid android and so far I've found that the sync contacts with Facebook option is missing
Sent from my LG-VS985 using Tapatalk
With latest invisiblek's CM12 build, bluetooth calling is fixed.
Just realized that ringtones will stick, on CM12, if you have them on the phone's internal storage. If you have them on your sd, you lose them on reboot.
Thanks for the reports!!
OP updated
Blue tooth calls also now fixed in cm-11 which is also now starting official nighlies
Thanks for the report.
OP updated
Sent from my G3, with mods made possible by team Codefire.
Delete
Hi. I built CyanogenMod 12 for LG P760/P765. It has some critical bugs like GPS problems.
What's not working/has bugs:
GPS isn't working
Wifi MAC adress is random (RIL issue)
WiFi Direct
Camera completly broken
Graphics glitch when locking screen
Kernel and rom features:
Ramhack 818Mb
Better battery life
OC to 1350 Mhz
GPU OC to 384 Mhz
Many tweaks
Sound boost on headphones
Updated screen driver
Power saving mode (in battery settings)
Internal sd disabled
Added BLN support (L9 BacklightMod app in Play Store)
Support for 5Ghz wifi
Bluetooth Low Energy support
Less battery drain by screen (lower screen refresh rate)
Better multicore managing
What you need:
LG P760/P765
Unlocked bootloader
Flashing:
Flash my recovery
Boot to TWRP
Make sure you have enabled EXT4 (if you haven't flashed CM11 before you can skip this step)
Flash ROM
Flash fix (if any)
Flash Gapps (if you want)
Reboot system now!
Download: http://artas182x.you2.pl/android-projects/cyanogenmod-12-lg-optimus-l9-ext4/
XDA:DevDB Information
CyanogenMod 12 for LG Optimus L9, ROM for the LG Optimus L9 P760, P765, P768
Contributors
artas182x
Source Code: http://github.com/artas182x
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2014-11-27
Last Updated 2014-11-26
Thanks for your work.
Is echo on call fixed or it's there like on aosp 5.0?
Doesn't camera work also for third party apps?
thanks for your work!
the truth that promises much change made.
Patch works for P768 PuntoAzul created by this device.
Thanks You Artas182x!!!
Bugs i found :
* Cannot connect to computer "USB computer connection" is not working..
* Battery usage data isn't available in battery settings
I can't say anything...
what about you @JulianJenner
Funny...
Redmi Note 1W Enhanched / MIUI 37.0.0 Stable Multilanguage / Tapatalk Pro 4.6.2
artas182x said:
Hi. I built CyanogenMod 11 for LG P760/P765. It has some critical bugs like GPS problems. [...]
Click to expand...
Click to collapse
I think u mean 12.
Thanks for ur work
Thank you for this!
Are you abandoning AOSP rom and only focusing on this now? Why did you prefer CM12 rather than AOSP?
Nice, can't wait for the major bugs to be fixed so I can try it out!
gps on cm12
Gps working for me (very very fast locking)
This rom is smoother than aosp 5.0.
Camera doesn't work with any app, also teslaled doesn't work.
Graphical glitches are also when rotate screen, not only when turn it off.
Gps works good after download lto with gps fixer. I think a little better than in cm11. I tried it on aosp and it doesn't work even with gps fixer.
I miss aosp task manager in notifications.
I didn't try calls yet to know if there is echo.
On aosp I have poor phone signal (half full) but on this rom it's full.
Is it just me or it is not possibile to get root privileges?
MirkoCe said:
Is it just me or it is not possibile to get robot privileges?
Click to expand...
Click to collapse
¿robot or root?
I'm rooted flashing supersu 2.30 beta (now updated to 2.35)
Ooops, i meant root of course! I thought there was no need for SuperSu (like in CM11).
My bad!
I can confirm, gps works well after downloading lto data im gps fixer. Unfortunately mobile data dont work for me. Artas good work!
So I tried the rom and it seems fairly smooth.
A part from the bugs already written in the first post
- mobile internet does not work, only wifi
-Privacy guard force closes if I try to open apps settings
-when I close a call dialer force closes
-if I try to delete call history in dialer it force closes too
-alarm doesn't work, clock application crashes
Haven't tried GPS but camera doesn't work anywhere, as state before. AOSP ROM seems more stable to me.
Great new CM version and artas fixing gonna give us soon a stable 5.0.
We have to thank to artas for his gift to us.
MirkoCe said:
So I tried the rom and it seems fairly smooth.
A part from the bugs already written in the first post
- mobile internet does not work, only wifi => for me both works
-Privacy guard force closes if I try to open apps settings
-when I close a call dialer force closes => it doesn't happen to me
-if I try to delete call history in dialer it force closes too => I can confirm this
-alarm doesn't work, clock application crashes => for me it works
Haven't tried GPS but camera doesn't work anywhere, as state before. AOSP ROM seems more stable to me.
Click to expand...
Click to collapse
More bugs I experienced:
Bluetooth fc's when trying to send a file.
Echo in calls seem fixed but sometimes caller can't hear me and I have to hang up and call again.
Uhm i guess I should have reinstalled. Maybe some configurations of mine were the problem. I'm gonna wait for a camera fix mainly, at least if I can use third party app.
Inviato dal mio Optimus L9 utilizzando Tapatalk
- Mobile internet does not work, only wifi
- ALARM - OK
- GPS - OK
- Something breaks the sound. How bad it will wake the phone or audio can not be that someone is calling, sms or even to activate the alarm.
- Off the phone and connected to the charger - lit display
- Camera doesn't work with any app.
- Echo in calls seem fixed but sometimes caller can't hear me and I have to hang up and call again.
- Stock ... Most visible when rotating an image.
- Lack of access to the phone when connected to a computer.