Hi,
Im looking for the Samsung Weatherbug Clock Widget from stock. Also I seen the Feeds and Updates APK which I installed but the header is pink is there a way to change that color please
Thanks
babyjake said:
Hi,
Im looking for the Samsung Weatherbug Clock Widget from stock. Also I seen the Feeds and Updates APK which I installed but the header is pink is there a way to change that color please
Thanks
Click to expand...
Click to collapse
that should be the right clock... as for the feeds and updates widget the one I uploaded is, according to Nitroglycerine (whos Eclipse GB rom I got it from), the SGS2 one so it should look different (not pink) as I don't know how to change the color without using a theme
anoninja118 said:
that should be the right clock... as for the feeds and updates widget the one I uploaded is, according to Nitroglycerine (whos Eclipse GB rom I got it from), the SGS2 one so it should look different (not pink) as I don't know how to change the color without using a theme
Click to expand...
Click to collapse
wont install thanks anyway
babyjake said:
wont install thanks anyway
Click to expand...
Click to collapse
did you try just putting them in /system/app and rebooting phone? i don't think they're supposed to be installed
anoninja118 said:
did you try just putting them in /system/app and rebooting phone? i don't think they're supposed to be installed
Click to expand...
Click to collapse
Yes tried that too no luck
Didn't work for me either.
~John
I know there's been compatibility issues with stock widgets on the newer roms, most likely due to lots of framework changes in the new builds... you could try posting in the rom thread though, maybe somebody got it running and could provide it as I usually don't use stock samsung widgets
anoninja118 said:
I know there's been compatibility issues with stock widgets on the newer roms, most likely due to lots of framework changes in the new builds... you could try posting in the rom thread though, maybe somebody got it running and could provide it as I usually don't use stock samsung widgets
Click to expand...
Click to collapse
Ok didnt know there was really I was going to say lol
Would be a so kind to proud the direct link
babyjake said:
Ok didnt know there was really I was going to say lol
Would be a so kind to proud the direct link
Click to expand...
Click to collapse
what rom are you using?
blazing through on my 4G Droid Charge
granted this thread is a bit old .. sorry but im running tsm inifinity with repacked kernel and this .apk will not install nor will in run when moved to system/app/folder
valve timing said:
granted this thread is a bit old .. sorry but im running tsm inifinity with repacked kernel and this .apk will not install nor will in run when moved to system/app/folder
Click to expand...
Click to collapse
I may be way off here but if i am following things right here [im kind of tired]
widgets for you are in imnuts post here http://rootzwiki.com/topic/11175-rominfinityrom/page__view__findpost__p__273678
valve timing said:
granted this thread is a bit old .. sorry but im running tsm inifinity with repacked kernel and this .apk will not install nor will in run when moved to system/app/folder
Click to expand...
Click to collapse
if the ones from the above link don't work I suspect it may be because they are touchwiz widgets and Infinity is a heavily modded touchwiz-based rom, something new probably borked them
edit: also the widgets I linked to earlier were pulled from a froyo rom, so may not work at all on a GB rom no matter what you do
Hi guys i have idea for new rom based on cyanogenmod 9 with lg optimus ui 3.0 but not have skills for make my own rom.
http://forum.xda-developers.com/showthread.php?t=1685484
for lockscreen use this
http://forum.xda-developers.com/showthread.php?t=1585684
http://forum.xda-developers.com/showthread.php?t=1597928
for cm9 theme use this
http://forum.xda-developers.com/showthread.php?t=1688250
other resources
http://forum.xda-developers.com/showthread.php?t=1635301 icon, wallpaper etc
http://forum.xda-developers.com/showthread.php?t=1692222 bootanimation
http://forum.xda-developers.com/showthread.php?t=1515983 richnote apk
Thanks for any dev or peoples help me.
great idea
i wish i could help ..but im a noob too with regards to rom development
i can give suggestions though
try PM'ing any AOSP/cm9/MIUI/AOKP devs ..they might reply you
Also T-Macgnolia he got some great understanding with regards to rom development too
ok waiting for any help with this rom
I mean YOU know you can just get the latest OPENSENSATION BUILD, then change the CM9 theme to that, install LG HOME and be on your way. Devs have already provided us with BRILLIANT CM9 and we dont need them to waste time on things like this. If you want it, you can easily install a couple of apks yourself. this is all it is.
Anyhow no hate intended, just download the theme apk install it, follow direction in lg forum and install it and be on your merry way. This is way to simple for any devs to waste time on. Be glad you have CM9 and will have CM10 while HTC is figuring out how to beat Samsung.
akbisw said:
I mean YOU know you can just get the latest OPENSENSATION BUILD, then change the CM9 theme to that, install LG HOME and be on your way. Devs have already provided us with BRILLIANT CM9 and we dont need them to waste time on things like this. If you want it, you can easily install a couple of apks yourself. this is all it is.
Anyhow no hate intended, just download the theme apk install it, follow direction in lg forum and install it and be on your merry way. This is way to simple for any devs to waste time on. Be glad you have CM9 and will have CM10 while HTC is figuring out how to beat Samsung.
Click to expand...
Click to collapse
i already try but example for lockscreen i not have linux and cant use diff/patch. I want the theme is default, cant edit framework apk for make this for default theme. And i not have idea for remove a voice from menu of lg launcher (force close). And for all this reason i need dev
bump a pmed a dev and this say help me with this but if other person want make the personally version is accepted.
In that case can't wait to try myself
Sent from my HTC Sensation using Tapatalk 2
The launcher can be added to system/app. For the lockscreen, there must be a way to merge the updater.script and the binary to the existing ones, i think it should be done with META-INF also. And there would be a possibility to replace system theme with the theme you requested.
Wait for the first release
Stumbled upon this recent discovery and just wanted to share the wealth! I extracted the MMS.apk from AOKP build 4 to see if it would work with Touchwiz and it does! Quick reply in the notifications window and all. Install it like any other system app; you'll need to be rooted and have a root explorer:
1. Download MMS.apk from below
2. Move to SD Card
3. ***Backup Touchwiz Messaging App "SecMMS.apk"*** by renaming the file to "SecMMS.apk.bak"
4. Move the downloaded MMS.apk to system/app
5. Fix Permissions to rw-r-r
6. Reboot
7. Hit your dougie or other victory dance of your choosing
I've attached screenshots to show that this is indeed working. The ROM I tried it on is incubus' JellyWiz RLS7 but it should work on any rom. I'm not responsible if you brick your phone or mess up your messaging app but it's pretty straight forward! If you're scared, go to church... or just nandroid :silly:
This is my first "helpful" post so if it's in the wrong section or if I've done something else that may cause WWIII than just let me know and I will fix it. I didn't see any other threads like this one though!
Edit: Didn't test thoroughly enough and as other users have pointed out, it FC's when trying to send or receive a picture message. Still, for someone who likes the quick reply, emoji, look and feel of AOSP, I think that it's a small price to pay. Also, this will ONLY work on Jelly Bean Roms!
Thanks
Randy Savage said:
Stumbled upon this recent discovery and just wanted to share the wealth! I extracted the MMS.apk from AOKP build 4 to see if it would work with Touchwiz and it does! Quick reply in the notifications window and all. Install it like any other system app; you'll need to be rooted and have a root explorer:
1. Download MMS.apk from below
2. Move to SD Card
3. ***Backup Touchwiz Messaging App "SecMMS.apk"*** by renaming the file to "SecMMS.apk.bak"
4. Move the downloaded MMS.apk to system/app
5. Fix Permissions to rw-r-r
6. Reboot
7. Hit your dougie or other victory dance of your choosing
I've attached screenshots to show that this is indeed working. The ROM I tried it on is incubus' JellyWiz RLS7 but it should work on any rom. I'm not responsible if you brick your phone or mess up your messaging app but it's pretty straight forward! If you're scared, go to church... or just nandroid :silly:
This is my first "helpful" post so if it's in the wrong section or if I've done something else that may cause WWIII than just let me know and I will fix it. I didn't see any other threads like this one though!
Click to expand...
Click to collapse
Where you able to send a pic message
Edit: FC when trying to send a mms
You should probably add that this will only work on jellybean based roms.
Edit: i'd like to point out that this isn't the most recent version of CM's messaging app. It's missing a lot of the things that they added.
Randy Savage said:
Stumbled upon this recent discovery and just wanted to share the wealth! I extracted the MMS.apk from AOKP build 4 to see if it would work with Touchwiz and it does! Quick reply in the notifications window and all. Install it like any other system app; you'll need to be rooted and have a root explorer:
1. Download MMS.apk from below
2. Move to SD Card
3. ***Backup Touchwiz Messaging App "SecMMS.apk"*** by renaming the file to "SecMMS.apk.bak"
4. Move the downloaded MMS.apk to system/app
5. Fix Permissions to rw-r-r
6. Reboot
7. Hit your dougie or other victory dance of your choosing
I've attached screenshots to show that this is indeed working. The ROM I tried it on is incubus' JellyWiz RLS7 but it should work on any rom. I'm not responsible if you brick your phone or mess up your messaging app but it's pretty straight forward! If you're scared, go to church... or just nandroid :silly:
This is my first "helpful" post so if it's in the wrong section or if I've done something else that may cause WWIII than just let me know and I will fix it. I didn't see any other threads like this one though!
Click to expand...
Click to collapse
it crashes when you send or recieve mms
Would love to have this though! Its a start...
I've been trying to get this to work since the day I bought the phone. I was using (and still am on my work phone) an inverted AOSP MMS.apk that I just absolutely dig. I was sad when it didn't work on Touchwiz ROMS.
I dug a bit deeper. I got to where you guys were at, I managed to get it to install on a JB TW ROM but it crashed on MMS, just as you all are experiencing. I dug deeper.
I next tried a logcat to see if I could sniff out the issue. Nothing was glaringly obvious as being the issue. I even went so far as to Pastebin it for a well known dev on here, and he pointed it to it being the Gallery as being the issue. Since it's an AOSP app, it was probably looking for an AOSP Gallery. So I tried that. I replaced the TW Gallery with the AOSP Gallery. Still, nothing. The dev hasn't had time to really help me out since, he's a pretty busy guy and isn't even supporting the device, he was more helping me since we're more friends than anything else.
I'm going to see if I can get ahold of another dev on here and see if he can spare some time to help. Problem is, he doesn't have this phone, but I do believe he has a Galaxy Note, or the Skyrocket. I PM'd a few devs supporting our phone with ROM's to ask if they could help, and I didn't receive a response. If anyone knows anyone who can help, I'd be glad to pass along what I have.
I would REALLY like to get this working on TW ROM's. I'd settle for the old school AOSP inverted one I'm using, but the CM/AOKP one is probably pretty similar.
I managed to get an ICS, AKA non Quick Reply version, working with TW builds. Should work with any ICS/JB builds. The file is here: http://forum.xda-developers.com/showthread.php?t=1921429
Can someone tell me wat im doing wrong or wat exactly im missing...i followed the instructions and the app itself is working but it's not popping up
Sent from my SGH-T999 using xda premium
It's not threading? Any help?
Sent from my GT-I9300
Op should really take the time to update his apps lol.
Sent from my Galaxy SIII
mexiken said:
I managed to get an ICS, AKA non Quick Reply version, working with TW builds. Should work with any ICS/JB builds[/url]
Click to expand...
Click to collapse
Thanks. Seems to work fine on stock/rooted TW. No QuickReply, but I think QuickMessage doesn't woked that well in CM10 anyway. I use SMS Popup from the Market.
Sent from my GT-P7510 using Tapatalk 2
can it be done the other way around?? i mean, can the stock secMms.apk be installed on AOKP roms??? i tried it on revolt rom and it didnt work!
dudders007 said:
can it be done the other way around?? i mean, can the stock secMms.apk be installed on AOKP roms??? i tried it on revolt rom and it didnt work!
Click to expand...
Click to collapse
Nooooo.... You need the tw framework for it to work. No tw apps will work on aosp or aokp.
[email protected]'$ [email protected]@XY
This might be a noob question, but I want to know that since our bootloader is locked, how we are able to port Cynaogenmod and other ROMs like Paranoid Android to Atrix 2? Recently official AOSP ROM was released for Moto RAZR which also has a locked bootloader. So why we can't have an official CM for Atrix 2?
What difference is there between a CM port and an official CM for unlocked bootloader device ?
Just some noob questions which came in my mind. Please clarify. Sorry for a silly question.
androiddecoded said:
This might be a noob question, but I want to know that since our bootloader is locked, how we are able to port Cynaogenmod and other ROMs like Paranoid Android to Atrix 2? Recently official AOSP ROM was released for Moto RAZR which also has a locked bootloader. So why we can't have an official CM for Atrix 2?
What difference is there between a CM port and an official CM for unlocked bootloader device ?
Just some noob questions which came in my mind. Please clarify. Sorry for a silly question.
Click to expand...
Click to collapse
It all surrounds around the kernel. Unlocked bootloader devices can run "custom" compiled kernels, and CM and the other "custom" non-stock based roms all have their own kernels too.
The reason that we can run "unofficial" versions is because your devs (me included), have to compile the ROM around the "stock" kernel, so that it can be installed right along side the stock kernel, and run without issue. All of the AOSPA, and PA, and such are the same exact way.
Anything that can be done on the Razr can pretty much be done on this phone. The thing is that your dev team is much smaller on the A2 as it was not a very popular device, so it takes longer if ever to get something since the devs make the choice to work on a specific ROM or not.
Also the "official" CM compiles are done by the cyanogen mod team themselves and they do all the coding and have an auto compile server to get the versions out to the public, so again it is up to the developers there to decide which phones they want to support. Again though if you look all the "official" build devices ALL have unlocked bootloaders in some form or fashion, so that the "custom" compiled kernel will install with out issue.
Actually, it looks like Hashcode and dhacker recently got the RAZR included in the "official" CM nightlies... http://wiki.cyanogenmod.org/w/Spyder_Info
So, if something stable enough is worked out for the A2 (i.e. kexec), then we could possibly see an "official" edison of some sort at some point... in theory.
For now, I'll be happy with stable "unofficial" builds..
alteredlikeness said:
Actually, it looks like Hashcode and dhacker recently got the RAZR included in the "official" CM nightlies... http://wiki.cyanogenmod.org/w/Spyder_Info
So, if something stable enough is worked out for the A2 (i.e. kexec), then we could possibly see an "official" edison of some sort at some point... in theory.
For now, I'll be happy with stable "unofficial" builds..
Click to expand...
Click to collapse
That is still not considered "official" cyanogen builds.....
If it is not listed here, then it is not 100% official:
http://get.cm
It is lets say.... an unofficial, "official" build, though. LOL
jimbridgman said:
That is still not considered "official" cyanogen builds.....
If it is not listed here, then it is not 100% official:
http://get.cm
It is lets say.... an unofficial, "official" build, though. LOL
Click to expand...
Click to collapse
Um, Jim.. spyder and umts_spyder are both listed there
Still, I think Hashcode and dhacker have the status/connections to get it dubbed "official"..
alteredlikeness said:
Um, Jim.. spyder and umts_spyder are both listed there
Still, I think Hashcode and dhacker have the status/connections to get it dubbed "official"..
Click to expand...
Click to collapse
so do I.... Don't forget who is on the cm coding team....
I did some looking internally at CM and found that these are semi-official, right now, with a big but, the kexec I am told is what is keeping it with the semi status...
They are looking into changing that for kexec based compiles, so.... Hopefully, that happens.
jimbridgman said:
It all surrounds around the kernel. Unlocked bootloader devices can run "custom" compiled kernels, and CM and the other "custom" non-stock based roms all have their own kernels too.
The reason that we can run "unofficial" versions is because your devs (me included), have to compile the ROM around the "stock" kernel, so that it can be installed right along side the stock kernel, and run without issue. All of the AOSPA, and PA, and such are the same exact way.
Anything that can be done on the Razr can pretty much be done on this phone. The thing is that your dev team is much smaller on the A2 as it was not a very popular device, so it takes longer if ever to get something since the devs make the choice to work on a specific ROM or not.
Also the "official" CM compiles are done by the cyanogen mod team themselves and they do all the coding and have an auto compile server to get the versions out to the public, so again it is up to the developers there to decide which phones they want to support. Again though if you look all the "official" build devices ALL have unlocked bootloaders in some form or fashion, so that the "custom" compiled kernel will install with out issue.
Click to expand...
Click to collapse
Thanks for the reply. I wish I could also develop something for Atrix 2. But I am not familiar with the development. How is it done? and where do you test it and all other things? Is there some starting tutorial there for it? Or maybe some place from where you all guys started learning the developement?
androiddecoded said:
Thanks for the reply. I wish I could also develop something for Atrix 2. But I am not familiar with the development. How is it done? and where do you test it and all other things? Is there some starting tutorial there for it? Or maybe some place from where you all guys started learning the developement?
Click to expand...
Click to collapse
I would start with my thread for all the tools you need.
http://forum.xda-developers.com/showthread.php?t=1404442
Then you can start with taking a shot at a stock based ROM, since they really are the easiest place to start. You will need some form of linux ubuntu is really the most supported distro for android dev work, so that is a good start. This can be a VM to start out with, you can use a free VM tool like virtual box, if you want to just to give it a try, but I will tell you a dual boot works much better, and I will be honest I have a machine that just uses ubuntu and does not run windows at all. I have a wine install for things like netflix and such, but other than that.... no windows. That is just me though.
The key is the android kitchen... and that ONLY runs on linux, that where you build your ROM at. There are guys like rdavisct, who do it on windows, but even he would tell you how much of a PIA it was for him, and he did eventually go to ubuntu with my help.
After that you can start to look at compiling roms like CM, aospa, and the like.
jimbridgman said:
I would start with my thread for all the tools you need.
http://forum.xda-developers.com/showthread.php?t=1404442
Then you can start with taking a shot at a stock based ROM, since they really are the easiest place to start. You will need some form of linux ubuntu is really the most supported distro for android dev work, so that is a good start. This can be a VM to start out with, you can use a free VM tool like virtual box, if you want to just to give it a try, but I will tell you a dual boot works much better, and I will be honest I have a machine that just uses ubuntu and does not run windows at all. I have a wine install for things like netflix and such, but other than that.... no windows. That is just me though.
The key is the android kitchen... and that ONLY runs on linux, that where you build your ROM at. There are guys like rdavisct, who do it on windows, but even he would tell you how much of a PIA it was for him, and he did eventually go to ubuntu with my help.
After that you can start to look at compiling roms like CM, aospa, and the like.
Click to expand...
Click to collapse
I don't want to be the antagonist here , but I did everything in Windows until I started my attempts at building from source.
Dsixda's kitchen works fine in Windows with Cygwin. I started off building pseudo-ROMs (or rebuilding the stock ROMs) with the kitchen, and then I eventually just used 7-zip and other tools and did it manually.
I currently use Ubuntu 12.04 64-bit in Virtual Box in Windows on my laptop to compile from source. But I did just install 12.10 fully on my old PC... 32-bit unfortunately.. I need to upgrade that comp, or find a work-around to build in 32-bit.. Anyhow, it runs much nicer than windows xp did.
Sent from my paranoid phone's mind
jimbridgman said:
I would start with my thread for all the tools you need.
http://forum.xda-developers.com/showthread.php?t=1404442
Then you can start with taking a shot at a stock based ROM, since they really are the easiest place to start. You will need some form of linux ubuntu is really the most supported distro for android dev work, so that is a good start. This can be a VM to start out with, you can use a free VM tool like virtual box, if you want to just to give it a try, but I will tell you a dual boot works much better, and I will be honest I have a machine that just uses ubuntu and does not run windows at all. I have a wine install for things like netflix and such, but other than that.... no windows. That is just me though.
The key is the android kitchen... and that ONLY runs on linux, that where you build your ROM at. There are guys like rdavisct, who do it on windows, but even he would tell you how much of a PIA it was for him, and he did eventually go to ubuntu with my help.
After that you can start to look at compiling roms like CM, aospa, and the like.
Click to expand...
Click to collapse
Thats awesome. I have both Red Hat and Ubuntu installed. What about the testing? After compiling do you test it directly on your Atrix 2? I have only one mobile and am afraid to test it directly on it. :crying:
androiddecoded said:
Thats awesome. I have both Red Hat and Ubuntu installed. What about the testing? After compiling do you test it directly on your Atrix 2? I have only one mobile and am afraid to test it directly on it. :crying:
Click to expand...
Click to collapse
Yes, that is the only way. That is why you have the fxz and rsd lite handy and ready, just in case. 20 min. and you are back up and running. If you are concerned go buy a 10-40 buck "burner" at Walmart and put your sim in it, for while you test. I am lucky that I still have my HTC hero lying around for just that purpose... Every time I bricked my a2 (doing bootloader work), that was my go to backup.
I never needed it while doing ROM work, because the worst that will happen is boot loops/soft brick, it is nearly impossible to hard brick the a2 testing a ROM that does not have a kernel in it.
jimbridgman said:
Yes, that is the only way. That is why you have the fxz and rsd lite handy and ready, just in case. 20 min. and you are back up and running. If you are concerned go buy a 10-40 buck "burner" at Walmart and put your sim in it, for while you test. I am lucky that I still have my HTC hero lying around for just that purpose... Every time I bricked my a2 (doing bootloader work), that was my go to backup.
I never needed it while doing ROM work, because the worst that will happen is boot loops/soft brick, it is nearly impossible to hard brick the a2 testing a ROM that does not have a kernel in it.
Click to expand...
Click to collapse
Thanks sir. Got that
Will try to contribute something if I can. Kudos to our dev team. You guys are doing a great job. Happy to be a part of a great community
jimbridgman said:
Yes, that is the only way. That is why you have the fxz and rsd lite handy and ready, just in case. 20 min. and you are back up and running. If you are concerned go buy a 10-40 buck "burner" at Walmart and put your sim in it, for while you test. I am lucky that I still have my HTC hero lying around for just that purpose... Every time I bricked my a2 (doing bootloader work), that was my go to backup.
I never needed it while doing ROM work, because the worst that will happen is boot loops/soft brick, it is nearly impossible to hard brick the a2 testing a ROM that does not have a kernel in it.
Click to expand...
Click to collapse
I took the Paranoid Android ROM from this page for practice. http://forum.xda-developers.com/showthread.php?t=2050705
I extracted it using Android Kitchen, but it says boot.img not found. Do we need to add boot.img from our phone or its not needed since we have a locked bootlader. Or should I take stock Atrix 2 ROM?
androiddecoded said:
I took the Paranoid Android ROM from this page for practice. http://forum.xda-developers.com/showthread.php?t=2050705
I extracted it using Android Kitchen, but it says boot.img not found. Do we need to add boot.img from our phone or its not needed since we have a locked bootlader. Or should I take stock Atrix 2 ROM?
Click to expand...
Click to collapse
Ok, so you need to let the kitchen create or import a "fake" one, as the kitchen was originally made for like samsung and htc phones and they require one, so the kitchen needs one, it will remove it when it builds the ROM and creates the zip file.
Also make sure you have the edison file, that was listed and where to put it was also listed in my thread on ROM building for the A2. That will help you create a proper updater-script when it builds the ROM, as well as give the proper mapping for our partitions on the A2.
jimbridgman said:
Ok, so you need to let the kitchen create or import a "fake" one, as the kitchen was originally made for like samsung and htc phones and they require one, so the kitchen needs one, it will remove it when it builds the ROM and creates the zip file.
Also make sure you have the edison file, that was listed and where to put it was also listed in my thread on ROM building for the A2. That will help you create a proper updater-script when it builds the ROM, as well as give the proper mapping for our partitions on the A2.
Click to expand...
Click to collapse
I will do it tomorrow. Really thank you for assisting me.
jimbridgman said:
Ok, so you need to let the kitchen create or import a "fake" one, as the kitchen was originally made for like samsung and htc phones and they require one, so the kitchen needs one, it will remove it when it builds the ROM and creates the zip file.
Also make sure you have the edison file, that was listed and where to put it was also listed in my thread on ROM building for the A2. That will help you create a proper updater-script when it builds the ROM, as well as give the proper mapping for our partitions on the A2.
Click to expand...
Click to collapse
One more doubt. I am building ROM from already built ROM i.e. the zip is already compiled, so how can I fix bugs like camera bugs and other things because they are already compiled i.e. in the form of apk.So should I use APK tool which is used to decompile the apk? Is there any difference while creating a ROM from source and creating it from already compiled zips.?? Silly question but I want to clear all these doubts
I downloaded the leaked 4.1 for Atrix 2. But I can't see the same folder format in that like system, META-INF? Why is that difference
androiddecoded said:
One more doubt. I am building ROM from already built ROM i.e. the zip is already compiled, so how can I fix bugs like camera bugs and other things because they are already compiled i.e. in the form of apk.So should I use APK tool which is used to decompile the apk? Is there any difference while creating a ROM from source and creating it from already compiled zips.?? Silly question but I want to clear all these doubts
I downloaded the leaked 4.1 for Atrix 2. But I can't see the same folder format in that like system, META-INF? Why is that difference
Click to expand...
Click to collapse
The issues for the camera are NOT in the apk itself, they are in the vendor libraries, the issue is that when vendor libraries are introduced for certai n things the ROM does not boot.
The best bet until you get better at C code and compiling ROMS, I would not mess with that. You can however build a working CM10.1 with a working camera by using a camera apk from the market, like 360 camera, and there are a few others, you can just drop that into /system/app and build the ROM and it should work for you.
Once you complie CM there is not much you can fix like that, rdavisct and I were doing just that until Wang released his source for the required A2 files (we did find a lot of issues and fix them, but they were actual missing libs and similar back then., It really is a lost cause to use the zip to "fix" "real compiled in bugs, because anything you do like that will not have the needed pieces compiled around it, some libraries will not work right since others that are from CM were not compiled around the ones from the phone, and think that they are part of the CM code, and are not "includes" in the compile.
You can however do a lot of customizing to the ROM to fit YOUR needs, but do not expect to fix any issues this way. Like I mentioned the camera is an easy one, you then just go to settings tell it your "default" camera app is the 360 camera, not the stock CM one.
jimbridgman said:
The issues for the camera are NOT in the apk itself, they are in the vendor libraries, the issue is that when vendor libraries are introduced for certai n things the ROM does not boot.
The best bet until you get better at C code and compiling ROMS, I would not mess with that. You can however build a working CM10.1 with a working camera by using a camera apk from the market, like 360 camera, and there are a few others, you can just drop that into /system/app and build the ROM and it should work for you.
Once you complie CM there is not much you can fix like that, rdavisct and I were doing just that until Wang released his source for the required A2 files (we did find a lot of issues and fix them, but they were actual missing libs and similar back then., It really is a lost cause to use the zip to "fix" "real compiled in bugs, because anything you do like that will not have the needed pieces compiled around it, some libraries will not work right since others that are from CM were not compiled around the ones from the phone, and think that they are part of the CM code, and are not "includes" in the compile.
You can however do a lot of customizing to the ROM to fit YOUR needs, but do not expect to fix any issues this way. Like I mentioned the camera is an easy one, you then just go to settings tell it your "default" camera app is the 360 camera, not the stock CM one.
Click to expand...
Click to collapse
Oh, ok. So can I try removing Moto Homescreen app and setting Nova Launcher as default?
And why is the difference between files between Moto 4.1 leak and Paranoid Android ROM. The regular mapping of folder is not there like META-inf , /system etc..
EDIT: I think I got it. Leaked Moto 4.1 is fastboot file and PA is flashable zip. I think I am right. Can I get the zip for Moto 4.1 leak?
4.1 leak is not a flashable zip.
The meta-inf folder items are for zips that are flashed in recovery.
And, not to dissuade you from jumping in to modding/dev'ing, but you may want to take things a bit slower... Start small.. And read/research a lot.
Sent from my paranoid phone's mind
androiddecoded said:
Oh, ok. So can I try removing Moto Homescreen app and setting Nova Launcher as default?
And why is the difference between files between Moto 4.1 leak and Paranoid Android ROM. The regular mapping of folder is not there like META-inf , /system etc..
EDIT: I think I got it. Leaked Moto 4.1 is fastboot file and PA is flashable zip. I think I am right. Can I get the zip for Moto 4.1 leak?
Click to expand...
Click to collapse
No, there is not a flashable "zip" for the Moto 4.1 leak, you will have to build that on your own with the Rom kitchen, since it is an FXZ, it will not have those flashable parts. The kitchen is very easy to use, it is menu driven and only takes about 30 min to an hour to do what it seems you want to do.
You can replace the launcher from within a flashable zip, but you might have issues, because the MOTO blur junk that is in their ROMS DEPENDS on it, if you do NOT leave it (moto blur launcher) in /system, then a number of things will not work that depend on the moto launcher (they are embedded in the xml files in the apks, and need to be edited to NOT look for the moto laucher), I think it is more trouble than it is worth, personally.
I would throw Apex in there if that is what you want, and then on first boot select it as your default launcher and be done with it, less issues and mess, other than the old moto launcher taking space in /system. BY the way ANYTHING that you put in /system is not really 100% upgrade-able by the market app, so like lets say you put apex in /system, then the market can not update the version in /system, since it is read only, and it will either fail the update, or try to put the newer updated files /data, so you will have things in two places for your 3rd party launcher. It is MUCH better to put any APKS that would come from the market into /data so they can get updates with out any odd issues, just a heads up...
--EDIT--
As alteredlikeness said about the same time I was posting, start a little smaller, and do a bunch of learning, because from what I see you asking about and posting in here, you have a good bit of learning to do, about how the directory structure and things are and work in android, as well as some ROM building basics.
I would just like to mention an amazing rom that i just recently discovered that wasn't in our section It is PurifieD 3.5 rom over in the GT-I9505 section it said that it would only work with twrp/cwm and i was able to get it to boot with safestrap 3.75 after 1 slight change it has the option to look like samsung touch wiz or pure aosp theme and aosp lockscrren and apps stock messaging light or dark theme aosp dialer and contacts, clock, browser and more so i encourage everyone to check it out because it is smooth!
http://forum.xda-developers.com/showthread.php?t=2454205
Screenshot of about device?
Sgh-i337
Att I337 Nj4 baseband
Murasakiii said:
Screenshot of about device?
Click to expand...
Click to collapse
If its only booted with twrp or cwm, what change did you make to make this boot and still have WiFi and I assume data? Maybe you should share in the all things general thread?
Disregard. This ROM is already posted there. I wonder how this one is compatible and we can't figure out why the others aren't.
Murasakiii said:
If its only booted with twrp or cwm, what change did you make to make this boot and still have WiFi and I assume data? Maybe you should share in the all things general thread?
Disregard. This ROM is already posted there. I wonder how this one is compatible and we can't figure out why the others aren't.
Click to expand...
Click to collapse
Yup. This ROM was ported by Gogollie. This was built with a TouchWiz kernel, that's why it boots, it isn't real GPE without the GPE kernel. Just themed with some AOSP apps.
npjohnson said:
Yup. This ROM was ported by Gogollie. This was built with a TouchWiz kernel, that's why it boots, it isn't real GPE without the GPE kernel. Just themed with some AOSP apps.
Click to expand...
Click to collapse
actually no 3.5 I have never ported. If its davy's ROM still its probably Stock International Wanam ROM Build with KNOX and other crap cleaned up with options to install AOSP apps by DSA creator of BlackBox another great Hybrid or its 100% TouchWiz with his Domination theme flashed over the top. If you dont know what Domination is in terms of a theme its one of the greatest themes ever made. I miss the option to go white with it sometimes tho. Its themed to look nearly identical to AOSP. Theres other Aroma options to MOD the ROM to act more like AOSP or install AOSP Apps like Calculators, Camera, and stuff. The Aroma installer is pretty nifty and lets you somewhat De-Bloat while installing it.
My newest ROM looks completely different and installs at half the size. Its also a minimal install / beast with speed and battery. I dont know its been posted here but you should be able to use it no problem. with safestrap just flash your modules to get wifi working. and if your at&T you might have to flash an apn patch to replace the apns from /etc directory with your own. or maybe manually entering them would work too. Its nearly all AOSP but yes in order to maintain good data signal, wifi, tethering, usb, etc I had to make a ROM over the TW so the Stock Kernel that most of AT&T/VZW has to run with a locked bootloader would be able to use these features of the phone with no problems. Theres also a "Smoke Weed Everyday"Nate Dogg Audio Clip during shutdown that I accidentally forgot to remove before releasing so if at work or school you might want to delete the file PowerOff.ogg from the /system/media/audio/ui folder you can also replace the file or PowerOn.ogg for startup sound with any mp3 or ogg file just rename it to that file name...
dOPE-PSOA
@gigilie This is so nice of you to post! And great to know that there are two additional Roms we can try to further get away from touchwiz. @guut13 have you tested these out/posted them?
Murasakiii said:
@gigilie This is so nice of you to post! And great to know that there are two additional Roms we can try to further get away from touchwiz. @guut13 have you tested these out/posted them?
Click to expand...
Click to collapse
I've ran Purified for a long time on the 4.4.2, it's a TouchWiz-based ROM so it works with Safestrap just fine. It's using the Domination AOSP them package, it's a solid rom and I'm happy to see it's update I'll have to switch back.
@guut13 - I'm testing it now ~ I'll let you know how it goes so you can update the index.
NighthawkXL said:
I've ran Purified for a long time on the 4.4.2, it's a TouchWiz-based ROM so it works with Safestrap just fine. It's using the Domination AOSP them package, it's a solid rom and I'm happy to see it's update I'll have to switch back.
Click to expand...
Click to collapse
Thanks for this, I'm gonna try it out.
I would like to know what was changed as well. Ive tried multiple kernels (stock) and multiple modules, and I cant get wifi to enable on this rom.