Related
I made a clean ROM based on the factory ROM for the Lenovo A789, A660 and P700i
Cleaned up ROMs:
- A789_S227_cybermaus_V2 (below)
- A789_S228_cybermaus_V2.1 (further below)
Ported ROMs (ported from P700i):
- A789_ROW_S105_cybermaus_ICS_V3 (further below)
- A789_ROW_S106_cybermaus_ICS_V3.1 (Further below)(also for A660 and P700i)
- A789_ROW_S107_cybermaus_ICS_V3.2 (Further below)(also for A660 and P700i)
The current and advised rom to use is A789_ROW_S106_cybermaus_ICS_V3.21
Based on factory ROM A789_S227_120827, and located in my Dev-Host. It is as close to factory as possible, which I hope will be good for stability. It is a flash-utility ROM, because it also holds the latest preloader, uboot and recovery. Assuming those are OK, followup fixes will be update.zip style.
Summery of changes:
- Rooted the phone with Chainfire SuperSu
- Set to boot in US-english, changed name of ROM
- Added MoreLocale for extra languages in 3rd party apps
- Removed Chinese apps, incl Chinese keyboard, removed SmsReg.apk
- Left Lenovo Security (anti-malware) and Lenovo (Go) Launcher intact
- Added Google GAPPS, Play Store, Maps, etc
- Added MobileUncle toolbox, SManager (root explorer). Titanium backup (free version)
- Added fix for location services
- Added CWMT recovery image (modded from 593cn.com)
- Added Skype, Whatsapp, and some others, as auto-install into userdata upon wipe
- Prepared busybox (you need to run script /system/xbin/installbusybox as root if you want it)
- Replaced bootup animation with clean Lenovo butterfly
- Replaced all some audio files with english named ones (thanks mabuc)
- Caller ID bug still present, sorry
- Just as a reminder, these ROMS have English and Chinese only.
Instructions:
By default, the ROM will not overwrite USERDATA or FAT. If you want a clean slate, first extract empty.userdata.rar and/or empty.fat.rar
- Read bgcngm flash tutorial.
- Read it again
- Start Flash Tool (v3.1222, in my Dev-Host)
- Load scatter file
- Take out USB cable and replace battery
- Press the download button in the flash tool
- Connect the USB cable
- Wait for the flashing to complete
A789_S228_cybermaus_V2.1 (no longer current, Use V3 instead)
Based on factory ROM A789_S228_120913, and located in my Dev-Host. Similar to V2, but newer, and a few extra fixes. It should be noted that the S228 is listed to solve unexpected crashes, so an important update in itself.
I do not have a A789, so it is a blind build. Until I get positive feedback, consider untested. Don't be the first to try if you are not experienced.
Summery of changes:
- Same as on V2, and additional
- Removed 2 more chinese apps that I forgot last time
- Prepared busybox (you need to run script /system/xbin/installbusybox as root if you want it)
- Added a tweak so USB-Debug notification is no longer shown
- Added a tweak so Wifi works on all 14 international channels (rather than only the 11 US ones, may be undone if you set a different locale)
Instructions:
This is a update.zip type ROM. So you need the custom recovery, see post #3,
A789_ROW_S105_cybermaus_ICS_v3.03
Based on P700i_ROW_S105_120920, see this separate post.
A789_ROW_S106_cybermaus_ICS_v3.11
Based on P700i_ROW_S106_121001, see this separate post.
Please note that this ROM I also build for the P700i and A660. See same post.
A789_ROW_S107_cybermaus_ICS_v3.2
Based on P700i_ROW_S107_121221, see this separate post.
Please note that this ROM I also build for the P700i and A660. See same post.
Below:
Post #2: Small review and fix of location services
Post #3: Custom recovery image
Post #4: Root your phone / install GAPPS
Also, many issues for the A789 are similar to those of the A750, so if you have questions, do search that Lenovo A750 thread to.
Thanks
Also thanks to bgcngm for his help, and to jazzor for his help
=================
BTW: Due to new forum rules, resulting in a large number of people that cannot post into developer threads and that subsequently PM me, I open op a new Q&A thread.
I am not going to be policing, so you can post where you like, but I invite everyone to use this new thread for any Q&A, and this thread for ROM releases and deep development talk only.
Consequently, if you PM'ed me, look for your reply in this new thread
Thanks
====================
PS: do drop me a reply if you use or tried it! Or press the 'thanks' button.
So, I got my first glimps at the A789. So to speak. My colleague was holding it while we were audio-skype, so I did not actually see it.
His A789 came with a Etotalk ROM by Dean, which I now suspect is a reworked Smileyvvv ROM with Sony Experia interface. Not bad, but as you know, I am a 'factory ROM' guy. My colleague may also be, because he had already replaced the the SE launcher with GO Launcher, which is the default Lenovo one. Also my colleague said it jammed a few times, which it still has not done on my factory A750 ROM.
Most of the phone worked, but a few tips for others out there:
- The phone still has the Called-ID bug. Even though it is newer 4.0,4. I know some of you claim this is solved on ICS Mediatek, but I still claim it is solved in *some* of the cases, not all, it also depends on how your provider sends the caller ID info. Anyway, you can work around it with the prefixer app as reported before.
- It did not come with the MobileUncle tool, but with the Etotalk tool. Which was not updated for the new MT6577 chip, so it had no Engineer Mode. Install the latest MU tool (version 20120813v2.2.0 its in my Dev-Host), so you get one with MT6577 Engineer mode.
- Recovery Mode was hard to get into. Like the newest A750 preloader, you have to press the power putton *just before* you press both volume buttons. But it did came with the CWMR Touch, though its Touch function was broken, so buttons only. They probably simply tried recovery images of other models, and did not properly build one with the A789 kernel, but it does not matter, it works well enough.
- Location services did not work. Update the phone with the ICS_locationfix_v1.3 update using recovery mode. While you are in recovery, also wipe cache. And finally, go into MobileUncle tool, the MTK Engineer mode, and in location settings, change the NetLoc from MEDIATEK to GOOGLE. Now your location services should work.
Lenovo A789 Recovery
I created a recovery image for the Lenovo A789 based on ClockWorkMod Touch 5.5.0.4. However, I do not own a A789, so until I have reports of it working, consider it untested. You can download it from my Dev-Host: File A789_S22x_recovery_cybermaus.rar
NOTE: It has come to my attention this recovery works well, except the nandroid backup function, which is broken. If you value nandroid backup, install the APKHOT one below.
While doing this, I also found a full APKHOT distro which had what seems to be a CLockWorkMod (non-Touch) recovery in it, so I extracted that and also uploaded it. That too you can download from my Dev-Host: File A789_S22x_recovery_apkhot.rar
Both of them you will have to flash using the flash tool, using bgcngm's excellent manual, and the V3.1222 of the flash utilities and drivers, also in my Dev-Host. If you flashed my V2 ROM, you do not need to do this, as the recovery is already part of that.
Once you have the recovery installed, you can enter it by pressing both VolumeUp/Down while booting the phone. Due to an issue with the preloader, it may be needed to press the power button slightly before both volume buttons. If the phone seems stuck, it means the preloader messed up, remove battery and try again.
Inside the recovery (the Touch variant) you can navigate not only by its physical buttons, but also by screen buttons, and by gestures: swipe up/down for up/down, left for back and right for enter.
The first few people using this, please report your findings, good or bad.
PS: As alwasy, thanks to bgcngm for his unpack utilities, which I used to modify the recovery.img
Lenovo A789 Root; GAPPS, Location DIY
Its been mentioned before, but if you have a working recovery (like above, hopefully), you can always yourself root your phone. Simply install (from inside the recovery) chainfire's "CMW installable ZIP"
Link to his post: (ignore his big red requires root warning)
The file you need is labeled "CWM installable ZIP" at the bottom.
Direct link to the file you need to install via recovery update.zip
And while you are at it: You probably also want to install the latest Google Mobile Services (better known as GAPPS) from CyanogenMod V9:
Explaining wiki from CyanogenMod
The file you need is called gapps-ics-20120429-signed.zip and can be found here
You probably also want to wipe your cache partition after doing this.
To complete this DIY of fixing factory ROM: On Chine phone typically the location services do not work. Update the phone with my A750 V1.3 update using recovery mode. (it works on the A789 because it is a minor update, but *DO NOT* any of the other A750 updates on the A789. I repeat, do *NOT* flash A750 on A789). While you are in recovery, also wipe cache. And finally, go into MobileUncle tool, the MTK Engineer mode, and in location settings, change the NetLoc from MEDIATEK to GOOGLE. Now your location services should work.
Good luck
PS: If either update.zip refuses to install, remember to turn off the checksum and assert checks in the recovery.
And thanks to Chainfire for his work, and the team at CyanogenMod for theirs.
cybermaus said:
Before I can help, please provide some info:
Can you tell me what ROM you have?
Which flash tools did you use to root?
Also, do you have a working recovery?
Click to expand...
Click to collapse
hwonggc said:
I fix the proximity thingy. it's caused by my lousy screen protector. But i've got another bigger problem now. I've accidentally uninstalled the default system home screen. I cant assess anything now. I tried flashing a recovery inside but it still doesn't work as factory. I use SP flash tool v3.1.222.00
---------- Post added at 06:32 AM ---------- Previous post was at 06:18 AM ----------
dont think my recovery is working. Could you please provide me with a working recovery? =(
Click to expand...
Click to collapse
Yes, a recovery is on the todo.
But for now, you did not answer my questions yet:
- Can you tell me what ROM you have? Or had. Original Lenovo Factory, Etotalk-Dean, some other?
- Which flash tools did you use to root? Or rather, which files did you flash using that tool to deal with root. Actually, the fact that you had to root it yourself probably means you had factory ROM, but please confirm.
As stated, I am uploading S221 original to my Dev-Host. Flash that with the flash tool. On short notice, that is all I can do. On longer notice, I will help you, but give me some time.
Edit: In fact: You you already have messed up your recovery, and I do not have a A789 to play with myself, you may be my guinea pig for the recovery build. So I will work on that today. (as today is not a working day for me anyway). If you do not mind being a tester. After all, the damage is already done, and you apparently already know how to flash using the utility.
EDIT: @ hwonggc : Please test recovery in post#3. Just update your post below with results, or PM me. I would like to avoid too many new posts on this while we are testing.
cybermaus said:
Yes, a recovery is on the todo.
But for now, you did not answer my questions yet:
- Can you tell me what ROM you have? Or had. Original Lenovo Factory, Etotalk-Dean, some other?
- Which flash tools did you use to root? Or rather, which files did you flash using that tool to deal with root. Actually, the fact that you had to root it yourself probably means you had factory ROM, but please confirm.
As stated, I am uploading S221 original to my 4Shared. Flash that with the flash tool. On short notice, that is all I can do. On longer notice, I will help you, but give me some time.
Edit: In fact: You you already have messed up your recovery, and I do not have a A789 to play with myself, you may be my guinea pig for the recovery build. So I will work on that today. (as today is not a working day for me anyway). If you do not mind being a tester. After all, the damage is already done, and you apparently already know how to flash using the utility.
Click to expand...
Click to collapse
Yes yes. I had the factory rom. I got the phone just yesterday evening and this afternoon it's half dead already. I use smart phone flash tool to root using a file i got from http://www.fight.org.ua/publications...novo_A789.html. Everything was fine until I deleted the original home UI and the apex launcher also. So there isn't anything I can do. I'm downloading the S223 from some russian site and try, hopefully I can find some luck there. Downloading slowly~ sighhhh.
---------- Post added at 07:49 AM ---------- Previous post was at 07:40 AM ----------
BTW~ i'm willing to test out your rom too! I wouldn't want to sound too demanding, put please please put in the play store will ya?
I posted the custom build, see first post. It may take a while before I can get it uploaded, I am on a bad link.
Also, there have been 20 downloads on the recovery image. Come on guys, someone must be able to provide feedback about it working or not!
A789_S227_cybermaus_V2 ROM is working
Hello
Thanks for Your work.
Your A789_S227_cybermaus_V2 ROM is working.
Simple Flashing and start without problems. Now I must check some functions.
Thx again
basell
Edit:
The 3g connections don't work at first run. After restore they start but in My opinion with less sensitivity (compare to stock rom). It's look like A789 loose some frequency on witch can work.
Edit2:
And they have some strange behavior - After couple min of data connection (on 3G) they disconnect with information - "Restricted access changed" and the same is when I try to choose network manually. After that sometimes they login to 3G sometimes they change to EDGE.
In Stock version (S221) was not this kind of problems.
Edit3:
In place with good 3G signal I have no problem with data transfer.
How Can I check on witch frequency (2100,900,850) I have connected My data transfer?
Thanks for testing
Well, I definitely did not mess with any of the 3G stuff. So if it is true that 3G is less sensitive, then I would claim it is true for the factory S227 vs factory S221, and not directly related to my cleanup of it.
But (sorry to say so) I have learned to take claims of improved or degraded radio sensitivity with a grain of salt, even for the factory ones.
Having said that: Restoring S221 radio into S227 firmware is easy. The radio is separate firmware file, and I can extract the S221, S223 and S227 firmware in a separate file, so you can test. Were you actually using factory S221, or some other?
As to whether it is using 2100, 900 or 850: I can probably figure out how to get that info, *BUT* reality is that your provider most likely has only one frequency anyway. Most, pretty much all, EU providers are on 2100. The phone could not get to 900, simply because your provider does not have that frequency in the air (not for 3G anyway). And 850 is not supported at all on this phone.
Anyway, inside MU utility, engineer mode, bandmode, you can check/set the frequencies that are supported.
But please run a proper test if 3G is really degraded. As stated. it is so often a empty claim, I am somewhat careful to follow it. You want me to extract the 3 versions of firmware files in update.zip files?
Also, what country/vendor are you? please list the MMC and MNC from inside the APN settings.
Hi
If You will prepare this files I can test it tomorrow.
I'm from Poland and I have two frequency on data transfer - 2100 and 900. But I don't know if A789 use only one or change them. The place I'm test the signal is poor and I don't see if I work on 2100 or 900.
If You can, pleas tell me what kind of tests I can do to do that properly
Ok, here they are. update.zip type.
I only have S221 and S227, but the firmware files were indeed different, in more than just their timestamps. Of course, normally I would assume newer is better. So to make it clear: below files only replace the radio&dsp firmware, not the phone firmware.
Try to test honestly for yourself. Same conditions, same place, same time (because network load can make a difference)
It is possible that 3G really is degraded in S227, but as mentioned, I learned to not jump to conclusions just because the network is having a bad day.
WARNING: I retracted the two attachment, because I made a typo in the installer script. While the firmware is for the A789 (MT6577), the installer script is for the A750 (MT6575). Sorry. I will upload the correct ones in a moment.... Anyone that took a copy of these files before Oct 14, delete them!!!
I suspect the install would simply have failed, no harm done, but best to get rid of all copies anyway
BTW: basell, is that why you asked how to install? Really, if you ask for help, you should provide a bit more info. Anyway, I attached newer scripts, if you still want to try.
sorry for My question but :
How to install this firmware?
Like any update.zip on android. Go into recovery (see post #3) and apply the update.zip
i have the problem that the netlocation doesn't work with google maps, i flashed the cyber update 1.3, nothing changed, what should I do now?
And this is on what phone and ROM?
Anyway, to quote myself: "While you are in recovery, also wipe cache. And finally, go into MobileUncle tool, the MTK Engineer mode, and in location settings, change the NetLoc from MEDIATEK to GOOGLE. Now your location services should work."
many thanks, Cybermaus, netlocation works again after your instruction
Hi,
Thank you very much for building the ROM !!
I am using it for 3 days now and I am happy to report no problems with it. Everything works and most important: no more freezes !!!
my A789 came with the Etotalk by Dean ROM which was mostly OK, but was freezing from time to time (some days not at all, other days several times a day - most of the times when hanging up a call or, when trying to do wake it from standby: I was pressing the power button, but the screen would not light up).
Other things I like about this ROM:
- all phone functions work great
- Google Play works perfectly
- is rooted
- it has the Lenovo battery app, which is great! I am not 100% sure if this is the reason, but the battery life went from 1 day to 2 days
- I had no issues flashing it
- CWMT recovery works
Also, so far, I did not experience any 3G issues
I have written a small review of the Lenovo Security app, which you guys may want to put back on your phone if it was cooked out of it.
jman0 said:
Thinking it twice, I've remembered another reason. One of the things I like most about the apkhot rom I'm using is that the external sdcard is mounted on /sdcard and not /mnt/sdcard2, which avoids problems with many apps. I tried one of the newest apkhot roms, based on s227, and none of the tricks to exchange /sdcard and /mnt/sdcard2 worked with it.
Click to expand...
Click to collapse
Well, that is actually an easy change to perform, just change the /etc/fstab.vold
However, if you go into settings->storage, the first option is default write disk. Change it from USB storage(the internal SD) to SD (the external SD)
So no hacking is needed at all.....
I've been running your rom for around 6 hours now. Everything runs fine. The 3G connection worked without much trouble. The only thing I haven't been able to do is performing a backup with the CWM Touch Recovery. So, I've just flashed the recovery I had on the apkhot rom I was using, using Mobileuncle tools, and now I've been able to create a backup.
So far, so good, and I've noticed a slight performance increase, too.
Q&A for CyanogenMod 12.0 for Photon Q
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 CyanogenMod 12.0 for Photon Q. 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!
So far so good for CM12, everything runs really smooth. Only issues are the default text app send button is grayed out and won't let you send but using Google messenger app it works fine. Is there any reason to why the send button wouldn't work?
LTE seems to work well but visually every now and then it seems to disconnect/reconnect but functions fine. And just a quick/dumb question which CDMA subscription should we use, RUIM/SIM or NV as I found info on RUIM/SIM but couldn't really find much on the definition of NV.
I really wanted to know that everybody has no problem at all in logging in Google+ with the latest version of its client.
I'm having trouble the most recent one that I can download from Play Store, : v5.1.0
I had to restore the backed up version of v5.0
I recently got the multimedia dock for this phone and I've noticed that some things don't work. None of the USB ports on the dock seem to interface with the OS, but any peripheral connected by a USB OTG cable (while not in the dock, of course) works just fine. Also, the device doesn't seem to detect that it is in a dock at all; I have it set to daydream when it's docked, but nothing happens.
Does anybody else have these issues? Is there a known or planned solution?
Thanks!
Hei just another quicky:
I had problems with twrp unable to mount /data on encrypted phone. I was never asked for passphrase also it did not detect data was formated as f2fs and assumed ext4.
After factory reset I reformated data and cache to f2fs again (as I think the performance gain is real) and cleanflashed latest cm12 nightly + gapps.
After setting up my phone it became slugish fast again, also battery did drain fast (also the phone did get real hot)
My circumvention so far is limiting Background processes to 2 within Dev options. Since then phone stays much cooler, everything works as expected normal cpu usage shows 2.5/3.2/3.5.
Before that phone was sometimes at 12/9/8 or so and thus bekame unresponsive/sluggish.
Does anyone know the standard count of background processes? Form Q?
Since i did not discover any strange behavior/lags since i switched to only 2 backgroundprocesses anyone knows what kind of usage could result in problems with lower backgroundprocesses?
Thanks in advance!
CM 12.0 nightlies I/O and issues
So I switched over to CM12 because of the ability to switch the filesystems to f2fs. And so far I have seen a pretty decent improvement in the response, speed, and general performance with CM12.
A few issues have come up though:
CM nightly 03232015
-the cLock widget just randomly stopped functioning. Worked for a day or two, then stopped working. I wasn't able to set the alarm and clicking on the time on the home screen does nothing. Disabled cLock and am using the default Deskclock instead (I need to be able to set alarms).
-the messaging app was not working correctly... I was able to receive texts but the send button was greyed out and would not let me click on it. This is both over Wi-Fi and 3G and 4G LTE. Had to revert to 8sms that I was using on CM10...
-the themes are applied inconsistently... not all apps or system dialogs are themed when I use ThemeDIY to create/apply my own theme.
-equalizer doesn't seem to make a big difference...
-doesn't seem to remember wifi logins... keep getting the "sign in to wireless network" notification (I've already signed in)... the sign in page does not open in Chrome, but rather a separate browser or system page that won't offer to save my password (though it does autofill the username)...
-weird issues using adb... even though I've authorized the computer, and have root access on the phone and am running adb root, it won't let me write to certain parts of the file system (I couldn't adb push bootanimation.zip /system/media/bootanimation.zip error was "read-only filesystem")
I know it's a nightly, just wanted to see if anyone else has these same issues and to make sure the developers are seeing this. For the record, I did a wipe and format (since I was going to change the file system,) and this is a clean install of both TWRP and CM12.
Thanks!
---------- Post added at 06:15 PM ---------- Previous post was at 05:58 PM ----------
breakerwaves said:
So far so good for CM12, everything runs really smooth. Only issues are the default text app send button is grayed out and won't let you send but using Google messenger app it works fine. Is there any reason to why the send button wouldn't work?
LTE seems to work well but visually every now and then it seems to disconnect/reconnect but functions fine. And just a quick/dumb question which CDMA subscription should we use, RUIM/SIM or NV as I found info on RUIM/SIM but couldn't really find much on the definition of NV.
Click to expand...
Click to collapse
I didn't know what to use either so I left it on NV. Haven't noticed a difference in signal or call quality or anything. I am guessing since we're on Sprint and there is no SIM card that RUIM/SIM won't work?
Im am currently running on NV too, but with german sim.
To the other problems you have, I don"t have those. Sms works. CLock works, alarms work... I am running without any themes just switched the stock trebuchet launcher to apex. I am also on f2fs.
I also would like to know the difference between NV and RUI/SIM, and which one should be preffered with simcard mod.
kecksk0enig said:
Im am currently running on NV too, but with german sim.
To the other problems you have, I don"t have those. Sms works. CLock works, alarms work... I am running without any themes just switched the stock trebuchet launcher to apex. I am also on f2fs.
I also would like to know the difference between NV and RUI/SIM, and which one should be preffered with simcard mod.
Click to expand...
Click to collapse
I can't speak to the RUI/SIM issue but I don't know how to switch themes off. As far as my SMS and cLocks idk it is possible that I disabled the wrong app I don't like to run more then the bare minimum. As for the theme I ended up downloading a dark theme from the app store which is wonderful looking!! It is called Nicholas' Dark Material. In case you're looking for dark like me.
Do you have issues with the gallery or camera? I think I saw somewhere on the xt897 forum a link to motorola's camera and gallery apps... are you able to change the save location for pictures or no?
I also had an issue where the navigation bar does not render right when I watch full screen video in landscape mode. May have to do with me forcing GPU render under developer options. I'd take it off but I can't remember how I got there lol
---------- Post added at 11:27 PM ---------- Previous post was at 11:21 PM ----------
I cannot set the custom color for notifications in CM12... but there is a post that says the colors were retained on an upgrade from CM11. Well I wiped and did a clean install rather than an upgrade so is there an .xml file or a settings I can edit? I'm comfortable with file manager and editor and adb and shell...
CM 12 update
I have a simple question so if I am not asking it in the right place, I apologize.
If I do one of the CM12 updates (the nightlies) through the Update in the Settings Menu on my phone, does it wipe the phone? Or does it only update relevant system files and keep my apps and data??
nasch007 said:
I have a simple question so if I am not asking it in the right place, I apologize.
If I do one of the CM12 updates (the nightlies) through the Update in the Settings Menu on my phone, does it wipe the phone? Or does it only update relevant system files and keep my apps and data??
Click to expand...
Click to collapse
If you only apply the update, it will not wipe the device. You would have to wipe it manually in recovery. It will apply a so-called "dirty flash" as you are not wiping any partitions.
CM12-->CM12, should be fine. Of course before you report any issues try a clean flash (or if it's a single app FC'ing, try clearing data on that single app).
I'm having tons of trouble using this with Sprint.
When I lock it to CDMA and/or EVDO mode, Logcat shows that it's trying to connect using a C Spire APN. If I lock it in LTE-only mode and select Sprint APN, it gets a good data connection. The APN menu is foolishly disabled for CDMA/EVDO so I cannot correct the issue. Why is it trying C Spire? How can I fix 3g and MMS settings to work?
CM11 worked great in all conditions, and MMS worked out of the box.
I'm trying to flash CM12 on a FreedomPop device and I'm getting the message "This package is for device: xt987,asanti_c; this device is asanti". I was able to flash CM11 from the nightlies page but no luck with CM12 nightlies nor with the CM12.1 that was posted here on XDA.
Any help to flash CM12 on this device? :good:
Alien987 said:
I'm trying to flash CM12 on a FreedomPop device and I'm getting the message "This package is for device: xt987,asanti_c; this device is asanti". I was able to flash CM11 from the nightlies page but no luck with CM12 nightlies nor with the CM12.1 that was posted here on XDA.
Any help to flash CM12 on this device? :good:
Click to expand...
Click to collapse
In the short term you can change the meta-inf file in the update.zip and change the assert line to allow asanti.
In the future, the CM maintainer probably needs to update the source to allow your device... odd that it worked in CM11 but not 12 tho.
Are you going from CM11 to CM12? Even if you clean flashed.
arrrghhh said:
In the short term you can change the meta-inf file in the update.zip and change the assert line to allow asanti.
In the future, the CM maintainer probably needs to update the source to allow your device... odd that it worked in CM11 but not 12 tho.
Are you going from CM11 to CM12? Even if you clean flashed.
Click to expand...
Click to collapse
Thanks for the tip!
First I tried to flash CM12 directly but got the error. Then decided to try with CM11 and it worked so I hoped it would work to update to CM12 but got the same error again.
Just to double check I'm not doing it wrong, this is what I tried to flash:
CM12 (Failed): http://download.cyanogenmod.com/get/jenkins/107228/cm-12-20150417-NIGHTLY-xt897.zip
CM11 (Success): http://download.cyanogenmod.com/get/jenkins/100850/cm-11-20150216-NIGHTLY-moto_msm8960_jbbl.zip
What I understood by reading around is that for CM12 I should use the xt897 file even though it's differently named than the CM11 one (moto_msm_8960_jbbl).
Can you please confirm that I'm using the correct CM12 one?
Thanks
Alien987 said:
Thanks for the tip!
First I tried to flash CM12 directly but got the error. Then decided to try with CM11 and it worked so I hoped it would work to update to CM12 but got the same error again.
Just to double check I'm not doing it wrong, this is what I tried to flash:
CM12 (Failed): http://download.cyanogenmod.com/get/jenkins/107228/cm-12-20150417-NIGHTLY-xt897.zip
CM11 (Success): http://download.cyanogenmod.com/get/jenkins/100850/cm-11-20150216-NIGHTLY-moto_msm8960_jbbl.zip
What I understood by reading around is that for CM12 I should use the xt897 file even though it's differently named than the CM11 one (moto_msm_8960_jbbl).
Can you please confirm that I'm using the correct CM12 one?
Thanks
Click to expand...
Click to collapse
Yes, that's the correct one.
The CM maintainer clearly states the reasoning in the CM12 thread:
kabaldan said:
Please note:
In CM12, the Motorola 2012 msm8960 device line has been de-unified again, so moto_msm8960/moto_msm8960_jbbl builds are dead from now on.
Please check the xt897 device link for new Photon Q builds.
Click to expand...
Click to collapse
arrrghhh said:
In the short term you can change the meta-inf file in the update.zip and change the assert line to allow asanti.
In the future, the CM maintainer probably needs to update the source to allow your device... odd that it worked in CM11 but not 12 tho.
Are you going from CM11 to CM12? Even if you clean flashed.
Click to expand...
Click to collapse
Adjusting the meta-inf to check for "asanti" instead of "asanti_c" worked perfectly. Thanks for your help!
Now I have to find out why after I flash gapps I start to get multiple crashes related to Google Services and Google Apps.
Edit: Well, just in case someone face the same problem in the future. I updated to the latest TWRP recovery directly from their webpage (initially I used Rashr app) and that solved all my problems, including the initial error when flashing CM12 nightly.
Q&A for CyanogenMod 12.1 for Photon Q
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 CyanogenMod 12.1 for Photon Q. 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!
Boot stuck and Bootlooping -fix
Sweet merciful crap. I just got through a 5 hour fight with my Photon Q trying to bring it up to cm-12.1.
In a nutshell, I figured the advise not to dirty flash 12.1 on top of 12 was defunct once it started showing up in the nightlies. Be warned - it is not. Your experience may mirror mine and you'll get stuck at boot.
What's worse is that when I went into TWRP-2.8.6.0 recovery and attempted to do a wipe of data/cache, it started making a mess of my partitions. Not able to mount /data, not able to mount /cache... No matter what order, or selection in the Advanced wipe, it seemed to be making more and more of a brick out of my device as I tried.
I followed some advise I found that suggested newer TWRP versions had problems with wiping on the Photon Q, and to try CWM recovery or stock recovery. Tried CWM to wipe, no dice, similar problems. Spent a good deal of time trying to find the stock recovery somewhere; I think I reached the end of the internet and it's not there.
Then I started trying older versions of TWRP found here:
http://techerrata.com/browse/twrp2/asanti
Then things got really bad. Every one of the ones I tried with "asanti_c" in the name bootlooped (tried about 5 of them). The battery started getting low and I couldn't flash the recovery any more from the bootloader, and it would seem the phone won't take a charge while in bootloader mode. So I had to let it bootloop while it charged, which of course took a long time because all the bootlooping was keeping the battery taxed.
Finally I flashed this one, 'cause I figured my phone was a brick anyway:
openrecovery-twrp-2.2.2.2-asanti.img
It started up. It was also happy to restore/wipe my data, cache, and system partitions. Back to the bootloader, flash back to TWRP 2.8.6.0, install the nightly cm-12.1 and appropriate gapps. This time no errors about partitions, everything seemed clean. Sure enough, boot it up normally, wait about 8 minutes on the flashy Android face, and it does the fold/drop thing and proceeds with the initial boot sequence.
So be careful everyone! I hope at least someone comes here and finds this if they've "Bricked" their photon Q, and that it saves them from the depths of despair that I found myself in! If only I'd have seen this trick in this thread, I would have been back up and running in 30 minutes or less!
Best wishes with your upgrades/recovery!
kabaldan said:
For now, just a test build before the official cm-12.1 nightlies for Photon Q will be enabled.
Download link (cm-12.1-20150405-UNOFFICIAL-xt897): http://d-h.st/2ul
Gapps (use gapps-lpmr1-...): http://d-h.st/users/dhacker29/?fld_id=27426#files
TWRP 2.8.6.0 recovery for xt897: http://d-h.st/lEHx
(feel free to provide mirrors on other/better file hosts)
Device specific source repos:
motorola/xt897: https://github.com/CyanogenMod/android_device_motorola_xt897/tree/cm-12.1
motorola/msm8960_jbbl-common: https://github.com/CyanogenMod/android_device_motorola_msm8960_jbbl-common/tree/cm-12.1
motorola/qcom-common: https://github.com/CyanogenMod/android_device_motorola_qcom-common/tree/cm-12.1
kernel: https://github.com/CyanogenMod/android_kernel_motorola_msm8960-common/tree/cm-12.1
Please note:
Since CM12, the Motorola 2012 msm8960 device line has been de-unified again, so moto_msm8960/moto_msm8960_jbbl builds are dead. Use xt897 specific builds when you go beyond CM11.
GSM users (SIM card mod):
Please switch the Settings>Mobile networks>Preferred network type to 'GSM/WCDMA auto' or 'GSM/WCDMA preferred' from 'Global' for correct modem functionality on GSM networks.
What's new in cm-12.1 for xt897:
Lollipop turned out to be very RAM demanding. 1GB RAM devices seem to be below the limit of what lollipop actually needs.
To overcome this issue, 256MB of RAM has been dedicated to zram (compressed swap living in RAM). Zram can give us a bit more of effectively usable RAM space.
To speed-up the zram operations, kernel has been updated to the latest zram code with support for the fast lz4 compression.
Another new kernel addition is cpu-boost driver that can boost cpu frequency e.g. when input events are happening (touch screen interaction) regardless of cpu governor in use.
Known issues:
- USB audio output (analogue) via USB>audio Y-cable (Motorola Car Dock/EMU audio) is not working correctly yet
- USB audio DACs/sound cards connected as USB OTG peripheral do not work correctly yet
Click to expand...
Click to collapse
I don't know that my posts are even going to be seen because I haven't made 10+ posts here yet and therefore it keeps throwing me to this Q&A thread. Regardless, I will try.
I'm now running the 12.1 4-21 nightly.
After my first initial struggle to get 12.1 installed/running, I found that I didn't actually have a data connection once I got out of wifi range.
Took many trials and lots of time to figure this out. Turns out that some of the AT&T APN's are missing "hipri" which they apparently need to work. Once I added that, I got my data connection.
Now I'm have a problem reliably connecting to AT&T. This wasn't the case with 12.0 at all, connected quickly every time. After a reboot, it keeps cycling trying to connect and quickly failing. I have to fight with it in the network selection settings. Eventually it'll succeed at a manual scan where I can select AT&T, or it will succeed at an automatic selection. This seems odd because when I run an adb logcat, it does seem to be trying to connect to AT&T on its own. So whether it would eventually connect on it's own and the busy work of me fighting with the network selection settings just makes me feel better some how that I'm fixing it, I'm not sure yet.
I can also confirm that the lock page says "No Service" even when the network is connected including data.
I hope these things help someone else out and perhaps lead to a fix. Happy to try stuff out or run a trace if it would help, just let me know.
I had exactly the same issues when trying to flash CM 12.1 (Not able to mount /data, not able to mount /cache... )
Fixed this by manually formatting each partition at one time. I also changed data and cache to f2fs
No need to go with older TWRP
But I still have the connection issues exactly as you describe in your second post.
I'm running Freedompop (on top of Sprint network)
By manually formatting, what do you mean? Did you use TWRP Wipe-Advanced and just select the partitions one at a time? That wasn't working for me for some reason, it kept on messing up the partitions and failing. What version of TWRP are you using, is it the latest 2.8.6.0 or...?
You're brave to go with f2fs. Do you feel it's performing better?
Just to clarify on the network provider point - I did the simcard hack to my Photon Q, this is how I am able to run it with AT&T. Interesting that the problem I described happens with the native CDMA/Sprint network as well.
I hope we get a fix for the connectivity issue soon. I feel a little uneasy praying that the phone doesn't lose its connection or reboot for fear that I can't get it connected again in a reasonable period of time.
turbozapekanka said:
I had exactly the same issues when trying to flash CM 12.1 (Not able to mount /data, not able to mount /cache... )
Fixed this by manually formatting each partition at one time. I also changed data and cache to f2fs
No need to go with older TWRP
But I still have the connection issues exactly as you describe in your second post.
I'm running Freedompop (on top of Sprint network)
Click to expand...
Click to collapse
Yes, I used 2.8.6.0
I don't remember exact steps I performed, but the idea is to get rid of that "Not able to mount" errors.
I also performed Wipe->Format Data while trying to get rid of that errors. Not sure if it was necessary.
So after several unsuccessful attempts I finally I decided to change /cache to f2fs, and this is where I noticed, that the error is gone! So I just repeat the same steps (Wipe->Advanced Wipe) for all partitions (changing to f2fs for /cache and /data partitions only)
The key was to select only one partition at a time! when I checked several, I get "Not able to mount" error for some partitions. I think it is TWRP bug.
And just an hour ago I flashed latest nightly CM12.1 build (4-22) and it looks like the Network connectivity issue is also solved! (UPDATE: NO IT IS NOT, still loosing connectivity periodically, and Exclamation sign appears)
I did not notice any change to f2fs but I have nothing to compare with, I switched to CM just after I received the phone. (I bought it from Freedompop for $25)
I have a feeling that your selection of f2fs for your cache and data partitions influenced your success with wiping. I attempted the same process numerous times, but without changing the partition file system, and was unable to get all the partitions to a proper state with TWRP 2.8.6.0.
I didn't see anything in the changelog (http://www.cmxlog.com/12.1/xt897/) that would suggest a fix was included for the connectivity problem in either the 4/22 or 4/23 nightly so I haven't tried updating just yet, preferring instead to try to prolong my existing connection until there is more hope that when I reboot I will be able to connect without struggling with it.
It's too bad we're not able to participate in the main thread as there is a more active discussion going on there. I suspect this is just a parking lot. Perhaps if we keep posting our ongoing findings here for a couple of more days we'll get over 10 posts and be able to generate some more activity on these issues.
turbozapekanka said:
Yes, I used 2.8.6.0
I don't remember exact steps I performed, but the idea is to get rid of that "Not able to mount" errors.
I also performed Wipe->Format Data while trying to get rid of that errors. Not sure if it was necessary.
So after several unsuccessful attempts I finally I decided to change /cache to f2fs, and this is where I noticed, that the error is gone! So I just repeat the same steps (Wipe->Advanced Wipe) for all partitions (changing to f2fs for /cache and /data partitions only)
The key was to select only one partition at a time! when I checked several, I get "Not able to mount" error for some partitions. I think it is TWRP bug.
And just an hour ago I flashed latest nightly CM12.1 build (4-22) and it looks like the Network connectivity issue is also solved! (UPDATE: NO IT IS NOT, still loosing connectivity periodically, and Exclamation sign appears)
I did not notice any change to f2fs but I have nothing to compare with, I switched to CM just after I received the phone. (I bought it from Freedompop for $25)
Click to expand...
Click to collapse
timekiller_9 said:
It's too bad we're not able to participate in the main thread as there is a more active discussion going on there. I suspect this is just a parking lot. Perhaps if we keep posting our ongoing findings here for a couple of more days we'll get over 10 posts and be able to generate some more activity on these issues.
Click to expand...
Click to collapse
The Q&A thread is no different from the other thread. I don't think the maintainer cares if you post questions in the dev thread, but some maintainers can get annoyed by that. That's the whole point of the Q&A thread, to ask questions... The dev thread is "supposed" to be for development discussion only, although that seems to rarely happen.
Thanks for the tips arrrghhh.
Other than to confirm that others have similar issues and it's not a matter of something I'm doing wrong, I don't really have any questions. There are a couple of pretty serious bugs in CM 12.1 for the Photon Q. I would like to participate in the development of fixes in so much as I can. I'm not likely to be able to pinpoint where in the code things are broken as that would take some pretty serious time familiarizing myself with the layout. That said, I am a systems engineer by trade and feel comfortable running all sorts of tests/traces.
arrrghhh said:
The Q&A thread is no different from the other thread. I don't think the maintainer cares if you post questions in the dev thread, but some maintainers can get annoyed by that. That's the whole point of the Q&A thread, to ask questions... The dev thread is "supposed" to be for development discussion only, although that seems to rarely happen.
Click to expand...
Click to collapse
Hey turbozapekanka,
Check out my latest response in the main (albeit meant for development, it's where the real action is) thread:
http://forum.xda-developers.com/photon-q-4g-lte/development/cyanogenmod-12-1-photon-q-t3073781/page5
I'm not sure if it'll work for CDMA but you may wish to try it. It would be good data to know if your problem lies elsewhere in any case.
Good luck!
turbozapekanka said:
Yes, I used 2.8.6.0
I don't remember exact steps I performed, but the idea is to get rid of that "Not able to mount" errors.
I also performed Wipe->Format Data while trying to get rid of that errors. Not sure if it was necessary.
So after several unsuccessful attempts I finally I decided to change /cache to f2fs, and this is where I noticed, that the error is gone! So I just repeat the same steps (Wipe->Advanced Wipe) for all partitions (changing to f2fs for /cache and /data partitions only)
The key was to select only one partition at a time! when I checked several, I get "Not able to mount" error for some partitions. I think it is TWRP bug.
And just an hour ago I flashed latest nightly CM12.1 build (4-22) and it looks like the Network connectivity issue is also solved! (UPDATE: NO IT IS NOT, still loosing connectivity periodically, and Exclamation sign appears)
I did not notice any change to f2fs but I have nothing to compare with, I switched to CM just after I received the phone. (I bought it from Freedompop for $25)
Click to expand...
Click to collapse
wifi
Has anybody problems with Wifi?
i cant turn it on. Its off in the extended Settings is the Message "Wifi ist activating" but nothing happens
Do you guys have any idea on why we got 'no new update' message from settings/update, even though we have an obvious nightly update? http://www.cmxlog.com/12.1/xt897/
palmwangja said:
Do you guys have any idea on why we got 'no new update' message from settings/update, even though we have an obvious nightly update? http://www.cmxlog.com/12.1/xt897/
Click to expand...
Click to collapse
It's a server side issue affecting all cm12.1 devices, should be fixed soon.
Has anyone's 'long press volume keys for playback control' stopped working? When my screen is off the volume keys don't seek tracks like they did in a previous nightly.
Also ,does smart lock work for you guys? I can see the option but can't seem to get it to recognise NFC or my face.
hi.
Will cm12.1 support all f2fs file? It is the system / data / cache all formats into f2fs, thanks.
hhvstp said:
Will cm12.1 support all f2fs file? It is the system / data / cache all formats into f2fs, thanks.
Click to expand...
Click to collapse
CM12 supports it, I would imagine 12.1 does as well...
Heck, there is a CM11 build floating around with support for it.
12.1 Sprint CDMA access
Since I haven't posted much, I could not reply to the thread, but here's what I did to get 3G data back.
Installed the 05/01/2015 12.1 build.
Edited the build.prop file
changed ro.carrier=
to
ro.carrier=Sprint
rebooted - and I now have data.......
Not sure "why" that worked, but It hasn't up until I made that change....
apns-conf.xml issues
Compared to CM11, several of the entries in the /system/etc/apns-conf.xml file from CM12.1 are missing the "default" type. This makes it impossible to actually select the APN settings for Ting, Credo and Sprint MMS. For instance, I'm on Ting and changing:
type="mms"
to:
type="default,mms"
And then deleting /data/data/com.android.providers.telephony/databases/telephony.db and rebooting made it possible for me to select TIng. Previously there was no radio button next to the entry.
I still have the problem where the "Access Point Names" menu usually says "Access Point Name settings are not available for this user" most of the time but now when I *am* able to enter that menu I can at least select the right APN setting.
---------- Post added at 04:09 PM ---------- Previous post was at 04:01 PM ----------
GreeGreeCreedle said:
Since I haven't posted much, I could not reply to the thread, but here's what I did to get 3G data back.
Installed the 05/01/2015 12.1 build.
Edited the build.prop file
changed ro.carrier=
to
ro.carrier=Sprint
rebooted - and I now have data.......
Not sure "why" that worked, but It hasn't up until I made that change....
Click to expand...
Click to collapse
Nice catch. It looks like ro.boot.carrier is set correctly but for some reason ro.carrier is unknown.
hi.
CM12.1 experience to perform part of the game will be LAG, turn off the sound, then you can ease, what is the problem?
millertoo said:
Compared to CM11, several of the entries in the /system/etc/apns-conf.xml file from CM12.1 are missing the "default" type. This makes it impossible to actually select the APN settings for Ting, Credo and Sprint MMS. For instance, I'm on Ting and changing:
type="mms"
to:
type="default,mms"
And then deleting /data/data/com.android.providers.telephony/databases/telephony.db and rebooting made it possible for me to select TIng. Previously there was no radio button next to the entry.
I still have the problem where the "Access Point Names" menu usually says "Access Point Name settings are not available for this user" most of the time but now when I *am* able to enter that menu I can at least select the right APN setting.
---------- Post added at 04:09 PM ---------- Previous post was at 04:01 PM ----------
Nice catch. It looks like ro.boot.carrier is set correctly but for some reason ro.carrier is unknown.
Click to expand...
Click to collapse
I don't have this device but hopefully this post helps those with apn issues. If I toggled network mode to lte only, the apn listings would actually show.
http://forum.xda-developers.com/showthread.php?p=61070073
This is the link to the guide for flashing cm 12.1 on our Honor 3C - H30-U10. I don't own any of these builds or fixes, i just wanted to make this thread so that these things are easily available to people who CRAVE for Cyanogenmod on their honor 3c devices like me and ask for some help regarding the installation of apks. http://www.carbontesla.com/2015/08/install-honor-3c-cyanogenmod-12-1-lollipop-custom-rom-unofficial/
this is the link to the various builds of cm 12.1 https://cloud.mail.ru/public/3SBd/vVnPaUJ4C/ , however the one which has 20150923 in its name doesn't seem to boot up after flashing so i have flashed the one with 20150309 in its name which boots up fine and works pretty well.
Flash the Gapps also for the play store and google play services to work. Here is the link for it - http://www.carbontesla.com/download-google-apps-gapps/
Now, i tried PA Gapps mini and cyanogen 12.1 Gapps but they didnt work for me but AFH Gapps did work. You guys can try the former ones as there might have been some issue at my side.
The IMEI lost problem is there which can be solved by either restoring IMEI numbers using MTK or this zip http://1drv.ms/1FNtZUj. This may not be a permanent fix and the SIM not detected error may start showing up after a reboot but, it can be fixed by re-flashing this zip at recovery OR another rather stupid looking workound XD XD by turning on the airplane mode before rebooting and then switching it off after the boot up has finished.
I couldn't find the "Select default storage option" in the storage settings nor could i find the select preferred app installation location option in the Apps settings, so i found a workaround for linking the /sdcard in the root folder to /storage/sdcard1. Here is the script for it which has to be run everytime after booting the device in the terminal emulator:
1. first gain root privileges by entering su int the terminal.
2. type: mount -o bind /storage/sdcard1 /sdcard
That's it!! Now the default storage is your external sd card, one drawback of this is that you can't access the internal storage. If you want to access it, reboot your device and everything will revert back. if you want to set the default storage to the ext sd card, follow the above steps again.
THE PROBLEM: Apparently apks dont get installed most of the times even after enabling Unknown sources in the developer options, i don't know if this is the problem of google services or something, i would like someone to help out with this issue.
EDIT 1: The one which has 20150923 in its name boots up just fine, it needs more than one time dalvik cache deletion and factory resets.
Thanks for sharing ... some upgrade or new information in the last days...
This rom has several bugs. The only one version i still prefer to use is 151129 version
The latest 151202 doesn't booting after flash. Seems there's something wrong with boot.img
Anyway, i wish the developers will keep research and improve this rom to fix the bugs
Nothing new has happened mate
internauta2000 said:
Thanks for sharing ... some upgrade or new information in the last days...
Click to expand...
Click to collapse
No new updates have been release
I'll check the builds again and report back if i find any fixes for the bugs ASAP
Thanks for notifying!
Rayquaza said:
This rom has several bugs. The only one version i still prefer to use is 151129 version
The latest 151202 doesn't booting after flash. Seems there's something wrong with boot.img
Anyway, i wish the developers will keep research and improve this rom to fix the bugs
Click to expand...
Click to collapse
could you please provide the link for these builds? these couldn't be found on cloud.ru site
CM 12.1 ROM Development:
http://forum.xda-developers.com/android/development/rom-cyanogenmod-12-1-port-huawei-honor-t3307520
Great WORK!!
kernel.killer said:
CM 12.1 ROM Development:
http://forum.xda-developers.com/android/development/rom-cyanogenmod-12-1-port-huawei-honor-t3307520
Click to expand...
Click to collapse
Your Thread is amazing! Great work @kernel.killer !! Love your work! The ROM worked perfectly on my phone after flashing the modemFix zip
Hello, i bring to you the QuickRemote app for your AOSP Marshmallow rom, CM13 or any rom based on CM13 (Resurrection Remix, Bliss, AICP), you may ask, "Why would i want QuickRemote on my AOSP rom if MM has native IR support and Peel or Anymote works without all this mambo jambo?
Well, even though what i just said is true, no remote controller app has the learning method enabled, even on a stock rom, only QuickRemote can enable the IR receiver to learn a controller that does not appear on the device/manufacturers list.
So, that's the reason we want QuickRemote to work on our AOSP rom.
So, before anything, i would like to thank @hikarisei23 because in a comment of his post HERE i found the files for QuickRemote to work on MM wich leads to the second person i want to thank wich is @syndre who on said comment, posted the files that worked on MM, also @KronicSkillz who helped a lot to troubleshoot and also confirmed that the method i'm posting here works.
Well, this is it, after personally testing with: Resurrection Remix, AICP and Bliss, all of them MM amd CM13 based, all of them with the stock kernel and Lambda Kernel i'm confident enough to post it here, days of testing and troubleshooting and 3 different roms later.
So first, the mandatory disclaimer, im not responsible for any problem that may result from using my method and the files i'm providing you, either with your phone or your self-esteem, it's your responsibility to read, re-read and only do what you are comfortable with.
What you will need:
1. - The phone, this only has been tested with Lg G2 and Lg G3, this may or may not work on another LG phone with IR, you can try, but at your own risk.
2. - The Rom, this only have been tested with AOSP roms either CM13 or CM13 based roms, again, you can try in another rom but at your own risk.
3. - Obviously a Custom Recovery (twrp, cwm, philz)
4. - The three zips im leaving at the end of the post, QRemote_AOSP_MM.zip Fix_Part1.zip and Fix_Part2.zip.
5. - Maybe necessary or not, depending on your rom, Universal init.d from Playstore HERE and Selinux Mode Changer from HERE.
6. - Root Access.
Ok, once you checked and have everything needed, we have to make a little prep on your Rom before starting to flash the zips.
Rom Preparation 100% Needed
You need to set Selinux to permissive, here is where you may or may not need Selinux Mode Changer, First go into "About Device" on your phone settings and in the bottom you will find an indicator for Selinux state, if its "Permissive" you are good to go, some Roms and Kernels have this set to Permissive by default, if it's Enforcing, search in your Rom or Kernel settings, some of them have an option to set it to Permissive, if your rom does not have any option to change it, you will need Selinux Mode Changer, you install it and set Selinux to permissive, after reboot you can check in About Device again to see if it succeded, if it does not work, try again and check the original post, most of the answers are there, i cant give support for this app, also, this app needs root rights, and preferably two reboots after setting Selinux to Permissive.
Next you need to have init.d support, again, some roms have it, but at least for the test that me and the other users did, even though you are pretty sure init.d is enabled it's better to just install Universal init.d from the Play Store and enable init.d manually after doing so, reboot the system at least two times and grant Root access.
Installation!
Now we are ready to start flashing, reboot into recovery and RECOMMENDED, do a Nandroid Backup just in case, but at the moment no boot loops or any other problems had raised from flashing this, but again, just in case. After that, flash the first file: QRemote_AOSP_MM.zip, reboot your system and let it settle for a bit, 1 minute at least.
Now is the part where almost everyone has problems, you have to check in your Sdcard root for a log file named Qremote.log, if the file is there, it means init.d is enabled and in the file it will say if Selinux is Ok, if you don't have the file, check back the first two prep steps and try again.
Now if everything is going ok, is time for the second file, Fix_Part1.zip, reboot and let the system settle again, you may have some force close errors from QuickRemote or QuicksetSDK, its ok, you can try and check if QuickRemote is working, in allmost every case it will not work just yet, but you may have some luck.
Now, is the time to flash the third file, Fix_Part2.zip, again, reboot and let the system settle, now, you should have a working QuickRemote app on you AOSP MM Rom.
This are the steps, if you need more information about what all of this is doing and why you need Selinux and init.d, also why you need to flash 3 files, you can read the troubleshooting section where i explain what i understand about it.
TROUBLESHOOTING
Well, if you are here, it means that this didn't work as planned, so lets make this like a FAQ so you just search your problem and get the answer for it.
P.- I can't see QuickRemote on my app drawer. A: be sure that QuickRemote.apk is not showing as "com.lge...." and has the default green Android icon on your app drawer, sometimes and for reasons unknown to me, this happens for the first day or so, it will automatically change to QuickRemote and it will have the correct icon at least 5 hours after you installed it, it can take more time. A2: Maybe the flashing proccess was not successful, re-flash the file, it will automatically delete previously flashed files and install a new copy of them.
P. - I get force close messages for QuickRemote or QuicksetSDK after completing the proccess. A: try to run QuickRemote after the system settled, most of the times is 1 minute, in some roms and for reasons unknown to me, this messages will appear at boot but after the system settled, you will be able to run QuickRemote without any problem.
P. - QuickRemote opens up but no manufacturers are showing and it also gets really slow. A: this problem shows when either QuicksetSDK is not correctly installed or Selinux is not set to permissive, the solution for the first problem is in my 2 part fix, the version of Selinux included in the first zip, works great with MM but for some reason it will not work out of the box, i dont know if it's missing some files but it may or may not even show under system apps list on your settings menu, what my 2 part fix does is that, deletes the version of QuicksetSDK that the first flash installs and installs a temporary copy of QuicksetSDK wich i believe, writes information needed for QuicksetSDK to work properly, but this newer temporary QuicksetSDK apk, will allmost never work on MM, you can try but allmost every time it will not work, it will constantly force close, so the second fix zip, will delete this temporary QuicksetSDK and the folder it creates in your Sdcard root and install the previous version of QuicksetSDK again, and now, if everything went well, it will work as it's supposed to, i really dont know why exactly, but it works.
A2: the first thing you will notice when you switch to MM is that allmost every app will ask for permission to your Sdcard or camera or microphone wich in LP was not doing, since 4.3 Google is taking extra steps to ensure that you and your information are better protected one of this steps is Selinux (Security Enhanced Linux) wich, for putting it in simple terms, is like a sandbox for your system, only some trust-signed apps can get out of that sandbox and copy files etc... Into your system, those not-so privileged apps cant output anything outside the sanbox and thats why you need to disable or "set to permissive" Selinux, so QuicksetSDK can make the changes necessary for QuickRemote to do its work, it's true that now your system is in a degree "more vulnerable" but if you are a user of this forum, the odds to install something that will damage your system or jeopardize your information are minimal, you need to be really silly to fall for those "your system has problems" or "your battery is gonna explode if you don't install this app" ads that appear on your phone on the daily basis, so, dont worry, but at the same time, just be carefull and have some common sense, if there is a way for this to work with Selinux set to Enforcing, i will update it in the same second.
P. - QuickRemote force closes whenever i try to open it. A: this is caused by either a bad zip flash, or problems with Selinux or init.d, follow the previous answer and the first installation steps again.
P. - I can see QuickRemote and QuicksetSDK on my apps list, no force closes but still no manufacturers. A: Be sure init.d is enabled, i had problems with Roms that had "native init.d support" and emulated init.d will not work, the only way i got no problems with this was with Universal init.d, install that even though you are "pretty sure" your rom supports init.d, the 10QuickRemote.sh script on your init.d tries to get your country to see if you will use the app in, either Korean or any other supported language, it will also give some permissions to a file and it will check if Selinux is Permissive and finally, it will log this to a file called Qremote.log on the root of your Sd, if you have problems and you cant see the file, the problem is 99% most of the time, init.d.
P.- I don't want to flash three files, isn't there a simpler way? A: Unfortunately no, at this moment and after A LOT of testing etc... This is the only effective way i found.
P. - I'm afraid to set Selinux to permissive and leave the door open for all kind of bad ju ju and stuff to invade my sacred Android system, what can i do? A: Skip this hole thing, at the moment, the only way to make this work on AOSP MM is by doing the previous, just be careful, get some common sense and everything will be just fine.
Well, thats all i can think of right now, if you have suggestions, problems or a better way to make this work, please tell me in the comments or PM me, i'm glad to help as far as i can, i hope this helps, i leave you with the needed files and proof that it works.
QRemote_AOSP_MM.zip - MEGA - DRIVE
Great job
Works great on Ressurection Remix 5.6.2. Well done.
Only issues I have are the force close when trying to edit the remote name, and icon and name of the app not showing correctly (which can be fixed with any custon launcher).
Petrit Ziu said:
Works great on Ressurection Remix 5.6.2. Well done.
Only issues I have are the force close when trying to edit the remote name, and icon and name of the app not showing correctly (which can be fixed with any custon launcher).
Click to expand...
Click to collapse
I have not seen those force closes, i have to check, and as i said, the icon and name will eventually get right, for me was 5 hours, but it can be a hole day, and all by itself will set the icon and name correctly, if you have more problems, send me a logcat for this app, maybe we can find why it force closes
Logcat
Logcat
Added to index
[INDEX][LG G2] ROMs, Kernels, Guides and more
@Petrit Ziu after seeing the logcat i think the problem is StrictMode Policy, wich is a policy in android to keep unintentional writes to the system away from the main thread, so the animations, ui etc... Can keep a steady flow and your system runs smooth, because this app was never intended for AOSP and the app comes from Lollipop, i think that the right signatures are missing and Android sees the action of changing the name to a controller "invalid" so it closes the QuickRemote App, lets wait for newer versions of QuickRemote after Lg releases MM to more IR enabled devices to see what app works best, this is the best we can do with the resources we have
@Art Vanderlay Thanks
@Jc_master I think it's already perfect, just pointed an issue i found, but it's totally not a problem for me. Thanks
Sent from my LG-VS980 using XDA Free mobile app
@Petrit Ziu thanks, and dont worry, i'm no developer but i'm learning so much from this, it's good for me to see this problems and know why they happen, it's good to have feedback and even better this errors, if you didn't tell me, i would not know, my system does the same and i had no idea, i will update the post with this information
not work for me
I flashed it a lot of time and patched it and it will be not even work for me :/
I always get FC
D802 CM13 Nightlies
Potter92 said:
I flashed it a lot of time and patched it and it will be not even work for me :/
I always get FC
D802 CM13 Nightlies
Click to expand...
Click to collapse
Well, the only thing i can reccomend is that you use the latest TWRP for your device, you have to follow the steps exactly as i explained and use exactly the apps and files i explain, if that does not work i can just reccomend using another rom, Resurrection Remix for example, your logcat seems to show a problem with the apk itself, you cam try and decompress the files and manually copy and assign permissions to the files but i can't show you how, i lack time to do it
Works great, thank you!
Only issue I've had is the app crashes every time I try to rename a remote.
It works on the D801 (T-Mobile) Bliss rom 6.0.1
just confirming it.
Although I do get some force quit when editing the remotes name etc...
LG D802 CM13 nightlies - works!
Jc_master said:
@Petrit Ziu after seeing the logcat i think the problem is StrictMode Policy, wich is a policy in android to keep unintentional writes to the system away from the main thread, so the animations, ui etc... Can keep a steady flow and your system runs smooth, because this app was never intended for AOSP and the app comes from Lollipop, i think that the right signatures are missing and Android sees the action of changing the name to a controller "invalid" so it closes the QuickRemote App, lets wait for newer versions of QuickRemote after Lg releases MM to more IR enabled devices to see what app works best, this is the best we can do with the resources we have
Click to expand...
Click to collapse
Is there a fix?
MM is out for G3
Thanks
U can change name using SQLite Editor like this:
https://play.google.com/store/apps/details?id=dk.andsen.asqlitemanager
Database: /data/data/com.lge.qremote/databases/qremotesettings.db
Table: tblDevices
Petrit Ziu said:
Works great on Ressurection Remix 5.6.2. Well done.
Only issues I have are the force close when trying to edit the remote name, and icon and name of the app not showing correctly (which can be fixed with any custon launcher).
Click to expand...
Click to collapse
I can confirm this force close on rename issue as well
Eselter said:
U can change name using SQLite Editor like this:
https://play.google.com/store/apps/details?id=dk.andsen.asqlitemanager
Database: /data/data/com.lge.qremote/databases/qremotesettings.db
Table: tblDevices
Click to expand...
Click to collapse
That did it! Not necessarily a solution to the problem but a sufficient workaround for now
On CM13 working great but on exodus I can't manage it to work.
Any one have try it on exodus rom?
Eselter said:
On CM13 working great but on exodus I can't manage it to work.
Any one have try it on exodus rom?
Click to expand...
Click to collapse
Same here. Works on every rom I've tried but exodus. Something funky is happening with the quickset SDK as its present in priv-app or app (forget which one) but doesn't show up in installed apps. I have selinux set to permissive and init.d enabled.
Hello, how to uninstall this qremote? Because I have tried peel smart remote, and it's works great. And the remote (peel) so detail from LG qremote.