Android 2.0.1-r5v0.6
Dead:
==============
After spending some time and looking over this rom and ways to make it work with out any legal issues. The most viable option was to build something like what cynanogen has built. His process takes the proprietary bits (all google apps including sync) and copies them off onto the SD card before doing a update. After the update it copies them back to the newly installed rom. This method basically does a automated backup/restore of your licensed applications. I can't do this for several reasons including that we are supposed to be coming from a 1.5 OS to a 2.0.1, which isn't compatible with the older application set.
Temporarily Offline:
==============
I am sorry to have to do this but we are now having more then just a small handful goofing with this ROM and I need to take this offline while I inspect each of the parts and make sure all licensing is in order since its a bit more then the google Opensource framework. I know that several other ROM creators have not paid much attention to it as I am going to now but I really don't want to upset any IP holders like what happened to Cynanogen a couple months back.
I will put it back up but I want to make sure that I am totally covered and don't have any issues.
version 0.6: download (offline)
==============
-fixed wifi thanks to http://forum.xda-developers.com/showthread.php?t=593620
-Now starts up with Android stock keyboard. (No longer needs HTC_IME.apk for second keyboard)
A few have asked for this ROM so I thought I would put it up here for anyone that wants to contribute to or take from it.
This ROM is only compatible with the Sprint CDMA HTC Hero. It is not finished and still requires some work but its good enough for my day to day use and I am sure others may find the same potential.
This ROM is vanilla android and what it takes to actually get it running on a CDMA phone. It is built off of this GSM variant. I am going to try and work to remove the google bits so that you can use Cynanogens method of extracting your own and then doing a follow up update to install them. My efforts for this is not to build a better rom but to build a cleaner base that has limited to no proprietary IP.
Credits to all on this forum how have helped or contributed in any way to building the roms that are here. I would point out names but there are to many to name. I am positive that anyone that pays attention to this forum will know who you are. I used many parts of these ROM's and many others on XDA to build this one.
This is my first ROM and was primarily made for myself to help me learn how to create a custom ROM.
Here is the link to my blog where I originally posted about this and a video of it booting.
Here is the Youtube video of it booting: http://www.youtube.com/watch?v=tRTh-rXKe-E
*Warning*: Don't attempt to flash this ROM onto anything else unless you know what you are doing! I am not responsible for any device malfunctions or "Bricks".
Notes on Installing:
- Run a Nandroid backup before you do anything.
- Make sure you do a full wipe first. (Sorry )
- Run the update zip found * Version 0.6 *(offline) from the recovery console.
To get the HTC keyboard installed: (Now Optional as of Version 0.6)
- Follow the instructions here.
Things that don't work:
- Gallery some times has issues.
- Camera
- Wired or Wireless Tethering (Now Testing)
- Orientation
- Trackball light
- Trackball click (Rolling and moving are fine)
- (Let me know if something else needs to go here.)
Possible issues that are not repeatable:
- speaker not working on out bound calls? I made 30 test calls to my home phone and was not able to replicate this issue. Needs to be verified (see here)
Awesome! Thanks! disregard my PM lol.. Great timing.
VoXHTC said:
Awesome! Thanks! disregard my PM lol.. Great timing.
Click to expand...
Click to collapse
LOL I was just getting to replying to you!
im trying it now nice work
Let me know if any of you have issues flashing. I still have it all right here in front of me if I need to make a change.
FYI: The first boot takes for ever as it registers all the APKS.
i just get the HTC_IME fource close i installed the one from the site like you said and installed it and i get this
thorracing1 said:
i just get the HTC_IME fource close i installed the one from the site like you said and installed it and i get this
Click to expand...
Click to collapse
So you installed both the HTC_IME.apk and the Clicker.apk? Did you do a adb push or a adb install?
Try and go into settings --> Language & Keyboard --> Touch Input --> Text Input?
I think its a force of habit with out really thinking to go there and calibrate but just going there may help.
Try that and let me know.
i just flashed it and pushed the keyboard and calibration app through adb and all is well. its working awesome. Thanks!!!
2.0t03speed said:
i just flashed it and pushed the keyboard and calibration app through adb and all is well. its working awesome. Thanks!!!
Click to expand...
Click to collapse
Awesome, keep the feed back coming as you have it!
please take note orientation doesnt work. please put in first post.
otherwise, great work!
should i do adb install or adb push?
blankd3ckskat3r said:
please take note orientation doesnt work. please put in first post.
otherwise, great work!
Click to expand...
Click to collapse
Got it listed now, that one bugs me... Must have been to worried about building this to remember it.
BTW thanks for the feed back!
thorracing1 said:
should i do adb install or adb push?
Click to expand...
Click to collapse
I would do an install or transfer them to your SD card and grab a app like Astro from the market to install them. Don't worry we will get you worked out.
dchadwick said:
Got it listed now, that one bugs me... Must have been to worried about building this to remember it.
Click to expand...
Click to collapse
lol well its a common problem, cant wait for a fix. really like what you did with this build
dchadwick said:
I would do an install or transfer them to your SD card and grab a app like Astro from the market to install them. Don't worry we will get you worked out.
Click to expand...
Click to collapse
Not able to get a working Keyboard Now I'm stuck in a boot loop. Tried installing through droid explorer.. no go.. tried installing from astro ..no go.. now it loads lockscreen.. dead... reboot..rinse and repeat
removed SDcard.. boots now trying to push.. but where do I push the apk files to?
blankd3ckskat3r said:
lol well its a common problem, cant wait for a fix. really like what you did with this build
Click to expand...
Click to collapse
Thanks, but I really can't take to much credit. Its a "Pick and Pull" from several ROMs. This one actually came from our GSM Brothers and then I used the CDMA tricks in this form to make it work.
I keep watching and playing with the Google Nexus Dumps. I would really like to get one of them up and running.
Based on your posting and replies I assume you are re-using the 2.6.27 kernel like the other roms?
VoXHTC said:
Not able to get a working Keyboard Now I'm stuck in a boot loop. Tried installing through droid explorer.. no go.. tried installing from astro ..no go.. now it loads lockscreen.. dead... reboot..rinse and repeat
Click to expand...
Click to collapse
Wow thats allot in a little space.
What I gather is that it originally booted, then after trying to install via droid explorer and then astro it now just dies after the lockscreen.
I am not sure where to start. I would just say to do a full wipe, then a clean install. Then if you have the sdk try the ADB install method as Cynanogen's post talks about.
I am working on trying to get the stock Android keyboard to work. If we can figure out that then we don't have to mess with the HTC one.
ok i got it i just adb pushed them to system/app works great
obelisk79 said:
Based on your posting and replies I assume you are re-using the 2.6.27 kernel like the other roms?
Click to expand...
Click to collapse
Yeah, actually some of your work if I remember correctly, thats why its got the same issues. My first goal when I built this for my self was to get past the blasted google bits sync loop. The more I worked into it the more I moved on to the 2.0.1 build with some of your stuff in it.
Your welcome to anything I have learned, its really not my work.
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
So, I've just installed Lineage OS on my phone.
Wanted to try a custom rom.
And when I try to connect to my Gear S2 Classic it states in a pop up.
The operating system on your phone has been modified in an unauthorized way.
and is not compatible with the Samsung Gear app.
Check your operating system and try again.
Any idea how to do it anyways?
Installing the safety net fix could help
Angle784 said:
So, I've just installed Lineage OS on my phone.
Wanted to try a custom rom.
And when I try to connect to my Gear S2 Classic it states in a pop up.
The operating system on your phone has been modified in an unauthorized way.
and is not compatible with the Samsung Gear app.
Check your operating system and try again.
Any idea how to do it anyways?
Click to expand...
Click to collapse
Could you solve it ??? I have the same problem.
Adding in to say that I too have this issue with LineageOS and my Gear S2 Classic. I remember someone on XDA offered some other (maybe older?) apks which allowed it to work for a while but now it seems after updating LineageOS to a newer nightly build, the Gear stopped working again. I'm on a OnePlus3 running the December 15th nightly.
Hey any idea ? I have same problem
I have the same problem
Updating your build.prop, change all "samsung" references to "htc" and you'll be able to open the app... I'm still fighting to get it to see my Gear 2, though.
I have it working on my Samsung Note 3 with Resurrection Remix 5.8.5 which is Lineage 14.1.
I also had to change manufacturer and another build.prop entry from samsung to something else (htc in my case) before I could download it from the playstore (got the same message, probably due to Knox not being there anymore and therefore Samsung thinking I have a modified Samsung phone which is true).
After that I think I also had to download from apkmirror com.samsung.accessory_3.1.73.71102-317371102_minAPI15(arm64-v8a,armeabi)(nodpi)_apkmirror.com.apk and com.samsung.android.gearoplugin_2.2.03.17121551-2117121551_minAPI18(arm64-v8a,armeabi,armeabi-v7a)(nodpi)_apkmirror.com.apk
It's working like on a original Samsung Touchwiz Rom now.
And of course you have to reset your watch to connect to your "new" phone.
Best regards
Amber
Hi, the only solution that helped me to resolve this issue is well explained in this post (more than 48 hours trying different solutions):
https://forum.xda-developers.com/gea...cm-rr-t3743138
My 50cts (or 500 words)
I have used the following to be able to connect my Samsung Gear S2 to my rooted Samsung Galaxy S7 running on lineage-14.1-20180214-nightly-herolte
I use TWRP (twrp-3.2.1-1-herolte.img.tar) as recovery manager to install .zip files onto my S7.
I had rooted my S7 by installing the LineageOS su add-on (addonsu-14.1-arm64), but due to SafetyNet issues which prevented my Gear S2 to connect,
I removed it with addonsu-remove-14.1-arm64.
So I installed Magisk (MagiskManager-v5.6.0.apk) to have Root and to hide Root and (part of) the SafetyNet 'Failing',
so Play Store and other programs will not know it is rooted.
I installed the following Samsung apk files to get my Gear S2 working:
com.samsung.android.gearoplugin_2.2.03.18011941N-2118011941_minAPI19(arm64-v8a,armeabi,armeabi-v7a)(nodpi)_apkmirror.com.apk
com.samsung.android.app.watchmanager_2.2.20.17113061-2117113061_minAPI18(nodpi)_apkmirror.com.apk
com.samsung.accessory_3.1.80.80109-318080109_minAPI15(arm64-v8a,armeabi)(nodpi)_apkmirror.com.apk
Via Magisk Hide option I have hidden root from the Samsung Gear application so it would not abend with the infamous "your device has been tampered with..." error
Finally you need to edit the /system/build.prop file and change all 6 occurrences of samsung into [email protected] (or htc if you prefer that),
so the application does not realize the hardware is in fact a Samsung and therefore not running the stock ROM, the bluetooth connection
to the Gear S2 will fail if build.prop contains samsung.
(I use Total Commander editor to edit the build.prop file but I think any editor will be able to do that if you are rooted.
and last but not least make sure the permissions of the build.prop file are -rw-r--rr or 644 in Linux terms because the Lineage ROM
will not boot if the permissions are not 644).
I installed the Samsung Health application from the play store and that seems to work fine.
MuSzAr said:
Hi, the only solution that helped me to resolve this issue is well explained in this post (more than 48 hours trying different solutions):
https://forum.xda-developers.com/gea...cm-rr-t3743138
Click to expand...
Click to collapse
The link you posted is giving a 404 error (probably because it has "..." in the name instead of the full thread name)--would you please post the full name of the thread so I can search for it?
Thanks
samej71 said:
The link you posted is giving a 404 error (probably because it has "..." in the name instead of the full thread name)--would you please post the full name of the thread so I can search for it?
Thanks
Click to expand...
Click to collapse
Hi,
This is the right link : https://forum.xda-developers.com/gear-s2/help/gear-s2-gear-manager-touchwiz-romscm-rr-t3743138
But you can search it : "Gear S2 (Gear Manager) works on non-TouchWiz Roms(CM, RR, Lineage etc)"
In case anybody has the same problem, this thread solved all of my issues. I have a Nexus 5 with lineage OS, and I could not get google play store to install the app. It didn't show up in play store on my phone, and online it said the app wasn't available for my device.
Fortunately [B @j to the 4n[/B] has made resigned versions of all three necessary apps (gear plugin, samsung health, samsung accessories) - and the Samsung Gear S3 is working flawlessly again.
https://forum.xda-developers.com/an...d-samsung-gear-app-android-n-samsung-t3547035
And a direct link to the drive folder, just in case: https://goo.gl/WjqOhv
Mirror 1, mirror 2
Thank you very much @j to the 4n.
MuSzAr said:
Hi, the only solution that helped me to resolve this issue is well explained in this post (more than 48 hours trying different solutions):
https://forum.xda-developers.com/gea...cm-rr-t3743138
Click to expand...
Click to collapse
Link not work !
SWAT10101 said:
Link not work !
Click to expand...
Click to collapse
The links for the files are in the post right above yours.