About Carbon
CarbonRom is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look at, build, and use our code on CarbonDev GitHub.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
Screenshots
{
"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"
}
Carbon Updates
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users.
Download Carbon
All Carbon downloads and further information such as features, changelog, and FAQ can be found on our goo.im page.
CARBON-JB-UNOFFICIAL-20131009-2208-epicmtd.zip
Changelog
For a detailed changelog, check out the changes made each night here:
Change Log
Support
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our goo.im page linked above. It's new, but expanding fast. Just like us!
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Ask a question on our IRC channel. Connect to #teamcarbon on irc.freenode.net or click here. You'll find several other Carbon fans and usually one or more devs as well. Please be polite.
Who is Team Carbon?
Andros11
BigShotRob
Bionic Beast
dg4prez
Kejar31
mattmanwrx
morfic
nocoast
pixeldotz
slick_rick
winner00
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
This is obviously an unofficial build, but it runs great on my phone - and heck it's built on an official Carbon rig, so that's good enough right?
Enjoy folks, let me know if you have any issues.
Use standard gapps for 4.3...
gapps-jb-20130813-signed.zip Mirror #1 Mirror #2
First on the new thread
Sent from my SCH-I500 using xda app-developers app
let's see if this one can make me happy. thanks for the new toy.
Effsi said:
let's see if this one can make me happy. thanks for the new toy.
Click to expand...
Click to collapse
FYI I have noticed that mobile data bug from CM10.2 seems present here... I was on wifi, went out, data would not hook up until I rebooted the device...
Going to doublecheck that I have all the patches needed from 10.2, but I think I do :/
arrrghhh said:
FYI I have noticed that mobile data bug from CM10.2 seems present here... I was on wifi, went out, data would not hook up until I rebooted the device...
Going to doublecheck that I have all the patches needed from 10.2, but I think I do :/
Click to expand...
Click to collapse
The relevant patches that cured this on the CM builds were http://review.cyanogenmod.org/#/c/50036/ and http://review.cyanogenmod.org/#/c/50035/. They are still not merged so you might not have them. If you do have them, then well, I can make sure I'm not using any other random patches.
Sent from my SPH-D700 using xda app-developers app
bbelos said:
The relevant patches that cured this on the CM builds were http://review.cyanogenmod.org/#/c/50036/ and http://review.cyanogenmod.org/#/c/50035/. They are still not merged so you might not have them. If you do have them, then well, I can make sure I'm not using any other random patches.
Sent from my SPH-D700 using xda app-developers app
Click to expand...
Click to collapse
Ah, they are not merged...
Yea, I don't have these. Thanks!
Edit - built, just need to test if this fixed it...
Edit 2 - tested, seems to work. Uploading new build now
There isn't any special gapps package for this, right?
Sent from my SPH-D700 using Tapatalk 2
jeffreyjicha said:
There isn't any special gapps package for this, right?
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
4.3 gapps should be fine.
I'll add that to one of the posts I stole!
Edit - done
for some reason I can't seem to get my phone to get a radio signal outside of wifi. probably just something wrong with my flash... I'll post back eventually when I can reflash if no one else says it works/doesnt work.
Data, calling and texting work fine for me. I sometimes get the same text twice, or I'll be having a conversation and I'll randomly get the other person's previous responses, again. Also, I've noticed the front facing camera doesn't work for me and it hasn't for awhile.
I should add that I've had both of these issues on CM10.1.3.1
Sent from my SPH-D700 using Tapatalk 2
jeffreyjicha said:
Data, calling and texting work fine for me. I sometimes get the same text twice, or I'll be having a conversation and I'll randomly get the other person's previous responses, again. Also, I've noticed the front facing camera doesn't work for me and it hasn't for awhile.
I should add that I've had both of these issues on CM10.1.3.1
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
thanks for that! I was thinking it was on my end.
edit : confirmed data working. reflashed modem in odin and all is well.
jeffreyjicha said:
Data, calling and texting work fine for me. I sometimes get the same text twice, or I'll be having a conversation and I'll randomly get the other person's previous responses, again. Also, I've noticed the front facing camera doesn't work for me and it hasn't for awhile.
I should add that I've had both of these issues on CM10.1.3.1
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Ah, thank you for confirming they are platform bugs.
I'll look into the front cam issue. Not sure about the multiple texts, but I use Google Voice, so I'm probably not the best use case.
I'm loving the active notifications tho!
Edit - so I just ran zDeviceTest, and the front cam worked as expected. Can you tell me where the front cam is failing for you?
arrrghhh said:
Ah, thank you for confirming they are platform bugs.
I'll look into the front cam issue. Not sure about the multiple texts, but I use Google Voice, so I'm probably not the best use case.
I'm loving the active notifications tho!
Edit - so I just ran zDeviceTest, and the front cam worked as expected. Can you tell me where the front cam is failing for you?
Click to expand...
Click to collapse
It just fails in general, like if I open the camera, and try to switch to the front camera, it FC's Gallery and then every time I open gallery or camera after that, it closes. The only thing I can do to use it again is to wipe data for gallery. Also I use Google Voice as well.So idk what the issue is there.
Sent from my SPH-D700 using Tapatalk 2
jeffreyjicha said:
It just fails in general, like if I open the camera, and try to switch to the front camera, it FC's Gallery and then every time I open gallery or camera after that, it closes. The only thing I can do to use it again is to wipe data for gallery. Also I use Google Voice as well.So idk what the issue is there.
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
For the text issue, did you enable Voice+, or are you using the GV app?
I also just tested this - open camera, switch to front camera - I see my ugly mug. Are you dirty flashing?
I did enable Voice+. Also I did a clean flash.
Sent from my SPH-D700 using Tapatalk 2
jeffreyjicha said:
I did enable Voice+. Also I did a clean flash.
Click to expand...
Click to collapse
This is the issue. Voice+ is known to cause problems like duplicate texts... I just use the GV app, I do not enable Voice+ personally and have never had this issue.
As for the front camera issue, perhaps clear cache on the gallery or camera app? That is strange, I can't seem to recreate it.
Well thanks for the info on Voice+. When I try to use the front camera, I usually clear data for it, idk if clearing cache will do anything different, but I'll check anyway.
Edit: Clearing cache does nothing.
Sent from my SPH-D700 using Tapatalk 2
jeffreyjicha said:
Well thanks for the info on Voice+. When I try to use the front camera, I usually clear data for it, idk if clearing cache will do anything different, but I'll check anyway.
Edit: Clearing cache does nothing.
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Hm. Can you use that app I mentioned earlier? Z-Device Test. See if the front cam works there...
Related
{
"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"
}
MIUI 1.3.5
brought to you by ahmgsk, fusingblackrose, asdfghjkl, Mike_77, darkierawr,
and the latest by deano0714...
So now to get started:
MIUI 1.8.19
All Credit goes to Deano0714 for getting it to boot and working on it!!
Working:
-It boots...
-Wifi (only with static IP)
NOT working:
-Everything else...
-SD card (fix may be on the way)
MIUI 1.3.5
Things NOT working:
1. Bluetooth
2. Auto rotation
3. Screen wake lag receiving call
4. MMS (recompiling apk soon. aka maybe fixed)
5. front facing cam (who uses this?)
6. camcorder
7. EXTREME lag when using MIUI music...(fixed by downloading MIUI music)
Important things working:
1. SMS
2. 3G
3. Theme manager (important to me lol)
4. Everything else??
Chopped Up MIUI
It has the first kernel ahmgsk had in rom and was supposed to fix things.
Before flashing:
1. PLEASE remember to wipe everything...
2. If ext4 flash either MIUI or Chopped up.
3. If RFS flash MIUI only. Il upload separate dual kernel later.
I assume by now you all know how to convert to EXT4...if not then just root with CWM 3.0.0.6 and boot into recovery. It will then convert you and you HAVE to flash an EXT4 rom before reboot..
DOWNLOADS:
1.8.19 crespo4g port: http://db.tt/AdPyiM8*** CLICK HERE ***[/URL]
CREDIT goes to deano0714 for getting it to boot and fixing issues!!
MIUI.zip : *** CLICK HERE ***
Chopped Up MIUI.zip : *** CLICK HERE ***
Original EXT4 kernel : *** CLICK HERE ***
Working MIUI Music : *** CLICK HERE ***
This is not my fix..credit to micahrodriguez7 for posting this. And lightninbug and mad-murdock....
Well guys thats all for now.
PLEASE report any unknown bugs you find.
Huge thanks to all testers at MIUI-DEV and here at XDA !!!
And to ahmgsk for helping whenever he can!! He is a great DEV!
reserved...for what? who knows, but everyone does it. lol
Oh i know..il post some pics!
Yay first after poster for once
Sent from my SPH-D700 using XDA Premium App
Found an SMS bug. anytime i try and send a message even 1 character past the limit for one message, the person receives nothing but a bunch of symbols. so you'd have to send the message everytime you get to the limit of one message in order to send a long message
Edit: Sorry Running Chopped up Miui
big_slug06 said:
Found an SMS bug. anytime i try and send a message even 1 character past the limit for one message, the person receives nothing but a bunch of symbols. so you'd have to send the message everytime you get to the limit of one message in order to send a long message
Click to expand...
Click to collapse
Lol thats an AOSP thing if im not mistaken..i think the solution is download another text app that has "auto separate" in settings...i think handcent works...maybe go!sms lol
nixo31 said:
Lol thats an AOSP thing if im not mistaken..i think the solution is download another text app that has "auto separate" in settings...i think handcent works...maybe go!sms lol
Click to expand...
Click to collapse
ok, kool. i love go sms you have any idea how to fix the bluetooth in chopped up? thas all i need for everyday use. i need it for my workout music ...still running it now since i skipped my workout today tho lol
big_slug06 said:
ok, kool. i love go sms you have any idea how to fix the bluetooth in chopped up? thas all i need for everyday use. i need it for my workout music ...still running it now since i skipped my workout today tho lol
Click to expand...
Click to collapse
lmao i skipped it too...for about a month xD and i think the problem is in the initramfs..so its in the kernel and i dont know much about that yet :/ i wonder if the bonsai kernel or ACS kernel fixes it? im sure it probably breaks something else lol
nixo31 said:
lmao i skipped it too...for about a month xD and i think the problem is in the initramfs..so its in the kernel and i dont know much about that yet :/ i wonder if the bonsai kernel or ACS kernel fixes it? im sure it probably breaks something else lol
Click to expand...
Click to collapse
haha, probably. well, i'll probably run this one through tomorrow unless u post another one you want tested. i keep my eyes peeled for any more bugs, but its looking doubtful so tho. great work
Very nice, glad to see and updated thread for this. No offense to ahmgsk, I know he's real busy with other development.... oh and life lol.
Sent from my SPH-D700 using XDA Premium App
So happy to see continued MIUI development. I'll have to flash this over once it's a bit more fleshed out
nixo31 said:
Is the theme manager working?? It should flash theme and reboot into same theme not new one.
EDIT: NEW thread is open!! All updates will be posted here..
Click to expand...
Click to collapse
theme manager is working on the twilight kernel like the rest.
it works, but sometimes when im changing my lockscreen it'll (theme manager) will force close on me but it does that on other kernels too
3g is still a little iffy with this kernel (twilight)
okay upon further testing.....
it seems that ALOT of kernels are working with MIUI
some are EXTRA buttery my gawd how they are snappy it seems.
Imo, Twilight seems like one of the fastest however a few things are broken and are missing from the initramfs (i.e. bluetooth) However wifi modules and the like are obviously included in the initramfs because it tethers.....
3g just isnt so great
back with more
good news/bad news
[KERNEL][CM7] Phoenix v0.01 || Updated: 04/09/2011 - 11:45
^^flashes. Bluetooth turns on and all. However, virtually impossible to use. it needs some tightening up or reworking period. hella static!!!!!!
3g works
wifi tether is borked (missing things in the initramfs)
edit: this kernel borks wifi.... booooooooooooooo
twilight kernel fixes the lag when music player is running/on
however, 3g is hella inconsistant.... i flash this kernel before and 3g was working.....now it doesnt wanna work
HELLA iffy
Hello asdfghjkl.
I didn't know we had that many problems!
I guess fusingblackrose underplayed the whole deal
big_slug06 said:
Found an SMS bug. anytime i try and send a message even 1 character past the limit for one message, the person receives nothing but a bunch of symbols. so you'd have to send the message everytime you get to the limit of one message in order to send a long message
Edit: Sorry Running Chopped up Miui
Click to expand...
Click to collapse
nixo31 said:
Lol thats an AOSP thing if im not mistaken..i think the solution is download another text app that has "auto separate" in settings...i think handcent works...maybe go!sms lol
Click to expand...
Click to collapse
big_slug06 said:
ok, kool. i love go sms you have any idea how to fix the bluetooth in chopped up? thas all i need for everyday use. i need it for my workout music ...still running it now since i skipped my workout today tho lol
Click to expand...
Click to collapse
Yup, it is an AOSP thing. Use something like handcent to split the messages
isnt it also relative to our cdma networks as oppose to gsm networks?
DOHH got soo excited thought devs were being sneaky with this one and just release something stable, but this is progress! keep it up!
It has to do with both, combination of AOSP and CDMA network. Dunno why since CDMA support was added in Android 1.6 (shoehorned into 1.5 by HTC for the Hero and by Samsung for the Moment).
I would suggest the mods to keep the thread clean and allow only the testers and the other people related to the ROM post here.
PS: No offence meant to other members.
Notice: These builds are experimental and most likely not fully, or at all working. Proceed at your own risk.
EDITS:
7/6- changed download link up a directory
7/6- added sd card fix that can be added to a build to allow sdcard use and JRW 28's build.prop to utils folder
This is where I am going to post all my CM9 and AOKP work. Please feel free to pitch in and help out if you can. You can PM me if you want privacy, but I would rather keep most of the discussion open in this thread so that others can see.
What do we have here?
Most if not all of what I will write about here is based on ROMS for other devices that can be found here. These ROMS are not meant to be used as a "daily driver" if you will, but more to be tested and hopefully improved until they work. The hope would be to get the radio working so they could actually be used to make calls.
Versions
I'm dividing the builds up into different categories
1. Nightly- They probably won't actually be nightly, maybe 2 some day and then not 1 for a week, but they are the most cutting edge, and may not even boot. Only nightly builds currently exsist.
2. Release Candidate (RC)- a bit stabler, will work fine, but will still have problems as listed.
Changelog
7/6/12:
Initial releases of AOKP and CM9. both are based of Droid 3 and AOKP appears not to boot
Problems
Here is a list of generic problems, along with ones specific to certain builds. I'll add on to this.
Generic:
1. No radio- This is the big one, no clue how we're gonna fix it
CM9 Nightlies:
1. no sd card
2. no wifi
3. no sound
AOKP Nightlies:
Downloads
All download can be found here: http://www.androidfilehost.com/main/Motorola_ATRIX_2_Developers/lkrasner/
Bug reporting
Please report bugs in this thread and be sure to state the following
1. which version (date +nightly, RC or Stable)
2. What the problem is
3. conditions required for it to occur
4 any other important details.
Example: 7/6/12 nightly no sound only in airplane mode also causing apps to force close when trying to play sound (that is all made up)
Want to help out with fixing? Please PM me or let me know here what you think you can fix, or ask me to give you a job. Thanks!!!
Just in case...
I will look into the taboo world of the RIL.... since I know that is off limits on XDA...
I will communicate anything through PM though, I just wanted to put it in here, so others knew not to discuss this here, and that I was going to see what I can achieve on cracking the RIL.
jimbridgman said:
I will look into the taboo world of the RIL.... since I know that is off limits on XDA...
I will communicate anything through PM though, I just wanted to put it in here, so others knew not to discuss this here, and that I was going to see what I can achieve on cracking the RIL.
Click to expand...
Click to collapse
why is it off limits?
Sent from my MB865 using xda premium
lkrasner said:
why is it off limits?
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Because it has to do with the radio, and opening it up. Modifying or talk of modifying radios, cell unlock, S-off, and hacking free cell service are all off limits on XDA. I am not 100% sure on all of it, so you might check with our mod.
I also sent you a PM too.
About the only thing I can do here is give the correct build.prop setting for CM9/AOKP to work on our phone, and that is the following:
Code:
ro.ril.hsxpa=2
ro.ril.gprsclass=12
ro.ril.hsdpa.category=28
ro.ril.hsupa.catergory=9
What I am going to do is a little more back door and "forcefull" if these setting don't work for anyone who has it loaded or is going to flash it.
right now I can't flash my A2, because I am running another bootloader/kexec type of hack to try to get my unsigned kernel to boot.
This weekend I will try and see what I can do with the actual ro.ril.so files.
Downloaded...can DB for mirrors if anyone needs. May hold off flashing myself until a little more fixing is done. Very excited to see the ball rolling now though. Great job guys...keep it up!
@lkrasner. You sir are bound and determined to get us non stock roms for this phone. Thank you for all of your efforts. I have the weekend off so i will be testing these roms over the next few days to see if i can help in any way. Thanks again.
Sent from my MB865 using xda premium
Here is a modified build.prop that does boot with AOKP if anyone wants to take a look at it
Build.prop
for those that downloaded the link please download this again as I had the wrong build.prop, it has now been corrected !!! My apologies!!!
I really like to thank all of you awesome guys for your so hard,dedicated and superb efforts to keep A2 one of the best and that too with so many many limitations and constrains.
I really salute you guys.God bless you.Keep up the good work.
A virtual cookie from me to all the awesome guys making this forum nice place ^_^
{
"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"
}
JRW 28 said:
Here is a modified build.prop that does boot with AOKP if anyone wants to take a look at it
Build.prop
Click to expand...
Click to collapse
I noticed a few little issues.
1) The following line is in there twice with different numbers:
Code:
persist.ril.mux.noofchannels = 8
persist.ril.mux.noofchannels=9
2) The ro.ril settings are a little different than our "known good" settings:
Code:
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.ril.hsdpa.category=28
ro.ril.hsupa.category=9
Try changing the the ro.ril.grpsclass to 12, as in my above post.
These are just the things that so far stand out to me to begin with.
If anyone wants to give them a try and let us know....
Archmag3 said:
I really like to thank all of you awesome guys for your so hard,dedicated and superb efforts to keep A2 one of the best and that too with so many many limitations and constrains.
I really salute you guys.God bless you.Keep up the good work.
A virtual cookie from me to all the awesome guys making this forum nice place ^_^
Click to expand...
Click to collapse
Thanks for the cookie, now go give yourself a treat and eat some virtual cheesecake :silly:
I think I will write up a quick shell script that changes the necessary properties in build.prop so that we can do it to any build and not worry about screwing up other things by totally replacing it.
How should I go about it? sed I guess? any other ideas.
lkrasner said:
I think I will write up a quick shell script that changes the necessary properties in build.prop so that we can do it to any build and not worry about screwing up other things by totally replacing it.
How should I go about it? sed I guess? any other ideas.
Click to expand...
Click to collapse
awk and sed or Perl, since Perl has the interpreters and edit functions for text already built in.
It might be best to just have the script create the correct build.prop no matter what, instead of edit it, that way we know that the correct file gets used, and not some "accidental" flub up that someone might have played with... sort of like a built in recovery so to speak. you can always back up any other versions.
jimbridgman said:
awk and sed or Perl, since Perl has the interpreters and edit functions for text already built in.
It might be best to just have the script create the correct build.prop no matter what, instead of edit it, that way we know that the correct file gets used, and not some "accidental" flub up that someone might have played with... sort of like a built in recovery so to speak. you can always back up any other versions.
Click to expand...
Click to collapse
but won't that be a problem with different builds? isn't the build.prop different for AOKP and CM9 and even for different ones of those possibly?
I would do Perl, but I have never used it in my life, so I would probably screw something up pretty bad, or just take forever to do it.
Rils are modified and created in other forums, so I wouldn't think it would be a problem for us.
Sent from my MB865 using xda app-developers app
gvsukids said:
Rils are modified and created in other forums, so I wouldn't think it would be a problem for us.
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
Knowing Jim, whatever he is trying to do is pretty crazy and really not meant for here, even if some stuff is
Updated OP with download link changed to my root directory so that you can see all my folders.
I will add other things that will be useful on the utils folder.
lkrasner said:
Knowing Jim, whatever he is trying to do is pretty crazy and really not meant for here, even if some stuff is
Click to expand...
Click to collapse
Yes you are right.... I am going to do something that has the possibility that I might have to go rogue and change and release proprietary code in an open format, and that is what is not allowed, and I can't even discuss it here. Anyone who would like more information can PM me.
Here is a rundown on the RIL, and why it is important:
http://www.netmite.com/android/mydroid/development/pdk/docs/telephony.html
We need it to be open source, but it is not, and it is usually propritary code. If I can find an open source version we are in luck and we can compile the CM9 version and just plug it in... otherwise I need to go and hack it.
jimbridgman said:
Yes you are right.... I am going to do something that has the possibility that I might have to go rogue and change and release proprietary code in an open format, and that is what is not allowed, and I can't even discuss it here. Anyone who would like more information can PM me.
Here is a rundown on the RIL, and why it is important:
http://www.netmite.com/android/mydroid/development/pdk/docs/telephony.html
We need it to be open source, but it is not, and it is usually propritary code. If I can find an open source version we are in luck and we can compile the CM9 version and just plug it in... otherwise I need to go and hack it.
Click to expand...
Click to collapse
Jesus, bet your just waiting for you cease and desist letter from Moto... again...
Try not to brick your phone, we need you.
EDIT: LOL!! I was just reading that same article. bet you got it as the first google result of "android ril"
lkrasner said:
Jesus, bet your just waiting for you cease and desist letter from Moto... again...
Try not to brick your phone, we need you.
EDIT: LOL!! I was just reading that same article. bet you got it as the first google result of "android ril"
Click to expand...
Click to collapse
Nope, that is the place where you can get the opensource RIL files and code... that is why I already knew about it... LOL you found it though so you know what I am on to and after here.
LOL, Yeah I expect a few of them to be honest, and I am guessing that once I crack the bootloader and the RSA cipher that a true suit will come... Oh well Moto can bite it...
The problem: All JB built AOSP/CM mms.apk files do not work with TW ROMS.
Observations: Most work fine, but crash on sending or receiving an MMS message. ICS built mms.apks do work, but since ICS doesn't have Quick Reply or MMS preview built in, it's a step behind.
Bounty requirements: Working JB (preferred 4.2 as it has Group Messaging built in) that doesn't crash on MMS sending or receiving. Also, Emoji support, Full timestamp support, soft keyboard type, and SMS to MMS converter. If you patch mms.apk directly via source, a changelog or link commit back to CM/Gerrit is required. An explanation of what was missing/changed if no direct code was patched.
Method of payment: All parties who join into the bounty will be solely responsible for payment, which are to be arranged between the two parties.
I will start by offering $5. If you would like to contribute to get this working, please post and I'll keep a running list and keep the thread updated with the current amount.
Update: Adrynalyne, of Team BAMF, was kind enough to lend a hand and provided a fix, which he details in this thread. Attached is the fix.
#Notes# The fix SOMETIMES hangs while sending an MMS issue. I've been able to reproduce, but never when I can capture a logcat of it. If you know how to enter/use logcat, and you want to help refine the fix even more, by all means, post in here or PM me. I actually don't think it has to do with the fix, but the mms.apk itself. But again, we need people who can post logcats to narrow it down.
This fix SHOULD work on ANY unmodified, deodexed framework.jar based on the VRBLK1 leak. If you don't know what this is, ASK your dev if they've modified the framework.jar. If your phone blows up, YOYO, you're on your own. As always, its a good idea to make a nandroid backup, just to be safe.
Update: Adrynalyne hammered out a working fix for BLK3, which I posted below. I tested it on Beans Build 8. Works like a charm
More importantly, please consider donating to adrynalyne here. He did this out of kindness, as a favor to me. He doesn't even own the phone, I had to test and send files and logcats to him. Any little bit helps, and I think it's awesome he helps out with a device his team does not directly support, and hope more devs in the future will help each other in this manner. Thanks.
I've never had a problem sending mms with AOSp roms, i've used AOKP, cm10 and now miui, no problems
CovXX said:
I've never had a problem sending mms with AOSp roms, i've used AOKP, cm10 and now miui, no problems
Click to expand...
Click to collapse
He isn't talking about aosp Roms.
CovXX said:
I've never had a problem sending mms with AOSp roms, i've used AOKP, cm10 and now miui, no problems
Click to expand...
Click to collapse
Read the first sentence. The problem is that the AOSP/CM mms.apks do not work on TOUCHWIZ BASED ROMs.
I'm using an Aosp messaging apk on clean rom. No problems sending mms or anything. Am I reading it wrong?
Sent from my SCH-I535 using xda premium
He is talking about getting the aosp/cm10 mms with quick reply to work on tw roms. The picture below is an example of what he is talking about.
{
"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"
}
The devs got the quick reply working so far but the app fc when viewing, sending or receiving a picture message.
also when you tap a thread with a MMS the app force closes
RCOVA said:
also when you tap a thread with a MMS the app force closes
Click to expand...
Click to collapse
We are almost there.
MMS force closes: fixed
MMS sending and receiving: mostly fixed. Possibly a signal issue as it sends OK at some times and not others. It receives fine.
adrynalyne said:
We are almost there.
MMS force closes: fixed
MMS sending and receiving: mostly fixed. Possibly a signal issue as it sends OK at some times and not others. It receives fine.
Click to expand...
Click to collapse
Damn...This is awesome. I cant wait!
You won't get the aosp group messaging because it requires framework tweaks
Sent from d2_vzw
con247 said:
You won't get the aosp group messaging because it requires framework tweaks
Sent from d2_vzw
Click to expand...
Click to collapse
That doesn't mean it can't be done. Can't never did nothin'. I'm starting with 4.1.x compatibility first.
As it stands, almost all my work so far to get AOSP MMS working has been framework code. I am going to post it here shortly so that I can get some more test results.
Edit: attached.
A couple things to note: Only send MMS through the app itself. In other words, don't try to send something from the gallery as MMS. Instead, open the MMS app and attach a file. I'll work on that limitation later.
This has worked for mexiken, both for receiving and sending, however sending becomes spotty. So let me know how it turns out. I do not know that this is the final fix and it may need some more work. I ran out of time due to Thanksgiving and family responsibilities. Once it fully works, I will be more than happy to share how I did it with everyone. Also, I modded the framework from his rom, so you might want to make a nandroid first, in case your JB TW rom isn't compatible. This is a test, and if your phone blows up, I hold no responsibility for it. I do not own this phone, so I cannot test it.
This package contains framework and a JB MMS app.
We've got it working on my phone, but I really don't know if it's my signal issues or what. I'm playing around with a few different combinations of files.
I will test further later tonight if I get out of the house. Worst case, I'll check tomorrow at work.
adrynalyne said:
That doesn't mean it can't be done. Can't never did nothin'. I'm starting with 4.1.x compatibility first.
As it stands, almost all my work so far to get AOSP MMS working has been framework code. I am going to post it here shortly so that I can get some more test results.
Edit: attached.
A couple things to note: Only send MMS through the app itself. In other words, don't try to send something from the gallery as MMS. Instead, open the MMS app and attach a file. I'll work on that limitation later.
This has worked for mexiken, both for receiving and sending, however sending becomes spotty. So let me know how it turns out. I do not know that this is the final fix and it may need some more work. I ran out of time due to Thanksgiving and family responsibilities. Once it fully works, I will be more than happy to share how I did it with everyone. Also, I modded the framework from his rom, so you might want to make a nandroid first, in case your JB TW rom isn't compatible. This is a test, and if your phone blows up, I hold no responsibility for it. I do not own this phone, so I cannot test it.
This package contains framework and a JB MMS app.
Click to expand...
Click to collapse
I'm not super familiar with how the framework works, so I figured I better ask before flashing this. I have a T-Mobile GS3 running a JB TW rom. Is the framework carrier or rom specific, meaning it would cause issues for me?
trickinit said:
I'm not super familiar with how the framework works, so I figured I better ask before flashing this. I have a T-Mobile GS3 running a JB TW rom. Is the framework carrier or rom specific, meaning it would cause issues for me?
Click to expand...
Click to collapse
I am going to assume so, yes. Once we verify it fully works, I can make versions for any version of phone...or post how it was done so others can (doesn't matter to me, I am doing this for free because mexiken is a good friend of mine).
Hello all!
Has anyone tried this on a VZW S3 yet? I'm running jelly beans stock rom with Nova launcher and I'm not feeling brave enough to try the fix just yet.
Sent from my SCH-I535 using xda app-developers app
Stre7ch said:
Hello all!
Has anyone tried this on a VZW S3 yet? I'm running jelly beans stock rom with Nova launcher and I'm not feeling brave enough to try the fix just yet.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I have the VZW S3 and can confirm it works in that it doesn't crash anymore, but it doesn't send reliably.
mexiken said:
I have the VZW S3 and can confirm it works in that it doesn't crash anymore, but it doesn't send reliably.
Click to expand...
Click to collapse
Good to hear, but what do you mean? Is it just MMS that won't send reliably or texts in general? What about receiving texts and MMS? Also, I know I'm a super noob, but how can I help with develop this?
Sent from my SCH-I535 using xda app-developers app
adrynalyne said:
That doesn't mean it can't be done. Can't never did nothin'. I'm starting with 4.1.x compatibility first.
As it stands, almost all my work so far to get AOSP MMS working has been framework code. I am going to post it here shortly so that I can get some more test results.
Edit: attached.
A couple things to note: Only send MMS through the app itself. In other words, don't try to send something from the gallery as MMS. Instead, open the MMS app and attach a file. I'll work on that limitation later.
This has worked for mexiken, both for receiving and sending, however sending becomes spotty. So let me know how it turns out. I do not know that this is the final fix and it may need some more work. I ran out of time due to Thanksgiving and family responsibilities. Once it fully works, I will be more than happy to share how I did it with everyone. Also, I modded the framework from his rom, so you might want to make a nandroid first, in case your JB TW rom isn't compatible. This is a test, and if your phone blows up, I hold no responsibility for it. I do not own this phone, so I cannot test it.
This package contains framework and a JB MMS app.
Click to expand...
Click to collapse
Thanks for your hard work! :victory:
Stre7ch said:
Good to hear, but what do you mean? Is it just MMS that won't send reliably or texts in general? What about receiving texts and MMS? Also, I know I'm a super noob, but how can I help with develop this?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Can you test it? Make a nandroid first. Verizon is having some MMS issues as well, which *may* attribute to this. I sent an MMS to my wife on a different phone today and it took a while for her to get it.
What I really need is a full logcat of when sending fails so I can figure out where its getting stuck. I believe mexiken told me he has about a 66% successful send rate.
Receiving always works AFAIK.
Try sending while on, and off WiFi.
Would love to help, unfortunately this does not seem to work on Synergy 118. tried with complete wipe as well as clearing Cache and Dalvik, still no dice. This looks like a great mod though.
Greetings
I have hundreds of files named RS_###.log in /data, all around 1000 Bytes.
They seem to be generated several times each day. Opening them produces a file with a bunch of numbers (pic)
I don't like it. It reminds me of the HTC logging debacle.
Can someone shed some light on this? My research came up fruitless.
Thank you
{
"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"
}
Unknown. I too had hundreds of them. I just did a batch delete.
I am running SlimRom's 4.2.2 Build 7 on the device atm, with lean kernel and crossbreeder.
Now, I literally have ~300 user apps on the phone, so my chance of tracking it down is slim to none, unless there is a 'file monitor' tool that can be used to historize what apps interact with what files (creating another .log file ). Is anyone aware of such a tool?
-t
That would be a good idea.
So no problems after batch delete? Do you do that weekly or something?
Batch delete rocked my system bad. I wouldn't advise that. Good thing I had a nandroid
I have 41 of them in my /data folder, all dated 2013/07/12. I didn't do anything special to the phone at all that week because we were on vacation, so I don't know what might have generated those files.
Stock rooted mf1.
<Don't ask me how I sent this>
HeadlessPonch said:
I have 41 of them in my /data folder, all dated 2013/07/12. I didn't do anything special to the phone at all that week because we were on vacation, so I don't know what might have generated those files.
Stock rooted mf1.
<Don't ask me how I sent this>
Click to expand...
Click to collapse
I have >200. Many from July 29. Not sure the significance of that date either.
Also surprised this thread isn't blowing up...
I've got a bunch of them too. Had two files created today, both with the same time. I checked the file properties and it shows the "owner" and "group" as camera, which is kinda scary. Makes me wonder what the camera is up to. My pictures are backed up to Google+, so I thought maybe it had something to do with that, but the oldest file was created on 7/30/13 and I've been backing up pictures a lot longer than that. I hate not knowing why these are being created.
Sent from my SCH-I535 using xda app-developers app
Bump
I've Googled RS log every way I can think of. The only thing I could come up with is an rs debugging log, which, according to Google, has something to do with app development and should be turned off before an app is released. Unless it is a really popular app, I doubt all of us downloaded or updated the same app unless it was a Google app. They have released a bunch of updates lately: maps, play store, play services, hangouts, etc. And we all know all the updates worked perfectly! At least some of those apps use the camera, so that could tie in. Or maybe it had absolutely nothing to do with any of this and I just lost 5 minutes of my life typing this :sly:
Sent from my SCH-I535 using xda app-developers app
OK, I think I may have something, but maybe someone else can try this to confirm it. Looks like it is Google Hangouts. Anytime i start a video call the file rs_0.log, rs_1.log, rs_11.log, are written too. Also there are files named cam_socket0 and cam_socket1 in /data. If I only use the front facing camera then cam_socket1 is written too. If I switch to the rear camera then cam_socket0 gets written to also. I've made 4 video calls this morning just to try it, every time I would then check the file properties and the access date and time matched when I made the call. I'm assuming it is renaming all the log files so that rs_0 is always the latest. If someone else can confirm this that would be great.
Sent from my SCH-I535 using xda app-developers app
roaddog665 said:
OK, I think I may have something, but maybe someone else can try this to confirm it. Looks like it is Google Hangouts. Anytime i start a video call the file rs_0.log, rs_1.log, rs_11.log, are written too. Also there are files named cam_socket0 and cam_socket1 in /data. If I only use the front facing camera then cam_socket1 is written too. If I switch to the rear camera then cam_socket0 gets written to also. I've made 4 video calls this morning just to try it, every time I would then check the file properties and the access date and time matched when I made the call. I'm assuming it is renaming all the log files so that rs_0 is always the latest. If someone else can confirm this that would be great.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
hmm...i've never used google hangouts...
Hmm... Well... I'm still thinking it has something to do with apps interacting with the camera. But chasing it/them down may be difficult. I just get worried about the camera being used without me knowing it.
Sent from my SCH-I535 using xda app-developers app
roaddog665 said:
Hmm... Well... I'm still thinking it has something to do with apps interacting with the camera. But chasing it/them down may be difficult. I just get worried about the camera being used without me knowing it.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
or the feds remotely switching your phone mic and camera. That was in the news the other day.
On another note, I just reflashed a clean install and haven't taken any pictures yet. ALSO...no RS log files yet. You may be on to something my friend...
Lol, well if it's the feds I'll have to give them some special pics! I'm probably already on some watch list anyway, so what the heck.
I took some pictures and it didn't change the rs log, so I'm thinking it is other apps accessing the camera. I know it happens with hangouts but there maybe more. I'm guessing it's something of google's and probably fairly harmless, but would still like to know.
Sent from my SCH-I535 using xda app-developers app
Speaking of "still," I'm "still" baffled by why nobody else has brought this up........
I've seen these too. No idea what causes them. They can get quite numerous.
I just use:
Code:
rm -Rf /data/RS_*.log
They don't seem to cause any problems, but I still wonder what the heck they are.
TA,
ALQI
alquimista said:
I've seen these too. No idea what causes them. They can get quite numerous.
I just use:
Code:
rm -Rf /data/RS_*.log
They don't seem to cause any problems, but I still wonder what the heck they are.
TA,
ALQI
Click to expand...
Click to collapse
Worked like a charm! Thanks for that bit of code.
BTW, I don't use hangouts and I had them too.
Sent from my Ktweaked PACmaned SGS3!
alquimista said:
I've seen these too. No idea what causes them. They can get quite numerous.
I just use:
rm -Rf /data/RS_*.log
They don't seem to cause any problems, but I still wonder what the heck they are.
TA,
ALQI
Click to expand...
Click to collapse
Can I do that from terminal emulator on the phone?
I did 2 video calls through Hangouts last night and I still have just the files from July 12. The cam_socket files were created at about the time of the calls though.
<Don't ask me how I sent this>
Well, I guess my hangouts theory is getting blown out of the water. every time I use hangouts I get an updated rs log file, however, I also get them if I haven't used hangouts.
Sent from my SCH-I535 using xda app-developers app
About Carbon
CarbonRom is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look at, build, and use our code on CarbonDev GitHub. and on our Gerrit CarbonDev Gerrit.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
Features
All of our features can be found on our site here:
Carbon Features
Here are some screenshots:
Carbon Screenshots
Carbon Updates
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users.
Download Carbon
All Carbon downloads and further information such as features, changelog, and FAQ can be found on our website.
Carbon Downloads
Changelog
For a detailed changelog, check out the changes made each night here:
Carbon Changelog
Support
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Ask a question on our IRC channel. Connect to #teamcarbon on irc.freenode.net or click here. You'll find several other Carbon fans and usually one or more devs as well. Please be polite.
Who is Team Carbon?
Find out here:
Carbon Team
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
Reserved
Also Reserved
can't see any downloads..
Sent from my XT897 using XDA Premium 4 mobile app
stevie13.xo said:
can't see any downloads..
Sent from my XT897 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
We're mirgrating to a new setup. I'll upload the last build to a mirror in the meantime.
Edit - sorry that took so long, work's been interesting today
http://oudhitsquad.com/arrrghhh/roms/carbon_kk/CARBON-KK-NIGHTLY-20140202-0248-xt897.zip
Thanks a lot... they're back up now.. Why'd they stop building? Is it automated?
Sent from my XT897 using XDA Premium 4 mobile app
stevie13.xo said:
Thanks a lot... they're back up now.. Why'd they stop building? Is it automated?
Sent from my XT897 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
We are migrating to a new setup. They are automated. We stopped them.
Okay. thanks!
Sent from my XT897 using XDA Premium 4 mobile app
i noticed a bug
1. getting a force close if i try to write something with the AOSP display keyboard and try to use "swyping".
2. on cm11 there was a quick settings tile for the quick settings menu, with which you could change data connectivity (2g, 3g, 2g/3g). i couldnt find it, is it really "missing" ?
3. some missing german translations (example for the display brightness menu, there you can adjust the settings or the complete "Carbon Fibers" option and its menues).
i am currently on carbon kitkat nightly from 02.02.2014.
pujdo1 said:
i noticed a bug
1. getting a force close if i try to write something with the AOSP display keyboard and try to use "swyping".
2. on cm11 there was a quick settings tile for the quick settings menu, with which you could change data connectivity (2g, 3g, 2g/3g). i couldnt find it, is it really "missing" ?
3. some missing german translations (example for the display brightness menu, there you can adjust the settings or the complete "Carbon Fibers" option and its menues).
i am currently on carbon kitkat nightly from 02.02.2014.
Click to expand...
Click to collapse
1. I think this is known... obvious workaround is to use another kb. I'll ask if there's some other fix, not sure why it hasn't been fixed yet...
2. I have one for LTE? Not sure what you mean.
3. I am not German Our gerrit is there, feel free to submit translations if it bothers you! :good:
pujdo1 said:
2. on cm11 there was a quick settings tile for the quick settings menu, with which you could change data connectivity (2g, 3g, 2g/3g). i couldnt find it, is it really "missing" ?
Click to expand...
Click to collapse
Look for a tile named NETWORK MODE. I'm not using this ROM, but CM and many other teams integrate this tile with this name.
Sent from Google Nexus 4 @ CM11
arrrghhh said:
1. I think this is known... obvious workaround is to use another kb. I'll ask if there's some other fix, not sure why it hasn't been fixed yet...
Click to expand...
Click to collapse
maybe look at the cm11 code ? there this problem is fixed. everything working fine.
2. I have one for LTE? Not sure what you mean.
Click to expand...
Click to collapse
i mean one to switch the network modes, as 3g consumes more battery as 2g.
3. I am not German Our gerrit is there, feel free to submit translations if it bothers you! :good:
Click to expand...
Click to collapse
can you please pm me how to do that, i would like to help with translating.
pujdo1 said:
maybe look at the cm11 code ? there this problem is fixed. everything working fine.
Click to expand...
Click to collapse
They use a different kb... not AOSP. It's weird, the kb doesn't FC for me... can you get a logcat? Did you flash clean? Did you try clearing data on just that app?
pujdo1 said:
i mean one to switch the network modes, as 3g consumes more battery as 2g.
Click to expand...
Click to collapse
Yes, I know what you mean. You must understand I do not have a GSM device, and this is not available for us. I had another user check who is on GSM, and it seems we are in fact missing this tile... I could only find LTE tile and Mobile Data tile. Should be easily added, I'll look into it.
pujdo1 said:
can you please pm me how to do that, i would like to help with translating.
Click to expand...
Click to collapse
Have you worked with any source code before, or building Android at all? It's a bit of a learning curve, even for simple translations...
You'll need to sync our source, make the modifications, then submit to gerrit.
Perhaps read this tut and see if it's something you would be interested in
http://www.mediawiki.org/wiki/Gerrit/Tutorial
Edit - apologies, I completely forgot we had an open review for a German translation... it was just merged
http://review.carbon-rom.com/#/c/1998/
I habe another Problem:
After some reboots all Widgets and shortcuts in homescreen are gone. Die a fresh installiert of with Rom with pa gapps full package for 4.4.2
pujdo1 said:
I habe another Problem:
After some reboots all Widgets and shortcuts in homescreen are gone. Die a fresh installiert of with Rom with pa gapps full package for 4.4.2
Click to expand...
Click to collapse
I'm... not sure what to say about that. Perhaps try a third party launcher, one that will allow you to save the layout...
I have not had this problem.
arrrghhh said:
I'm... not sure what to say about that. Perhaps try a third party launcher, one that will allow you to save the layout...
I have not had this problem.
Click to expand...
Click to collapse
i reinstalled and redownloaded the carbon rom twice. nothiing helped. the stange thing is, that the google experience launcher saves the homescreen layouts sometimes after a reboot and sometimes everything is gone. the same gapps package with cm11 works without any problems on my phone. i like some of the acarbon features, but this whole bugs are annoyiing me right now... :/
pujdo1 said:
i reinstalled and redownloaded the carbon rom twice. nothiing helped. the stange thing is, that the google experience launcher saves the homescreen layouts sometimes after a reboot and sometimes everything is gone. the same gapps package with cm11 works without any problems on my phone. i like some of the acarbon features, but this whole bugs are annoyiing me right now... :/
Click to expand...
Click to collapse
Use what works for you.
i just reflashed cyanogenmod 11 and noticed the same bug with disappearing shotcuts on homescreen. it was complete empty after a reboot (only the icons near the menu button, there phone, text messaging, camera is on stock, are still there). this happens random and firstly widgets are gone and after ths the shortcuts after a other reboot. very strange, this even happend on m new fresh install. also some times my phone wont get past boot loader unlocked message, then i have to hardreset it. seems relly strange... any ideas
pujdo1 said:
i just reflashed cyanogenmod 11 and noticed the same bug with disappearing shotcuts on homescreen. it was complete empty after a reboot (only the icons near the menu button, there phone, text messaging, camera is on stock, are still there). this happens random and firstly widgets are gone and after ths the shortcuts after a other reboot. very strange, this even happend on m new fresh install. also some times my phone wont get past boot loader unlocked message, then i have to hardreset it. seems relly strange... any ideas
Click to expand...
Click to collapse
are you using/have been using/have some app for the purpose of storage swapping? eg. app2sd, link2sd...?
mrvek said:
are you using/have been using/have some app for the purpose of storage swapping? eg. app2sd, link2sd...?
Click to expand...
Click to collapse
nope i never used such tools