Hi, I am a relative newbie to ROM flashing and the like. Additionally I dont have a very deep computer knowledge base. I have rooted my Samsung Captivate and have flashed a ROM (which flashed properly, but didn't quite work). I have three questions about ROM usage and such:
1. I know kernels basically add aspects to the ROM you are running, but when should you flash these? How do you flash them (same process as with ROMs? do you just do it over-top of the Rom you currently have loaded? etc...)
2. If a newer version of the ROM you have running comes out, do you have to start over and completely wipe the device over again and do the whole process from start, or can you load a newer version of your current ROM over the one you have?
3. I have been hearing/reading about some problems with the Android Market disappearing on certain ROMs when the market updates, how can i avoid this/fix this?
Thanks. Sorry the basic/stupid questions.
1. Yes
2. There are WIPE versions and NO WIPE version. Usually you can use the NO WIPE version and keep everything. But sometimes if the roms are too different you get problems and errors, then it is recommended to flash a WIPE version.
3. Hm did not experience this yet, but there are fixes somewhere .
Whats up... No question is a stupid one buddy.... (Sometimes )
To answer your first question about kernels. Flashing kernels aren't a must. You don't have to flash them really, unless there is a need. Kernels for the most part can often change the way Android handles stuff like memory management, battery resources and even multitasking. They change (tweak) the way the Android OS itself interacts with the phones hardware. That's all a kernel is really. So read up on them before flashing them because each has their advantages and disadvantages. For example, the kernel I use gives me a good RAM boost and much better battery life but it suffers on the multitasking side and I have to do other stuff to compensate for that. That's how it is. As far as flashing them is concerned. That depends. Usually, you just flash them through recovery (Like a ROM) but I would suggest you follow the instructions they give you (if it exists).
Your second question is simple. Just follow the instructions they give you for installation. Some ROMS require a full wipe and others don't. It just depends on the ROM. When in doubt, follow the instructions (again if it exists).
Your third question is a weird one, I've never heard about that really. BUT.... Some ROMS may or may not include the GAPPS applications (Google Apps).
If the ROM you flash doesn't have Google Apps built in, it would literally be missing. You would have to flash it separately. Usually in those cases though, at the download location for that ROM, they would also provide links for GAPPS zip files to flash separately so you can have the option to go with Android Market, Gmail and such OR you can use an alternative. Short of that..... never heard of that issue before..... If the issue is happening after the Market app updates, in that case it might be some type of ROM issue, you'll probably have to somehow get the updated Vending.apk (Android Market) remove/backup the original and reinstall it manually (the way you would a regular apk). I'm guessing though....
Don't you just love research........
Thanks. And now, inevitably, answers lead to more questions.
With regards to kernels, how do I know which one's do what, are compatible with which ROMs etc. I feel like its the kinda thing that needs a giant database for them, but i know there isn't.
Also, is the process for flashing other .zip files the same (though either Rom manager or a built in Recovery option). For example, a bootanimation.zip?
Ultimately I hate the idea of asking overly simply questions, but I just don't know what I dont know, nor what is supposedly implied. Thanks.
Don't sweat it...... I'm in the same boat so I have no hangups....
I think I know what you mean when it comes to kernels. Ultimately, learning about kernels requires a lot of reading in many forums (Just like this one)... Why?.... Because in many instances the persons posting the kernels might not always give you an exact breakdown on exactly what it does..... so I understand. Your best bet would be scanning XDA. I've found all sorts of really excellent kernels lying around and the devs here love documentation so there is a good chance you'll know what it does...
You could also try DroidBasement: http://droidbasement.com/db-blog/
They actually have just what you wanted, a database....kind of. They have a very large variety of kernels for different devices so its a good place to start as well.
They also tend to do a breakdown of what each kernel is capable of, the device it should be used on and so on.
About flashing zip files. Generally speaking, most zip files are flashed through recovery but its not written in stone. Following the instructions concerning said zip files are always very important. Always look for instructions before you do so at least at first. In the case of bootanimation.zip.... They are not always flashable. But if it is flashable, you can flash it through recovery which would be the best method....
If you want though, you can replace the original bootanimation.zip file with the new one manually, once you have root and some type of root explorer (for example RootExplorer for Android).
Generally, the boot animation directory is usually, /System/Media so you can check to see if its there and if it is, just backup the original and replace it with the new one.... That should work... Always nandroid before doing so though.... before doing anything really....
Thanks. I actually had a question about nandroid but forgot. Basically, what is it. I realize contextually that it's a backup program and apparently works through the recovery menus. I read a ROM flashing step-by-step that mentioned it but couldnt figure out where to get it (not in the market unlike Ti-bu which i use currently).
Nandroid is a backup program that basically creates a flash image of your phone... If you've ever heard of "Ghosting" or "Imaging" a Hard Drive, its exactly the same thing.
Its really as good as it gets as far as data backup is concerned. Its also a low level backup, so even file structures would be recorded.. In other words, you can completely screw up your phone (file partitions everything!!!!) but once you can boot to recovery, your phone can be restored. That's why its so important because its your safety net....
Its not something that you can install like an apk, so its not in the market.
You would have to flash a custom recovery. If you have one already, it should be located in one of the menus (It changes depending on the type (brand) of recovery).
If you don't see the option in your recovery then its probably not custom and you're going to have to do some digging on these forums and maybe a bit of googling for instructions on exactly how to do so. Because it could change from device to device.
Nandroid also allows you to backup your sd-ext partition as well, so if you switch cards, you can restore to another card.... Its really incredibly handy and I wouldn't suggest you do anything until you can create nandroid backups....
Now, I'm having an interesting problem I posted this same thing in general Captivate forums but maybe someone who is looking at this/answering me knows. here's what i posted there:
have a Captivate that I recently flashed Di11i's 7.1.1 to, before that I had flashed my first ROM which was Serendipity 6.2. Both times I have found that I don't get incoming calls. People calling me get 2-3 rings, and then a traditional "busy signal" sound. On my end, either the phone vibrates once but the screen doesnt change from whatever screen I'm on. Or, The screen goes black like its going to the incoming call screen, but the black screens only flashes and goes away, as does a force close message box that goes away quickly without me clicking it.
Everything else on my phone works as far as I can tell, I've been running my current ROM for about 5 days without issues other than this one. This same exact problem also happened when I flashed Serendipity 6.2 (which I only kept for like a day because of this problem)
Ok....I currently use a G1 and most of my experience has been on HTC Devices. I'm not sure of how to reply to this as I have never really modded Samsung devices before. So I'm not really familiar with software and hardware differences (Like Bootloader, Recoveries, Radios and such). But based on what you're describing.... It sounds like a ROM or maybe a radio issue. Maybe its an issue with the phone app itself. If the app is somehow buggy then thats exactly what would happen. When the phone rings the phone app would try to run but then force close....
I'm guessing here, but it could also be a radio issue because you're getting a busy tone as well which is not good. Maybe the ROM requires a specific Radio version BEFORE its flashed.... Check the source of the download and determine if it requires a specific Radio version.
In my experience though, if the correct radio version isn't used for a ROM that requires it, the phone just won't boot..... but then again, I don't know what would happen on a Samsung Captivate.... Not sure if I can help on this one because I don't have any info on that type of hardware. I don't own one you see.....
What about if you found out a new kernel isn't as good as the old kernel, how would you go on to take away the new kernel to replace it with the old kernel? Is it the same process or even harder?
vlen22 said:
What about if you found out a new kernel isn't as good as the old kernel, how would you go on to take away the new kernel to replace it with the old kernel? Is it the same process or even harder?
Click to expand...
Click to collapse
NOW THIS IS ANNOYING..
u have to flash ur rom again..
but fortunately u dont need to do and wiping data or partitioning sd card.. jus flash rom..
Its not something that you can install like an apk, so its not in the market.
zeemar007 said:
NOW THIS IS ANNOYING..
u have to flash ur rom again..
but fortunately u dont need to do and wiping data or partitioning sd card.. jus flash rom..
Click to expand...
Click to collapse
The rom kernel that I downloaded, or flashing clockwork recovery mod? Like adrenylyne's kernel for the thunderbolt.
EDIT: Never mind, I found out. I didn't mean any harm if MY POST was annoying.
If you have two kernels, in a flashable zip, you can just flash them over each other to exchange them (turn off any modification the kernel did befor though, like lagfix).
New question, I had an app (quick office) that came on my captivate. Now that I've flashed di11i's 7.1 I don't have it anymore. This is particularly peculiar because all the other native apps are still here:samsungs media player from example. How do I go about getting this missing app back on my phone. I have all the backup files on my computer so I should have the .apk (although I'm not entirely sure how to install those properly) thanks
Sent from my SAMSUNG-SGH-I897 using XDA App
Hello there are rom custom for my sm-g350 pls ?
Izuna30 said:
Hello there are rom custom for my sm-g350 pls ?
Click to expand...
Click to collapse
1st this is i8260/i8262 section not sm g350
2nd this is dev section not Q&A
ngoralph said:
1st this is i8260/i8262 section not sm g350
2nd this is dev section not Q&A
Click to expand...
Click to collapse
Pretty sure this is q&a
Sent from my GT-I8262 using XDA Free mobile app
frost245 said:
Pretty sure this is q&a
Sent from my GT-I8262 using XDA Free mobile app
Click to expand...
Click to collapse
afaik it was moved as i have reported it
Gotta get this working!
Hello everyone, I'm new to this forum, although I have spend a big amount of time here (before registering), reading through posts about customizing ROMs, etc.
First things first:
- I have a Samsung Galaxy Core Plus G350 (or G3500 whatever suites you), and I would like to customize it's stock ROM, no rooting involved. I did manage to customize, or I should say minimize, my stock ROM for my Samsung Galaxy Xcover 2 (S7710), rooted it, changed lot's of things, just to get rid off unwanted apps, services and maximize performance. And that worked out pretty well .
Being I'm a guy who likes things to be neat (I'll get to that in a sec ), and pretty much as close to factory build as it can be, I'm not trying to do anything flashy with my G350, just want to remove stupid apps and that's it.
When I said neat, I meant Odin flashing ROM neat. I prefer it to CWM Rom installing technique (although this is clean as well, one would have to have a memory card, memory card reader (or working USB drivers if one has to transfer files directly to the phone), CWM Recovery Firmware (no support for G350), and compatible Custom ROM...you get the picture, not much of a trouble, but a hassle if some of the components are missing....Odin flashing... clean and easy, anyone can use it.
My problem is:
After completing all modification, my system.img file appears with a lock, when I compile it. I'm not sure about the memory allocation, I did calculated it correctly ( i hope ) but that shouldn't be a problem, my main problem is the stupid lock on system.img file icon, before I compress everything to tar and checksum it. Ofc the flashing fails and my best guess its because of that lock in the icon, and Odin stops on system.img file. Does anyone know why is this happening, I didn't have any issues with Xcover's ROM packing, every time I finish with the modification in Xcover system.img file, unmount the file, and everything is fine. Even the flashing part.
I'm packing everything in Ubuntu 14.04 ...I am familiar with linux base systems but I ain't a wiz and flashing in Win 7.
Does anyone know the solution to this, I'm doing something wrong for sure, or I'm overlooking something, any help is very welcome.
Sorry for this extensive text and bad English (not my native language), I figured someone would appreciate some info.
Best regards.
AlexInHell said:
Hello everyone, I'm new to this forum, although I have spend a big amount of time here (before registering), reading through posts about customizing ROMs, etc.
First things first:
- I have a Samsung Galaxy Core Plus G350 (or G3500 whatever suites you), and I would like to customize it's stock ROM, no rooting involved. I did manage to customize, or I should say minimize, my stock ROM for my Samsung Galaxy Xcover 2 (S7710), rooted it, changed lot's of things, just to get rid off unwanted apps, services and maximize performance. And that worked out pretty well .
Being I'm a guy who likes things to be neat (I'll get to that in a sec ), and pretty much as close to factory build as it can be, I'm not trying to do anything flashy with my G350, just want to remove stupid apps and that's it.
When I said neat, I meant Odin flashing ROM neat. I prefer it to CWM Rom installing technique (although this is clean as well, one would have to have a memory card, memory card reader (or working USB drivers if one has to transfer files directly to the phone), CWM Recovery Firmware (no support for G350), and compatible Custom ROM...you get the picture, not much of a trouble, but a hassle if some of the components are missing....Odin flashing... clean and easy, anyone can use it.
My problem is:
After completing all modification, my system.img file appears with a lock, when I compile it. I'm not sure about the memory allocation, I did calculated it correctly ( i hope ) but that shouldn't be a problem, my main problem is the stupid lock on system.img file icon, before I compress everything to tar and checksum it. Ofc the flashing fails and my best guess its because of that lock in the icon, and Odin stops on system.img file. Does anyone know why is this happening, I didn't have any issues with Xcover's ROM packing, every time I finish with the modification in Xcover system.img file, unmount the file, and everything is fine. Even the flashing part.
I'm packing everything in Ubuntu 14.04 ...I am familiar with linux base systems but I ain't a wiz and flashing in Win 7.
Does anyone know the solution to this, I'm doing something wrong for sure, or I'm overlooking something, any help is very welcome.
Sorry for this extensive text and bad English (not my native language), I figured someone would appreciate some info.
Best regards.
Click to expand...
Click to collapse
As far as I know, the lock shows, that you don't have the write permission on this file
Sent from my SM-G350 using XDA-Developers mobile app
Q&A for [ROM][2.3.6] AEON v1.4SL STABILITY AT ITS FINEST
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][2.3.6] AEON v1.4SL STABILITY AT ITS FINEST. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Where to go from here
Not sure what happened, hope this didn't get posted twice.
Hi,
I am still happily using the Samsung Infuse 4G, and was running the stock GB 2.3.6. No real issues, and although starting to get a sense of it being dated was having no issues and in no rush to go out and upgrade. However, we recently purchased a 2015 Subaru Legacy with their Starlink multimedia system. The Infuse, as it was with the stock GB had no problems connecting via BT for phone and audio functionality. But, the car system reports that the phone is not compatible for messaging. In my endeavors to understand why, I thought, maybe incorrectly, that GB does not support the MAP profile.
So, that led me to, is it possible to add that, and how do you do it, or is it time to upgrade? Flash a new ROM? I can't seem to find much on the specific issue I am trying to resolve and if a new ROM would fix it, but since the phone is way out of warranty I decided to try rooting and flashing a ROM. I am new to this so I went with the Aeon 1.4 ROM based on GB 2.3.6 (I think), hoping that it was a bit less risky. Everything went well and seems to be working fine. But, it did not fix the messaging issue with the car. I assume because it is really still GB.
Am I going about this wrong? Would a flash up to ICS or beyond possibly do it? I am not totally against a new phone, but till now I wasn't even thinking about a new phone. Suggestions? Which ICS, or other ROM would you recommend? Thanks all.
Hi there,
mainwheel said:
Would a flash up to ICS or beyond possibly do it? I am not totally against a new phone, but till now I wasn't even thinking about a new phone. Suggestions? Which ICS, or other ROM would you recommend? Thanks all.
Click to expand...
Click to collapse
I think your car requires the newest bluetooth protocol (4.0), something that is primarily hardware based.
I could be (and hopefully am) wrong here, but the only way to find out is to do a ROM walkabout.
ICS is out right off the bat, as bluetooth was borked in that version (IIRC). You'll need to upgrade to that in the process anyway, as CWM for this device doesn't like drastic changes.
I am biased, but I would try CarbonROM 4.4.4 (the latest, unofficial build) or at the very least CM 10.1. The former would have the best chance of support (being latest firmware available), but it may be overkill for your situation (newer versions = harder on battery life).
So I would try CM 10.1 after stepping up to ICS (having done a full nandroid before all this), and if the car still refuses to connect, try Carbon. Then you may be able to prove me wrong.
Hope this helps.
Sent from my MeMO Pad 8"
joel.maxuel said:
Hi there,
I think your car requires the newest bluetooth protocol (4.0), something that is primarily hardware based.
I could be (and hopefully am) wrong here, but the only way to find out is to do a ROM walkabout.
ICS is out right off the bat, as bluetooth was borked in that version (IIRC). You'll need to upgrade to that in the process anyway, as CWM for this device doesn't like drastic changes.
I am biased, but I would try CarbonROM 4.4.4 (the latest, unofficial build) or at the very least CM 10.1. The former would have the best chance of support (being latest firmware available), but it may be overkill for your situation (newer versions = harder on battery life).
So I would try CM 10.1 after stepping up to ICS (having done a full nandroid before all this), and if the car still refuses to connect, try Carbon. Then you may be able to prove me wrong.
Hope this helps.
Sent from my MeMO Pad 8"
Click to expand...
Click to collapse
Thanks very much for your reply.
Being a hardware issue is something I have considered, but not knowing enough to understand why it might work virtually flawlessly for phone and audio streaming in the car, I was hopeful the hardware would support additional Bluetooth profiles, that are added with a new ROM. But then again, I would not be surprised to do the walkabout and end up at the store for a new phone in the end anyway.
I will be looking for an ICS ROM, but it sounds like it doesn't matter which one I use because I won't be staying there?
I have done, and will do again, backups, but I am little unclear on a few things. CWM is on the phone, but I actually used ROM Manager for the flashing I've done. Are they the same thing? It uses CWM. Also, I've seen various references to making sure the phones identity (not sure that's the right term) is saved, and I take that to mean that after flashing the phone may no longer be able to access phone carrier service. Is that a real possibility? And, is it necessary to remove the SD card? Thanks again.
mainwheel said:
Thanks very much for your reply.
Being a hardware issue is something I have considered, but not knowing enough to understand why it might work virtually flawlessly for phone and audio streaming in the car, I was hopeful the hardware would support additional Bluetooth profiles, that are added with a new ROM. But then again, I would not be surprised to do the walkabout and end up at the store for a new phone in the end anyway.
I will be looking for an ICS ROM, but it sounds like it doesn't matter which one I use because I won't be staying there?
I have done, and will do again, backups, but I am little unclear on a few things. CWM is on the phone, but I actually used ROM Manager for the flashing I've done. Are they the same thing? It uses CWM. Also, I've seen various references to making sure the phones identity (not sure that's the right term) is saved, and I take that to mean that after flashing the phone may no longer be able to access phone carrier service. Is that a real possibility? And, is it necessary to remove the SD card? Thanks again.
Click to expand...
Click to collapse
I would recommend Entropy's ICS build, which I have a mirror of, accessed from my signature link.
ROM manager loads CWM (same author, ROM manager is IIRC just the Play Store delivery mechanism for CWM), so once you have CWM, you are good to go for your walkabout.
Yes, you want to make sure to back up your IMEI information first, because that stuff can get lost, which if lost, will deny you access to your carrier. There is a way to retrieve it if lost on this device, but an ounce of prevention is worth a pound of cure. Check the CM10.x thread on instructions how to flash (with links to the IMEI backup).
No need to remove the SD card, but if you don't need it for a flash, I would remove it anyway (or back up it's contents to your PC first - in case in the unlikely event - I'm paranoid about those things - CWM goes a little liberal with the factory reset).
Hope this helps.
joel.maxuel said:
I would recommend Entropy's ICS build, which I have a mirror of, accessed from my signature link.
ROM manager loads CWM (same author, ROM manager is IIRC just the Play Store delivery mechanism for CWM), so once you have CWM, you are good to go for your walkabout.
Yes, you want to make sure to back up your IMEI information first, because that stuff can get lost, which if lost, will deny you access to your carrier. There is a way to retrieve it if lost on this device, but an ounce of prevention is worth a pound of cure. Check the CM10.x thread on instructions how to flash (with links to the IMEI backup).
No need to remove the SD card, but if you don't need it for a flash, I would remove it anyway (or back up it's contents to your PC first - in case in the unlikely event - I'm paranoid about those things - CWM goes a little liberal with the factory reset).
Hope this helps.
Click to expand...
Click to collapse
Thanks Joel. I have now installed Entropy. Don't know whether everything else is working, but I do know that I can not connect to my wifi. Keep getting "authentication problem." I see that it is a known problem, but I'm not finding a solution. Not quite ready to go the next step (time constraint), so I'm hoping there is a fix, or at least a workaround. Kind of a bummer not having access to wifi. Any suggestions?
mainwheel said:
Thanks Joel. I have now installed Entropy. Don't know whether everything else is working, but I do know that I can not connect to my wifi. Keep getting "authentication problem." I see that it is a known problem, but I'm not finding a solution. Not quite ready to go the next step (time constraint), so I'm hoping there is a fix, or at least a workaround. Kind of a bummer not having access to wifi. Any suggestions?
Click to expand...
Click to collapse
I wouldn't worry about it. Entropy is just a step-through (because BlueTooth is broken as well) and there are other ways to get the other ROMs onto the device (if they are not there already) such as adb push or MicroSD + Built-in Filemanager App. Higher versions will have that fixed anyway.
Downloadable CM 10.1
joel.maxuel said:
I wouldn't worry about it. Entropy is just a step-through (because BlueTooth is broken as well) and there are other ways to get the other ROMs onto the device (if they are not there already) such as adb push or MicroSD + Built-in Filemanager App. Higher versions will have that fixed anyway.
Click to expand...
Click to collapse
Thanks again Joel.
I don't have a lot on my data plan, so I rely on wifi quite a bit. But for now, not a big deal and will try to upgrade asap. No issues with getting the file to the phone, but I am having some difficulty finding a downloadable CM 10.1 (actually it is 10.2), and a gapps file for it. The XDA forum I went to doesn't work and if I go to the mirror site it tells me the file is too big or something and I'm not able to download. Haven't scoured the internet looking for it, thought I might save some time if you know where I can get it. If not, I'm thinking just try the Carbon ROM, assuming I can find it. I know you recommend CM first. George
mainwheel said:
Thanks again Joel.
I don't have a lot on my data plan, so I rely on wifi quite a bit. But for now, not a big deal and will try to upgrade asap. No issues with getting the file to the phone, but I am having some difficulty finding a downloadable CM 10.1 (actually it is 10.2), and a gapps file for it. The XDA forum I went to doesn't work and if I go to the mirror site it tells me the file is too big or something and I'm not able to download. Haven't scoured the internet looking for it, thought I might save some time if you know where I can get it. If not, I'm thinking just try the Carbon ROM, assuming I can find it. I know you recommend CM first. George
Click to expand...
Click to collapse
Hi George,
My signature link contains the CM10.1 ROM (and Gapps) as well. I had problems with CM10.2 back in the day (wouldn't install), so I would recommend 10.1 over 10.2.
My Dropbox may be exhausted for the day (sometimes it gets like that) but I may have a copy on well, Copy, that I could send if necessary. Just let me know if you have problems downloading from my mirror first.
joel.maxuel said:
Hi George,
My signature link contains the CM10.1 ROM (and Gapps) as well. I had problems with CM10.2 back in the day (wouldn't install), so I would recommend 10.1 over 10.2.
My Dropbox may be exhausted for the day (sometimes it gets like that) but I may have a copy on well, Copy, that I could send if necessary. Just let me know if you have problems downloading from my mirror first.
Click to expand...
Click to collapse
Joel,
Maybe I'm just missing something. Not having a problem downloading, I'm having a problem finding the files to download.
The only link I find (it's the link that says something about development files?) takes me to the XDA CM 10.2 forum where I wasn't able to get it. Maybe I'm just missing it in your signature links. I see references to Carbon and other stuff. George
mainwheel said:
Joel,
Maybe I'm just missing something. Not having a problem downloading, I'm having a problem finding the files to download.
The only link I find (it's the link that says something about development files?) takes me to the XDA CM 10.2 forum where I wasn't able to get it. Maybe I'm just missing it in your signature links. I see references to Carbon and other stuff. George
Click to expand...
Click to collapse
George,
Each list item has two links....the original source item (thread), and then the dropbox download link (labelled "download") so you are looking for this.
Hope this helps.
joel.maxuel said:
George,
Each list item has two links....the original source item (thread), and then the dropbox download link (labelled "download") so you are looking for this.
Hope this helps.
Click to expand...
Click to collapse
DOH! Didn't even see that there were two links. Sorry about that. Think I've got everything now, and can find it again if I need it. Now to do the work. Thanks for your help. Will let you know how it goes. George
mainwheel said:
DOH! Didn't even see that there were two links. Sorry about that. Think I've got everything now, and can find it again if I need it. Now to do the work. Thanks for your help. Will let you know how it goes. George
Click to expand...
Click to collapse
Hi Joel,
Got it upgraded to CM 10.1. All seems well. Unfortunately, it did not fix the compatibility problem with messaging and our car, as you correctly suggested might happen. Is there anything about Carbon that gives you reason to think it might work? As I said in the original post, I made some assumptions about the problem (Bluetooth MAP profile based on some reading), and that might be a software fix. But, of course, I may be completely wrong about it. Thanks. George
mainwheel said:
Hi Joel,
Got it upgraded to CM 10.1. All seems well. Unfortunately, it did not fix the compatibility problem with messaging and our car, as you correctly suggested might happen. Is there anything about Carbon that gives you reason to think it might work? As I said in the original post, I made some assumptions about the problem (Bluetooth MAP profile based on some reading), and that might be a software fix. But, of course, I may be completely wrong about it. Thanks. George
Click to expand...
Click to collapse
Hello again George,
Nothing about Carbon in general, but KitKat, yes...
Android 4.4 support for two new Bluetooth profiles to let apps support a broader range of low-power and media interactions. Bluetooth HID over GATT (HOGP) gives apps a low-latency link with low-power peripheral devices such as mice, joysticks, and keyboards. Bluetooth MAP lets your apps exchange messages with a nearby device, for example an automotive terminal for handsfree use or another mobile device. As an extension to Bluetooth AVRCP 1.3, users can now set absolute volume on the system from their Bluetooth devices.
Click to expand...
Click to collapse
Gone this far, might as well give it a shot. :fingers-crossed:
joel.maxuel said:
Hello again George,
Nothing about Carbon in general, but KitKat, yes...
Gone this far, might as well give it a shot. :fingers-crossed:
Click to expand...
Click to collapse
I guess it couldn't stay easy. My attempt to install CARBON (two different download versions) failed, I am getting an error I don't understand.
First, when I go to wipe dalvik I get E: unknown volume for .... (/sd-ext) I can not read it very well because of the background image. Where I put the ... it looks like path.
Then
This ROM uses an imcompatible partition layout
Your /data will be wiped upon installation
Run this update.zip again to confirm install
Then
assert failed: run_program("/tmp/updater.sh") == 0
E:Error in /sdcard/CARBON-KK-NIGHTLY-20141102-0915-infuse4g.zip
(Status 7)
Installation aborted.
Any ideas what this means? I can reload CM 10.1, so I am not bricked or anything. I appreciate your help.
I did try to get some help from the IRC forum at CARBON, but haven't gotten any replies.
George
mainwheel said:
I guess it couldn't stay easy. My attempt to install CARBON (two different download versions) failed, I am getting an error I don't understand.
First, when I go to wipe dalvik I get E: unknown volume for .... (/sd-ext) I can not read it very well because of the background image. Where I put the ... it looks like path.
Then
This ROM uses an imcompatible partition layout
Your /data will be wiped upon installation
Run this update.zip again to confirm install
Then
assert failed: run_program("/tmp/updater.sh") == 0
E:Error in /sdcard/CARBON-KK-NIGHTLY-20141102-0915-infuse4g.zip
(Status 7)
Installation aborted.
Any ideas what this means? I can reload CM 10.1, so I am not bricked or anything. I appreciate your help.
I did try to get some help from the IRC forum at CARBON, but haven't gotten any replies.
George
Click to expand...
Click to collapse
There's this tutorial (section 27), but what may be happening is a drastic change in ROM's for CWM (which falls under what status 7 error scope - along with corrupted IMEI, etc).
My upgrade path long ago (coincidentally) was Stock -> CM9 -> CM10.1 -> Beanstalk 4.4.2 -> CarbonROM 4.4.4.
You can, however cheat, by disabling voodoo lagfix in CWM settings. Otherwise, you may need to find the oldest CarbonROM Kitkat you can grab (4.4.2), to make that last (small) jump to 4.4.4.
If still doesn't work, roll back to CM10.1, make sure everything is order (including calling), and try again.
joel.maxuel said:
There's this tutorial (section 27), but what may be happening is a drastic change in ROM's for CWM (which falls under what status 7 error scope - along with corrupted IMEI, etc).
My upgrade path long ago (coincidentally) was Stock -> CM9 -> CM10.1 -> Beanstalk 4.4.2 -> CarbonROM 4.4.4.
You can, however cheat, by disabling voodoo lagfix in CWM settings. Otherwise, you may need to find the oldest CarbonROM Kitkat you can grab (4.4.2), to make that last (small) jump to 4.4.4.
If still doesn't work, roll back to CM10.1, make sure everything is order (including calling), and try again.
Click to expand...
Click to collapse
Thanks again Joel.
I may have to bag this whole project. Must be a little late doing this. Too much time and trouble searching for files that can't be downloaded. I could not find an early CarbonROM KitKat to download. I could not find a BeanStalk to download. I find links that point to a defunct website. I did finally find a CM11 which I did download, but I did not see a gapps file to go with it, unless I can use any 4.4 gapps. Also, when I run CWM there is no reference to lagfix. I appreciate all the help, but I don't want to take any more of your time. George
mainwheel said:
Thanks again Joel.
I may have to bag this whole project. Must be a little late doing this. Too much time and trouble searching for files that can't be downloaded. I could not find an early CarbonROM KitKat to download. I could not find a BeanStalk to download. I find links that point to a defunct website. I did finally find a CM11 which I did download, but I did not see a gapps file to go with it, unless I can use any 4.4 gapps. Also, when I run CWM there is no reference to lagfix. I appreciate all the help, but I don't want to take any more of your time. George
Click to expand...
Click to collapse
Hi George,
Any 4.4.2 Gapps will work. I am uploading one right now (along with older Beanstalk and CM11)...
https://www.dropbox.com/sh/smohomrdx0oqn76/AACfrsgXTEHhDmVtwEWj6EA5a?dl=0
...it may take an hour for files to appear, so keep posted, if still interested.
Also, another way to disable voodoo lagfix (if not found in CWM) is to create a folder on internal storage called Voodoo, and then a folder inside that called disable-lagfix.
Hope this helps.
joel.maxuel said:
Hi George,
Any 4.4.2 Gapps will work. I am uploading one right now (along with older Beanstalk and CM11)...
https://www.dropbox.com/sh/smohomrdx0oqn76/AACfrsgXTEHhDmVtwEWj6EA5a?dl=0
...it may take an hour for files to appear, so keep posted, if still interested.
Also, another way to disable voodoo lagfix (if not found in CWM) is to create a folder on internal storage called Voodoo, and then a folder inside that called disable-lagfix.
Hope this helps.
Click to expand...
Click to collapse
Thanks Joel. I appreciate the help and will try to make some time to install these files. Will let you know. George
joel.maxuel said:
Hi George,
Any 4.4.2 Gapps will work. I am uploading one right now (along with older Beanstalk and CM11)...
https://www.dropbox.com/sh/smohomrdx0oqn76/AACfrsgXTEHhDmVtwEWj6EA5a?dl=0
...it may take an hour for files to appear, so keep posted, if still interested.
Also, another way to disable voodoo lagfix (if not found in CWM) is to create a folder on internal storage called Voodoo, and then a folder inside that called disable-lagfix.
Hope this helps.
Click to expand...
Click to collapse
Hi Joel,
Unfortunately, none of these 4.4.x versions will install, same error. And placing Voodoo/lagfix/ folder doesn't seem to work either, same error. If the problem is the jump to the next version is too great, maybe an earlier version of something, 4.2 or earlier? George