[ROM][PORT][JB 4.2.2][PA3.60][AOKP-MR1][CM10.1]P.A.C True All in 1 ROM[HALO][OPD] - HTC One X+

Hi, this is the first PORTED ROM I release, and also the first P.A.C. ROM for the HOX+, I tryed to build from source for about 2 weeks and keept fixing errors, making needed files to just get new errors and new needed files not found and in the end I tryed to build CM just to see if I can even build that, and it worked, so I realised PACman was a bit over my powers and gave up and deleted the source, but after a bit KaptKeefmenneke sent me his PACman 22.1.1 and I sterted porting newer versions over it with great success, so here I am posting this rom after geting permisions from both KaptKeefmenneke and [vertigo] to post it.
This rom is for the INTERNATIONAL ONE X+
This rom was ported from the NEXUS4 over an unreleased P.A.C. 22.1.1 for the HOX+
I will update the rom as long as I can, and fix as many bugs as I can with my limited development knoledge.
This rom also has an OPD (OpenPDroid) patch that can be flashed after flashing the rom.
I hope you will enjoy it as much as I do.
Not working:
-no vibration when touching the touch buttons-did all that came into my mind but still can't make the vibrations work, even did the framework-res.apk edit that should enable it and no luck, if anyone has any Ideea I'd like to hear it.
-headsets not recognised, looking to find a fix but I am kinda blind at this part because I don't know what files contain things related to headset.
-same things as in all other aosp roms
-you tell me
Bugs:
-same things as in all other aosp roms
-OS is allways in black mode, the PAC in Black toggle doesen't do anything.
-you tell me
NOTE: for bugs that need it, post logs, I did not include the Sharelogs and Performance Tool apk's so you will have to download them, sorry, also even if I am not too much of a developer I can mostly read logs, also post if you find any fixes for any bugs, don't expect me to be able to fix all the bugs that may appear, remember I am preety new in the development thing and my knoledge is limited (verry limited as far as I understand) and my time is also limited due to school.
Working:
-mostly everything as far as I can see
I would not recommend using this rom with Xposed Framework even if it is great just because of the same reason it is not really working ok on AOKP (it will take longer for the SystemUI to load)
Downloads:
Rom: http://www.mediafire.com/download/mg8sdj47cs5fq9k/enrc2b_PAC_JB_4.2.2-v23.0.0.zip
Gapps: http://goo.im/gapps/gapps-jb-20130301-signed.zip
Kernel: Use CM10.1 kernel, DO NOT use the included kernel as many things will not work with it (wifi, bluetooth, etc)
OpenPDroid patch: http://www.mediafire.com/download/1..._4.2.2-v23.0.0-openpdroid-20130612-update.zip (No dark mode in Messages app, will try to fix, but don't think I can till I will manage to build from source) for the moment I would say just use XPrivacy if you can live with the SystemUI startup delay added by XPosed.
Thanks to...
ParanoidAndroid Team
CyanogenMod Team
AOKP Team
P.A.C. Team
Maxwen and Lloir for theyr great work on this device
[vertigo] for making the NEXUS4 rom (here:http://forum.xda-developers.com/showthread.php?t=21468790)
KaptKeefmenneke for making the P.A.C. 22.1.1 rom for enrc2b
FFU5y for OpenPDroid
mateorod for the Auto-Patcher

Reserved for changelog

Reserved also just in case.

I've removed some posts about permissions. Feel free to continue via PM and CC me if need be

Sorry if I missed it, but which version of the HOX+ will this work on?
For my purposes, does it work with AT&T version?

Arvoreen said:
Sorry if I missed it, but which version of the HOX+ will this work on?
For my purposes, does it work with AT&T version?
Click to expand...
Click to collapse
Nope, this is also for the international variant
Sent from my HTC One X+ using xda premium

aardappel12 said:
Nope, this is also for the international variant
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
I was afraid you would say that....

I might be wrong but shouldn't this be under the original android development section.
Nice work btw
Sent from my HTC One X+ using Tapatalk 2

flipside101 said:
I might be wrong but shouldn't this be under the original android development section.
Nice work btw
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Nope, due to the fact that it is not built from source

Headphone/Earphone jack doesn't work. Music just plays on the phone speaker.
And is multi user supposed to work? I can't seem to setup a second user.

KiGWa said:
Headphone/Earphone jack doesn't work. Music just plays on the phone speaker.
And is multi user supposed to work? I can't seem to setup a second user.
Click to expand...
Click to collapse
Will have a look as soon a I reupload the rom, thanks for reporting.

Just so people are aware, pacman can and does have HUGE issues with some apps on the market.

Could someone that has this installed tell me if they have any problems with the signal (not getting signal at all), cause a friend had it when he flashed it to his X+ and I also did have the problems after wiping data, then fixed the problem as my friend told me to and then wiped data again and set up the device and did this process again and again lots of times and I only got that once, but at the first wipe data I had my data from the 22.1.1 pacman rom, if anyone else has this problem I will post a how to fix it in the OP, I am not sure if it is related to the rom or not, that is why I am not adding the bug and fix to the OP, for me it happened only once, and my friend has lots of apps installed so it may have been caused by an app for him, test if you have this problem and tell me please.

Ranomez said:
Could someone that has this installed tell me if they have any problems with the signal (not getting signal at all), cause a friend had it when he flashed it to his X+ and I also did have the problems after wiping data, then fixed the problem as my friend told me to and then wiped data again and set up the device and did this process again and again lots of times and I only got that once, but at the first wipe data I had my data from the 22.1.1 pacman rom, if anyone else has this problem I will post a how to fix it in the OP, I am not sure if it is related to the rom or not, that is why I am not adding the bug and fix to the OP, for me it happened only once, and my friend has lots of apps installed so it may have been caused by an app for him, test if you have this problem and tell me please.
Click to expand...
Click to collapse
I did not have any issue with signals on both wifi and mobile network. Though, before i adb pushed the rom/gapps zip, I did a full wipe of the system, data and caches. The phone was like totally empty before i install this ROM.

KiGWa said:
I did not have any issue with signals on both wifi and mobile network. Though, before i adb pushed the rom/gapps zip, I did a full wipe of the system, data and caches. The phone was like totally empty before i install this ROM.
Click to expand...
Click to collapse
Ok, thank you, also could you tell me if it is just me or even if the PAC in black toggle is off the os is still in the black ui?

Ranomez said:
Ok, thank you, also could you tell me if it is just me or even if the PAC in black toggle is off the os is still in the black ui?
Click to expand...
Click to collapse
yup, os ui is black even toggle is off.

Ranomez said:
Could someone that has this installed tell me if they have any problems with the signal (not getting signal at all), cause a friend had it when he flashed it to his X+ and I also did have the problems after wiping data, then fixed the problem as my friend told me to and then wiped data again and set up the device and did this process again and again lots of times and I only got that once, but at the first wipe data I had my data from the 22.1.1 pacman rom, if anyone else has this problem I will post a how to fix it in the OP, I am not sure if it is related to the rom or not, that is why I am not adding the bug and fix to the OP, for me it happened only once, and my friend has lots of apps installed so it may have been caused by an app for him, test if you have this problem and tell me please.
Click to expand...
Click to collapse
got no data signal,too.please post your solution.had same issue while trying to port pa2.5x (from N4,too),but never explored why.
thnksAlot,alex

maerdance said:
got no data signal,too.please post your solution.had same issue while trying to port pa2.5x (from N4,too),but never explored why.
thnksAlot,alex
Click to expand...
Click to collapse
Go to settings->More->Mobile Networks, wait for it to load, click automatically connect around 3 times, it will give you an error, but in 1 min you should be connected and allmostly sure that it should not happen again.
EDIT: Found a real solution, will upload a fixed rom when I get home in 5 and a half hours, at school now and getting ready for a exam.
EDIT2: found the solution and updated apktool to decompile framework, apply fix and recompile and get errors at recompiling......is there a special apktool for pacman or something?

->Ranomez:Go to settings->More->Mobile Networks, wait for it to load, click automatically connect around 3 times, it will give you an error, but in 1 min you should be connected and allmostly sure that it should not happen again.
chaos leads to a new order. how did you find out this kind of weird(individual?)
input/output behavier.
I suppose we found a proof of that android should be labelled alive : )
will 'apply' later. thank you for your afford in this rom in general.
greets, alex

maerdance said:
->Ranomez:Go to settings->More->Mobile Networks, wait for it to load, click automatically connect around 3 times, it will give you an error, but in 1 min you should be connected and allmostly sure that it should not happen again.
chaos leads to a new order. how did you find out this kind of weird(individual?)
input/output behavier.
I suppose we found a proof of that android should be labelled alive : )
will 'apply' later. thank you for your afford in this rom in general.
greets, alex
Click to expand...
Click to collapse
I may be sleepy or something wrong with me cause I just woke up and I can't remember half of yesterday but I don't understand anything of what you sayd.
Also for anyone that wants to help me can you please try to apply the fix at the bottom of the OP in this thread http://forum.xda-developers.com/showthread.php?t=1908008 to the framework in my rom, cause for me it doesen't work, I can not recompile the framework even if I don't change anything, so I decompile it and try to recompile and fail, also I get some errors at the decompilation part also, but it seems to decompile.....
EDIT: anyone having a problem that when you talk with someone the other person hears himself, cause dad told me that today, but no one else told me till now?

Related

[ROM][Guide][4.0 US+INTL]GT-I9000 rom ports

WANTED: Users to port SGS roms to the 4.0. You will need to know how to complete a full restore if something goes wrong, but that's it. I cannot go through the forums searching for good SGS roms, as I have several threads to manage, and a rom to work on. The steps are easy for you though, and if you port a rom I will add it in the OP.
First of all, I want to say that I take NO credit on any of these roms. All I did was port them over and add speed tweaks, or added ones that users have ported. If the rom creators or mods have any issue whatsoever with this thread, I will happily take it down, even though I think it would be a large contribution to the 4.0 community. I will continue to update this forum with info as I go along.
I, after a fortunate afternoon of boredom, have managed to successfully begin porting I9000 roms to our devices! Fortunately, they are similar enough that it boots without any modifications. I will put up here any ports that I make, and any that the users create. Note that these WILL NOT BE UPDATED! These are one-time ports, to be used and improved upon by the community. Anything that is broken now will stay broken, unless a user decides to fix/update it, then I will include it in the OP.
What *should* work in all ported roms:
wifi
GPS
home buttons
everything else
What will probably *not* work on ported roms:
Bluetooth
Camera
backlight on buttons
Ported roms:
~GamerzRom odexed V11-~
Link to original thread: http://forum.xda-developers.com/showthread.php?t=1656081
Added:
V6 supercharger, and build.prop tweaks from it.
init.d tweaks from my rom
ext4 filesystem
Advanced mount options
Auto zipalign and Database optimize
Removed apps that do not work on our Player (such as the Dialer)
Download:http://www.mediafire.com/download.php?ctuu2w295w2xlk6
~Saurom~
Original thread:http://forum.xda-developers.com/showthread.php?t=1388342
Ported download link:http://www.mediafire.com/download.php?csua40hkg1r3m86
~JellyBeanRom~
Original thread: http://forum.xda-developers.com/showthread.php?t=1260709&highlight=gb
Ported download link:http://www.mediafire.com/download.php?mgec81f3ifck221
~Ario Rom (ported by ChaosChris)~
Ported thread link : http://forum.xda-developers.com/showthread.php?p=29950015#post29950015
Original thread: http://forum.xda-developers.com/showthread.php?t=1536558
To use these Roms:
You MUST use a Gplayer kernel! GT-I9000 kernels will not boot!
A full wipe may be necessary with some roms if you encounter issues.
Converting (for porters)
Steps:
1. Download wanted rom (must be GB)
2.Move the zip to the internal sdcard
3.Reboot into recovery
4.Flash zip, then boot into download mode
5.Flash a SGP kernel
6. apply my mod pack to the rom, by either copying/pasting the system directory over the SGS rom's system directory, or by pushing it via adb, (eg. adb push /path/to/modpack /system).
7. Profit!
NOTE: after applying this, porters may want to remove non-working packages such as the dialer and mms, as they may cause issues with the end result if they are kept in. Do not delete phone.apk though!! This is required for the camera and some other things, and breaks stuff on certain roms. You have been warned.
NOTE: If you use this modpack, please give me credit, and link back to this thread so that more people can use it. Also, you should probably link back to the ported rom's thread as well, to avoid "ripping off" those devs.
Modpack:
Changelog
V1-
Preliminary release
Fixes wifi and GPS
Includes v6 supercharger and init.d tweaks
V2-
fixed vold.fstab so sdcard is mounted properly.
Download:
ModpackV1:
http://www.mediafire.com/download.php?diaq6im4i18ktf7
NOTE:Note that this is preliminary. It fixes everything listed, and attempts to fix some broken things. Your mileage may vary. This is not a cwm flashable zip! you much extract and adb push this over the existing system directory. This is mainly intended for porters, so users apply at your own risk. This will work, but is a very early release.
Modpack V2 (thanks to ChaosChris):
https://docs.google.com/open?id=0B9OVlH2Pl76DZk5Pa3lJVXlrYzA
Looking good! Does the gamerz port have the 388mb of ram, I thought that was kernal related?
Sent using Tapatalk
iJimaniac said:
Looking good! Does the gamerz port have the 388mb of ram, I thought that was kernal related?
Sent using Tapatalk
Click to expand...
Click to collapse
Yeah, it says that because it includes semaphore's kernel, which raises the max rom to 380, which we could do on our kernel's, but apparently that breaks a lot of stuff if you go much further then 350 (according to klin).
is the wifi fixed in your port or do we have to do your fix after flashing?
Just a word of advice, make sure you get permission from the devs! Also surely this will work with ICS roms right? Just swap out the SGS kernel with the SGP CM7 kernel and it should work (I think)
Sent by my Robot Butler
Supermaster34 said:
Just a word of advice, make sure you get permission from the devs! Also surely this will work with ICS roms right? Just swap out the SGS kernel with the SGP CM7 kernel and it should work (I think)
Sent by my Robot Butler
Click to expand...
Click to collapse
check over in the operation: ics for the 4.0 thread I believe they are already attemping to use the cm7 kernel to boot a cm9.
daniel644 said:
is the wifi fixed in your port or do we have to do your fix after flashing?
Click to expand...
Click to collapse
Yeah, it is fixed before you flash. Once I manage to iron out a few more bugs, I will probably release a "conversion pack" that fixes all the issues. I already have one that fixes wifi and gps, but bluetooth and camera have me stumped, and I do not want to replace the entire hw/lib folder, because some of these roms have lib optimizations, but I may have to.
Sent from my GT-I9000 using xda app-developers app
Supermaster34 said:
Just a word of advice, make sure you get permission from the devs! Also surely this will work with ICS roms right? Just swap out the SGS kernel with the SGP CM7 kernel and it should work (I think)
Sent by my Robot Butler
Click to expand...
Click to collapse
Since I am merely redistributing their work, not incorporaring it into anything I have made, or taking any credit for it, I don't asking permission is necessary. I may be completely off base, but I think that as long as you give devs 100% credit, and link to their original work, it is okay. It may not be the best option, but neither is asking EVERY dev if I can port their rom, or ask permission for user-ported roms.
Youay have an idea there, althouh I think that zaclimon has tried it, and he said it wouldn't boot. I have 2 efs backups, so I guess I can try, although even if the kernel boots, I bet I will have to do a LOT more work before it is usable. I also believe that he said the issues may have been rom based, so here it goes, and wish me luck.
Sent from my GT-I9000 using xda app-developers app
hanthesolo said:
Since I am merely redistributing their work, not incorporaring it into anything I have made, or taking any credit for it, I don't asking permission is necessary. I may be completely off base, but I think that as long as you give devs 100% credit, and link to their original work, it is okay. It may not be the best option, but neither is asking EVERY dev if I can port their rom, or ask permission for user-ported roms.
Youay have an idea there, althouh I think that daniel has tried it, abd he said it wouldn't boot. I have 2 efs backups, so I guess I can try, although even if the kernel boots, I bet I will have to do a LOT more work before it is usable.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
I've already tried with a cm7 kernel and I got an error of looping (netd1.0 starting) that's why I'm trying to do something. Now I need to backport 3.0.8 usb gadget drivers.
zaclimon said:
I've already tried with a cm7 kernel and I got an error of looping (netd1.0 starting) that's why I'm trying to do something. Now I need to backport 3.0.8 usb gadget drivers.
Click to expand...
Click to collapse
Whoops, I meant you . I will try with a official cm9 build from the SGS forums, and see if that fares any better. Probably will not, but it doesn't hurt to try.
EDIT: well, nevermind about that. He seems to have pulled all of his download links, and I cannot get to the CM7 build. Oh well...
I am going to try anyway with the I9000 package since it seems to have EXT4 support, and I *think* that was what was bootlooping me earlier. This as all just my hopeful rationalization, of course . A lot farther out there, but maybe I can use a SGP5.0 kernel to get it booting. A LOT less likely, but hey, i'm experimenting .
EDIT: I cannot try ICS, since I need to reboot into recovery a second time, and I cannot do that, as I have the intl bootloader on my US device, and it would require it to be booting first.
hanthesolo said:
Whoops, I meant you . I will try with a official cm9 build from the SGS forums, and see if that fares any better. Probably will not, but it doesn't hurt to try.
EDIT: well, nevermind about that. He seems to have pulled all of his download links, and I cannot get to the CM7 build. Oh well...
I am going to try anyway with the I9000 package since it seems to have EXT4 support, and I *think* that was what was bootlooping me earlier. This as all just my hopeful rationalization, of course .
Click to expand...
Click to collapse
I think we should do like entrophy's because I get bored from mtd. Also just tried the gamerz rom port. As I see the camera works, don't know about bluetooth (it can turn on). Vibration works too. I was able to connect to wifi pretty fast and I have one word for this rom. FAST!!!!
Good job!!
zaclimon said:
I think we should do like entrophy's because I get bored from mtd. Also just tried the gamerz rom port. As I see the camera works, don't know about bluetooth (it can turn on). Vibration works too. I was able to connect to wifi pretty fast and I have one word for this rom. FAST!!!!
Good job!!
Click to expand...
Click to collapse
Well, thet camera shows a preview, but fails when a pic is taken, for some reason. Bluetooth does turn on, but is not seen by any other devices, and cannot scan for others either. I did do a little tweaking with Gamerz, so it will be even faster than it was already, which is pretty blazing! I have 2 more that I can put up (I have a preliminary package that I just adb push over the system files that works for now). I have also gotten the camera apk onto my rom, and it works really well! It doesn't take 5 MP pics, or record 720p video (which may be because I am using Terrasilent, which reduces the amount of Vram the system can have), but tap to autofocus and everything else works pretty well. I have a sneaking suspicion that the camera is soft limited, not hard-limited.
I also noted that the external sd card isn't working too (a problem with vold.fstab I'll correct it right now)
zaclimon said:
I also noted that the external sd card isn't working too (a problem with vold.fstab I'll correct it right now)
Click to expand...
Click to collapse
I don't use an externel sdcard, so thanks for pointing that out! I will include a fixed version in my mod pack.
hanthesolo said:
I don't use an externel sdcard, so thanks for pointing that out! I will include a fixed version in my mod pack.
Click to expand...
Click to collapse
Here's the vold.fstab if you need it
Okay, it seems that the zip hosed my partitions (converted them to yaffs2 and mtd), so I am going to perform a full restore, and just keep porting GB roms. As soon as you can get the usb gadget driver working, zaclimon, I guess I can keep working on it, but for now I will just keep to GB.
Two more roms up! I will probably not port any other unless I see an especially good one, but I will put up my mod pack tomorrow.
has anyone found out if the ported roms enable tv out or has someone found out if tv out support is in the i9000 kernal?
TV out has to have hardware, or your not going anywhere. I think the galaxy player lacks the hardware unfortunately. If it does have the hardware, it was very dumb of Samsung not to enable it.
Sent using Tapatalk
iJimaniac said:
TV out has to have hardware, or your not going anywhere. I think the galaxy player lacks the hardware unfortunately. If it does have the hardware, it was very dumb of Samsung not to enable it.
Sent using Tapatalk
Click to expand...
Click to collapse
what hardware does the galaxy s i9000 have that allows for tv out? I thought the galaxy s i9000 and the galaxy player 4.0 had the same gpu?

Cyanogenmod Stock Browser stuck in desktop mode?

Hey guys, my question is essentially what the title says. I find that in CM10 based roms, that whenever I use the stock cyanogen mod browser, it automatically goes into desktop mode (and is stuck there. The desktop mode checkbox, however, is unchecked.) I'm fairly sure it worked before I used the touch pad fix here - http://forum.xda-developers.com/showthread.php?t=1893343 - So I think it might be a framework/build.prop issue, but I'm not sure. I've been looking to fix this problem everywhere but haven't really been able to find a solution. Do you guys have any idea what the fix might be?
hey..this was better on general section or in some thread..i remember you posted this on one of the roms..but seems to be a general cm10 problem..so maybe better install another browser for your needs.
smokerman said:
hey..this was better on general section or in some thread..i remember you posted this on one of the roms..but seems to be a general cm10 problem..so maybe better install another browser for your needs.
Click to expand...
Click to collapse
Oh I asked in your racing jb rom thread, but now I'm trying to make a cm10 based rom of my own, and it seems that after testing many other Cm10 roms, everyone has this issue. But I think it's a build.prop thing, cause I'm sure that before, on Sonygenmod Cm10, it worked normally, but after I applied the touchpad fix, that's when it started messing up.
Since this is more of a universal problem, I thought all the devs here might have some insight on a fix for this.
fishvtt said:
Oh I asked in your racing jb rom thread, but now I'm trying to make a cm10 based rom of my own, and it seems that after testing many other Cm10 roms, everyone has this issue. But I think it's a build.prop thing, cause I'm sure that before, on Sonygenmod Cm10, it worked normally, but after I applied the touchpad fix, that's when it started messing up.
Since this is more of a universal problem, I thought all the devs here might have some insight on a fix for this.
Click to expand...
Click to collapse
even with FXP rom you have this issue..and it doesnt have touchpad fix..so cant be caused by that.
smokerman said:
even with FXP rom you have this issue..and it doesnt have touchpad fix..so cant be caused by that.
Click to expand...
Click to collapse
Oh ok guys, I can confirm that this is a framework problem. Not a build.prop problem. To figure this out, I used four different versions of the sonygen cm10 mod. First version was with old build.prop and old framework, witch worked fine, and the second was with old framework, but new build.prop, which also worked fine. New framework, old build.prop did not give me the mobile version of google, however, as long with the new build.prop, new framework.
So now, we just need to find out what exactly is wrong with the new version of the framework. I feel like the new framework causes the phone to look like a tablet to the cyanogenmod stock browser, but I'm not sure.
With this post I have attached both the new framework, and the old framework, if anyone else wanted to run any tests on their own. (or figure out what's wrong).
I can also supply both build.prop's if you guys think it's necessary.
I should also say, that this is an issue, for without the new framework, touchpads won't be able to work. So if anyone can help modify the new framework or anything, I would really appreciate the help.
smokerman said:
even with FXP rom you have this issue..and it doesnt have touchpad fix..so cant be caused by that.
Click to expand...
Click to collapse
Hey, smokerman, would you know how to mess with .jar files. I kinda want to go exploring to see if I can do anything.
you have here a simple guide by @CriGiu
http://forum.xda-developers.com/showthread.php?t=2322231
could help you.:good:
fishvtt said:
Oh ok guys, I can confirm that this is a framework problem. Not a build.prop problem. To figure this out, I used four different versions of the sonygen cm10 mod. First version was with old build.prop and old framework, witch worked fine, and the second was with old framework, but new build.prop, which also worked fine. New framework, old build.prop did not give me the mobile version of google, however, as long with the new build.prop, new framework.
So now, we just need to find out what exactly is wrong with the new version of the framework. I feel like the new framework causes the phone to look like a tablet to the cyanogenmod stock browser, but I'm not sure.
With this post I have attached both the new framework, and the old framework, if anyone else wanted to run any tests on their own. (or figure out what's wrong).
I can also supply both build.prop's if you guys think it's necessary.
I should also say, that this is an issue, for without the new framework, touchpads won't be able to work. So if anyone can help modify the new framework or anything, I would really appreciate the help.
Click to expand...
Click to collapse
The framework inside the patch in the first post of sonygenmod solves that issue
(it was caused by an older framework)
CriGiu said:
The framework inside the patch in the first post of sonygenmod solves that issue
(it was caused by an older framework)
Click to expand...
Click to collapse
Oh ok, I'll try testing that out.
CriGiu said:
The framework inside the patch in the first post of sonygenmod solves that issue
(it was caused by an older framework)
Click to expand...
Click to collapse
All right, well that seems to do the trick. When I try to use the touchpad activator app, it gives me the "error 5 expected reciever of type android.view.ViewRoot, but got android.view.ViewRootImpl". But, Dead Trigger works perfectly how it's supposed to, and the stock browser is using the mobile version now. Just remember to make the necessary build.prop changes as outlined in Fahrenheit's guide.

[Q&A] [DEV][ROM] - Pantech Burst - CM-11.0 porting

Q&A for [DEV][ROM] - Pantech Burst - CM-11.0 portinghttp://forum.xda-developers.com/android/development/dev-pantech-burst-cm11-0-porting-t2938360http://forum.xda-developers.com/android/development/dev-pantech-burst-cm11-0-porting-t2938360
Please use this thread to all questions not related with develop.
Greetings.
I didn't want to spam this thread with a useless "thank you" post but it's pretty quiet around here anyway so what the hey. THANK YOU SO MUCH!!! This is seriously freaking awesome. I was convinced development for the Burst was going to die with that final build of SlimBean. It feels so nice to be running KitKat (way to go, 4.4.4!) on this tiny little guy who refuses to die. That bug with the test build where opening SnapChat caused a kernel panic seems to be completely gone, so thanks for taking away my excuse for ignoring my SnapChat account lol. The battery life leaves much to be desired but I'm pretty sure that's the phone and not the ROM. Thank you so much again, this is excellent work :highfive:
thisisapoorusernamechoice said:
The battery life leaves much to be desired but I'm pretty sure that's the phone and not the ROM.
Click to expand...
Click to collapse
We must not forget that the device has a battery of 1600mA, for this reason it is normal that the the device have a short battery life.
There is always the possibility of purchasing an extra battery with external charger.
Greetings.
You're right of course and this is a great rom. I apologize if it came off like I was complaining or criticizing, this is great work and I'm utterly grateful to have cm11 on my old Burst.
Thank you mifl for cm11.
First of all thanks to all devs for cm11.
I am loving it by far.
Now on topic. I have two questions-
1). Is there any app that can control vibration intensity of phone, nothing from playstore works.?
DU rom from marduk have it inbuilt and works flawlessly but rom has bugs of wifi tethering, Bluetooth and random restart. I rely on tethering heavily so i am on cm11. Is there anyway i could get it on cm11?
2). Anyone facing any random restarts.?? I faced some random restarts recently when using multiple tabs of UCbrowser. Though i wasnt able to catch anything from log. I will post if it happens next time.
3). It is taking too much time to charge if handset is kept on usage.?? Well mine does. But charger is of samsung (.7A)..
Thanks for sharing this great Rom.
God bless you.
Thanks.
herecomesmaggi said:
First of all thanks for cm11. I am loving it by far.
Now on topic. I have two questions-
1). Is there any app that can control vibration intensity of phone, nothing from playstore works.? DU rom from marduk have it inbuilt and works flawlessly but rom has bugs of wifi tethering, Bluetooth and random restart. Is there anyway i could get it on cm11 of mifl.?
2). Anyone facing any random restarts.?? I faced some random restarts recently when using multiple tabs of UCbrowser. Though i wasnt able to catch anything from log. I will post if it happens next time.
3). It is taking too much time to charge if handset is kept on usage.?? Well mine does. But charger is of samsung (.7A)..
Thanks for sharing this great Rom.
God bless you.
Thanks.
Click to expand...
Click to collapse
First the rom is not my property. It is compiled from PantechDevTeam repositories.
If you want to get the DU version, you must wait to be released this compilation or you compile DU from marduk191 repositories.
Of the mistakes you've written would be important you will provide a log, to study errors.
Greetings.
Find a 1.0 A charger, it still won't be ideal but I think you'll notice improvement
Thank you for replying. I tried using Asus zenphone 5 charger of 1.25A it worked great.
Glad I could help. If I remember correctly it was your comments on the old CM 10 thread that originally led me to Slim Bean, which was a great improvement back on jelly bean. So thank you too lol
I have found a way to lower the intensity of vibration feedback of buttons..
You will need to decompile framework-res.apk and have to look for values. Xml in res folder some where at last there will be line <integer-array name="config_keyboardTapVibePattern"> Just change its value to suitable. Recompile and flash. Btw i am using value "2" instead of 40.
Thanks.
If u need a proper guide ping me...
whatsapp camera : black screen
i am using cm11 latest build. when ever i open camera in whatsapp application i see black screen.. but if i click the snap is taken.. same with bar code scanner app as well.. tried to check the log but there is no error registered for this.. i thing i have missed some setting..
Issues Installing Custom Firmware
First of all, thanks for all your work on Burst development. Here's my issue. I installed ICS from the Pantech website and then rooted my phone a year or two ago with "The Burst Hack Tools" mentioned in the instructions. I found the instructions to install custom firmware and tried installing CM11. Everything seemed to be going fine until I restarted my phone. I upgraded CWM to 6.0.2.7 touch version and retried. Same result. The third time I thought I may have forgot to wipe the cache so I was sure to do that. Same result. Question: Do I need to do a clean install of stock 4.0.4 Ice Cream Sandwich before intalling CM11? Thanks for your help.
---------- Post added at 06:41 PM ---------- Previous post was at 06:36 PM ----------
mifl said:
We must not forget that the device has a battery of 1600mA, for this reason it is normal that the the device have a short battery life.
There is always the possibility of purchasing an extra battery with external charger.
Greetings.
Click to expand...
Click to collapse
I've had good luck with this battery: Onite 1800mAh Battery for Pantech Burst P9070. Found on Amazon. I do notice the 200 mAh difference.
SparkyMcfly said:
First of all, thanks for all your work on Burst development. Here's my issue. I installed ICS from the Pantech website and then rooted my phone a year or two ago with "The Burst Hack Tools" mentioned in the instructions. I found the instructions to install custom firmware and tried installing CM11. Everything seemed to be going fine until I restarted my phone. I upgraded CWM to 6.0.2.7 touch version and retried. Same result. The third time I thought I may have forgot to wipe the cache so I was sure to do that. Same result. Question: Do I need to do a clean install of stock 4.0.4 Ice Cream Sandwich before intalling CM11? Thanks for your help.
Click to expand...
Click to collapse
Please see PDT Wiki page to install a new recovery to cm-11.0. After make this you must follow the Guide to Installing Custom Firmware in Pantech Burst Wiki Page.
Greetings.
mifl said:
Please see PDT Wiki page to install a new recovery to cm-11.0. After make this you must follow the Guide to Installing Custom Firmware in Pantech Burst Wiki Page.
Greetings.
Click to expand...
Click to collapse
Thanks for the directions. I flashed the latest version of CWM and reinstalled CM11. It has been working great. The only issue I've noticed is that if I turn off the phone and turn it back on, apps that have been moved to the external SD card "disappear". They are still there, I just have to add the icons back. From what I've read, this is a problem with Android? Any suggestions on how to fix it?
SparkyMcfly said:
Thanks for the directions. I flashed the latest version of CWM and reinstalled CM11. It has been working great. The only issue I've noticed is that if I turn off the phone and turn it back on, apps that have been moved to the external SD card "disappear". They are still there, I just have to add the icons back. From what I've read, this is a problem with Android? Any suggestions on how to fix it?
Click to expand...
Click to collapse
I have no answer to this, but I would also like to know if there is a work around or fix to this
SparkyMcfly said:
Thanks for the directions. I flashed the latest version of CWM and reinstalled CM11. It has been working great. The only issue I've noticed is that if I turn off the phone and turn it back on, apps that have been moved to the external SD card "disappear". They are still there, I just have to add the icons back. From what I've read, this is a problem with Android? Any suggestions on how to fix it?
Click to expand...
Click to collapse
This is a known bug in the code of Android 4.4. I think this can be solved with Xposed Module:
* http://www.xda-developers.com/fix-external-storage-handling-with-xposed-module/
Greetings.
Help with Xposed
mifl said:
This is a known bug in the code of Android 4.4. I think this can be solved with Xposed Module:
* http://www.xda-developers.com/fix-external-storage-handling-with-xposed-module/
Greetings.
Click to expand...
Click to collapse
So I installed Exposed from here: http://dl-xda.xposed.info/modules/de.robv.android.xposed.installer_v33_36570c.apk
Then I installed HandleExternalStorage from the Play store: Play Store: http://tinyurl.com/nnajr7f
I went into Exposed and enabled HandleExternalStorage. Then rebooted. Icons dissapeared.
I uninstalled a couple of apps that were on the SD and reinstalled. Rebooted. Still missing
Icons. Any help would be greatly appreciated. Thanks.
Volume wake
Please excuse my ignorance but how can one set wake on volume keys? Its a small detail that is driving me crazy.
Gapps for Cm11 pantech burst
Is there another link to Gapps for cm11 on pantech burst? the link at github si giving a 404 error. plzzz help
First I would love to say thanks to everyone who helped put this ROM together :good:
Second, I'm having a problem with my storage. When I go to apps, my internal storage and external SD storage got mixed up, now I can't download entering from the play store. Please help!!

[ROM] [Project ] Pure AOSP 5.0.2+Google Updates (1/01/2015)

The idea behind this project is to compile a Pure AOSP ROM. The difference is I have been little by little including and testing new changes and fixes added to the AOSP code from Google that has not yet been tagged or added to the release branch and will most likely be added into a future Lollipop update., hence the reason for 5.0.2_Plus. The only change added that was not committed by Google is that the ZIP can be flashed in TWRP without replacing TWRP with the Stock Recovery and that is it.
There is more coming but would like to first verify my testing on what has been done so far. The idea is to stay ahead of the curve with fixes and updates coming down from Google before they are released. As offered in the development Q&A Thread I started with this idea is that anyone who is able is welcome to jump on and help. All and all is just sifting over the AOSP Master branch adding new commits that have not yet been tagged as part of a release branch. Thought of the idea after reading a statement from Google true or not that allot of bug fixes have already or are in the process of being added into ASOP. These commits all come from the master branch developers do not build from and is more of a staging ground for future releases. A few of these commits are less than a week old. Anyhow so Instead of this being my Rom I would like us to just all have the most updated code base to work with so let me know and will give full permission to the Github organization. We wiil just need to set up separate branches for testing to insure our Master branch is stable at all times so it can be used and trusted by all our devs to use in their Roms. I am sure we can gather a team of testing volunteers. Otherwise this is again 100% AOSP code without any modifications outside what has been committed by Google and planned on keeping it this way. Although I am posting like stated above would not like to think this is my Rom but more for the community in general so our Developers have the latest stable code to work with when creating Roms and am not just posting because as Google has proven with Lollipop the more testers the better as we all have different set-ups and use are devices differently but I also wanted to give the project/idea a bit of attention.
A Few Added Update Examples.
https://github.com/Android-AOSP/And...mmit/a05556633ae5a6d1db164597b93f8b6cbbdf2608
https://github.com/Android-AOSP/And...mmit/e6beb1369165f97a4df24a1d1966c41e392c44e7
https://github.com/Android-AOSP/And...mitM/be42994b5a42914071adddfd5d989950e8e47bd9
https://github.com/Android-AOSP/And...mmit/0c89e1b9395093f71cf73508553d5e4058093ec0
https://github.com/Android-AOSP/And...mmit/4c53a7872b1f37ec184801f16d39584ca3b9bcce
https://github.com/Android-AOSP/And...mmit/9d2f14442f2e1d1507dbdc6cc7b9348513a907f9
https://github.com/Android-AOSP/And...mmit/905c6e72ecdc6e170744649b78e8fbb919f71efd
https://github.com/Android-AOSP/And...mmit/1a96e2b079e8007fe965bd30cd02cb191a613510
https://github.com/Android-AOSP/And...mmit/4fcbf285db7f9e20795783b676963d42499dbd64
https://github.com/Android-AOSP/Android-AOSP_bionic/commit/eaf5aa7d22bd2f6b2eae4c81a60950f89e2d7df4
https://github.com/Android-AOSP/And...mmit/74574e8aa5a2de32e10364fd2f495023fff2a267
https://github.com/Android-AOSP/Android-AOSP_build/commit/49657b7a459ee90b3635bef989f8f9728d564068
https://github.com/Android-AOSP/Android-AOSP_build/commit/1df3707a04651966ca17796f321d23ab3ed6ed2e
https://github.com/Android-AOSP/And...mmit/6fe9c73738e9da0192971576d120802d4c094556
https://github.com/Android-AOSP/And...mmit/44c1c3235d29095c4d987d19155c7260d1a33e0f
https://github.com/Android-AOSP/And...mmit/33baf53861712c3f84606a017943e36bdc680b50
https://github.com/Android-AOSP/And...mmit/a975a08cfb30ad6b2994647c0c6f09e2abd20e28
https://github.com/Android-AOSP/external_protobuf/commit/1a96e2b079e8007fe965bd30cd02cb191a613510
https://github.com/Android-AOSP/external_protobuf/commit/4fcbf285db7f9e20795783b676963d42499dbd64
https://github.com/Android-AOSP/frameworks_base/commit/cc50afe3bdcc3adfa0f4121bf461996996e69a3e
https://github.com/Android-AOSP/frameworks_base/commit/1be740dd60f4d95e1f9ac4aac7e4d6148e3b2dd1
https://github.com/Android-AOSP/frameworks_base/commit/1cca2282dc9a3b7ecc08729af201923842ddfc86
https://github.com/Android-AOSP/frameworks_base/commit/7db1192e72b45111556631dba125a635edff3235
https://github.com/Android-AOSP/frameworks_base/commit/b29136581cc3181e59193e0b6448f0c3f5990081
https://github.com/Android-AOSP/build/commit/de655233a4308340fc71490e86fd0f218cc7fec4
https://github.com/Android-AOSP/build/commit/ab6f841841a0930c7e178a949ada39152e24540f
https://github.com/Android-AOSP/hardware_libhardware/commit/9ede7f730bca338cd3ccad8962e253f28ae17976
https://github.com/Android-AOSP/hardware_libhardware/commit/d4f431fec4136f6eeee919ac3190762fba832942
https://github.com/Android-AOSP/hardware_libhardware/commit/898bcd96e3d80e99d9200cceb4af754bae6d5f4a
https://github.com/Android-AOSP/bionic/commit/d90f39af35c1f2a9972198f92e803e3ca73ac910
Downloads
Download Rom
aosp_hammerhead-ota-5.0.2_plus_r4.zip - 191.35 MB
aosp_hammerhead-ota-5.0.2_plus_r3.zip - 191.35 MB
aosp_hammerhead-ota-5.0.2_plus_r2.zip - 191.34 MB
aosp_hammerhead-ota-5.0.2_plus.zip - 191.34 MB
PA-Gapps
http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900
So far I have been using the "Mini Modular package" for testing without any issues.
Root
Root is optional but recommend SuperSU
http://forum.xda-developers.com/showthread.php?t=1538053
Have had version 2.37 in storage and had been using without issue but updated to 2,40 with last test without any issues. What can I say Im lazy that way so unless having an issue just used what works but figured most would grab the latest so thought it best to give it a test before posting.
Kernel is also %100 stock but including a shameless plug for my Starship Kernel as in testing have worked well together and is the only other Kernel verified though am sure you should not have any problem with other AOSP/Stock Kernels.
Starship Kernel
Starship-lollipop_Kernel-3.4.36_r1.zip - 7.65 MB
Starship Kernel Source
https://github.com/Starship-Android/android_kernel_lge_hammerhead-starship/tree/lollipop
As usual I am not responsible for your device and you are using anything posted in this thread at your own Risk.
Is %100 pure AOSP so no screen shots as am sure you are aware what it looks like at this point.
Change Log 5.0.2_plus_r4
Removed the below commit "Add ip6-localhost to /system/etc/hosts."
https://github.com/android/platform_system_core/commit/25147416bb105914c3cdf8fd65ca7cc20dae0f3e
Looks like a few apps are not fans of having an ip6 entry for localhost. Transparent Weather Widget for example can not find the device location with the enty included.
In looking for the cause of the above issue also reverted.
https://github.com/android/platform_frameworks_base/commit/e4ec09da0b4a31e23f1a19bdd1ea99e0f87cadac
Honestly reverted looking for the cause and did not remember to restore once identifying the cause. Overall is an old commit and dont think will make any difference whatsoever or would have been tagged for use in a past release so not going to bother.
Before the ip6-localhost commit issue had been identified by a user from the Nexus 4 version of this project was testing newer commits. The following few had been in testing at the time and included with the N4 Mako build. They are just a few of what was intended but because updating to r4 for the bug fix these are included in the r4 release.
Add missing <string.h> includes.
https://github.com/Android-AOSP/and...mmit/718568d982f92a93da19bfb8d4ea6dd996913e25
Add missing <string.h> includes.
https://github.com/Android-AOSP/and...mmit/8cb6a047d89479e4f65e0bcfa1642b4891463c04
Fix missing parenthesis.
https://github.com/Android-AOSP/android_aosp_build/commit/49657b7a459ee90b3635bef989f8f9728d564068
Remove superfluous OpenSSL include paths.
https://github.com/Android-AOSP/and...mmit/b9e7a844fc751b9fdda7d452dee361f15815199b
Besides this am about %80 done Starship L Rom and have offered to join a development team so lots going on but plan to keep this up and finish my new Starship L rom. Otherwise looking very much foreword to once again working as part of a team as since I started developing 3 years ago these last few month of Nexus ownership has been the first time I have worked alone and so much more prefer having a team to work with and discuss things with. Love my cat but pretty sure he doesn’t understand what I am talking about and my friends although interested are intimidated believing developing is so over their heads they could never do it .
woot woot
Vero good
Why 2014
Good ROM, but since I am a Sprint user, the update-device.zip fix doesn't seem to work on this ROM, nor does the update profile/prl zip fix, which is important for calls.
Like the idea! Only complaint us that you could hide some text like the github picks and downloads under a spoiler
Edit. Oh and first page woot woot!
Sent from my Nexus 5 using XDA Premium 4 mobile app
The only thing bothers me is the aosp dialer icon, so anti-material, can someone solve that out?
Any bugs?
iamterence said:
Good ROM, but since I am a Sprint user, the update-device.zip fix doesn't seem to work on this ROM, nor does the update profile/prl zip fix, which is important for calls.
Click to expand...
Click to collapse
I am on T-Mobile and looks like neither Google or myself had been thinking about Sprint users. Needs to take a look
chairshot215 said:
I am on T-Mobile and looks like neither Google or myself had been thinking about Sprint users. Needs to take a look
Click to expand...
Click to collapse
Much appreciated, good sir. If nothing can be done, all will still be well. Still appreciate your efforts.
iamterence said:
Much appreciated, good sir. If nothing can be done, all will still be well. Still appreciate your efforts.
Click to expand...
Click to collapse
Think if rooted with bussybox installed fix may then work. Otherwise think would need to either build the fix in before compiling or build non block based and add files into the zip. Took a quick look and the fix I downloaded called on bussybox in the update-script when flashing so installing bussybox may fix the sprint fix, lol. Otherwise does not look like a hard fix taking a quick look at cm12. Have a meeting at 1:00 and look into some time after.
Any other download mirror ?
It is hardly possible for me to download the rom from dev-host
hunzhang said:
It is hardly possible for me to download the rom from dev-host
Click to expand...
Click to collapse
?????????
chairshot215 said:
Think if rooted with bussybox installed fix may then work. Otherwise think would need to either build the fix in before compiling or build non block based and add files into the zip. Took a quick look and the fix I downloaded called on bussybox in the update-script when flashing so installing bussybox may fix the sprint fix, lol. Otherwise does not look like a hard fix taking a quick look at cm12. Have a meeting at 1:00 and look into some time after.
Click to expand...
Click to collapse
Forgive my noobness, as I'm usually on point with this stuff, but how can I root WITH busybox? Would I need to boot up and then download the app from the store? Because if so, I can't get past the setup screen without constant update device FC's.
Now, what IS interesting is that if I just flash the ROM and update-device.zip, o don't get the FCs. But as soon as I flash gapps, that's when things start to head south.
iamterence said:
Forgive my noobness, as I'm usually on point with this stuff, but how can I root WITH busybox? Would I need to boot up and then download the app from the store? Because if so, I can't get past the setup screen without constant update device FC's.
Now, what IS interesting is that if I just flash the ROM and update-device.zip, o don't get the FCs. But as soon as I flash gapps, that's when things start to head south.
Click to expand...
Click to collapse
Sorry maybe bad word placement on my part but had meant root the Rom and then install busybox which requires root. You should be able to download SuperSU and then flash it in recovery. Once SuperSU is installed can download busybox installer from playstore.
This is the version of SuperSU I have used the last few builds.
https://www.dropbox.com/s/1y5m5vvtp55o4f0/BETA-SuperSU-v2.44.zip?dl=0
Still may be hard if you are having FC issues on setup. I am honestly not an expert but would not think being on Sprint would cause FC issues but again I don’t really know. If you are experiencing FC issues would try a full wipe including data if not done so previously and install again. Not sure its the case but I first tried a dirty flash from 5.0 stock to an AOSP build and all my Google Apps which I believe set-up wizard is included but was OK for me would not work, Not the best solution but ended up un-installing and reinstalling all my Google Apps. After that everything was OK. Think the issue was caused by having flashed different versions of the Google Apps that did not vibe with the updates from the play store. After I dirty flashed again from 5.01 to 5.02 using same version of Gapps and did not have any issues. Not saying is the case but not doing a data wipe can cause some strange bugs not always seeming to be related to the bugs experienced. I once had an issue back in the days og GB that my wifi had stopped working. Had been on forums and bugging out for a few days and then for some unrelated reason wiped the MMS app data in application settings and performed a reboot. First thing I noticed was wifi was working. How bad data from the MMS app could have broke wifi is still an unsolved mystery but just to be sure restored a Nandroid with the bad wifi twice and was able to reproduce the fix both times by wiping MMS data.
Otherwise let me know if anyone else has experienced a FC during set-up but only if you have wiped the data partition. I have otherwise flashed about 15 times so far and have yet seen an app FC on me.
kowalsfee said:
The only thing bothers me is the aosp dialer icon, so anti-material, can someone solve that out?
Click to expand...
Click to collapse
Yeah not all of AOSP is Material. I myself after flashing download a root file explorer and remove the calendar, voice dialler, music and MSS apk's and then download Google Calender and the new Google Messenger apps from the play store. I also install the Google Calender and have been using Google Inbox in place of Gmail. Otherwise not much else from Google as I also have an N7 and N9 so in general keep the phone slim and load up the now N9. Was not a fan at first but now a days can no longer use the N7. Only thing about the N9 that still bugs me is they copied Apple with the 4:3 aspect ratio. Is awesome for old TV shows on Netflix but all others pretty much take the same space they would have on the N7 making the larger screen pretty much null and void. Otherwise had been pretty disappointed at first but has grown on me big time.
Added a bunch more updates. Still working on a fix for sprint users but have a good idea what needs to be done.
Also had added from Google a record bug report option with power off seems I forgot to remove before building but all it does is dump a bug-report in storage. Has no other effect. Otherwise smooth a butter and bug free.
Any chance for a Mako port? I have a Nexus 5 myself, but someone I know has a nexus 4 that's acting up (SoD) and so i thought that this might help them out.
I just flashed over to this ROM from stock 5.0.1 I am hoping that this build will fix the memory leak I've had on the official build. So far everything seems to work well except for the security settings. Anytime I try to open it settings simply force closes. Does anyone else have this issue? I usually use smart lock so I am sad to see this broken. I have a unlocked nexus 5 running on AT&T and I did a full wipe before flashing. I also flashed the recommended GApps package. Thanks in advance
Yeah thats my bad uploaded the wrong .zip including a stock file experementing for Sprint Users. Will recompile and post correct build. Everything else should be the same so once fix is posted should be ok to just wipe system & cache before install. Just need to also reflash same gapps package as before.
Also going to post manifest so can build for all Nexus devices. Can also build it special if needed. If you guys are seeing improvments with the Updates let me know and can start posting builds for all Nexus devices. I only have the 7 (2013), 9 and 5 for testing. I see a few big improvmets but curious what others think before starting to build for every Nexus. Know a few apps like messaging are still not material and was surprised to see old school Music first time building pure AOSP but wanted purity so have laft those things be.
Is r2 the release build with the Sprint fixes?

HELP CM 12.1 turn off screen after boot, any one is using CM???

Hi team,
I been trying to instal CM 12.1 on LS990 but after boot the screen turn off and the phone dosent respond, i try to remove the battery and boot again but keep the same error. i realy like CM 12.1 on my old phones but never have this issue before,
Also there is a way that i can install LG camera on CM??
Please ask if you need more info
Gustavo linux said:
Hi team,
I been trying to instal CM 12.1 on LS990 but after boot the screen turn off and the phone dosent respond, i try to remove the battery and boot again but keep the same error. i realy like CM 12.1 on my old phones but never have this issue before,
Also there is a way that i can install LG camera on CM??
Please ask if you need more info
Click to expand...
Click to collapse
cam depends on lg framework , cm uses default android framework, so no, unless one port all the work
if a rom doesnt work , just installen a new one or redownload or other version etc
if your realy out of the head just reinstall default rom and start over
not booting can have so many isseus , its just to simple as get a rom that you know that sould work as everybody is using it.
afcorse you can have user error like not have been wiping and other smale things you get to know when you do rom flashing
Jhinta said:
cam depends on lg framework , cm uses default android framework, so no, unless one port all the work
if a rom doesnt work , just installen a new one or redownload or other version etc
if your realy out of the head just reinstall default rom and start over
not booting can have so many isseus , its just to simple as get a rom that you know that sould work as everybody is using it.
afcorse you can have user error like not have been wiping and other smale things you get to know when you do rom flashing
Click to expand...
Click to collapse
I try diferents dates off CM but all of it have the same issue, y try other roms and work perfect.....
CM 12 issues
Hello seen your post and thought I may be able to help... After I first rooted my G3 the first ROM I wanted to try was CM. I tried cm11 Eos first worked like a charm so I thought about trying cm 12 well I ran into problems. Third time was a charm it would try to boot and my phone would just shut off or would never stop loading I was confused. So instead of downloading the ROM on my PC and dropping onto storage I reload stock backup and downloaded straight from browser in my phone. Now I'm not sure why but it worked so either I got two bad downloads or transfer from PC to phone corrupted the file either way it worked and cm12 is bomb as hell I also found a port of quick remote and lg camera but the cm camera is fine and quick remote takes a little tinkering to work but I'm on night lies and so far no bugs for me Bluetooth WiFi GPS all work haven't tried nfc but I may just to see... If you have any questions let me know I freaked when I could not get it working but seen too many people saying it worked great so I didn't give up...
SalemGDU said:
Hello seen your post and thought I may be able to help... After I first rooted my G3 the first ROM I wanted to try was CM. I tried cm11 Eos first worked like a charm so I thought about trying cm 12 well I ran into problems. Third time was a charm it would try to boot and my phone would just shut off or would never stop loading I was confused. So instead of downloading the ROM on my PC and dropping onto storage I reload stock backup and downloaded straight from browser in my phone. Now I'm not sure why but it worked so either I got two bad downloads or transfer from PC to phone corrupted the file either way it worked and cm12 is bomb as hell I also found a port of quick remote and lg camera but the cm camera is fine and quick remote takes a little tinkering to work but I'm on night lies and so far no bugs for me Bluetooth WiFi GPS all work haven't tried nfc but I may just to see... If you have any questions let me know I freaked when I could not get it working but seen too many people saying it worked great so I didn't give up...
Click to expand...
Click to collapse
I will try directly to the phone and i will coment.... FYI y download it from UBUNTU (chromium) and WINDOWS 10 (Chrome)
I'm currently using it but haven't had any issues. If I can help somehow, let me know
Belongs in q&a not Android development
Sent from my LGLS990 using Tapatalk
Mods please get this outa here
Sent from my LG-ls990 using Xparent BlueTapatalk 2

Categories

Resources