So with Android version 4.4 KitKat being able to run on devices with as low as 512 MB of RAM comfortably, will this allow rom developers to further develop/improve custom roms for the Amaze with Android 4.4 with little to no bugs in the future? Let the speculation begin...:fingers-crossed:
I wish they would develop that for this device, but I'm not so certain that they will because we don't even have an unofficial 4.3 port as yet (well, as far as I've looked. Only 4.0, 4.1, 4.2.......)
Darian_A said:
So with Android version 4.4 KitKat being able to run on devices with as low as 512 MB of RAM comfortably, will this allow rom developers to further develop/improve custom roms for the Amaze with Android 4.4 with little to no bugs in the future? Let the speculation begin...:fingers-crossed:
Click to expand...
Click to collapse
Only if HTC, Qualcomm, and Texas Instruments provide the corresponding updated sources for development. Otherwise what few developers that are left here will still be banging their heads against the wall to port it.
Darin_Ram said:
I wish they would develop that for this device, but I'm not so certain that they will because we don't even have an unofficial 4.3 port as yet (well, as far as I've looked. Only 4.0, 4.1, 4.2.......)
Click to expand...
Click to collapse
We do have 4.3.
http://forum.xda-developers.com/showthread.php?t=2423642
KT-82166 said:
We do have 4.3.
http://forum.xda-developers.com/showthread.php?t=2423642
Click to expand...
Click to collapse
Ooohh I had forgot about this!!
My bad, we do have a 4.3
It was buggy for me, so I went back to tmobile ICS
Idk, I like the sense and sense keyboard more than CM keyboard.
Roms
Darin_Ram said:
Ooohh I had forgot about this!!
My bad, we do have a 4.3
It was buggy for me, so I went back to tmobile ICS
Idk, I like the sense and sense keyboard more than CM keyboard.
Click to expand...
Click to collapse
I prefer the old Sense Keyboard. how can I get it back on my CM 10 rom ?
so far I managed to install CM10 rom
updated the contact manager to get it to synchronize with Facebook
but what it lacks is the snapshot ability using power + home button which doesnt work on CM10 rom
and the filp to silent the phone... also the volume controls are not so good during calls.
the volume is always at its highest even if I lower it. also the speaker is not as high as it used to be on the ICS rom
but I have to say CM10 is a better battery saver
runs smoother then ICS stock
and looks good
Sense Jellybean...
Once we have sense Jellybean, the next working will be KitKat.
We are very close to having the very first Sense jellybean rom
4.3 roms
The evervolv rom is currently the best "4.3" rom for the Amaze. Found here: evervolv.com/devices/ruby.
Although, the mobile data is very choppy. It will connect but it's seems to when it wants. Not sure about the intricacies of that. But, a bit of a dealbreaker for me at this point. The good news is evervolv has been updating this rom with
tweaks and bug fixes everyday. So, it looks very promising. Also note, I have found an "unofficial" cm10.2
build by sportsstar89 but the sound does not work. If you search 'ruby' on goo.im you will find it. I would post a link
but the site seems to be down atm. I am currently running cm10/1006-nightly, what i've found to be the best jelly bean
rom at this point. There is also an unofficial cm10.1 build that is pretty good as well. It can be found here: droidfirmwares.com/cm10-1-android-4-2-2-jelly-bean-custom-firmware-for-htc-amaze-4g.html/2. I ran it for quite a while w/o any noticeable
trouble. I just prefer official cm builds i guess.
Fadiayad said:
I prefer the old Sense Keyboard. how can I get it back on my CM 10 rom ?
so far I managed to install CM10 rom
updated the contact manager to get it to synchronize with Facebook
but what it lacks is the snapshot ability using power + home button which doesnt work on CM10 rom
and the filp to silent the phone... also the volume controls are not so good during calls.
the volume is always at its highest even if I lower it. also the speaker is not as high as it used to be on the ICS rom
but I have to say CM10 is a better battery saver
runs smoother then ICS stock
and looks good
Click to expand...
Click to collapse
I don't think you can get the keyboard on CM10 unless there's an app or someone made a port or something.
The snapshot feature works differently with Cyanogenmod cause they use the long press power button then selecting screenshot, though you'll have to enable the feature in the system settings.
Flip to silent the phone? Must be a feature I don't use lol
Idk, I liked the ICS stock tmobile (I de-bloated it myself using root uninstaller. Got rid of anything pertaining to t-mobile and it runs like a dream.)
Nenamark2 benchmark averages at 47 fps.
Antutu results are a little over 9000 (Let the Dragon Ball Z jokes start now lmao)
Overclocking is something that I would have loved to do on this stock rom, but I'll just run V6 Supercharger script instead.
Though pushing min. clock to about 1.2ghz gives a slight difference in benchmarks.
Hmmmmmm.......
It would take a lot of developer skills to get it on this device. CM said if they didn't officially support the device before, they won't start now regardless of ram specs. The s4 has it, but even better there is a dev for the international s4 that has made a 4.3.1 ROM which is made up of 85% straight Google source with 15% cm commits to get it to work on our device. And IMO, aosp is better and more stable than cm10.2 and has way less lag.
Sent from my GT-I9505 using Tapatalk
Thanks to jeepers007 and Evervolv we're getting ourselves some KitKat- http://forum.xda-developers.com/showthread.php?t=2524691
It's only a matter before the bugs are worked out. So nice to see the Amaze still getting some love. :good:
from what i have seen and heard kit kat will be better on amaze
Darian_A said:
Thanks to jeepers007 and Evervolv we're getting ourselves some KitKat- http://forum.xda-developers.com/showthread.php?t=2524691
It's only a matter before the bugs are worked out. So nice to see the Amaze still getting some love. :good:
Click to expand...
Click to collapse
Unfortunatelly jeepers007 bricked his device
The problem is with mounting the sdcards. Google changed how the cards are mounted and we don't know how to get both cards to mount while the phone isn't connected to the computer.
And exactly what happened to Ravike is what happened to jeepers.
Sent from my HTC_Amaze_4G using xda app-developers app
I want to ask here in general that is porting risky??
Because it lookin that jeepers007 bricked his phone...
What one should not do while porting Roms...!??
Any.suggestions
Sent from my Amaze 4G using xda app-developers app
chevycowboyusa said:
The problem is with mounting the sdcards. Google changed how the cards are mounted and we don't know how to get both cards to mount while the phone isn't connected to the computer.
And exactly what happened to Ravike is what happened to jeepers.
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Chevy perhaps you guys are going about things the wrong way. Instead of putting so much energy into getting a 3.4 kernel up and running maybe its better to stay with 3.0 and work around it. This is what the most successful developers have been doing on other legacy devices. For example, Tytung is still using basically the same kernel 2.6.29 for every version of Android since Froyo and his version of JellyBean-4.3 / CM-10.2 is much further along than anyone here is. He has faced the same issue of not having updated sources that everyone here has. In discussions on his board he's mentioned that it was easier to modify elements which require ion to pmem than developing an ion kernel from scratch to fully support that device. Perhaps our Amaze would be better served if developers here take the same approach. Use what we already have and just workaround it.
Now as to the mounting issue, the fact that both internal and external SD-cards are recognized and can be mounted via adb suggests that It's a configuration problem. Perhaps init scripts need slight modification or symbolic links created to get them mounted correctly. Again I hate to keep bringing up Tytung, but he worked around MTP issues by simply not implementing it in his newer ROMs. The old method of accessing the SD storage worked well with our devices, why must we reinvent the wheel? Yes MTP is more secure which is the primary reason for its adoption, but really, do we need it if implementing it correctly is only bringing about more problems?
Edit: Another thing to consider is Jellybean-4.3 introduced SELinux in permissive mode which means potential security risks are only logged, but nothing is done about it. KitKat incorporates SELinux in enforcing mode which introduces a whole range of new issues I'm sure developers here have never had to deal with before. I know from my experience with Gentoo that SELinux can be a royal pain in the ass to administer. Which is why I don't use it in my rig. I can't tell you how many times I've seen bug reports where a package fails on an SELinux install that works as expected for everyone else. I also can't tell you how many times I've seen packages pushed into the stable repository only to be moved back into unstable when SELinux users complain about it not working for them. It truly is a ***** to setup and have running correctly. To me this is just another reason to get out a stable fully functioning Jellybean-4.3 in which to build off of before trying to tackle KitKat-4.4 which is going to be a far more difficult nut to crack.
Just my 2 cents
Odysseus1962 said:
Chevy perhaps you guys are going about things the wrong way. Instead of putting so much energy into getting a 3.4 kernel up and running maybe its better to stay with 3.0 and work around it. This is what the most successful developers have been doing on other legacy devices. For example, Tytung is still using basically the same kernel 2.6.29 for every version of Android since Froyo and his version of JellyBean-4.3 / CM-10.2 is much further along than anyone here is. He has faced the same issue of not having updated sources that everyone here has. In discussions on his board he's mentioned that it was easier to modify elements which require ion to pmem than developing an ion kernel from scratch to fully support that device. Perhaps our Amaze would be better served if developers here take the same approach. Use what we already have and just workaround it.
Now as to the mounting issue, the fact that both internal and external SD-cards are recognized and can be mounted via adb suggests that It's a configuration problem. Perhaps init scripts need slight modification or symbolic links created to get them mounted correctly. Again I hate to keep bringing up Tytung, but he worked around MTP issues by simply not implementing it in his newer ROMs. The old method of accessing the SD storage worked well with our devices, why must we reinvent the wheel? Yes MTP is more secure which is the primary reason for its adoption, but really, do we need it if implementing it correctly is only bringing about more problems?
Edit: Another thing to consider is Jellybean-4.3 introduced SELinux in permissive mode which means potential security risks are only logged, but nothing is done about it. KitKat incorporates SELinux in enforcing mode which introduces a whole range of new issues I'm sure developers here have never had to deal with before. I know from my experience with Gentoo that SELinux can be a royal pain in the ass to administer. Which is why I don't use it in my rig. I can't tell you how many times I've seen bug reports where a package fails on an SELinux install that works as expected for everyone else. I also can't tell you how many times I've seen packages pushed into the stable repository only to be moved back into unstable when SELinux users complain about it not working for them. It truly is a ***** to setup and have running correctly. To me this is just another reason to get out a stable fully functioning Jellybean-4.3 in which to build off of before trying to tackle KitKat-4.4 which is going to be a far more difficult nut to crack.
Just my 2 cents
Click to expand...
Click to collapse
Well I tried what you said thing is sense is entirely different than CM or aosp the sources are there for public in both of them... But sense is a closed source and sense jb rom libs are compiled according to 3.4 kernel by HTC.. If we want to update the 3.0.16 kernel we have to enable ion with it then have to make the necessary libs along with it as well according to sense source, also must make ion enabled libs we have to make them all according to sense source.. Even the simple fixes of sense is really hard cuz HTC Sense is a complicated system :/... Tytong and almost all the cm devices lower than villec2 still use pmem kernels not ion... Not even cm team making ion enable kernels and ion enabled roms for us cuz it's a lot of work even tho its basically aosp..
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
ravike14 said:
Well I tried what you said thing is sense is entirely different than CM or aosp the sources are there for public in both of them... But sense is a closed source and sense jb rom libs are compiled according to 3.4 kernel by HTC.. If we want to update the 3.0.16 kernel we have to enable ion with it then have to make the necessary libs along with it as well according to sense source, also must make ion enabled libs we have to make them all according to sense source.. Even the simple fixes of sense is really hard cuz HTC Sense is a complicated system :/... Tytong and almost all the cm devices lower than villec2 still use pmem kernels not ion... Not even cm team making ion enable kernels and ion enabled roms for us cuz it's a lot of work even tho its basically aosp..
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for you comments, now I fully understand your dilemma. The issue isn't just getting a working JB ROM, it's getting a working JB/sense ROM. You see I'm sense agnostic. My HD2 had sense with windows, but all of the best android ROMs for it were aosp or cm based, so I got used to not having it. Now I've got it again with the nrg ROM so I use it. When I ran Tytung's cm ROMs I always customize anyway. To me cm or aosp is like having a blank canvas to paint on. You have the basic features, but It's infinitely customizable to taste. Sense gives a different platform. You can still customize, but It's not as flexible to customize as aosp or cm. In a way it's factory customized. Either way I'd just love to see a fully functioning JB on our devices. Please keep up the good work!
Ciao
I've asked somthing in above post..
Can anyone reply please... I want to start my work though....
Sent from my Amaze 4G using xda app-developers app
shubham211995 said:
I want to ask here in general that is porting risky??
Because it lookin that jeepers007 bricked his phone...
What one should not do while porting Roms...!??
Any.suggestions
Sent from my Amaze 4G using xda app-developers app
Click to expand...
Click to collapse
I'm not the most experienced but from my knowleged you should be ok as long as you watch what partitions you format.
Sent from my HTC_Amaze_4G using xda app-developers app
Related
To go 2+ days without freezing and/or randomly rebooting?
Lol huh? I don't have this problem ever...
So far:
Deck ROM: yes, could go weeks without rebooting.
CleanROM: yes, only had it about 2 days but no problems
Synergy: no, tried every kernel and it wouldnt go more than about 12 hours without a hard crash.
About all I've tried at length
Sent from my PG86100 using xda premium
Nope. And it always screws up when I need it the most.
Sent from my PG86100 using Tapatalk
My personal ROM has actually never needed a reboot or crashed.
Via My HTC Evo 3D On The Now Network From Sprint.
Every ROM I've ran except some of myn's nightlies were completely stable.
Synergy - very stable
Cyanogenmod - seems to be the stablest
InfectedROM - Kind of stable
Myn's 2.3 - Not really stable, but these are experimental nightly builds we have
If it reboots randomly and freezes a lot, there is most likely too many apps running or similar stuff that is causing that. I use my phone heavily and have never experienced reboots/freezes/shutoffs.
Steelh never had an issue works for days before reboot just to clean up
Gotcha, nice replies guys.
I refuse to run ROMs with several broken things, aside from AOSP, which is understandable.
Cm7 on airplane mode. No service so im good with wifi. 3D movies. ONLY reboot I ever had was adding 2000 songs to my sdcard. Phone couldnt handle it for 10 minutes. Then it scanned properly and good to go again.
Whooo! (Cole Voice...)
Basically, the reason I'm asking is because virtually every single frequently updated Sense ROM in the development section is full of issues people are having. I'm trying to understand why they are so popular if they are riddled with issues every other update. Do people not enjoy stable phones? I've been running the same ROM since July and to this day there isn't a single 'new' feature that has been implemented in ROMs these days that I don't want. If there happens to be one, it doesn't need a full flash.
My question is: Why are so many people using Sense ROMs that have nothing but issues and stuff that doesn't work properly? Since HTC has already provided a fairly solid foundation with the Stock ROM, how are so many Sense ROMs broken?
If the answer is aesthetics and looks, why not take a stable ROM, and work from there to get the look you want?
I'm also trying to understand the mind of a "Flashaholic" and besides AOSP or MIUI, there doesn't seem to be enough differences between these Sense ROMs other than kernels and random fiddling with the framework that really differentiate them. For a person that understands how ROMs work and can easily determine the core differences between them, I can tell you exactly what differences that ROM A has from ROM B, and yet, the user opinion is much wider.
Take for instance ROM A, which has a cute tagline in its title and is made by a 'veteran' so to speak. The changelog and file-by-file difference between that and ROM B, made by a seemingly unknown person are pretty small, but the audience seems to think ROM A is much more 'stable' and 'fast' than ROM B.
Aside from messing with the framework, I have done side-by-side comparisons of where most of the ROMs features claim to shine--its tweaks to memory, ram usage, cpu, kernel, etc; which reside mostly in the /system/etc folder and under build.prop and the differences are so small and most of the tweaks are identical. With that said, framework 'tweaks' make a minimal difference in every day situations and most phones will perform almost identical to the Stock ROM. The real differences lie in random build.prop tweaks and init.d scripts which mostly come from poorly documented sites and sources that were meant for Desktop computers and/or older phones like the G1 and can actually have a negative effect on our current phone's performance. I'm sure HTC has done enough research that their method of ROM delivery is probably optimal for most people.
At any rate, I'm interested in more discussion from the people in this thread.
Id like to try your dualcore mod with 1st core at 700mhz and 2nd core at 500mhz. Can you make the file for me? But is it possible to get a screen off profile with it?
Whooo! (Cole Voice...)
I have flashed before due to aesthetics but now I'm on a hunt for a smoother (stutter free) rom. I also like having extra settings that some offer like synergys, and Eternity, and having beats is a plus although not necessary. The closest I've gotten is Eternity 1.3.1 w/stock look along with Tiamat sense 1.0.3 kernel and flashable script by Smokin. Smokins script made a difference in smoothness for me specially in the app drawer. The only issue that plagues my phone is intermittent black screen during calls.
Other reason I flash is sometimes I get tired of things and want something new to play with. Makes me feel I have a new device.
knowledge561 said:
Id like to try your dualcore mod with 1st core at 700mhz and 2nd core at 500mhz. Can you make the file for me? But is it possible to get a screen off profile with it?
Whooo! (Cole Voice...)
Click to expand...
Click to collapse
I can pretty much build a script that can accomplish this
aznmode said:
I have flashed before due to aesthetics but now I'm on a hunt for a smoother (stutter free) rom. I also like having extra settings that some offer like synergys, and Eternity, and having beats is a plus although not necessary. The closest I've gotten is Eternity 1.3.1 w/stock look along with Tiamat sense 1.0.3 kernel and flashable script by Smokin. Smokins script made a difference in smoothness for me specially in the app drawer. The only issue that plagues my phone is intermittent black screen during calls.
Other reason I flash is sometimes I get tired of things and want something new to play with. Makes me feel I have a new device.
Click to expand...
Click to collapse
That I can understand, but with the differences between Sense ROMs being so small, why? I suppose looks is a good enough reason as any, especially if you don't know how or feel like trying to extract the apks or images needed to make your current ROM look like the ROM you're installing.
freeza said:
I can pretty much build a script that can accomplish this
Click to expand...
Click to collapse
Thanks. Im on cm7. Do I send you this build.prop or init.d or something? Also I use setcpu, im guessing I wont be able to use it anymore? Screen off profile would be 192-384mhz
Whooo! (Cole Voice...)
Senseless I get way better 4g coverage than any other ROM I've tried. With others my 4g would go on and off every 3-4 minutes. It really bugged me out.
Sent from my 62 inch 3d tv.
I flash roms to have wireless tether mainly. Recently i like using sprint hotspot and it ia easier to flash a modified stock rom instead of tracking down the flashable hack. Other than staying up to date with software without breaking root, i dont see a reason not to be stock rooted. I buy htc for sense so aosp roms just arent for me. Im running infected eternity 1.4.1 and love the themed look just because it seperatea me from the rest if the world, if i wanted to fit a mold i would be rocking that girly iphone.
Sent from my PG86100 using XDA Premium App
Freeza,
What ROM are you using?
Sent from my PG86100 using XDA App
yousefak said:
Synergy - very stable
Click to expand...
Click to collapse
First time I've heard anyone claim synergy is stable. Even the synergy devs have given up trying to get non stock kernels to run reliably with it and have recommended limping along by flashing the stock kernel over the included one until the ROM can be fixed.
As to why so many problems: I think half of it is kernel compatibility and half is in the baking. Some bake in the latest version of this or that apk that hasn't been thoroughly tested. Market 3.2 is a good example. Doesn't work: can't buy paid apps. Same problems occur with other apps like all the borked superuser updates between 3.0.2 and 3.0.6. So with all the pushing to include the latest versions of every low level app baked into the ROM, of course there will be some mismatches.
Not a fan of AOSP ROMs. Most of those don't have 20% of the stuff working like 4g, 3d camera, and other stuff. Most say right at the top, "dont expect this to work... Or that to work". No thanks.
Sent from my PG86100 using xda premium
Could dual cores always being on cause damage to the phone?
Via My HTC Evo 3D On The Now Network From Sprint.
So I bought a SG2 a couple days ago (moving from Iphone 3gS). I'm kinda disappointed in battery life and my friend recommended installing a custom rom. I have CM9 on my Touchpad so I figured I'd give it a go on my phone too. As it is, I like the look/feel of the stock device (maybe I just don't know better) so I am thinking that using something more stable like CM7 would be more beneficial. Is there any major differences?
Cm9 is based of ICS and Cm7 of gingerbread.
Sent from my SGH-I777 using XDA
Yes, I knew that, but is it worth using a more unstable build vs CM7?
mojoe_24 said:
Yes, I knew that, but is it worth using a more unstable build vs CM7?
Click to expand...
Click to collapse
Cm9 isn't unstable. I'm perfectly fine on it.
Sent from my SAMSUNG-SGH-I777 using xda premium
CM9 is real stable for nightly status
Sent from my SGH-I777 using Tapatalk 2 Beta-6
In my opinion, CM9 is more stable than CM7 ever was on I9100/I777.
There's a variety of reasons for this, it's mainly that 6 months later, everyone involved knows MUCH more about the device than they did when ICS was first released and most of the CM maintainers either took breaks or started working CM9.
This especially holds true for I777 - When atinm took a break and codeworkx started working ICS, we didn't know a fraction of what the REAL differences between I9100 and I777 were that we do now. As a result the I9100/I777 device trees are MUCH closer together now than they were for CM7.
Just guessing, but I think CM9 will end up being better overall. Each version of Android brings unique challenges for the devs. For instance, CM7 on our device suffers from a Market bug that will cause periodic freezes. I don't think anyone is reporting that with CM9.
On my old phone, under CM6, they had a hell of a time getting the OS to read the voicemail number from the SIM card. When Gingerbread came out, it was never a problem from the beginning.
If battery life is your main concern, I recommend Entropy512's Daily Driver kernel. (Samsung-based ROMs only). He's working on one for ICS but his GB kernel has been used by thousands across what I guess to be dozens of ROMs.
EDIT: ^^The man himself^^
Thegodfather156 said:
CM9 is real stable for nightly status
Sent from my SGH-I777 using Tapatalk 2 Beta-6
Click to expand...
Click to collapse
x2
Never had a single problem with it so far. CM7 would only last 30 mins on my phone before I had to uninstall it due to stuff not working or crashing.
No clue what matters to you, but here are some specific differences as of April 9:
CM9 does not have the headphone volume bug that CM7 did, BUT...
...on CM9 the correct volume does not get restored after playback is interrupted by a notification
CM9 does not support notification LEDs, BUT...
...on CM7 Notification LEDs causes a wakelock (battery drain)
CM9 does not have as many extended features as CM7 (yet)
CM9 GPS is (at least anecdotally) not as good as CM7 (for now)
CM9 overclocking/undervolting support is brand new
Edit: CM9 does not have Theming (yet)
CM9 does not support USB Mass Storage, need to use MTP (inconvenient on Linux)
CM9 will not have Phone Goggles
The biggest factors (for me):
CM9 is ICS
CM9 has developers' attention
halfsoul said:
No clue what matters to you, but here are some specific differences as of April 9:
CM9 does not have the headphone volume bug that CM7 did, BUT...
...on CM9 the correct volume does not get restored after playback is interrupted by a notification
CM9 does not support notification LEDs, BUT...
...on CM7 Notification LEDs causes a wakelock (battery drain)
CM9 does not have as many extended features as CM7 (yet)
CM9 GPS is (at least anecdotally) not as good as CM7 (for now)
CM9 overclocking/undervolting support is brand new
Edit: CM9 does not have Theming (yet)
CM9 does not support USB Mass Storage, need to use MTP (inconvenient on Linux)
CM9 will not have Phone Goggles
The biggest factors (for me):
CM9 is ICS
CM9 has developers' attention
Click to expand...
Click to collapse
Brilliant explanation! Thanks! Should be linked to by the CM9 thread!
halfsoul said:
No clue what matters to you, but here are some specific differences as of April 9:
CM9 does not have the headphone volume bug that CM7 did, BUT...
...on CM9 the correct volume does not get restored after playback is interrupted by a notification
CM9 does not support notification LEDs, BUT...
...on CM7 Notification LEDs causes a wakelock (battery drain)
CM9 does not have as many extended features as CM7 (yet)
CM9 GPS is (at least anecdotally) not as good as CM7 (for now)
CM9 overclocking/undervolting support is brand new
Edit: CM9 does not have Theming (yet)
CM9 does not support USB Mass Storage, need to use MTP (inconvenient on Linux)
CM9 will not have Phone Goggles
The biggest factors (for me):
CM9 is ICS
CM9 has developers' attention
Click to expand...
Click to collapse
There is an app for USB Mass Storage. I prefer using it over MTP.
http://forum.xda-developers.com/showpost.php?p=24084600&postcount=113
CM9 is based on Android 4.0 ICS and is currently in the Alpha/Nightlies status.
CM7 is based on Android 2.3 Gingerbread and is currently the Stable branch of CynaogenMod
I just figured CM7 would have been more stable. Maybe I'll look into CM9 then. I plan to root my phone today. Part of the reason I wanted CM7/9 was to get rid of bloatware, but it seems a root can do it too.
mojoe_24 said:
I just figured CM7 would have been more stable. Maybe I'll look into CM9 then. I plan to root my phone today. Part of the reason I wanted CM7/9 was to get rid of bloatware, but it seems a root can do it too.
Click to expand...
Click to collapse
You know there are other options than CM, right? If you aren't one of the ridiculous TouchWiz haters (doesn't seem that way since you mentioned you like the default look of the phone) then go download and install SHOstock2 from the development forum. It's fast, stable, and just flat-out works. Easily the best of the ICS ROMs, IMO. When CM9 gets to a stable release state I'll give it a try, but the AOSP ROMs (mainly CM9 and AOKP) just aren't quite ready for prime time IMO if you look at the issues/bugs that still exist in them. Some people enjoy flashing new builds all the time and taking part in the dev process...personally I just want something that works. That's not to say that SHOstock2 is a finished ROM yet, but it's way farther along than the others. Give it a try - as someone who only recently made the leap from stock, I couldn't imagine ever going back.
hbar said:
You know there are other options than CM, right? If you aren't one of the ridiculous TouchWiz haters (doesn't seem that way since you mentioned you like the default look of the phone) then go download and install SHOstock2 from the development forum. It's fast, stable, and just flat-out works. Easily the best of the ICS ROMs, IMO. When CM9 gets to a stable release state I'll give it a try, but the AOSP ROMs (mainly CM9 and AOKP) just aren't quite ready for prime time IMO if you look at the issues/bugs that still exist in them. Some people enjoy flashing new builds all the time and taking part in the dev process...personally I just want something that works. That's not to say that SHOstock2 is a finished ROM yet, but it's way farther along than the others. Give it a try - as someone who only recently made the leap from stock, I couldn't imagine ever going back.
Click to expand...
Click to collapse
Ditto... I'm running ShoStock2 for the better part of two weeks and can't deny that I'm in love. Previously to that I ran UnNamed and ShoStock for GB and loved both. The best thing to do is give them a try to see what you like. Our opinion may be biased based so I suggest you give the ROM's a try so you know what you like.
Sent from my SGH-I777 using xda premium
I'm actually kinda confused on what exactly Touchwiz is. If it's only the launcher than I switched to Launcher Pro, but I can't imagine it gaining that much hate if that is all it is.
mojoe_24 said:
I'm actually kinda confused on what exactly Touchwiz is. If it's only the launcher than I switched to Launcher Pro, but I can't imagine it gaining that much hate if that is all it is.
Click to expand...
Click to collapse
It's built into the framework. It's not just a launcher and theme.
AOKP is pretty damn stable. The only bug is the mentioned CM9 issue with notifications lowering music volume. Also GPS is slow to lock sometimes for me. Other than that it's a great ROM. I gave ShoStock a try but just prefer the look of AOKP
mojoe_24 said:
I'm actually kinda confused on what exactly Touchwiz is. If it's only the launcher than I switched to Launcher Pro, but I can't imagine it gaining that much hate if that is all it is.
Click to expand...
Click to collapse
touchwiz is so much more than a launcher
its the entire UI, the phone dialer, the contacts, the lockscreen, the SMS app, nearly everything you see on your phone is a Touchwiz UI. it is an overlay over the real android lurking below.
mojoe_24 said:
I'm actually kinda confused on what exactly Touchwiz is. If it's only the launcher than I switched to Launcher Pro, but I can't imagine it gaining that much hate if that is all it is.
Click to expand...
Click to collapse
TouchWiz is a launcher and is Standard for Samsung GSII. It's all about taste if you ask me. I personally enjoy using ToichWiz or Apex launher over anything else. It's really up to you to determine what you like and how you want it to function.
Sent from my SGH-I777 using xda premium
I mean this question in the most sincere way. I know there are some incredibly talented people out there working very hard on AOSP roms. I'm just legitimately curious and admittedly ignorant. What is so difficult about removing the HTC sense rom and replacing it with a pure stock android rom like what's found on the nexus? I know a rom like CM9 aims to add back in a lot more to the AOSP so I can imagine how difficult that must be to get everything working. If all that's being done though is just installing a pure Android rom on a phone already running Android (with a bunch of crap added in), what would make that a difficult task, that to the best of my knowledge, is still not done yet? At the risk of further showing my ignorance, what makes it different from the PC world where you could re format a PC and install a fresh windows OS on it, and get rid of all the OEM bloatware.
Thank you.
A lot of it must be rewritten from scratch because the drivers and what not are proprietary.
Please use the Q&A section to post questions in.
For starters, you dont get AOSP ROMS by removing HTC sense. You get AOSP ROMS by building from scratch from googles code.
Thats what takes so long. Getting googles code to work with our proprietary (read: no source for the devs) drivers.
The other part of it is the devs arent working on ICS(CM9). They've skipped that completely and are working on jellybean (CM10)
Deck has a build that is pretty friggin sweet.
Rxpert said:
For starters, you dont get AOSP ROMS by removing HTC sense. You get AOSP ROMS by building from scratch from googles code.
Thats what takes so long. Getting googles code to work with our proprietary (read: no source for the devs) drivers.
The other part of it is the devs arent working on ICS(CM9). They've skipped that completely and are working on jellybean (CM10)
Deck has a build that is pretty friggin sweet.
Click to expand...
Click to collapse
How close to a daily driver would you say Deck's CM10 build is right now? Last I checked the only thing missing was the camera which helped out with some other bugs that had been happening. I could probably live without a camera if everything else seems to be in tip-top shape.
strangemcd said:
How close to a daily driver would you say Deck's CM10 build is right now? Last I checked the only thing missing was the camera which helped out with some other bugs that had been happening. I could probably live without a camera if everything else seems to be in tip-top shape.
Click to expand...
Click to collapse
It hasn't been updated in a few days, so what you've heard last still stands. Give it a flash and check it out.
Rxpert said:
It hasn't been updated in a few days, so what you've heard last still stands. Give it a flash and check it out.
Click to expand...
Click to collapse
Latest has camera I hear?
Sent from my EVO using xda app-developers app
PsiPhiDan said:
Latest has camera I hear?
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Rear camera works, switching to FFC or camcorder caused a FC/Reboot.
Still a daily driver for me.
Where do you go to find the latest build?
It's all on irc look in the cm9 thread and the camera's actually fixed now now its just video and Google now is gimmicky you need to do a fresh flash, its updated usually everyday
Sent from my EVO using xda app-developers app
flyhighx said:
I mean this question in the most sincere way. I know there are some incredibly talented people out there working very hard on AOSP roms. I'm just legitimately curious and admittedly ignorant. What is so difficult about removing the HTC sense rom and replacing it with a pure stock android rom like what's found on the nexus? I know a rom like CM9 aims to add back in a lot more to the AOSP so I can imagine how difficult that must be to get everything working. If all that's being done though is just installing a pure Android rom on a phone already running Android (with a bunch of crap added in), what would make that a difficult task, that to the best of my knowledge, is still not done yet? At the risk of further showing my ignorance, what makes it different from the PC world where you could re format a PC and install a fresh windows OS on it, and get rid of all the OEM bloatware.
Thank you.
Click to expand...
Click to collapse
Because we're waiting for you to build it.
whats the battery life like for decks rom?
joebarkho said:
whats the battery life like for decks rom?
Click to expand...
Click to collapse
I'm not running it right now but it's aosp so i'd imagine a little bit better than sense right now. But maybe not since it's not fully polished.
joebarkho said:
whats the battery life like for decks rom?
Click to expand...
Click to collapse
For Deck's CM10 I get about a day. At 15 hours yesterday I was at 34%. I don't use my phone a whole lot but that's texts and emails and some web browsing. Wifi on all day and BT on for a few hours.
joebarkho said:
whats the battery life like for decks rom?
Click to expand...
Click to collapse
I've been on cm10 for a while and I can get thru a day with normal to heavy usage with roughly 20%+ left its pretty good just remember to callibrate
Sent from my EVO using xda app-developers app
So i got my DNA last week and have been playing around with it for awhile (trying several different roms) but i havent found one that fits me perfectly.
I'm looking for one that is desensed
remap hardware keys
Works with Verizon (though 99% of them do)
Beats audio enabled
HTC keyboard (though i can go without)
The two closest i've gotten is VipersDNA and the Unofficial CM port.
I really like CM only real problem is that beats doesnt really work with it (and i know it has dsp but just doesnt sound as well and i cant get eq perfect)
Viper is almost perfect besides a few nitpicks (I miss my scrollable wallpaper and dont like user a different launcher on top) and i prefer the task manager on CM a bit better (though ive never had the phone lag once which is amazing i like hitting recent and closing all apps, but i can easily go without)
Anyone have any suggestions? I've tried several others but can't find one just right...
kitex2 said:
So i got my DNA last week and have been playing around with it for awhile (trying several different roms) but i havent found one that fits me perfectly.
I'm looking for one that is desensed
remap hardware keys
Works with Verizon (though 99% of them do)
Beats audio enabled
HTC keyboard (though i can go without)
The two closest i've gotten is VipersDNA and the Unofficial CM port.
I really like CM only real problem is that beats doesnt really work with it (and i know it has dsp but just doesnt sound as well and i cant get eq perfect)
Viper is almost perfect besides a few nitpicks (I miss my scrollable wallpaper and dont like user a different launcher on top) and i prefer the task manager on CM a bit better (though ive never had the phone lag once which is amazing i like hitting recent and closing all apps, but i can easily go without)
Anyone have any suggestions? I've tried several others but can't find one just right...
Click to expand...
Click to collapse
Every phone runs things differently in all reality best to try them all yourself. For me its nos or nos gpe
Sent from my HTC6435LVW using xda app-developers app
cstrife999 said:
Every phone runs things differently in all reality best to try them all yourself. For me its nos or nos gpe
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I tried nos gpe earlier today but had a few to many bugs for me, or I did somthing wrong. It had data connection but my 3g 4g icon wouldn't show and no hardware key remap. And kept giving me no service icon but I could make calls , but that one is super close too
I am on CM 10.1 Right now. Only gripe is the camera, not nearly as good as stock sense since it isn't the sense camera but i can live with it. Some of the customization features dont work either. I wouldn't say it is perfect but it is getting there and the DEVs are doing an amazing job for something that is free. Im just waiting for the bugs on GPE to be worked out so I can switch to that.
Sent from my HTC6435LVW using xda app-developers app
I'm currently on EclipticNA by Hawknest. It's Sense 5 based so you still have Beats Audio and the HTC Keyboard. All system apps and some user apps are blacked out and inverted, which I love. This ROM is VERY fast, and with Crpalmers kernel it's faster than light! For desensing, just freeze or uninstall Sense, and use whatever other launcher you want. Recent apps button is remapable. There's "press for recents", "press for recents, hold for menu", and "press for menu, hold for recent".
Other than that, when all the kinks in Newt's GPE ROM get worked out, that would be good for your needs.
Sent from my Ecliptic DNA
Romwise
Firstly I wanna start out by saying that having to post 10x before i can post to help development is annoying. But i do understand why. So im posting this as my first post to start my way to be able to help development. Im currently rocking a Droid dna. Roms Ive so far liked for this phone Ill list with a brief reason why in order.
1. Team Venom Viper rom. Fast stable and mods out the bum. No issues
2. EclipticNa inverted. Best sense 5 rom to me. Fast stable and saves so much battery with the invert
3. Supercharged hatka. Pretty fast decent mods. And stable.
Ive flashed and used 8 of the roms from xda for the dna so far. When Im able to post for development Ill start giving detailed reviews and helping the devs out. U guys can help a guy out by giving me a thumbs up or something. Thanks.
kitex2 said:
I tried nos gpe earlier today but had a few to many bugs for me, or I did somthing wrong. It had data connection but my 3g 4g icon wouldn't show and no hardware key remap. And kept giving me no service icon but I could make calls , but that one is super close too
Click to expand...
Click to collapse
There is a new version of NOS GPE out, version 1.0.3, which fixed all the force reboot and data issues for me, all I had to do was cycle airplane mode two or three times for it to pick up Verizon's connection. Smoothest ROM I've tried so far.
It makes sense that it would work well, because it's coming from an AOSP rom made by HTC for the One. I've had problems with small things not working on other custom ROMs, like HDMI. GPE 1.0.3 has no issues like that so far.
GreenfireX said:
There is a new version of NOS GPE out, version 1.0.3, which fixed all the force reboot and data issues for me, all I had to do was cycle airplane mode two or three times for it to pick up Verizon's connection. Smoothest ROM I've tried so far.
It makes sense that it would work well, because it's coming from an AOSP rom made by HTC for the One. I've had problems with small things not working on other custom ROMs, like HDMI. GPE 1.0.3 has no issues like that so far.
Click to expand...
Click to collapse
I believe it's Sense based to look like AOSP, hence the name Google Experience.
orangechoochoo said:
I believe it's Sense based to look like AOSP, hence the name Google Experience.
Click to expand...
Click to collapse
According to newtoroot it's the HTC version of AOSP 4.3 made for the Google Play Edition of the One, so it should be as close to stock as possible..... It also has no hints of sense in any of the apps or menus....
GreenfireX said:
According to newtoroot it's the HTC version of AOSP 4.3 made for the Google Play Edition of the One, so it should be as close to stock as possible..... It also has no hints of sense in any of the apps or menus....
Click to expand...
Click to collapse
Except for beats that's from sense, not aosp, and if it were pure aosp it wouldn't be 400megs, it'd be like 150. Its desensed from HTC, that's it. It also works quite well, and rather then being bland and boring (to me) it is a very excellent choice for non sense but pretty perfect running.
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
Except for beats that's from sense, not aosp, and if it were pure aosp it wouldn't be 400megs, it'd be like 150. Its desensed from HTC, that's it. It also works quite well, and rather then being bland and boring (to me) it is a very excellent choice for non sense but pretty perfect running.
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
True, I guess ultimately it's the best AOSP ROM available for the DNA, although I'd love to see a team like Venom come out with a more custom experience based off of it.
"Anandtech's Brian Klug discovered that both the Developer Editions of the HTC One and the Samsung Galaxy S 4 will not receive software updates directly from Google because they're not running pure Android Open Source Project (AOSP) software, but instead a combination of the OEM kernel and the stock Android skin. As a result, the Google Play edition devices may not receive new Android versions as quickly as standard Nexus devices."
http://arstechnica.com/gadgets/2013...one-and-galaxy-s-4-arent-quite-nexus-devices/
I'm still wondering what other "stuff" is in the Google Editions; pure AOSP is under 200 MB, add gapps which is under 100 MB, and then there's _____?
pio_masaki said:
Except for beats that's from sense, not aosp, and if it were pure aosp it wouldn't be 400megs, it'd be like 150. Its desensed from HTC, that's it. It also works quite well, and rather then being bland and boring (to me) it is a very excellent choice for non sense but pretty perfect running.
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
newts work gas always been top notch. when something goes wrong, he has it fixed asap. pretty quick about it too. been following since my dinc2 days
-HTC Droid DNA-
If your looking for a Sence 5 Rom , you must try http://forum.xda-developers.com/showthread.php?p=44076330 by hawknest, it is a beautiful rom
Sent from my HTC DNA using xda premium
JWhetstone02 said:
newts work gas always been top notch. when something goes wrong, he has it fixed asap. pretty quick about it too. been following since my dinc2 days
-HTC Droid DNA-
Click to expand...
Click to collapse
I had issues with version 1 and 2, but 3 has been on my phone since he released it and only had an initial data issue (put the phone in airplane mode twice and it fixed it)
Hopefully by now he OP has narrowed down his choices, so continuing with another subject that came up: why have an original development and a development forum?
Is the distinction that an original development ROM is compiled from source even if the ROM has cherry-picks from another ROM and is based on something such as CM, while the development forum are for ROMs that are ported from one device to another which is made to fit over the Sense base since there is no public Sense source to compile from, or is a modification of a manufacturer's ROM?
orangechoochoo said:
Hopefully by now he OP has narrowed down his choices, so continuing with another subject that came up: why have an original development and a development forum?
Is the distinction that an original development ROM is compiled from source even if the ROM has cherry-picks from another ROM and is based on something such as CM, while the development forum are for ROMs that are ported from one device to another which is made to fit over the Sense base since there is no public Sense source to compile from, or is a modification of a manufacturer's ROM?
Click to expand...
Click to collapse
Built from source = original development
Built from a factory ROM or otherwise pre compiled image, including from other devices (this covers current MIUI as well) = development
The Roms in development because they have cherry picks but are source built should be in original development, but whatever the mods decide I guess.
That's how I understood it when it was originally posted by XDA when it started.
Tapatalked from my HTC DNA - MoKee
Hello this thread is intended for development purpouses only. Do not post thank you posts, request posts or anything not related to the main purpose. You have a thanks button if you are thankful.
Well warching at what lg did with kitkat using bad jb blobs for gpu that resulted in abnormal cpu usage for rendering and in slowness and glitchness I decided to set up Team Neutron. This team will build a working cm10 that is smooth which is possible.
Well now anyone with abilities can join after i talk to them. Not here on topic but after they pm me.
Atm i would want to know if the following people will join me withoit egos secrets or drama. I will split iobs and watch over the project. I will work on it myself.
Kernel
@airidosas252
Rom dev from source
@weritos
Please confirm or infirm my invitation. This could be my last project for this device since it has almost no support. It will be a good one though.
I understand correctly
Going to collect СM10 ??
We are gonna get a super stable cm 10 if you want to work with me
Sent from my LG-P710 using XDA Free mobile app
christi9503 said:
We are gonna get a super stable cm 10 if you want to work with me
Sent from my LG-P710 using XDA Free mobile app
Click to expand...
Click to collapse
This is certainly good
But for the models 715 to gather a working network will be problematic, СM10 not support two SIM cards
That is right but we are never going to get a stable cm11 because of the gpu. We can make 1 sim work i think
Sent from my LG-P710 using XDA Free mobile app
Edit: @weritos
The best we can get is a JB based rom like CM10.2 at most. After we get the single sim working we can patch somehow for the P715 to use one sim (some ramdisk tweaking).
What I am thinking off:
let's pull the blobs only from our phone. See if we can get it running. We analyze the log and see what are we missing then add them 1 by 1 (this will give us maximum stability that can be attained).
let's remake that device tree with only the 100% necessary things and we can always add up on top of that. Let's not take TeamHackLG base. Of course we will use the 7x27a settings (SoC's are almost the same). Well, the best thing is to make some display things for our own 8225 socket. It will take a while but all we need is in our kernel. We can focus on this later to improve the stability even more.
Well. Our first goal is to make it boot using ONLY the blobs from our device + the GPU drivers I managed to obtain (they are optimized for JB). After we get that working we should worry about other things. Kernel should be modified just to boot (in the first stage). After we get a fully working device (RIL, WIFI etc) we can work on a better kernel, optimization, overclock, deep-sleep and everything we want. I also watched in the LG Ramdisk (from stock). It's a bunch of garbage half of it could be deleted. Well I am pulling the blobs tonight, download cm10.2 source and let's get to work my friend. Imo we should focuse on the boot first. Ofc if you have any opinion I am always to open it and if your idea turns to be a better one (since none is perfect) we will go for that.
EDIT2: There is a fetch error in cm10.2 let's try with branch jellybean.
christi9503 said:
That is right but we are never going to get a stable cm11 because of the gpu. We can make 1 sim work i think
Sent from my LG-P710 using XDA Free mobile app
Edit: @weritos
The best we can get is a JB based rom like CM10.2 at most. After we get the single sim working we can patch somehow for the P715 to use one sim (some ramdisk tweaking).
What I am thinking off:
let's pull the blobs only from our phone. See if we can get it running. We analyze the log and see what are we missing then add them 1 by 1 (this will give us maximum stability that can be attained).
let's remake that device tree with only the 100% necessary things and we can always add up on top of that. Let's not take TeamHackLG base. Of course we will use the 7x27a settings (SoC's are almost the same). Well, the best thing is to make some display things for our own 8225 socket. It will take a while but all we need is in our kernel. We can focus on this later to improve the stability even more.
Well. Our first goal is to make it boot using ONLY the blobs from our device + the GPU drivers I managed to obtain (they are optimized for JB). After we get that working we should worry about other things. Kernel should be modified just to boot (in the first stage). After we get a fully working device (RIL, WIFI etc) we can work on a better kernel, optimization, overclock, deep-sleep and everything we want. I also watched in the LG Ramdisk (from stock). It's a bunch of garbage half of it could be deleted. Well I am pulling the blobs tonight, download cm10.2 source and let's get to work my friend. Imo we should focuse on the boot first. Ofc if you have any opinion I am always to open it and if your idea turns to be a better one (since none is perfect) we will go for that.
EDIT2: There is a fetch error in cm10.2 let's try with branch jellybean.
Click to expand...
Click to collapse
That's a great idea, but first you should try CM10, 10.2 will be very slow on this device, since it is using hardware much more, and it is slower compared to CM10. But that's just my opinion.
True. @shiftyHungary: well after researching it seems cm10.2 is more optimized and from what I am seeing the most stable version of cm for 7x27 is cm10.2 we should work with that imo. There is a sync error because there was some fights over some source. will be fixed easy by replacing in repo with the path that it's used for cm11 or jsut delete that repo. Don't know which one yet. Researching.
Sent from my LG-P710 using XDA Free mobile app
Wow, it's a good new!! Thank you Chri.,
Sent from my Xperia M2 LTE using XDA Free mobile app
christi9503 said:
True. @shiftyHungary: well after researching it seems cm10.2 is more optimized and from what I am seeing the most stable version of cm for 7x27 is cm10.2 we should work with that imo. There is a sync error because there was some fights over some source. will be fixed easy by replacing in repo with the path that it's used for cm11 or jsut delete that repo. Don't know which one yet. Researching.
Sent from my LG-P710 using XDA Free mobile app
Click to expand...
Click to collapse
Okay, you know that better than me, I just shared my experience with my previous devices. Pm me if any help needed.
Well yeah. I really want CM also. I made my own version of CM11 it's smoother than the one we have but still mile away from what it should be even with hard-core optimization because CPU is too high because of the CPU. @weritos ->much respect to this guy, though I disliked some of the things were handled, I give props to him and I am thinking it's a good opportunity to work together and share idea with him (none has nothing to lose). Yeah cm11 will not be our deal and all the graphic glitches in games and stuff it's not because weritos CM11 it's because of LG being LG... With Cm 10.2 we have a way better chance (this came to my mind when actually trying to fix AOKP Ril problem which was based on CM10). I could feel the full powa!!!. Cm copiled GOOD from source will be butter (not in games and stuff ofc it's and Adreno 203 after all) smooth at least in UI and current day-by-day operations.
CM10.2 from the source code
christi9503, As soon as I pass all my exams
I redid the device tree under CM10.2, alter and drop provider (use LG)
But I tell immediately there will be problems with WiFi, Network
Well we can solve problems if we work rogether mosr likely. Best of luck with your exams. I am finishing blobs tonight and i made like half of the device tree. Tonight or tomorrow i will look in the ramdisk and will delete all that is useless
Sent from my LG-P710 using XDA Free mobile app
Well @weritos. Blobs are done (didn't pull the GPU ones since I will be using the ones I have found). Device tree is not fully done but it will be. I am building right now the first build. Using display CAF so it will take a while to get caf to work.
Edit: I will learn to use github and push repos there. Easier to work.
Cristi,
For now, use stock Kitkat kernel sources (just compile them using GCC 4.6 and you're good to go)
Because, once we modified stock kernel for certain things to work, like Wi-Fi, I can duplicate those and merge with my own customized kernel.
I'll work my ass off at my own kernel tonight, since I discovered certain problems.
Anyway, CM10.2 is a way better choice than CM11.
If Google didn't change whole lot of things in Kitkat, things would never have got that messy as it is now.
airidosas252 said:
Cristi,
For now, use stock Kitkat kernel sources (just compile them using GCC 4.6 and you're good to go)
Because, once we modified stock kernel for certain things to work, like Wi-Fi, I can duplicate those and merge with my own customized kernel.
I'll work my ass off at my own kernel tonight, since I discovered certain problems.
Anyway, CM10.2 is a way better choice than CM11.
If Google didn't change whole lot of things in Kitkat, things would never have got that messy as it is now.
Click to expand...
Click to collapse
Looking at the actual ramdisk kernel doesn't need modification for wi-fi to work. Same for RIL. Seeing as how it is handled we might be missing some bins or libs it'll be hard but it's possible to get ril with only our device files. This company called LG is just ****ing with us. Working on ramdisk for over 1 hours. There are A **** LOAD of duplicated files, obsoled, not used files. Working on it.
christi9503 said:
Looking at the actual ramdisk kernel doesn't need modification for wi-fi to work. Same for RIL. Seeing as how it is handled we might be missing some bins or libs it'll be hard but it's possible to get ril with only our device files. This company called LG is just ****ing with us. Working on ramdisk for over 1 hours. There are A **** LOAD of duplicated files, obsoled, not used files. Working on it.
Click to expand...
Click to collapse
And for those reasons I started to mistrust them as a company.
Good thing there are other devices, which really do the helping out.
Anyway, CM10.2 will be easier to get working on our device than CM11.
airidosas252 said:
And for those reasons I started to mistrust them as a company.
Good thing there are other devices, which really do the helping out.
Anyway, CM10.2 will be easier to get working on our device than CM11.
Click to expand...
Click to collapse
The mess they made. They just dirty patched mostly anything. My last LG device for sure.
Sometimes I am really thinking what big companies think. Another update. Sometime there is echo on what you are talking and stuff (like you hear your voice if you talk in the mic). It is because LG doubled some uevents or even tripled them. So they get inited like 3 times. This might solve the mic problem forever also.
airidosas252 said:
And for those reasons I started to mistrust them as a company.
Good thing there are other devices, which really do the helping out.
Anyway, CM10.2 will be easier to get working on our device than CM11.
Click to expand...
Click to collapse
WiFi will not work immediately
Rild will not work
weritos said:
WiFi will not work immediately
Rild will not work
Click to expand...
Click to collapse
We will work that out my friend. Better if it takes 1 week or so to fix just 1 problem than making a messy fix and having instability and stuff. Quality over quantity. In the end that is the best combo.
Amyway, how everything is moving?
Wi-fi isn't a big deal breaker. We'll fix it, as well as RIL.
And we should avoid using modules.
Sent from my LG-P710 using XDA Free mobile app