"Push" email not pushing - Motorola Droid Bionic

Never mind, fixed it.
Please delete post.

schmaltzy said:
Never mind, fixed it.
Please delete post.
Click to expand...
Click to collapse
Care to share? My push email stopped working recently and I don't understand what happened.
-- Sent from my DROID BIONIC on the KEXEC() enabled latest Linux kernel compiled for Key Lime Pie, with backwards compatibility.

Related

Source Code

Hey, I just saw that Motorola has released the source-code for our beloved Razr I on sourceforge.
So in theory it should be possible to compile our own androids. I was wandering whether anybody is working on this / has tried that?
http://sourceforge.net/projects/razr-i.motorola/
Thorsten
Yes, we could use that if they'd give us a non-corrupted kernel source. We already knew this.
I've had a brief attempt at this but always get build errors at make.
So far I've tried with cyanogenmod ics release and aosp but not entirely sure how to overlay the motorola repos. Most are fairly obvious and can be merged into device, external, hardware etc but don't know where to put the Motorola folder...
turl set up a device tree for the razri a while ago but it hasn't been touched since:
https://github.com/turl/android_device_motorola_smi
@Vistaus - Motorola updated did updated the source after the initial corrupt version.
Okay thanks for the info.
Maybe naive, but what about trying to contact Motorola and ask them how the build-pocess works? Or do you think they would not help?
Thorstenk said:
Okay thanks for the info.
Maybe naive, but what about trying to contact Motorola and ask them how the build-pocess works? Or do you think they would not help?
Click to expand...
Click to collapse
I've built my own kernel from source months ago but forgot to include the modules too so I had no WiFi or bluetooth lol oh well.
mattlgroff said:
I've built my own kernel from source months ago but forgot to include the modules too so I had no WiFi or bluetooth lol oh well.
Click to expand...
Click to collapse
Sounds good!
Could you explain how you did it?
cbanbury said:
I've had a brief attempt at this but always get build errors at make.
@Vistaus - Motorola updated did updated the source after the initial corrupt version.
Click to expand...
Click to collapse
That is not what developers say and I doubt developers will lie about it.
Thorstenk, the instructions for building the kernel are in the README.
The instructions for building in the WIFI/bluetooth modules are also pretty clear.
I may try another build with just these, I was running into problems when trying to build with all 37-38 folders overlayed...
Thanks man, will give it a try, unfortunately I am not very experienced ...
cbanbury said:
Thorstenk, the instructions for building the kernel are in the README.
The instructions for building in the WIFI/bluetooth modules are also pretty clear.
I may try another build with just these, I was running into problems when trying to build with all 37-38 folders overlayed...
Click to expand...
Click to collapse
cbanbury said:
Thorstenk, the instructions for building the kernel are in the README.
The instructions for building in the WIFI/bluetooth modules are also pretty clear.
I may try another build with just these, I was running into problems when trying to build with all 37-38 folders overlayed...
Click to expand...
Click to collapse
This was how I did it. Just followed the readme. Modules didn't work right though as I said.
Sent from my XT890 using Tapatalk 2
Just tried to compile the whole thing which did not work, overlaying everything is definitely not sufficient. I guess we need to do more.
After that I tried to bake a kernel, wich did not work as well, always another build error. I am working on a mac which probably makes the situation that bad, no idea.
Dont get why they do not provide a tar-ball where everything is included ...
mattlgroff said:
This was how I did it. Just followed the readme. Modules didn't work right though as I said.
Sent from my XT890 using Tapatalk 2
Click to expand...
Click to collapse
I'm on a mac also, it shouldn't be an issue if you are on a case sensitive file system n using correct java, gcc etc.
Check the version of xcode you are using as well, I had to install version 3.
Oh and post the error message. I got to the point where it was complaining about multiple copies of busybox from the overlayed folders (which is why I think we don't need all of them)
Sent from my XT890 using xda app-developers app
New WebKit Part Online and a new README -> how to compile the complete ROM IMHO.
http://sourceforge.net/projects/razr-i.motorola/files/razr-i/9.8.2I-50_SMI-26/
lord0815 said:
New WebKit Part Online and a new README -> how to compile the complete ROM IMHO.
http://sourceforge.net/projects/razr-i.motorola/files/razr-i/9.8.2I-50_SMI-26/
Click to expand...
Click to collapse
README instructions are the same as ICS, hope it works this time..
lord0815 said:
New WebKit Part Online and a new README -> how to compile the complete ROM IMHO.
http://sourceforge.net/projects/razr-i.motorola/files/razr-i/9.8.2I-50_SMI-26/
Click to expand...
Click to collapse
Yes, I bothered Motorola for this last night. Glad they sorted it so quickly.
Also don't include the recovery folder at the moment.
I had an unsuccessful build this morning so I think there's still some things missing...
Sent from my XT890 using xda app-developers app
cbanbury said:
Yes, I bothered Motorola for this last night. Glad they sorted it so quickly.
Also don't include the recovery folder at the moment.
I had an unsuccessful build this morning so I think there's still some things missing...
Sent from my XT890 using xda app-developers app
Click to expand...
Click to collapse
Keep bothering ! :good:
Theres a new tree online SMI-28 maybe with a working kernel source this time?!
http://sourceforge.net/projects/razr-i.motorola/files/razr-i/9.8.2I-50_SMI-28/
https://android.googlesource.com/pl...-linux-4.4.3/+show/refs/tags/android-4.1.2_r1
Didn't have time to look at this over the weekend but will try a build tonight. Hopefully they fixed everything this time *fingers crossed*
cbanbury said:
Didn't have time to look at this over the weekend but will try a build tonight. Hopefully they fixed everything this time *fingers crossed*
Click to expand...
Click to collapse
My hopes are in you! So very good luck!
diogo.sena said:
Keep bothering ! :good:
Click to expand...
Click to collapse
WAY OFFTOPIC:
Wow! You also come here from moto defy! Regards!
Enviado desde mi XT890 usando Tapatalk 2

[VIDEO] How To Flash Android 4.4 To Your Nexus 4

Hey everyone, me again! So with Android 4.4 out for the Nexus 4, I thought some folks might need a little help installing it, or maybe just need a visual aid to help. So I made a How To video. Hopefully it helps some people :fingers-crossed: If it does, maybe hit that "Thanks" button?
Thanks dude just what I was looking for!
Sent from my Nexus 4 using Tapatalk
Does this break anything? I am really tempted to do it!
Sent from my Nexus 7 using xda app-developers app
TheSmokingAndroid said:
Hey everyone, me again! So with Android 4.4 out for the Nexus 4, I thought some folks might need a little help installing it, or maybe just need a visual aid to help. So I made a How To video. Hopefully it helps some people :fingers-crossed: If it does, maybe hit that "Thanks" button?
Click to expand...
Click to collapse
Thanks, just what I was looking for. If I cant find a toolkit to do it with then I have no doubt with your video I can get it done. I don't want to wait! Welll done.
TheSmokingAndroid said:
Hey everyone, me again! So with Android 4.4 out for the Nexus 4, I thought some folks might need a little help installing it, or maybe just need a visual aid to help. So I made a How To video. Hopefully it helps some people :fingers-crossed: If it does, maybe hit that "Thanks" button?
Click to expand...
Click to collapse
I am getting a status 7 error. Any idea how i can fix that?
Seems to break root. I can't get back to cwm.
Sent from my AOSP on Mako using XDA Premium 4 mobile app
justibasa said:
Seems to break root. I can't get back to cwm.
Sent from my AOSP on Mako using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have an easy root fix for once you update to 4.4 if you have Mac
I modified the Root.Nexus.4.zip file for Mac on here, updated it to CWM 6.0.4.3 image, and SuperSU 1.65 image. Just unzip, and run the Root.Nexus.4 terminal shell script with the N4 in fastboot with USB connected to the Mac, I think you can use a similar script for PC and prob need USB drivers if you don't have them already. Hope this helps
I'm unable to post a link on here since I'm a newb, PM if you want the link to the zip
Thanks
Another build available here : http://www.androidauthority.com/android-4-4-kitkat-nexus-4-nexus-7-download-unofficially-313352/.
Flashed this in CWM, everything, including root is absolutely fine. (I flashed SuperSu 1.65 zip). But for the proper google experience, have to wait for the factory images.
The lockscreen widgets functionality (except for the camera widget) seems to have been removed, can anyone find that option anywhere?
Edit: Lockscreen widgets can be enabled in Settings->Security.
aravindsagar said:
Another build available here : http://www.androidauthority.com/android-4-4-kitkat-nexus-4-nexus-7-download-unofficially-313352/.
Flashed this in CWM, everything, including root is absolutely fine. (I flashed SuperSu 1.65 zip). But for the proper google experience, have to wait for the factory images.
The lockscreen widgets functionality (except for the camera widget) seems to have been removed, can anyone find that option anywhere?
Edit: Lockscreen widgets can be enabled in Settings->Security.
Click to expand...
Click to collapse
that is PA AOSP which was built and posted hours ago, also has a thread in orig android dev.
as for lockscreen widgets. they're working fine. look into settings-lockscreen
gonemad02 said:
that is PA AOSP which was built and posted hours ago, also has a thread in orig android dev.
as for lockscreen widgets. they're working fine. look into settings-lockscreen
Click to expand...
Click to collapse
Yeah, just thought I would share this link as well, since for some people, it seemed to break root, but this build worked fine for me, including root.
aravindsagar said:
Yeah, just thought I would share this link as well, since for some people, it seemed to break root, but this build worked fine for me, including root.
Click to expand...
Click to collapse
sorry it's on Settings > Security > then turn it on from there bro! oh alright. enjoy kitktat, have a break!
Do you have some manual to downgrade to 4.3? Because when i do it i lose signal and wifi..
Sent from my Nexus 4 using xda app-developers app
I might wait
Well i was going to try but guess i hold off for official release.Thank you for the videos nice work.

Knox_Out/Complete and Brutal Knox Destruction Updated/7/17/14

Hate being spied on and possible monitored,don't like your device telling you what you can do with it..Me too,so I fixed that.I have made this as Samsung Universal as possible.Some devices have different knox items/locations. I have tried to locate and remove as much as possible.If you see or know of an item I missed please post location and file/apk name.Removal of item's did not trip knox counter.Enjoy.
Does not remove knox from bootloader.
See removed item's below
View code here
ui_print("Removing Knox in System");
delete("/system/app/KNOXAgent.apk");
delete("/system/app/KNOXAgent.odex");
delete("/system/app/KLMSAgent.apk");
delete("/system/app/KLMSAgent.odex");
delete("/system/app/KnoxAttestationAgent.apk");
delete("/system/app/KnoxAttestationAgent.odex");
delete("/system/app/KNOXStore.apk");
delete("/system/app/KNOXStore.odex");
delete("/system/app/KnoxSetupWizardClient.apk");
delete("/system/app/KnoxSetupWizardClient.odex");
delete("/system/app/KNOXStub.apk");
delete("/system/app/KNOXStub.odex");
delete("/system/app/KLMSAgent.apk");
delete("/system/app/KLMSAgent.odex");
delete("/system/app/ContainerEventsRelayManager.apk");
delete("/system/app/ContainerEventsRelayManager.odex");
delete("/system/app/ContainerAgent.apk");
delete("/system/app/ContainerAgent.odex");
delete("/system/app/KnoxVpnServices.apk");
delete("/system/app/KnoxVpnServices.odex");
delete("/system/app/SecurityManagerService.apk");
delete("/system/app/SecurityProviderSEC.apk")
delete("/system/containers/framework/KNOXModeSwitcher.apk");
delete("/system/containers/framework/sec_container_1.zzzKnoxLauncher.apk");
delete("/system/priv-app/KNOXAgent.apk");
delete("/system/priv-app/KNOXAgent.odex");
delete("/system/priv-app/KLMSAgent.apk");
delete("/system/priv-app/KLMSAgent.odex");
delete("/system/priv-app/KnoxAttestationAgent.apk");
delete("/system/priv-app/KnoxAttestationAgent.odex");
delete("/system/priv-app/KNOXStore.apk");
delete("/system/priv-app/KNOXStore.odex");
delete("/system/priv-app/KnoxSetupWizardClient.apk");
delete("/system/priv-app/KnoxSetupWizardClient.odex");
delete("/system/priv-app/KNOXStub.apk");
delete("/system/priv-app/KNOXStub.odex");
delete("/system/priv-app/KLMSAgent.apk");
delete("/system/priv-app/KLMSAgent.odex");
delete("/system/priv-app/containereventsrelaymanager.apk");
delete("/system/priv-app/containereventsrelaymanager.odex");
delete("/system/priv-app/ContainerAgent.apk");
delete("/system/priv-app/ContainerAgent.odex");
delete("/system/priv-app/KnoxVpnServices.apk");
delete("/system/priv-app/KnoxVpnServices.odex");
delete("/system/priv-app/SecurityManagerService.apk");
delete("/system/priv-app/SecurityProviderSEC.apk")
delete("/system/etc/secure_storage/com.sec.knox.store");
delete("/system/etc/secure_storage/com.sec.knox.seandroid");
ui_print("Removing Knox in Libs");
delete("/system/lib/libknoxdrawglfunction.so");
delete("/system/lib/libknox_encryption.so");
ui_print("Removing Knox in Data");
delete("/data/data/com.sec.knox.containeragent");
delete("/data/data/com.sec.eventsmanager");
delete("/data/data/com.sec.enterprise.knox.attestation");
delete("/data/data/com.sec.knox.app.container");
delete("/data/data/com.sec.knox.seandroid");
delete("/data/data/com.sec.knox.store");
delete("/data/data/com.samsung.klmsagent");
delete("/data/data/com.samsung.knox.rcp.components");
delete("/data/data/com.sec.enterprise.knox.cloudmdm.smdms");
delete("/data/data/com.sec.knox.bridge");
delete("/data/data/com.sec.knox.knoxsetupwizardclient");
delete("/data/data/com.sec.knox.setupwizardstub");
ui_print("Knox Removed");
Changelog: 7/7/14
Updated uninstaller
7-17/14: Added removal of annoying security policy updater
i used on my i537 only thing left was
(com.sec.knox.eventsmanager) /system/app/containereventsrelaymanager.apk and /system/app/containereventsrelaymanager.odex
(com.sec.knox.containeragent) /system/app/ContainerAgent.apk and /system/app/ContainerAgent.odex
(com.sec.enterprise.app.knoxvpn) /system/app/KnoxVpnServices.apk and /system/app/KnoxVpnServices.odex
(com.sec.knox.app.container) /system/containers/framework/KNOXModeSwitcher.apk
(com.sec.android.app.knoxlauncher) /system/containers/framework/sec_container_1.zzzknoxlauncher.apk
will edit if i find more
Thank you very much. I will add ASAP.
blaz1nr said:
Thank you very much. I will add ASAP.
Click to expand...
Click to collapse
how do I use this ie install it please
Flash in recovery
updated
can this be flashed through stock recovery or do i need to have safe strap running?
Safestrap
blaz1nr said:
Safestrap
Click to expand...
Click to collapse
hello my gf is flashing it on her phone and she is still getting the security policy update message does this remove it?
wolf45801 said:
hello my gf is flashing it on her phone and she is still getting the security policy update message does this remove it?
Click to expand...
Click to collapse
I uploaded wrong version. I have one that stops that. will update soon.
Delete SecurityProviderSEC.apk from the script. It's an Android app. You NEED this if you want to use the Android Keychain.
You want a more KNOX and Sammy's root protection-free /system partition? Add this to script:
/system/bin/tima_dump_log
/system/bin/containersetup
/system/tima_measurement_info
/system/preloadedkiosk/
/system/preloadedsso/
/system/app/Bridge.apk
/system/app/EdmSimPinService.apk
/system/app/EdmSysScopeService.apk
/system/app/EdmVpnServices.apk
/system/app/KnoxMigrationAgent.apk
/system/app/KnoxSetupWizardClient.apk
/system/app/KnoxSetupWizardStub.apk
/system/app/RCPComponents.apk
/system/app/MDMApp.apk
/system/app/UniversalMDMClient.apk
/system/app/SysScope.apk
/system/priv-app/SPDClient.apk
/system/framework/com.policydm.features.jar
/system/framework/ContainerProxies.jar
/system/app/Bridge.odex
/system/app/EdmSimPinService.odex
/system/app/EdmSysScopeService.odex
/system/app/EdmVpnServices.odex
/system/app/KnoxMigrationAgent.odex
/system/app/KnoxSetupWizardClient.odex
/system/app/KnoxSetupWizardStub.odex
/system/app/RCPComponents.odex
/system/app/MDMApp.odex
/system/app/UniversalMDMClient.odex
/system/priv-app/SPDClient.odex
/system/framework/com.policydm.features.odex
/system/framework/ContainerProxies.odex
/system/lib/libcordon.so
/system/lib/libmealy.so
/system/lib/libspdkeygen.so
/system/lib/libtyrfingr.so
/system/lib/libtwifingr.so
/system/etc/permissions/com.policydm.feature.xml
/system/etc/permissions/mycontainerbadge.png
/system/etc/permissions/sec_mdm.xml
/system/etc/secure_storage/com.sec.knox.seandroid/
/system/etc/secure_storage/com.sec.knox.store/
Also, delete this lines from build.prop:
ro.config.knox
ro.config.tima
ro.config.timaversion
ro.security.mdpp.ux
security.mdpp
ro.security.mdpp.ver
ro.security.mdpp.release
security.mdpp.result
If you also want to save some of your privacy without breaking any functionality, delete this:
/system/app/TcpdumpService.apk
/system/app/SilentLog.apk
very very fine exelent ....thanks
this has only effect on tw based roms?
Success
Tried it on i537 and worked. After install and reboot it showed a screen "Android is Upgrading, optimizing apps x of 133". After that, checked the phone and it appears that it's working properly. Thanks!!
pinyata said:
can this be flashed through stock recovery or do i need to have safe strap running?
Click to expand...
Click to collapse
blaz1nr said:
Safestrap
Click to expand...
Click to collapse
Sorry guys, but what this mean?
I have stock 4.4.2 on S4 LTE 9506 Europe.
No idea what Safestrap is
So, can I simply run the script or I need to do something else first?
Thanks
J
blaz1nr said:
I uploaded wrong version. I have one that stops that. will update soon.
Click to expand...
Click to collapse
Was the updated version posted? Im also receiving these messages
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
Well I updated the script with the changes/additions iJo09 posted with the exception of the build.prop since I've modified mine beyond what iJo09 mentioned and doubt many other people would want the changes. It flashed alright and my phone booted, but I haven't tested beyond that yet since it's late.
-edit-
So far my phone's working as expected with no issues or errors.
Kyuta Syuko said:
Well I updated the script with the changes/additions iJo09 posted with the exception of the build.prop since I've modified mine beyond what iJo09 mentioned and doubt many other people would want the changes. It flashed alright and my phone booted, but I haven't tested beyond that yet since it's late.
-edit-
So far my phone's working as expected with no issues or errors.
Click to expand...
Click to collapse
Has anyone tested this version? Results?
Does it rid of the annoying security update messages?
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
pvchip3 said:
Has anyone tested this version? Results?
Does it rid of the annoying security update messages?
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
Click to expand...
Click to collapse
I haven't received any security update messages and as I stated in my edit no issues so far phone's running as expected.
Kyuta Syuko said:
I haven't received any security update messages and as I stated in my edit no issues so far phone's running as expected.
Click to expand...
Click to collapse
Im still receiving the security updates after flashing your zip...any suggestions?
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app

[ADT1][ROM]Stock molly images - Unbricking

Introduction:
This is a restore zip for restoring/debricking a molly device (ADT-1).
The contents are as close to stock as possible, and is intended to fix broken otas.
Click to expand...
Click to collapse
File List:
update-molly-Stock-LPV79-1.zip
Click to expand...
Click to collapse
FAQ:
Will this fix my <non molly device>?
No, this rom is only for mollys, it will brick any other device.
Will OTAs work after flashing this?
Yes, that is the purpose of this
Do I need to be on a certain bootloader to use this?
No, it includes the original bootloader.
Do I need a custom recovery to flash this?
Yes, the stock recovery will not accept update zips that are not signed by google
Is this rooted?
No, the stock rom is not rooted, neither is this
My device won't finish booting after flashing.
If you were not originally on the same rom, you may need to do a factory reset to finish the process. Android does not like rom downgrades without a factory reset
Click to expand...
Click to collapse
Changelog:
Nov 3, 2014: Initial Page
Click to expand...
Click to collapse
2char
I made a gallery of it because I felt like it: Update - Imgur
Awesome! Thanks! I needed a way to restore my OTA abilities after rooting and doing some testing for someone. Did you make these yourself? And how? If you don't mind me asking. I didn't think dd would work without root.
death2all110 said:
Awesome! Thanks! I needed a way to restore my OTA abilities after rooting and doing some testing for someone. Did you make these yourself? And how? If you don't mind me asking. I didn't think dd would work without root.
Click to expand...
Click to collapse
All custom recoveries have root by default, my ADT1 isnt rooted, I did all my work though CWM.
TheManii said:
All custom recoveries have root by default, my ADT1 isnt rooted, I did all my work though CWM.
Click to expand...
Click to collapse
Duh. Didn't think of that... Haha. Thanks!
Could someone who has updated to LPX13D please post a system dump? Im needing it for an OUYA port that im working on. Thanks
It's already been posted here:
http://forum.xda-developers.com/showpost.php?p=56186872&postcount=69
death2all110 said:
It's already been posted here:
http://forum.xda-developers.com/showpost.php?p=56186872&postcount=69
Click to expand...
Click to collapse
Thanks, never would have found it there.
TheManii said:
2char
Click to expand...
Click to collapse
Thanks! Do you have to have a USB keyboard in order to move around in CWM on the ADT-1?
ScubaXsays said:
Thanks! Do you have to have a USB keyboard in order to move around in CWM on the ADT-1?
Click to expand...
Click to collapse
Yes a USB keyboard is needed to move around CWM on the ADT-1
death2all110 said:
Yes a USB keyboard is needed to move around CWM on the ADT-1
Click to expand...
Click to collapse
Thanks so much for the quick response, you're the best.
ScubaXsays said:
Thanks so much for the quick response, you're the best.
Click to expand...
Click to collapse
No problem. I had the same problem initially
death2all110 said:
Yes a USB keyboard is needed to move around CWM on the ADT-1
Click to expand...
Click to collapse
ScubaXsays said:
Thanks so much for the quick response, you're the best.
Click to expand...
Click to collapse
Yes you need a usb keyboard to use CWM currently, there may be an update in the future to enable the dev button on the back to select in cwm like it does in fastboot. Until if/when that happens you either need a keyboard or to do everything manually via adb.
I don't have a keyboard however, I did all my work/testing with only adb.
TheManii said:
Yes you need a usb keyboard to use CWM currently, there may be an update in the future to enable the dev button on the back to select in cwm like it does in fastboot. Until if/when that happens you either need a keyboard or to do everything manually via adb.
I don't have a keyboard however, I did all my work/testing with only adb.
Click to expand...
Click to collapse
Thanks for the articulate follow-up. I started to do things manually via ADB. :good:
anyone can post a complete lpx13D CWM backup , stock recovery or at least system.img
I've messed up my ADT1 and it can't seem to take the image I've found yet
@TheManii Are there any custom roms or anything like that for the ADT-1? I just got one in the mail from I assume google. I'm ready to begin , but I don't honestly know what people are interested in seeing on this device I have a madcatz mojo using all the adt-1 binaries except audio running cm-12 and android tv from this device. So if anyone is interested in that let me know please.
Unjustified Dev said:
@TheManii Are there any custom roms or anything like that for the ADT-1? I just got one in the mail from I assume google. I'm ready to begin , but I don't honestly know what people are interested in seeing on this device I have a madcatz mojo using all the adt-1 binaries except audio running cm-12 and android tv from this device. So if anyone is interested in that let me know please.
Click to expand...
Click to collapse
Hello UD,
There isn't any custom roms for the ADT-1 (So yours would be the first)
I for one would love to see a more recent build than the last OTA (LPX13D - OCT 29th) There have been rumors that we'd get the final Android Lollipop but nothing has surfaced.
How much work is involved in rolling an AOSP+ADT-1 Binaries+Android TV dependencies?
Cheers Rob.
halfluck said:
Hello UD,
There isn't any custom roms for the ADT-1 (So yours would be the first)
I for one would love to see a more recent build than the last OTA (LPX13D - OCT 29th) There have been rumors that we'd get the final Android Lollipop but nothing has surfaced.
How much work is involved in rolling an AOSP+ADT-1 Binaries+Android TV dependencies?
Cheers Rob.
Click to expand...
Click to collapse
It's possible https://www.youtube.com/watch?v=Og-GDeRhJno but I could not get all the apps correctly working the main one being playstore , but I will try again look at the android build number and build date. I basically made a google apps package based on the adt-1 this is before I had one so possibly now I can get us an aosp 5.0.2 base working the Mojo in terms of hardware is similar to the adt-1 and for me to boot 5.0 on the mojo I needed adt-1 updated tegra 4 binaries so this shouldn't be hard at all once I work out the playstore issues.
Unjustified Dev said:
It's possible https://www.youtube.com/watch?v=Og-GDeRhJno but I could not get all the apps correctly working the main one being playstore , but I will try again look at the android build number and build date. I basically made a google apps package based on the adt-1 this is before I had one so possibly now I can get us an aosp 5.0.2 base working the Mojo in terms of hardware is similar to the adt-1 and for me to boot 5.0 on the mojo I needed adt-1 updated tegra 4 binaries so this shouldn't be hard at all once I work out the playstore issues.
Click to expand...
Click to collapse
Wow that is really impressive work, The current build on the ADT-1 is flaky at best for me, i'd love to see how a more recent build performs and if it prevents me from having to do a daily reboot.
Cheers Rob.
@Unjustified Dev just got mine on Tuesday. are you thinking releasing sources on your team github. i saw that a device and kernel repository was created but they are empty.
PS: nice to talk to you again been a while.

Merging Sparsechunks

I really want to fix the HDR camera bug, and I think I know how, but I need to merge the sparsechunks contained in the most recent 5.1 image. I can't seem to figure out how to do that. Can anyone enlighten me?
EDIT: Never mind. I figured it out.
TheSt33v said:
I really want to fix the HDR camera bug, and I think I know how, but I need to merge the sparsechunks contained in the most recent 5.1 image. I can't seem to figure out how to do that. Can anyone enlighten me?
EDIT: Never mind. I figured it out.
Click to expand...
Click to collapse
May I ask how you managed to do it? I need to do exactly the same thing, but for my Moto 360.
TheSt33v said:
I really want to fix the HDR camera bug, and I think I know how, but I need to merge the sparsechunks contained in the most recent 5.1 image. I can't seem to figure out how to do that. Can anyone enlighten me?
EDIT: Never mind. I figured it out.
Click to expand...
Click to collapse
What bug?
Sent from my DROID RAZR M using XDA Free mobile app
fritzhy said:
May I ask how you managed to do it? I need to do exactly the same thing, but for my Moto 360.
Click to expand...
Click to collapse
I merged them using the tool in the OP of this thread, and I removed the Motorola header and footer using the instructions in JulesJam's post: http://forum.xda-developers.com/showthread.php?t=2749797&page=5
Removing the header and footer is necessary if you want to mount the image in Linux as ext4 and modify it. Of course, that's assuming Motorola puts the header and footer into Android Wear images. I'm not entirely sure that they do.
mrkhigh said:
What bug?
Sent from my DROID RAZR M using XDA Free mobile app
Click to expand...
Click to collapse
Back in the Mofo days, there was an issue where camera apps would force close if you tried to take a picture with HDR enabled on 5.1. Setting SElinux to permissive fixed it.
TheSt33v said:
Back in the Mofo days, there was an issue where camera apps would force close if you tried to take a picture with HDR enabled on 5.1. Setting SElinux to permissive fixed it.
Click to expand...
Click to collapse
Oh, I thought you figured out how to merge the sparsechunks. Anyway, right after asking you, I found a Windows tool to do it: http://forum.xda-developers.com/showthread.php?p=50656564
I had to modify the batch scripts a bit, but it worked. So if anyone else comes here for that, there you go!
TheSt33v said:
I really want to fix the HDR camera bug, and I think I know how, but I need to merge the sparsechunks contained in the most recent 5.1 image. I can't seem to figure out how to do that. Can anyone enlighten me?
EDIT: Never mind. I figured it out.
Click to expand...
Click to collapse
There's no HDR bug on these phones. I use HDR every day for a year, since I got two Quark phones on both stock rooted ROM and custom ROM.
If you had a problem on Mofo that has nothing to do with this phone, but the fake root or something with Mofo.
ChazzMatt said:
There's no HDR bug.
Click to expand...
Click to collapse
As I mentioned previously, this old post was referring to the fact that camera apps force closed on 5.1 based roms that were flashed using mofo after taking a picture with HDR enabled. This issue was solved by myself and everyone else who made mofo-ready roms by setting SElinux to permissive. It is not relevant, and has not presented, on phones with with unlocked bootloaders. And yes, I realize that there never was anything wrong with the functioning of HDR, but everyone else was referring to it as the "HDR bug," so I kept this term to avoid confusion.
TheSt33v said:
As I mentioned previously, this old post was referring to the fact that camera apps force closed on 5.1 based roms that were flashed using mofo after taking a picture with HDR enabled. This issue was solved by myself and everyone else who made mofo-ready roms by setting SElinux to permissive. It is not relevant, and has not presented, on phones with with unlocked bootloaders. And yes, I realize that there never was anything wrong with the functioning of HDR, but everyone else was referring to it as the "HDR bug," so I kept this term to avoid confusion.
Click to expand...
Click to collapse
Sorry, I didn't see it was an old post. Didn't realize someone had resurrected it.
I'm still trying to figure out why Motorola went with sparse chunks, instead of traditional deltas.
Sent from my DROID Turbo via Tapatalk. Now with that cyanogenmod goodness.

Categories

Resources