Develop Bugs

Custom rom off LG ICS

Is it possible to create a custom rom based off of LG's ICS. I have tried a few things but I end up with security error everytime I try to edit the rom. The reason I ask is because the LG rom seem much more fluid and smooth than CM9. One of the reasons I want to do this is to get rid of the annoying scrolling carrier logo on the notification bar. Anyone know how to do this?
Dave,

Maybe you should just wait for the real release that will come in a couple of week every one will do rom from that (for sure I will)
Sent from my LG-P930 using xda premium

Sounds good. What are you planning to do to the rom when you get the full ics release?

Need to make full deoxide and root ..I'm waiting too
Sent from my LG-P930 using XDA

Are you planning to make it more "stock" ics?

davefootball123 said:
Are you planning to make it more "stock" ics?
Click to expand...
Click to collapse
Isn't that what CM9 is for?

I suppose so, Its just that CM9 is sluggish compared to the LG ics.

Am I the only person in the world that chose ICS over JB?

Am I the only person in the world that chose ICS over JB?
When I got my Nexus GSM, I instantly upgraded it to JB. Don't misunderstand me, JB was really awesome. However, simple and featureless... I supposed that's why people make ROMs, to build on what Google gave us.
Well, I like features, lots of features, so I installed AOKP M6. And I absolutely love that ROM, but I am wondering if there is anything comparable to it that's JB based. Guess in my mind I am waiting for AOKP JB ROM to move into couple milestone revisions...

AOKP's current builds can be found here:
http://rootzwiki.com/topic/30659-all-devices-in-source-aokp-jellybean-nightlies-update-nightly/
(Sorry for cross-forum posting...TeamKang is Rootzwiki exclusive now. I don't want to step on any toes by posting this thread on XDA)
They're lacking in comparison to the ICS builds...but if you check the change-log in the OP...it's got quite a bit.
But no, you're not alone.
I stayed on ICS a lot longer than most did. I only switched over due to my love of AOKP...and the fact that %90 of my "required" mods are already included. Except for the Remove NavBar option...but I've been making a flashable .zip for that since they were first released for personal use and for anyone else who wants it.

Nope. Recently downgraded again, see my signature. xD
Sent from my Galaxy Nexus using xda app-developers app

I stayed on M6 until two days ago.
I finally thought JB had evolved enough.
Happy so far.
Sent from my Galaxy Nexus using Tapatalk 2

Some people just like it simple, that's part of why they chose to go with a nexus.
Android is beautiful.

I went the opposite way, at least for a time. I typically "require" the features found in CM, but ran Bigxie's stock builds for a few weeks and was very happy that way, just had to install a few apps to fill in the gaps, notification toggles, an app for profiles and quiet hours, etc... The overall feel of JB trumped that of ICS for me. For me even a vanilla JB build is better than a great ICS build with customizations, etc...
That said, I've been on a CM10 kang for 2-3 weeks now.

This thread makes no sense. You don't like ICS better. Its just that aokp happened to not merge everything yet. Once there is a JB equivalent are you still saying you'd stay with ICS?

RogerPodacter said:
This thread makes no sense. You don't like ICS better. Its just that aokp happened to not merge everything yet. Once there is a JB equivalent are you still saying you'd stay with ICS?
Click to expand...
Click to collapse
Yea, I don't get this. Sounds like you enjoy ics better because the devs have had it longer. Jb just came out!
Sent from my Galaxy Nexus using xda app-developers app

I've been considering downgrading to ICS for the sake of having better Lightflow reliability. Even after the July 17 update, it's still not working right for me. Tried a bunch of options, nothing made too much difference.

I tend to go back and forth because HBOgo and MAXgo aren't compatible with jb yet. But that's the only reason to go back for me.
Sent from my Galaxy Nexus using xda premium

Jubomime said:
I tend to go back and forth because HBOgo and MAXgo aren't compatible with jb yet. But that's the only reason to go back for me.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
This and the auto dimming is annoying. Not having flash sucked at first but I found stick it worked great as an alternative. I have decided that im gonna sick with aokp m6 until jb is official for Verizon
Sent from my Galaxy Nexus using xda app-developers app

Yes, you might be the only one
Sent from my Galaxy Nexus

Jelly Bean ROMs are still new. Soon enough they will catch up with what ICS ROMs have.
Sent from my Galaxy Nexus using xda app-developers app

I stayed with ICS til less than a week ago, but I'm now running JB liquid. It has all the features I've grown accustomed to minus hold power key to toggle torch (which only worked 30% of the time anyway).
My only problem is auto brightness doesn't work as smoothly as on ICS (solved with a configurable brightness toggle), and GPS take about 15 seconds longer to lock. Both seem to be universal to JB.
Sent from my Galaxy Nexus using xda premium

[Discussion] Returning to older versions of Android

Hey,im bored so id like to start a discussion.
So my question is,has anyone ever went from 4.2.1 jb to 4.1.2? Or even ICS?
I've went from 4.2.1 to 4.1.2,cm10.00 stable,and it's a major difference. Both it lacks some features,but much much better in speed and overall stability.
I've been thinking about to go from my cm10.1 nightly to cm9.1.
Lets see your thoughts

I don't think going back to ICS would be any good since you'll lose all the speed improvements from project butter. I'm considering gong back to 4.1.2 myself tho
Sent from my Galaxy Nexus using xda app-developers app

4.1.2 is much faster and more stable than 4.2,believe me
Look!Look at my pucture! Yes! I am a demon,my girlfriend caught me accidentaly whe she was taking a picture!

DeHuMaNiZeD said:
4.1.2 is much faster and more stable than 4.2,believe me
Look!Look at my pucture! Yes! I am a demon,my girlfriend caught me accidentaly whe she was taking a picture!
Click to expand...
Click to collapse
I agree with the "more stable" part, since I had to stray from stock kernel to avoid SAD (suddenly absent display). But faster? No. At first 4.2 slowed my phone down, after a factory reset the speed and smoothness has been identical.
So now using rasbean and dax modified trinity my phone is as stable as it was on stock 4.1. Now I wait for 4.2.2.
Sent from my Galaxy Nexus using xda premium

Im returning to cm10.0.0 untill cyanogen releases cm10.1 4.2.2
Look!Look at my pucture! Yes! I am a demon,my girlfriend caught me accidentaly whe she was taking a picture!

I hate the lockscreen on 4.2... I keep trying CM 10.1 and AOKP builds but I still hate it.
4.1.2 is going to be on my phone from now on until there is a way to revert the lockscreens!!
Overall I don't see the need for 4.2 yet. I can install the 4.2 camera and keyboard. So I don't think I am missing out on anything but some new animations

I'm so used to CM10.1 I don't think I could go back now!

I used cm10.1 for a while then went back to lastest cm10 nightly. It just feels much better in use and at least for me battery life is better.

I find 10.1 more stable and I get better battery life too. The lock screen is definitely nicer looking on 10 I'll give you that one.
Sent from my Galaxy Nexus using xda premium

Sourcery has too many customizations to go anywhere and it's extra
stable with ak kernel. Major updates all the time. Latest gives us
combined nav and status bars crazy boot animation and much more.

Lockscreen doesnt bug me. But the overall stability. 4.2.1 even lags here and there.
And cm10.1 is good,and id use AOKP,but its kinda slow. And i hate transparent status bar and nav bar. It just doesnt go with me.
Look!Look at my pucture! Yes! I am a demon,my girlfriend caught me accidentaly whe she was taking a picture!

I went from 4.2.1 to 4.1.2 to cm 10.0 and I love it
Sent from my Galaxy Nexus using Tapatalk 2

New GNex owner here... I tried going back to 10.0 stable from stock 4.2.1, but I kept getting keyboard FC's. I believe this was due to me running stock 4.2.1 before flashing... Maybe someone can confirm that I'll need to flash stock google 4.1 image before I try to go back to 10.0?
Like others, I just don't like the 4.2.1 lockscreen at all.

I think that doesnt really matter. You should wipe everything before and after,and find 4.2 keyboard for cm10,it works just fine.
Look!Look at my pucture! Yes! I am a demon,my girlfriend caught me accidentaly whe she was taking a picture!

4.1.2 is where I'm staying for a while.

Isn't this discussion similar to other 4.2 vs 4.1 threads ? And those who went back to ICS are in minority I guess.

DeHuMaNiZeD said:
I think that doesnt really matter. You should wipe everything before and after,and find 4.2 keyboard for cm10,it works just fine.
Look!Look at my pucture! Yes! I am a demon,my girlfriend caught me accidentaly whe she was taking a picture!
Click to expand...
Click to collapse
Man, I tried everything... Twice. No go on the stock keyboard. Kept getting fc message about it closing.
Sent from my Galaxy Nexus using xda app-developers app

gatorstew said:
Man, I tried everything... Twice. No go on the stock keyboard. Kept getting fc message about it closing.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Here's what i did,i got a same problem.
Wipe
Flash the rom
Flash gapps
Boot it fo the setup screen
(Keyboard fc here)
Reboot into recovery
F
Dirty flash rom and gapps again and it works!
(Dirty flash:flash witouth wiping)
Sent from my Galaxy Nexus using xda premium

DeHuMaNiZeD said:
Here's what i did,i got a same problem.
Wipe
Flash the rom
Flash gapps
Boot it fo the setup screen
(Keyboard fc here)
Reboot into recovery
F
Dirty flash rom and gapps again and it works!
(Dirty flash:flash witouth wiping)
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thanks, I'll give it a go.
Sent from my Galaxy Nexus using xda app-developers app

I am surprised, I know every phone is a little different but I used to have to plugin around 10 or 10:30 with only 5% left now I plug in around 11 and I still have 40 to 45%. I used to suffer from the phone not turning on at least once a day I would have to pull battery (tried multiple ROMs same on each) now it has been running for a week no issue. I guess I will count myself lucky and not mess with it.
Sent from my Galaxy Nexus using xda premium

i need an AOSP ROM w/ HDMI working???

I have just switched back to the gs3 from the Note 2 because I S3 has so many great AOSP Rom's available and the size of the Note 2 was becoming somewhat of an inconvenience for day to day use. After flashing Baked Black Bean which was amazingly smooth, I discovered that HDMI out was not functioning, and I use HDMI almost every day so it's an almost necessary feature for me. I also tested Illusion, Slim Bean, and Liquid Smooth and I had no luck with HDMI out.. I'm thinking I won't be having any luck with this on 4.2, but I was hoping maybe someone may know how to get it working, or maybe there's a kernel I could flash that would allow it? Any advice would be appreciated.
Can anyone confirm HDMI out working on any AOSP Rom's, even 4.1 would be great! Thanks in advance to anybody who may be able to help

Have you try ed 4.1 stock base roms

JJR85 said:
Have you try ed 4.1 stock base roms
Click to expand...
Click to collapse
I tried PAC man rom, but at that point I'd tried several and threw the towel in, lol. I guess I'll have to try a few more when Iget the ttime.

I meant 4.1.1 pacman is 4.1.2 or a ROM that's stock base lol
Sent from my SGH-T999 using xda app-developers app

JJR85 said:
I meant 4.1.1 pacman is 4.1.2 or a ROM that's stock base lol
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I tried Jelly Bam & really thought that might have HDMI functioning since it has the TW launcher, but no such luck. I even tried switching to lean kernel on Baked Black Bean, but that was a no go too. . I really think it's probably the AOSP kernels that don't support it, so I think I'm out of luck.

You should ask the dev if it supports hdmi
Sent from my SGH-T999 using xda app-developers app

Gunshy after 2 bricked phones

Really want to flash some of these newer asop roms but i am gunshy after bricking 2 Htc one's after installing CM 10.2 and Carbon Rom on phone #2.
I frequently flashed tons of roms on my gs3 and gs4 and never had a brick i couldn't recover from.
Can someone give me some reassurance that its ok to try asop roms again? Really itching to flash them again!
Thanks in advance for any advice.
Sent from my HTC6500LVW using xda app-developers app

dlscott1111 said:
Really want to flash some of these newer asop roms but i am gunshy after bricking 2 Htc one's after installing CM 10.2 and Carbon Rom on phone #2.
I frequently flashed tons of roms on my gs3 and gs4 and never had a brick i couldn't recover from.
Can someone give me some reassurance that its ok to try asop roms again? Really itching to flash them again!
Thanks in advance for any advice.
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
how are you brcking them? i'm not trying to be a ****, but it sounds like it's more you than the roms or devices.

First one i was fiddling with dsp manager on cm10.2 and the phone cut off in the middle of a song. 2nd time is more my fault
I messed with transition settimgs and sweep to wake kernal settings on carbon rom. The phone overheated and the speakers and data were broken.
I havent done anything i hadn't done on my s3 or s4. Maybe this phone is more delicate? Maybe it was the asop roms? Maybe i have terrible luck? Im kinda stumped.
Sent from my HTC6500LVW using xda app-developers app

dlscott1111 said:
First one i was fiddling with dsp manager on cm10.2 and the phone cut off in the middle of a song. 2nd time is more my fault
I messed with transition settimgs and sweep to wake kernal settings on carbon rom. The phone overheated and the speakers and data were broken.
I havent done anything i hadn't done on my s3 or s4. Maybe this phone is more delicate? Maybe it was the asop roms? Maybe i have terrible luck? Im kinda stumped.
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
as far as i'm aware, and somebody please correct me if i'm wrong, but AOSP doesn't play perfectly well htc phones. that's why officially there's GPE vs AOSP.
but, as long as you can get back your bootloader you'll be fine on trying AOSP.
right now you can try santod's tiktak 4.4 rom. it works amazingly well and uses 4.4's launcher and lock screen so you get more or less the AOSP/GPE experience.

You have to be careful running ROMs not meant for the phone, meaning AOSP ROMs, MIUI, ect.. anything not HTC Sense.
That's the beauty of S-OFF as well.
We luckily have an RUU for S-OFF users if you do want to dig into AOSP ROMs, some.. not all are bound to have issues, such as data, when returning back to HTC ROMs. Flash the RUU and problem will be solved.
You need to be careful running custom ROMs that run anything but stock kernel also. Custom kernels can over heat, every phone is different.

I flashed between sense and CM10.2 with zero problems. And I did it frequently. I liked both so much I could never decide. Have settled on sense........for now.
Sent from my HTC6500LVW using Tapatalk

dlscott1111 said:
Really want to flash some of these newer asop roms but i am gunshy after bricking 2 Htc one's after installing CM 10.2 and Carbon Rom on phone #2.
I frequently flashed tons of roms on my gs3 and gs4 and never had a brick i couldn't recover from.
Can someone give me some reassurance that its ok to try asop roms again? Really itching to flash them again!
Thanks in advance for any advice.
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Always check the md5 signature of your downloaded ROM before flashing in recovery, to make sure you dont have a bad download.
Also, sometimes what may seem to be a bricked phone can be recovered by using the RUU to put everything back stock. If you can get to your phone's boot loader screen by turning on with power plus volume down, you probably aren't hard bricked.
If you are worried about changing system settings that result in boot loops, try keeping a stable nandroid backup on your phone that you can revert to if anything goes wrong.
Sent from my HTC6500LVW using Tapatalk 2

Thanks! The first brick was completely dead after cm10.2 flash 10.16 nightly. I read later that that nightly had problems with dsp, which i was fiddling with when it bricked. Maybe the dsp issue will never happen again i dunno.
2nd brick was on carbon rom after i messed with kernal settings (swipe to wake). Did the ruu but it didn't bring back speakers or data. Maybe i need to stay away from kernal settings period. Thx for the advice!
Sent from my HTC6500LVW using xda app-developers app

dlscott1111 said:
Thanks! The first brick was completely dead after cm10.2 flash 10.16 nightly. I read later that that nightly had problems with dsp, which i was fiddling with when it bricked. Maybe the dsp issue will never happen again i dunno.
2nd brick was on carbon rom after i messed with kernal settings (swipe to wake). Did the ruu but it didn't bring back speakers or data. Maybe i need to stay away from kernal settings period. Thx for the advice!
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Yeah, like many others like Andy have said, anything AOSP is a bit riskier because it isn't the original. For me I always stick to sense based roms, and I've never had a problem
Sent from my HTC6500LVW using Tapatalk