md5: bd12716827ef6e2e0b073d25b62e051c
Note: I haven't tested this one out personally. My razr m is on the back burner right now as I'm switching providers and moving to the nexus 5.
Edit: Don't forget the new gapps.
Posted 17 March 2014 - 10:28 AM
md5: bd12716827ef6e2e0b073d25b62e051c
Note: I haven't tested this one out personally. My razr m is on the back burner right now as I'm switching providers and moving to the nexus 5.
Edit: Don't forget the new gapps.
Posted 18 March 2014 - 01:41 AM
md5: bd12716827ef6e2e0b073d25b62e051c
Note: I haven't tested this one out personally. My razr m is on the back burner right now as I'm switching providers and moving to the nexus 5.
Edit: Don't forget the new gapps.
I have flashed this and it is working fine so far. I love this rom. I did a dirty flash over 3.6 and a dirty flash over the gapps.
Thanks for your work!
Posted 20 March 2014 - 03:11 PM
Posted 20 March 2014 - 03:15 PM
Posted 21 March 2014 - 10:57 AM
md5: 765e8025be2c6d82bb06ccb676c43c5a
Posted 21 March 2014 - 01:36 PM
Posted 21 March 2014 - 03:30 PM
Posted 21 March 2014 - 04:05 PM
Is the volume fixed in this build? The 3.8 build I'm on now the in call volume is so low I can bearly hear anyone talking on the other end
Sent from my XT907 using Tapatalk
There was a commit that deals with losing volume persistance after reboot. Maybe that will have some effect on your problem?
Flashed latest build without a problem. 1st time on SlimKat. Keep getting error 24 when trying to install RomToolbox Pro. Never had that before. Any ideas?
Sent from my XT907 using Tapatalk
Are you using the slim 3.x gapps?
Posted 21 March 2014 - 04:19 PM
Posted 21 March 2014 - 08:17 PM
Posted 22 March 2014 - 06:32 AM
I'm using the minimal gapps from post #61. You think I need the AIO gaps? I usually just use mini or modular
Sent from my XT907 using Tapatalk
No, that should be fine.
Update: ROM Toolbox Lite installs without a problem. RT Pro still gives me an error. Weird.
Sent from my BN NookHD+ using Tapatalk
Check this:
Posted 22 March 2014 - 07:33 AM
Posted 22 March 2014 - 07:54 AM
Posted 24 March 2014 - 03:42 PM
md5: 913e65643bad2ee61b0b202b1286967f
There's also a new gapps available even though it is the same filename. I pointed to some new repos in this build in order to clean out some leftover junk and made a fresh build environment. Github was having issues last night which is why we skipped a version, but I managed to pull everything together today.
Posted 30 March 2014 - 07:05 AM
Maybe I missed it but I don't see it anywhere in the thread.
Is this only for unlocked bootloaders?
Posted 30 March 2014 - 02:01 PM
Maybe I missed it but I don't see it anywhere in the thread.
Is this only for unlocked bootloaders?
Posted 02 April 2014 - 10:14 AM
md5: 9e1142218170dca9150823ca7c2f5ca8
Edit: GPS is disabled in this build.
Should be the same as stable 4, someone bumped the build number early.
The slimrom blog recommends doing a full wipe when updating to the new 4.x gapps.
Posted 04 April 2014 - 03:21 AM
md5: 9e1142218170dca9150823ca7c2f5ca8
Should be the same as stable 4, someone bumped the build number early.
The slimrom blog recommends doing a full wipe when updating to the new 4.x gapps.
Does anyone else have GPS issues with this build?
I cannot get a position at all and apps like GPS status crash on startup.
I did a full wipe (reset to factory and format of system) and installed the new gapps.
Cheers
Posted 04 April 2014 - 06:46 AM
Does anyone else have GPS issues with this build?
I cannot get a position at all and apps like GPS status crash on startup.
I did a full wipe (reset to factory and format of system) and installed the new gapps.
Cheers
There are definitely some changes that could be responsible for this. Let me look into it.
Edit: Should be fixed in the next minor release. This bug affects all of the xtXXX Razr hardware. Nothing I can do at the moment. If a fix is committed before the release, I'll do a rebuild.
Posted 05 April 2014 - 04:58 AM
There are definitely some changes that could be responsible for this. Let me look into it.
Edit: Should be fixed in the next minor release. This bug affects all of the xtXXX Razr hardware. Nothing I can do at the moment. If a fix is committed before the release, I'll do a rebuild.
Thanks for following up. Much appreciated.
0 members, 6 guests, 0 anonymous users