{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
UNIFIED BUILDS FOR MOTO_MSM8960 DEVICES
Code:
[B][I]Photon Q[/I][/B] (xt897 - asanti_c - Sprint )
[B][I]Atrix HD[/I][/B] (mb886 - qinara - AT&T)
[B][I]Droid Razr M[/I][/B] (xt907 - scorpion_mini - Verizon)
[B][I]Razr M[/I][/B] (xt905 - smq_u - GSM)
[B][I]Electrify M[/I][/B] (xt901 - solstice - US Cellular)
[B][I]Droid Razr HD[/I][/B] (xt926 - vanquish - Verizon)
[B][I]Razr HD[/I][/B] (xt925 - vanquish_u - GSM)
IMPORTANT:
There are 2 builds for moto_msm8960 devices.
moto_msm8960 - Is for devices that have updated to the official KitKat OTA/SBF
moto_msm8960_jbbl - Is for devices that remain on official Jelly Bean OTA/SBF
GOT BUGS?:
How to post a bug report
MAINTAINERS:
Dhacker29
Nadlabak (kabaldan)
EPinter
Skrilax_CZ
LINKS:
WEBSITE
BLOG
GITHUB
RAZRQCOM-DEV TEAM
CHANGELOG
BUG REPORTS
INSTALLATION:
Download ROM
[*] Download GAPPS
[*] Place both on SDcard.
[*] Reboot to recovery
[*] Do a factory reset
[*] Flash ROM
[*] Flash GAPPS
[*] Reboot and enjoy
DOWNLOADS:
ROMS
MOTO_MSM8960 - [KitKat Bootloader]
NIGHTLIES
EXPERIMENTAL
SNAPSHOT - M10 & newer only
Click to expand...
Click to collapse
MOTO_MSM8960_JBBL - [Jelly Bean Bootloader]
NIGHTLIES
SNAPSHOT [M5 thru M8] [M10 and newer]
Click to expand...
Click to collapse
GAPPS
GAPPS - AOSPA
GAPPS - GOO.im
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------------------------------------
TEST BUILDS
------------------------------------------------------------------------------------------------------------------------------------------
UNOFFICIAL CM12 LOLLIPOP - by dhacker29
> https://twitter.com/dhacker29/status/533142687873265664
PROGRESS
> https://twitter.com/dhacker29
DISCUSSION
> http://forum.xda-developers.com/droid-razr-m/general/round-candies-sticks-t2938748
------------------------------------------
DOWNLOADS
------------------------------------------
ROM:
> http://d-h.st/users/dhacker29/?fld_id=41187#files
GAPPS:
> http://d-h.st/users/dhacker29/?fld_id=27426#files
This is what I have been running for about two weeks now. Smooth and stable and the Nightlies dirtyflash with no problem. I'm using TWRP 2.7.0.0 as my recovery.
Sent from my DROID RAZR M using Tapatalk
should i flash the snapshot first, or just flash latest nightly?
L3van said:
should i flash the snapshot first, or just flash latest nightly?
Click to expand...
Click to collapse
Just the latest nightly.
The latest nightly is 2.08 correct?
Sent from my XT907 using XDA Premium 4 mobile app
romma1 said:
The latest nightly is 2.08 correct?
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
CM has unified CM11 for all Moto MSM8960 devices, thus individual nightlies stopped on Feb 18th. Please look under the device name of "moto_msm8960" instead of "xt907" for up-to-date nightlies (just use the link provided by OP).
Sent from Google Nexus 4 @ CM11
Thanks Andyyan...
Sent from my XT907 using XDA Premium 4 mobile app
low in-call volume
Hi, my wife's Razr M has been rocking the official, unified CM11 without any issues besides in-call volume. Whether on speakerphone or using the earpiece, call volume is very low and no amount of adjusting it up and down gets it up to as loud as it should sound. I was reading about people modifying the "snd_soc_msm_2x" file in /system/etc/snd_soc_msm but there are so many values there and so many repeated things that I'm not entirely sure what and how many values I'd have to adjust. Has anyone else successfully increased in-call volume (without totally distorting audio) and has the "snd_soc_msm_2x" file to share for this device? Thanks!
bofis said:
Hi, my wife's Razr M has been rocking the official, unified CM11 without any issues besides in-call volume. Whether on speakerphone or using the earpiece, call volume is very low and no amount of adjusting it up and down gets it up to as loud as it should sound. I was reading about people modifying the "snd_soc_msm_2x" file in /system/etc/snd_soc_msm but there are so many values there and so many repeated things that I'm not entirely sure what and how many values I'd have to adjust. Has anyone else successfully increased in-call volume (without totally distorting audio) and has the "snd_soc_msm_2x" file to share for this device? Thanks!
Click to expand...
Click to collapse
I haven't had this problem, but I found a [GUIDE] in the Nexus 5 forum that could help you out.
So glad to see an official release!!!
Is there an screen dimming (or staying dim) issues in this release, or has that been fixed now?
Livewire18 said:
So glad to see an official release!!!
Is there an screen dimming (or staying dim) issues in this release, or has that been fixed now?
Click to expand...
Click to collapse
Curious about the screen issue as well.. I know that I read about a kernel somewhere that fixes it, but I have been so busy in every area of my life I have not had the ability to keep up much. I totally missed the unified rom update... I was wondering why I kept seeing msm8960 posts all over the XT907 threads. Mystery solved!!!
Oh, I did DL the latest Milestone, so I will flash it for the heck of it.
Thanks- Scott (romma1)
Livewire18 said:
So glad to see an official release!!!
Is there an screen dimming (or staying dim) issues in this release, or has that been fixed now?
Click to expand...
Click to collapse
romma1 said:
Curious about the screen issue as well.. I know that I read about a kernel somewhere that fixes it, but I have been so busy in every area of my life I have not had the ability to keep up much. I totally missed the unified rom update... I was wondering why I kept seeing msm8960 posts all over the XT907 threads. Mystery solved!!!
Oh, I did DL the latest Milestone, so I will flash it for the heck of it.
Thanks- Scott (romma1)
Click to expand...
Click to collapse
The backlight issue still persist, and i'm unaware of any fix for it.
ATTACK said:
The backlight issue still persist, and i'm unaware of any fix for it.
Click to expand...
Click to collapse
Do you know if this is with all 4.4 roms for the Razr M, or just specific roms? I know there are rumors about 4.4.2 coming from Motorola soon for our phones, and I would assume they would have fixed it for an official update.
Livewire18 said:
Do you know if this is with all 4.4 roms for the Razr M, or just specific roms? I know there are rumors about 4.4.2 coming from Motorola soon for our phones, and I would assume they would have fixed it for an official update.
Click to expand...
Click to collapse
I think the issue is just on custom ROMs with "hacked" kernels. Once we get the updated kernel and drivers, then I sure it will be fixed. On my Galaxy Nexus, there is no issue with 4.4.2.
I can confirm that the screen light issue persists. Other than that, the latest build is fantastic.
Update: after about one day of running this, the lighting issue is too annoying for me. Back to a stable JB rom..
I put Brightness into the quick toggles and either toggle auto-brightness if it's a problem, or have just been manually setting the brightness somewhere in the middle and that's fine for most of the day anyway.
Only issue now is random reboots that I'm not sure are software or an issue with the power button sticking :-\ Has anyone else had the phone vibrate and then reboot on them suddenly?
bofis said:
I put Brightness into the quick toggles and either toggle auto-brightness if it's a problem, or have just been manually setting the brightness somewhere in the middle and that's fine for most of the day anyway.
Only issue now is random reboots that I'm not sure are software or an issue with the power button sticking :-\ Has anyone else had the phone vibrate and then reboot on them suddenly?
Click to expand...
Click to collapse
I haven't had any random reboots.
Quick easy way to deal with the screen dim on wake issue is when you wake the phone up and notice it is dim (before unlocking) just hit the power button again turning it off and again turning it back on. Works for me.
Everything is running fine except I get some stalls that render the phone unresponsive for 20-30 seconds then all is fine. Can't identify any triggers that cause it though. Doesn't happen very often either.
Headset controls are blown too. I have no clue why, but every time I press my button it acts like a screen cursor. Ex. Say I'm on the home screen and I press the button. First press highlights the Google search bar, second click actually "clicks" it.
Just a question since this is a CM11 thread... Once kernel source is released, does anyone know if we will see some better CM11 builds with the issues fixed?
Related
DISCLAIMER
You need to have an unlocked bootloader to use this ROM & kernel. Also I or any contributor in the software DOES NOT take responsibility of damages caused to your phone by using this ROM.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1. Copy ROM zip and gapps zip to sdcard
2. *if your kernel has no recovery* extract boot.img from ROM zip and flash to device using command
Code:
fastboot flash boot boot.img
3. Reboot device and go to recovery by pressing Vol-UP when LED is pink
4. If coming from 4.1 or 4.0 ROM wipedata/factory reset your phone
5. Flash ROM zip
6. Flash Gapps zip
7. Reboot and enjoy.
Milestone 2 :
mirror1 : http://goo.im/devs/aokp/mint/aokp_mint_jb-mr1_milestone-2.zip
mirror2 : http://androtransfer.com/get.php?p=AOKP/mint/aokp_mint_jb-mr1_milestone-2.zip
Official Nightlies (automatically built every 4 days on AOKP buildbox) :
http://aokp.co/devices/mint
Unofficial Test Builds (will contain experimental changes for testing) :
http://goo.im/devs/kxp/jb-mr1/mint
http://uploaded.net/folder/3qwd0q
Gapps :
http://goo.im/gapps/...0301-signed.zip
We spend countless of hours doing this for next to nothing. Posts, views, and donations encourage me, and everyone else who helps out.
Donate to AOKP
Donate to CyanogenMod
Every donation is cherished and loved.
If you'd like to help contribute by writing code, feel free to stop by IRC and talk to us!
http://android.championswimmer.in/aokp-changelog
Check out the ROM source on github. Open source, in the spirit of community kangage.
CREDITS
I cannot thank more for the hard work of FreeXperia Team (Jerpelea, Bin4ry, Kali-, Entropy512, Codeworkx and others) for working on Xperia devices.
Also huge thanks to Sony Mobile AB for having been very developer-friendly and helping us in all sorts of ways.
reserved
Nice! The bug list is the same as FXP 211, am I right?
Geo2160 said:
Nice! The bug list is the same as FXP 211, am I right?
Click to expand...
Click to collapse
yes it is
it shall always be
i merge fixes that FXP finds. and in the rare cases I can find fixes before the CM guys can, i push back to FXP
so both ROMs usually have the same buglist
nice to see you @Xperia T Original Android Development:good: whats the reason for the switch?:silly:
Are mobile data, phone signal working or is ril still not solved?
LosKhan said:
Are mobile data, phone signal working or is ril still not solved?
Click to expand...
Click to collapse
Changelog FXP
CM10.1
- latest cm 10.1
- GSM (T)
Click to expand...
Click to collapse
i think its working... (not tested by me)
not think so. i tried. for me no phone signal. wifi is working.
a new build is up
should have in-call audio fixed
Thanks man.
It's on the uploaded.to mirror which sucks big time.
Can't get it to download.
arifqur said:
Thanks man.
It's on the uploaded.to mirror which sucks big time.
Can't get it to download.
Click to expand...
Click to collapse
it's on both goo and uploaded
another build uploading as I speak...
try that
most/all audio problems shall be gone now
and now I want someone to list out all bugs
I start
1. Camera not working
2. Landscape video playback skewed
championswimmer said:
it's on both goo and uploaded
Click to expand...
Click to collapse
Thanks. Found it on the Goo Mirror.
Currently downloading.
Re: [AOKP][JB4.2] {T} KangXperiaProject
championswimmer said:
another build uploading as I speak...
try that
most/all audio problems shall be gone now
and now I want someone to list out all bugs
I start
1. Camera not working
2. Landscape video playback skewed
Click to expand...
Click to collapse
Just installed and using now.
Noted a gallery force close upon first boot. Also gallery3d failed, not sure if that's expected due to camera not working. Gallery is working fine though.
I tried to exit the settings and got a force close message from setup wizard. I have a screenshot, and then noticed the wallpaper changed back to default after having changed it. It has just happened the once.
I made a phone call and sound was working ok (just a quick call).
First time using aokp, but I'm impressed so I'll use it for longer and let you know of any bugs I come across
Many thanks,
Lunar.
Sent from my Xperia T using xda app-developers app
Re: [AOKP][JB4.2] {T} KangXperiaProject
Hello champ,
I was using my dock when i went to sleep last night, having the phone charge whilst using the night mode clock. I woke up a couple of hours later and the phone turned itself off at some point. The charge light was on but it hadn't charged at all.
A moment ago after using the phone to check Facebook and Twitter, it was left alone with the screen off, and it managed to switch itself off. No reboot, just off.
I have not adjusted the performance settings at all.
Cheers,
Lunar.
Sent from my Xperia T using xda app-developers app
lunarjetman1 said:
Hello champ,
I was using my dock when i went to sleep last night, having the phone charge whilst using the night mode clock. I woke up a couple of hours later and the phone turned itself off at some point. The charge light was on but it hadn't charged at all.
A moment ago after using the phone to check Facebook and Twitter, it was left alone with the screen off, and it managed to switch itself off. No reboot, just off.
I have not adjusted the performance settings at all.
Cheers,
Lunar.
Sent from my Xperia T using xda app-developers app
Click to expand...
Click to collapse
please try to get the bug again...
after this, make a logcat then Champ can recognize the bug
Br
Miustone
Re: [AOKP][JB4.2] {T} KangXperiaProject
Miustone said:
please try to get the bug again...
after this, make a logcat then Champ can recognize the bug
Br
Miustone
Click to expand...
Click to collapse
Hello,
I've reinstalled the rom last night to give it another go and try and catch a logcat (will be the first time, I presume adb logcat -v long is the best technique).
I haven't had the same problem yet, only watching video which I guess is expected.
I'll keep it running for a while, seems very nice.
[Edit] trying to use the swag wallpapers, a lot of them aren't loading up, is that a common problem? Would a logcat help?
Cheers,
Lunar.
Sent from my Xperia T using xda app-developers app
So...
My Impressions are:
-Unstable (Reboots with Screen On and Off)
-All System Sounds And Music let freez the ROM
-Battery drain is very extrem (No Changes in Performance Control)
-Many stuff is buggy (Swag Wallpaper,Ui Settings ect.)
So not a daily driver for me... back to stock Wait for FXP214 Release with fixed Sound (In Call,Music Audio,Loudness on Speaker ect.)
Next release of KXP with fxp214?
And another request... Can u change the Startlogo (FXP->KXP)? Would to give me more AOKP feeling )
Thanks for all Champ :good:
new nightly uploaded
new build up
includes working camera (no camcorder)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is an unofficial port of the latest version of ParanoidAndroid to the Xperia T.
INSTRUCTIONS
1. FORMAT SYSTEM
2. FACTORY RESET
3. INSTALL ROM, GAPPS
4. WIPE CACHE & DALVIK CACHE
5. REBOOT
PA 3+ UPDATES DO NOT NEED A FACTORY RESET, BUT YOU NEED TO INSTALL GAPPS AS WELL.
CREDITS,
The FXP Team (Kali- especially), codeworkx, Entropy512, AOSP/Google, CyanogenMod, D4rKn3sSyS, aaronpoweruser, molesarecoming
BUGS,
No HDMI out - from CM10.1
Broken stuff:
GPS
Very infrequent reboots - once a week for me
Video playback on default video player
HDMI out
Changelog:
24/07/2013:
* Update of PA sources to 3.68
* Pull in all the CM fixes
19/06/2013:
* Massive update of PA to 3.60 - adds HALO and a ton of other stuff
* Pull in all the CM fixes since previous release including camera, video recording and stability
* Fix bug where RIL subsystem crashes when a call is placed
13/04/2013:
Initial release
Thank you for your excellent work. Can we expect to TX?
nnmka said:
Thank you for your excellent work. Can we expect to TX?
Click to expand...
Click to collapse
Maybe. I need testers as I don't have one myself. Also if CM10.1 isn't working well then this won't either.
Wow, can't wait to flash this! Will post a report. Very nice to see more roms for these devices!
Oh my god, finally!
LE: While trying to format system I get this strange error:
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p12
Click to expand...
Click to collapse
Should this be any reason to worry?
Not particulraily. Just retry that step.
Sent from my Xperia T using Tapatalk 2
Well, it worked. I am running it now. It seems that the camera button doesn't work any more. Neither does the headset button.
Both need to be fixed in cm I'm guessing.
Sent from my Xperia T using Tapatalk 2
I've been testing this extensively for the last 12 hours or so.
I can not, under any circumstances, make a call. I get an "out of service area" error and the signal bar drops to zero for a couple of seconds everytime I try to make a call. Receiving calls, SMS and data work fine.
Also, I can't get to recovery. I get this image:
http://cdn.howtogeek.com/wp-content/uploads/2012/12/android-recovery-mode.jpg
I tried flashing the kernel from your unofficial/test build in the CM10.1 thread. This fixed the recovery issue, but I still can't make any calls.
Here is a noobish logcat dump. The last events should be some of my attempts in making calls.
http://www73.zippyshare.com/v/83080195/file.html
Hope this helps!
Geo2160 said:
I've been testing this extensively for the last 12 hours or so.
I can not, under any circumstances, make a call. I get an "out of service area" error and the signal bar drops to zero for a couple of seconds everytime I try to make a call. Receiving calls, SMS and data work fine.
Also, I can't get to recovery. I get this image:
http://cdn.howtogeek.com/wp-content/uploads/2012/12/android-recovery-mode.jpg
I tried flashing the kernel from your unofficial/test build in the CM10.1 thread. This fixed the recovery issue, but I still can't make any calls.
Here is a noobish logcat dump. The last events should be some of my attempts in making calls.
http://www73.zippyshare.com/v/83080195/file.html
Hope this helps!
Click to expand...
Click to collapse
The issue with recovery is that you haven't flashed one to the FOTA partition. I would recommend flashing TWRP which is available on the Android Development section.
As to making calls that issue was meant to be fixed a few weeks back in CM. Not sure what happened there
Well, calling works fine in your CM10.1 build. I'll see if it works in the new FXP release, which will hopefully be today. I'm also going to try TWRP right now.
Geo2160 said:
Well, calling works fine in your CM10.1 build. I'll see if it works in the new FXP release, which will hopefully be today.
Click to expand...
Click to collapse
Just remembered - we switched back to source built RIL yesterday - that seems to have broken it. It'll be broken on today's CM10.1 nightly and FXP build as well then :/
Well, there goes my hope of messing with properly implemented pie controls for the week . But I guess it's for the greater good. Keep up the good work!
Turns out that it was actually a PA only problem. I'm trying to isolate the reason. It is not my priority right now though. I'm testing other things right now.
Sent from my Xperia T using Tapatalk 2
tilal6991 said:
Just remembered - we switched back to source built RIL yesterday - that seems to have broken it. It'll be broken on today's CM10.1 nightly and FXP build as well then :/
Click to expand...
Click to collapse
sry i do not understand RIL means the Radio driver right? so no Phone Calls and SMS? Is Wifi working?:silly: (Wifi is the only Thing i need to play with my T)
and is your Camera fix included?:fingers-crossed:
Thanks again for your Awesome work! You bring the T Development to roll:highfive:
Miustone said:
sry i do not understand RIL means the Radio driver right? so no Phone Calls and SMS? Is Wifi working?:silly: (Wifi is the only Thing i need to play with my T)
and is your Camera fix included?:fingers-crossed:
Thanks again for your Awesome work! You bring the T Development to roll:highfive:
Click to expand...
Click to collapse
RIL= Radio Interface Layer
Everything works fine except video recording and outgoing calls.
i got random reboots. i tried a logcat, my first try.
i observed freeze and following reboot while changing camera picture size (4:3 to 16:9) with ProCapture - camera + (sometimes)
same while deleting list of recent apps
also the playstore simply close itself while trying search apps (sometimes, no freeze, no reboot, just closed playstore)
and the game Candy Crush Saga lags sometimes/horrible sound then (this game should run smooth normally)
maybe the attachement help you?
Very nice tilal! Couldnt find any bugs except for the ones already existing in FXP.
If you need me to build / mirror some stuff shoot me a PM. I haz access to xda build server
Cheers!
Hi, I sent you a few PM and then I saw your signature, sorry. I'm trying to build for the xperia ZL and was wondering if you could point me in the right direction. Could you share what you added to the pa vendor files like:
Adds
Removes
Dependencies
Maybe just your local manifest?
Thanks lot
Andres
PARANOID ANDROID for Unified moto_msm8960
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Unified means it includes:
Code:
asanti_c (xt897 - Photon Q - Sprint)
qinara (mb886 - Atrix HD - AT&T)
scorpion_mini (xt907 - Droid Razr M - Verizon)
smq_u (xt905 - Razr M - GSM)
solstice (xt901 - Electrify M - US Cellular)
vanquish (xt926 - Droid Razr HD - Verizon)
vanquish_u (xt925- Razr HD - GSM)
DOWNLOAD
Paranoid Downloads:
[OFFICIAL]
GOO.IM
msm8960_jbbl builds
msm8960 builds
[UNOFFICIAL] (custom builds with my own changes, may or may not be more frequent then official)
On Drdevs
(moto_msm8960 builds) mega.co.nz
(msm8960_jbbl builds) mega.co.nz
Paranoid GAPPS:
on AFH
Also, see the PA Gapps thread/links on xda for more links and info.
INSTALL
Always wipe data first if coming from a different ROM.
Format /system partition
Install ROM, then Gapps, fixes and/or mods and/or alternate kernel, wipe cache & dalvik, and reboot
CREDITS/THANKS
Google/AOSP
ParanoidAndroid Team
CyanogenMod Team
STS-Dev-Team
razrqcom-dev-team
and many others....
**************************************************
My Sources
Are all on my Github page
**************************************************
**************************************************
Also, Andre on G+ started a build bot for aospa-legacy devices I'll paste the link in here once I find it and that way one of us will have the latest build. Link!
/* Changelog (Top is the newest bottom is the oldest) */
06-11-2014 { offical pa changlog here. As for my changes just updates from cm for our device if you wanna look just go and look on my github kitkat stuff will be slowing down as work starts shifting over to lollipop. Asking when its done/coming will make it take longer. }
09-02-14 {
Here are Pa's changes in their own changlog thread/post just click me. As for our device changes I've merged in the latest fixes for msm8960 as well as fixed msm8960_jbbl. So whether your moto did or didn't get the 4.4.2 offical update it should be appearing there eventually if it's supported by cm.}
06-02-14 {
Haven't updated this changelog cause I'm lazy. Check pa's page for their changes as for our devices included in moto_msm8960 I've been pulling in upstream changes from dhacker + cm as of TODAY 06-02-14 the patches for 3.4 kernel has been pushed so you will need to update your bootloader to stock 4.4.2. Simply backup or setup flash the ota and then flash the newest paranoidandroid. }
03-27-14 {
Everything is working exepct nfc won't turn off from settings.
And included gestures on by default & extra keys from cm in aosp keyboard. [If you want it just check that you don't flash gapps that replace keyboard.]
Let me know if anything else does't work, post here NOT on paranoid's G+ page
}
Edit : My bad I did not read about the unified thing!
Gonna test the ROM right now!
This rom have been build bro and have been shared as well for the entire family.
work perfect on my mb886,thanks
notification peek
why is my notification peek option disapear?
i rebbot it and puff gone =( im on 27 build
GRIDSpawn said:
why is my notification peek option disapear?
i rebbot it and puff gone =( im on 27 build
Click to expand...
Click to collapse
Did peek ever make it into this build...?
Also, what's the consensus on using ART with PA?
Thanks for this build! I'll report back tomorrow after a full day Thank you thank you.
msassounian said:
Did peek ever make it into this build...?
Also, what's the consensus on using ART with PA?
Thanks for this build! I'll report back tomorrow after a full day Thank you thank you.
Click to expand...
Click to collapse
Yeah, peek first build is the 0327. Mine is working without issues. Didn't tried ART yet but it seems PA don't recommend it. Nevermind, it's the usual warning from CM and PA. I'm switching to it now to do some testing.
I heard peek was wakelocking and draining battery awfully, any comments on how is working now?
Sent from my RAZR HD using xda app-developers app
How is the OTA working to install 3-27? I flashed 3-25. I use the OTA on my Nexus 10 w/ TWRP. I'd like to see if the OTA works with the Moto and Philz CWM
juanepichio said:
Yeah, peek first build is the 0327. Mine is working without issues. Didn't tried ART yet but it seems PA don't recommend it. Nevermind, it's the usual warning from CM and PA. I'm switching to it now to do some testing.
Click to expand...
Click to collapse
hmm...is there something i need to do to activate peek? i don't see it...
looks like it should be under settings>display>peek notifications but i don't see anything...strange.
I'm not seeing peek either.
Sent from my RAZR HD using xda app-developers app
The build provided in the first post it's wrong
You have to download the 26 build and update it from ota
Sent from my RAZR HD using XDA Premium 4 mobile app
jblaylock said:
How is the OTA working to install 3-27? I flashed 3-25. I use the OTA on my Nexus 10 w/ TWRP. I'd like to see if the OTA works with the Moto and Philz CWM
Click to expand...
Click to collapse
OTA works great. I flashed 0323 and updated to 0327 afterwards without issues. Although i'm using CWM touch 6.0.4.4 there should be no problem.
msassounian said:
hmm...is there something i need to do to activate peek? i don't see it...
looks like it should be under settings>display>peek notifications but i don't see anything...strange.
Click to expand...
Click to collapse
That's where you should see it. Remember previous builds didn't have peek on it. Flash 0327 and it would be there.
---------- Post added at 08:06 PM ---------- Previous post was at 07:56 PM ----------
Hydr0id said:
I heard peek was wakelocking and draining battery awfully, any comments on how is working now?
Click to expand...
Click to collapse
I can't be really objective yet because I had this installed 1 day ago. Didn't noticed an "awfully battery draining" but it could be better. We're awared how keeping peek active could impact on battery performance because those 10 sec sensor window. It has some issues already, sometimes sensors won't respond and it won't wake up when you pick it up. But peek is on beta yet and all-in-all is working as espected.
So I flashed the 3/27 build and idk if I'm missing something but I have like no options...no extra goodies no peek no pie seemed like stock KitKat so I restored my previous ROM, I'm still interested in trying this seemed smooth just no extra tweaks or settings on my end...am I the only one with this issue? Clean wipe flashed through twrp wiped cache and all that jazz lol
Peek doesn't work well in my pocket when a notification arrive inside my pocket it Unlocks by itself
Sorry if my English is bad xD
Sent from my RAZR HD using XDA Premium 4 mobile app
GRIDSpawn said:
Peek doesn't work well in my pocket when a notification arrive inside my pocket it Unlocks by itself
Sorry if my English is bad xD
Sent from my RAZR HD using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Peek is still in beta its going to be buggy/glitchy until everything is sorted out
GRIDSpawn said:
The build provided in the first post it's wrong
You have to download the 26 build and update it from ota
Sent from my RAZR HD using XDA Premium 4 mobile app
Click to expand...
Click to collapse
interesting....i'll give that a shot.
msassounian said:
interesting....i'll give that a shot.
Click to expand...
Click to collapse
Didn't see this sorry I will also try this!
Also, probably a very dumb question. but does coming from the unofficial AOSPA build count as coming from a different ROM (AKA require a factory reset?) or is just a system/cache wipe okay.
Don't install OTA update for - 20150704 - Instead install a newer build from here for now until a new OTA is out
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
INSTRUCTIONS
1. FACTORY RESET (IF COMING FROM ANOTHER ROM)
2. INSTALL ROM
3. INSTALL SUPERSU
4. THEN GAPPS
5. REBOOT AND ENJOY
CREDITS
@MikeCriggs, @DC07 for some OP stuff
Google/AOSP,
Ayysir,
CyanogenMod,
ParanoidAndroid team,
ParanoidAndroid Legacy team,
XDA,
And anyone else I forgot
LINKS:
XDA Forum
PA Github
Legacy Github
PA Gerrit
Legacy Gerrit
XDA:DevDB Information
ParanoidAndroid, ROM for the Moto G
Contributors
Kayant
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Version Information
Status: Beta
Created 2015-05-23
Last Updated 2015-08-16
Bugs
Bugs
- Same as CM12.1
Changelog
20 May
https://plus.google.com/+Aospal/posts/HXncwLNiKG2
- MSIM: Fix issues
- MSIM: Ability to hide empty sim card notifications
- Sound: connect/disconnect notification support (with ability to specify tone)
- Add option to disable search bar on recents
- Heads Up snooze (swipe up on a heads up notification initiates this)
- Change default mode of AppOps to make it more reliable
- Misc Bug Fixes
- Language translations (Thank you to our great Translators!)
- ParanoidOTA: fix inability to download OTAs
- M8 & Sirius: Enabled QuickBoot
28 May
https://plus.google.com/+Aospal/posts/XKXtu8Kir4t
Changelog:
- Wake on plug
- Home button wake
- Theme Engine bug fixes
- Volume Panel enhancements
- Low-level optimizations to our core base
- Loads of bug fixes for several NPEs, ANRs and OOMs.
Kayant said:
Bugs
- Same as CM12.1
Click to expand...
Click to collapse
Thank you for bringing us such a wide variety of ROMs for our device.
I am going to start calling you Smitty Werbenjagermanjensen , because you are number one!
Sent from my Moto G 4G LTE (XT1045) Retail US variant
ROM: SaberMod 14 (5.1.1) 5/22 build
Carrier: Cricket Wireless
Travisholt92 said:
Thank you for bringing us such a wide variety of ROMs for our device.
I am going to start calling you Smitty Werbenjagermanjensen , because you are number one!
Sent from my Moto G 4G LTE (XT1045) Retail US variant
ROM: SaberMod 14 (5.1.1) 5/22 build
Carrier: Cricket Wireless
Click to expand...
Click to collapse
ROFL, thought I was the only one who actually used that joke hahaha.
So Kayant you made this official legacy device, congratulations!
I have always wanted AOSPA on the 4g, even thought of building it myself, I'm glad you did it.
omg i was thinking everyone is building of cm why is there no aosp builds? and here it comes thank u so much for your hard work.. must ... flash... immediately !
Well PA was my favourite ROM of all times, thanks for bringing this ROM to peregrine. I flashed this this morning, I'd really love to see some of the features that PA offered in 4.4.4., as for now it doesn't really have any customization option.
Thanks Kayant, been using your kernel and is great.
Fellas I'm having a problem with the initial setup.
As soon as the setup screen (the blue one with the language selector) starts, the phone goes back to booting again from the boot animation.
It shows the language screen for about 2-3 seconds then goes back to boot animation. First time I've seen this type of error.
I clean flashed everything...
Kayant said:
Bugs
- Same as CM12.1
Click to expand...
Click to collapse
Is a PA rom, CM based or AOSP based? I've read some comments applauding this rom for the variety it adds, but I have only come across CM12.1 roms so far and if this has bugs from CM12.1 then isn't it too CM12.1 based?
Secondly, SOOOOOOO EXCITED to flash this been waiting for PA for my phone forever but never had a device (too many samsungs in my life) which had any rom. YES FOR MOTO!
Lastly, I know this is listed as BETA but then on the PA website it says it is STABLE. what's the different dev stages for this rom?
Thanks so much for the effort Kayant!
thecraiglee said:
Is a PA rom, CM based or AOSP based? I've read some comments applauding this rom for the variety it adds, but I have only come across CM12.1 roms so far and if this has bugs from CM12.1 then isn't it too CM12.1 based?
Secondly, SOOOOOOO EXCITED to flash this been waiting for PA for my phone forever but never had a device (too many samsungs in my life) which had any rom. YES FOR MOTO!
Lastly, I know this is listed as BETA but then on the PA website it says it is STABLE. what's the different dev stages for this rom?
Thanks so much for the effort Kayant!
Click to expand...
Click to collapse
It's AOSP based. Why you will find the same/near the same bugs on every rom for a device is because to build the rom for a device you need something called a device tree - https://github.com/AOSPA-L/android_device_motorola_peregrine
That same device tree is used for all Peregrine roms and contains all the necessary configs, files and such to make a rom boot up and run on a device as such every rom built with the same device tree we have the same device bugs expect ones included by the rom.
Although our device is different in that it also needs - https://github.com/AOSPA-L/android_device_motorola_msm8226-common which is a shared device tree for all Moto G devices as they all share the same hardware for the most part.
Hey guys, how is battery working for you?
Mine is being unreal, just got 3 hours SoT and still have 50% with wave gesture turned ON, but I have the funny feeling that it will suddenly drop to 0, I just hope the hotfix solves it. Just wanted to ask, it seems that the recent fix to radio wakeclocks and removal of p-thread has really done a miracle with my battery and hope yours too.
Kind regards.
Duuh, wrong thread.
I'm having an annoying bug. Everything is great about this ROM but I can't open toggles on Quick Settings. If I keep pressing the WiFi toggle, normally WiFi settings (not the quick setting menu but the settings app itself) should open, but instead nothing happens. This is the same for all toggles (location, screen rotation..) Could you perhaps fix this?
beeeto said:
Hey guys, how is battery working for you?
Mine is being unreal, just got 3 hours SoT and still have 50% with wave gesture turned ON, but I have the funny feeling that it will suddenly drop to 0, I just hope the hotfix solves it. Just wanted to ask, it seems that the recent fix to radio wakeclocks and removal of p-thread has really done a miracle with my battery and hope yours too.
Kind regards.
Duuh, wrong thread.
Click to expand...
Click to collapse
Fail beeeto, fail
Sent from my Moto G 4G LTE (XT1045) Retail US variant
ROM: SaberMod 14.1 (5.1.1) 5/22 build
Carrier: Cricket Wireless
Sparubens said:
I'm having an annoying bug. Everything is great about this ROM but I can't open toggles on Quick Settings. If I keep pressing the WiFi toggle, normally WiFi settings (not the quick setting menu but the settings app itself) should open, but instead nothing happens. This is the same for all toggles (location, screen rotation..) Could you perhaps fix this?
Click to expand...
Click to collapse
There is no fix because that's how it works in AOSP until that function is added to it which it hasn't been added yet in PA.
Thanks for your answer. Please let me know when this is added because this is by far the smoothest ROM I've tried. CM12-based roms seem to slow down after an amount of running, this one stays smooth. Good job!
probable bug?
The rom runs well on my xt1039, but finding only small problem: I have a bar (disturbance effect) that goes from the bottom to the top of the display. It looks to boot, and not go away.
You help me?
77b14 said:
The rom runs well on my xt1039, but finding only small problem: I have a bar (disturbance effect) that goes from the bottom to the top of the display. It looks to boot, and not go away.
You help me?
Click to expand...
Click to collapse
Put your device to sleep for a minute or so and it should go away.
hand wave ambient display
The hand wave feature used in build 14 of @beeeto cm12.1 sabermod is amazing and I was wondering if you had any plans of implementing it into your ROM?
This rom is very good, but as beeto build 14.1, is possible to migrate his kernel to this rom?
This seems to be running really nicely. I've always had a soft spot for PA ROMs and this is working smoothly and I've had no major issues so far.
Sent from my XT1045 using XDA Free mobile app
Kayant said:
Put your device to sleep for a minute or so and it should go away.
Click to expand...
Click to collapse
Thank you for your help.
Just turn off the display and everything is ok. :good: :good: :good:
Another question: You are running the GPS module (My detects no satellites)? with stock rom works with AOSPA custom rom not.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SlimROM is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
The entire SlimTeam works together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and Gerrit.
----------------------------------------------------------
-- Changelog & Updates --
----------------------------------------------------------
Known issues:
*Motorola cameras will not work correctly when using non-stock DPI; Victara stock DPI = 480
*Gestures must be toggled off then back on (in settings) before they work correctly
*Root
Apply root via developer settings.
SuperSU doesn't work with the current cm kernel:
Until CM's kernel compression is supported by SuperSU, or until we switch to using a different kernel, the built-in root is our easiest (maybe only?) option.
Downloads:
6.1: https://www.androidfilehost.com/?w=files&flid=74028&sort_by=date&sort_dir=DESC
beta_7.1: https://www.androidfilehost.com/?w=files&flid=82824&sort_by=date&sort_dir=DESC
GApps:
Testing using:
Banks Gapps
OpenGapps
Root:
- Built-in to 6.x
- or use SuperSU 2.79
I am a builder, NOT a developer.
I can incorporate fixes that others have accomplished, but I won't be blazing any trails.
Source (device): https://github.com/DubMoto/
Source (firmware): https://github.com/SlimRoms/platform_manifest
-Cyril
Awesome work, I was going to do it but got too lazy to sync the repo haha
It works on XT1092?
Currently, i'm using remix for that matter.
Nice ROM. Very Fast.
The echo issue fix can easily be incorporated into the build, but have you experienced any downsides as a result of this change?
newtoncd said:
Another member posted this and fixed my issue:
modify the following settings in build.prop to read:
--ro.qc.sdk.audio.fluencetype=fluence
--persist.audio.fluence.speaker=false
Click to expand...
Click to collapse
Flebite said:
Thank you, I had the speaker echo problem and your solution fixed it.
So no problem anymore for me, 3rd phone on remix and it is great !
Is there an option for notification led blinking? I have only the option "always on" now on v5.6.8.
Thanks.
Click to expand...
Click to collapse
Hi,
I didn't noticed any problem yet. I did a call with the stock line (from remix rom) "--persist.audio.fluence.speaker=true", echo problem was there. Then I modified it to "false", reboot the phone and did a 5mn call and the loudspeaker was fine.
the other line was already set to "fluence".
i always loved slim on all my devices, gonna test it now. i hope this ROM doesn't get abandoned like SlimLP for this device was. great work
Lynse said:
i always loved slim on all my devices, gonna test it now. i hope this ROM doesn't get abandoned like SlimLP for this device was. great work
Click to expand...
Click to collapse
I don't think so.. Slim is back!!! Weeklies for officially supported devices already started! So the OP could become a device mantainer for victara
bart.found said:
I don't think so.. Slim is back!!! Weeklies for officially supported devices already started! So the OP could become a device mantainer for victara
Click to expand...
Click to collapse
great!!
Sent from my XT1097 using Tapatalk
A week now with this wonderful ROM... battery gives almost 6h on screen... Biohazard Audio working... just 2 random reboots... but still no found a cause... everything is working...
Slimroms has recently switched from Wednesday to Friday releases, and hosts the general changelog at: https://slimroms.org/#/
There still isn't much customization at this stage, so I'll continue uploading alpha builds, but I probably won't xda-announce them until they reach beta status.
OMS (the replacement for layers) is in gerrit, but I have no idea when that'll be ready for debut.
Cheers
-Cyril
odrareg80 said:
A week now with this wonderful ROM... battery gives almost 6h on screen... Biohazard Audio working... just 2 random reboots... but still no found a cause... everything is working...
Click to expand...
Click to collapse
i have never had 6hours of SOT> How is that possible?
roddem said:
i have never had 6hours of SOT> How is that possible?
Click to expand...
Click to collapse
Dunno... maybe because i don't use games... but video... i see a lot... and normally conected on WiFi...
hamzaalijoiyah said:
[ ... ]
I switched to Mokee before noticing it, but does [DU] rom also have the RTC reset bug that I'm seeing in almost every CM based rom recently? Time just resets to build date(and time) whenever device is switched off.
Click to expand...
Click to collapse
chinadyj said:
I confirm the time reset bug. Do you know if there are cm or aosp based roms fix this bug?
Click to expand...
Click to collapse
hamzaalijoiyah said:
Not that I know of.... i tried DU, RR, Mokee and CM nightly(though I forgot the date), all had same bug. I switched to Stock because I switch off my phone a lot and just couldn't live with it...
Click to expand...
Click to collapse
Can you describe this issue further? If I turn the device off, and then restart it, the date and time are incorrect?
I can't seem to reproduce the behavior on Slim. The date and time are always correct, even after I have the device turned off.
These victara builds use CM's device-code, but the ROM is NOT CM-based.
-Cyril
cyril279 said:
Can you describe this issue further? If I turn the device off, and then restart it, the date and time are incorrect?
I can't seem to reproduce the behavior on Slim. The date and time are always correct, even after I have the device turned off.
These victara builds use CM's device-code, but the ROM is NOT CM-based.
-Cyril
Click to expand...
Click to collapse
Yeah that'a the issue..... whenever I restart my device, its time goes back to build date and time.... I haven't used Slim yet but I found it on CM and all recent releases of CM based roms.... Guess CM code is resetting RTC at each boot but its just a speculation... Good to hear Slim isn't effected by this bug...
Has anyone been able to gain root access on this ROM? When i tried it, my clock and battery got all funky (Battery registers 4,007% and clock changes time at random) and wifi stops working altogether.
Pandelicia said:
Has anyone been able to gain root access on this ROM? When i tried it, my clock and battery got all funky (Battery registers 4,007% and clock changes time at random) and wifi stops working altogether.
Click to expand...
Click to collapse
Root is built-in, enable it from developer settings.
When I use a root app, I get the expected prompt, and the device behaves as expected.
(screenshots attached)
-Cyril
I'm getting foreclosures when I do layers I love the room though
hutchjim said:
I'm getting foreclosures when I do layers I love the room though
Click to expand...
Click to collapse
Yeah, this is currently a known slim issue. There's a frameworks issue, and Slim is waiting to see how OMS/substratum works, to decide whether to implement it or not... Glad you're enjoying the rom, there's a little bit more customization every week.
-Cyril
Great ROM. I'm not getting any LED notification, anyone else have this issue?