Develop Bugs

[Q] cyanogen - is it out?

I read on here he posted a status on twiter but was wondering if it's out and how to install it?
Thanks

Its called cyanogen and no, it hasn't been released as of yet.
[G2/HTC Vision]

Lol @ Crayogen... Anyway like luis86dr said it's not out yet. There were some nightly builds (unstable versions) posted yesterday but they got taken down pretty quickly. When CM6.1RC1 is released it will be available in the Developer section. You'll know when it's there; it'll be hard to miss.

luis86dr said:
Its called cyanogen and no, it hasn't been released as of yet.
[G2/HTC Vision]
Click to expand...
Click to collapse
fixed thanks! any idea when ti should come out... also is it an app you can run or does it require some other coding and so on? Sorry very green to android

gravis86 said:
Lol @ Crayogen... Anyway like luis86dr said it's not out yet. There were some nightly builds (unstable versions) posted yesterday but they got taken down pretty quickly. When CM6.1RC1 is released it will be available in the Developer section. You'll know when it's there; it'll be hard to miss.
Click to expand...
Click to collapse
lol Thanks! I just hope it easier than over clocking... it took me a good bit to overclock yesterday... but it was simple as changing the binary file name.

tbssimp said:
fixed thanks! any idea when ti should come out... also is it an app you can run or does it require some other coding and so on? Sorry very green to android
Click to expand...
Click to collapse
The first rule of CyanogenMod is that you never ask for an ETA (when it will be released). Just thought I'd get that out of the way before someone strangles you for asking
CyanogenMod is a complete OS (Operating System) replacement. Also known as a ROM. In order to install CM, you will need a permanently rooted device. After rooting, you will need to install Clockwork Recovery, which will allow you to back up your current ROM and install the new one. It's fairly easy as long as you follow the steps in the links I posted, and of course follow the steps that will be posted in the CyanogenMod thread when it comes out.

tbssimp said:
fixed thanks! any idea when ti should come out... also is it an app you can run or does it require some other coding and so on? Sorry very green to android
Click to expand...
Click to collapse
Cyanogen is a ROM. Not a app, big difference. Also to install the rom you will need to perm-root your phone.
Check the development section on how to do this and since your new to android I recommend you study up on adb / fastboot until your comfortable with the root process. Its really easy but any mistake in the commands will result in your g2 becoming a display model.
Once your rooted go to market and download clockworkmod.
Once downloaded open and flash recovery.
Walaaa, your ready for roms and all the bad stuff we shouldn't do to our phones. Hope this helps.
[G2/HTC Vision]

Cyanogen
Coming from Windows Mobile, I am used to flashing ROMs left and right. But what makes Cyanogen ROMs so special? From the sounds of it, it is the next best thing since sliced bread.

GermanGuy said:
Coming from Windows Mobile, I am used to flashing ROMs left and right. But what makes Cyanogen ROMs so special? From the sounds of it, it is the next best thing since sliced bread.
Click to expand...
Click to collapse
Well I've never actually run CM before... But from what I understand what makes it so great is that it is based off AOSP (Android Open Source Project) code, adds some extra features, and some optimizations. Basically it's like if you took all the complaints you had about Android and fixed them, then you'd have CyanogenMod.
I think CM is especially good for people who don't have a Vanilla Android phone (like the G1, G2, and Nexus One). For instance my Vibrant came with a lot of proprietary apps and bloatware preloaded, and has a "TouchWiz" interface throughout the entire OS. CM will fix all that

luis86dr said:
Cyanogen is a ROM. Not a app, big difference. Also to install the rom you will need to perm-root your phone.
Check the development section on how to do this and since your new to android I recommend you study up on adb / fastboot until your comfortable with the root process. Its really easy but any mistake in the commands will result in your g2 becoming a display model.
Once your rooted go to market and download clockworkmod.
Once downloaded open and flash recovery.
Walaaa, your ready for roms and all the bad stuff we shouldn't do to our phones. Hope this helps.
[G2/HTC Vision]
Click to expand...
Click to collapse
OOOO I didn't know it was a no no to ask the ETA lol sorry...
Well so far I have the vissionary perm root and I have clockwork... I tried backing up the ROM with clockwork before I overclocked the phone... it shut teh phone down and when restarted it sshowed a screen with the android guy and an ! inside a up arrow? I didn't know if it was suppose to do that or if that was bad I pulled the batt and restarted and it started fine so I am guessing I didn't really back up the rom... is that bad if i might want to get back to stock one day?

GermanGuy said:
Coming from Windows Mobile, I am used to flashing ROMs left and right. But what makes Cyanogen ROMs so special? From the sounds of it, it is the next best thing since sliced bread.
Click to expand...
Click to collapse
From my experience with the G1, cyanogen ROMs have always been stable and relatively bug-free with a lot of additions and ability to customize stuff within the ROM.

It's too bad that CM6 only uses ADW as the Launcher, I use LauncherPro Plus (stock ain't bad either) and I hope ADW is as fast & smooth as LauncherPro Plus.

TL24 said:
It's too bad that CM6 only uses ADW as the Launcher, I use LauncherPro Plus (stock is ain't bad either) and I hope ADW is as fast & smooth as LauncherPro Plus.
Click to expand...
Click to collapse
i use ADW now and have no problems...
does CM 6.1 RC1 come pre themed or are we able to add a theme on top of it? i really hate this white status bar haha

Yeah, the non-stock launcher has always been the deal-breaker for me, too. I'm enjoying stock rooted with bacon bits for now.

Do you HAVE to use ADW Launcher with CM 6.1? Or once we install CM 6.1 (whenever that is) can we uninstall ADW Launcher and install LauncherPro Plus?

TL24 said:
Do you HAVE to use ADW Launcher with CM 6.1? Or once we install CM 6.1 (whenever that is) can we uninstall ADW Launcher and install LauncherPro Plus?
Click to expand...
Click to collapse
You don't have to use it you can install any other launcher you like.

gravis86 said:
You don't have to use it you can install any other launcher you like.
Click to expand...
Click to collapse
Good to know! Just had to ask since this is my first Android device and installing CM 6.1 would be my very first time installing a ROM.

I use Launcher Pro on my other phones running CyanogenMod. It works great. Sometimes I leave ADW installed, other times I remove it completely.

Great to hear..... Now.... If only Cyanogen would release CM 6.1 already lol

seancneal said:
Yeah, the non-stock launcher has always been the deal-breaker for me, too. I'm enjoying stock rooted with bacon bits for now.
Click to expand...
Click to collapse
Ok. I think I got bacon bits installed too but what exactly (or where can I go to read up on) does bacon bits give me? I had already installed busybox and I got the superuser extra from rom manager; so, tell me what else I'm getting and how do I best utilize these tools. I basically need a noob guide, but hey I've gotten this far (rooted also killed Google Goggles before the OTA update so I had to roll back then forward) I'm getting it slowly and my little bit of linux exp helps me a little bit too Thanks to whoever for whatever info you can point me to in advance.
On the thread, I been using ADW for a bit now... solid with (main reason) open source development, lots of themes, etc. Used the Launcher Pro (free) and liked it slightly better for feel, but I like something that can be looked at and improved via collaboration.

What I would like is a simple ICS rom, but there are none!

Yep.
I just wish there was stock ICS for the HOV. Vanilla ics rom is close but it still has sense left over.
cm9 is far too unstable, and all my attempts at flashing various roms of JB are instable/not daily driver ready.
There don't seem to be any truly usable roms for this device. Stock sense is the only build in which everything works.
It's either one thing or another. If the camcorder works, the build might not work with simple apps like voxer. If voxer works, then mms won't work. If JB runs perfectly stable, then maybe the camcorder doesn't work. Does a rom that works without bugs like this exist? Here are a list of things I would need in a daily driver rom:
1. Camcorder- I'm a skater and I like to film fun edits of me and my hoodrat friends doing hoodrat things on our skates.
2. MMS - Such a simple necessity.
3. App compatibility -It drives me crazy when my important apps like voxer, instagram, facebook, and launchers lag badly or crash every time I open them
4. LAG - this is why I can't upgrade to JB, I thought provision Rom was AMAZING until I started using my apps (see #3)
5. Simple Multitasking
6. Random reboots - doesn't bother me too much but I could see it happening in some situation where I would need the phone immediately and have to try and explain to someone that "Herp, muh super custom droid phone likes to reboot so you'll just have to wait."
So far the only thing I can think of doing is building a stock ics rom (which I have no idea how to do). Any tips, first timer here.
Right now I just flashed back to stock and am going to run the de-sense tool. Why must OEMs ruin everything we love?
I hate to complain like this and I'm very glad there are devs working on the problems I describe. I guess I'm just venting my frustration. I love this phone but I have spent so much time trying to get a stock android experience that works. I would just buy galaxy nexus or an S3 but I'm a college and pre-paid cheap phones are the only way to fly right now, man. Sorry to sound so negative throughout the post but these are simply my observations in contrast with my needs and wants.
BTW first post on here. Don't hate me plz.

What do you mean CM9 is unstable?
Sent from an awesome phone

ryanlow134 said:
What do you mean CM9 is unstable?
Sent from an awesome phone
Click to expand...
Click to collapse
Exactly cm9 is 100% stable. Do a fill wipe before you flash
Sent from my One V using xda app-developers app

ok thanks! The only cm9 I could find was on the cdma dev forum and it said a number of things including the camcorder didn't work.
...and then I googled it and found exactly what I needed. Flashing now. We'll see how this works. Was there something I'm missing? I looked at this one [CDMA/PRIMOC][ROM] Unofficial CM9 for PrimoC Beta
480p video recording kind of suck but it'll have to do I guess.

Before u go knocking on peoples stuff how about u make a effort to fix it ur self and u can't say well I don't know how. Well sir u know that little company that bought android os yea sell they Also have a easy to use search bar and so does this little site u are on
And last how about u try and talk to the developers by posting in threads and asking if thus is a problem or even try p.m the developers the problem and I know that for sure u never messeaged me about a application messing up on our provisions rom
Thanks for using provisions ROM and do remember have a nice day.
Sent from my PK7630000 using xda app-developers app

Please check user's face. We are not responsible for your 'horrific' experiences while trying custom roms build by us if you are too noob enought to not do a full wipe before you flash a rom.
Thank you and see you in the other side!

1ceb0x said:
you are too noob enought to not do a full wipe before you flash a rom.
Click to expand...
Click to collapse
No. Just because this is my 3rd post doesn't mean I haven't done my homework.
sbkjuggalo said:
And last how about u try and talk to the developers by posting in threads and asking if thus is a problem or even try p.m the developers the problem and I know that for sure u never messeaged me about a application messing up on our provisions rom
Click to expand...
Click to collapse
I did for the Vanilla ICS rom. Sorry about yours but I was going through a series of JB on my device and they all had the same problems with app compatibility/stability.

DrZaiusIsAlive said:
No.
I did for the Vanilla ICS rom. Sorry about yours but I was going through a series of JB on my device and they all had the same problems with app compatibility/stability.
Click to expand...
Click to collapse
Dude before flashing you must wipe your device properly.
Sent from my One V using xda app-developers app

DrZaiusIsAlive said:
No. Just because this is my 3rd post doesn't mean I haven't done my homework.
I did for the Vanilla ICS rom. Sorry about yours but I was going through a series of JB on my device and they all had the same problems with app compatibility/stability.
Click to expand...
Click to collapse
Don't know about comatibility/stability. Using CM10 from Lloir and works flawless for me, and yes, I'm using mms, camcorder, apps of a wide range, and yes, this is my primer and only phone, so I can say that it is stable too. Only camcorder problem I found that autofocus is somehow misbehaving in video recording.
Full wipe is essential for stability if you flash a rom that is based on something else, than the last one you used. I even erase sometimes the sdcards android and secure partitions if must. I tried Lloir's slimbean just this morning and seems promising enough, really thinking about to change to that rom permanently.

Full wipe means:
Factory reset (this will delete cache and dalvik cache - this will also remove the .android_secure folder)
Wipe system
Flash rom
Flash the correct kernel in bootloader
Reboot your phone
Voila, rom without any issues at all!
Don't tell me you did all these and you still have problems with JB and other custom roms. I just don't buy it. Everyone here that uses a custom rom are so enthusiastic about them, they don't even wanna get back on sense. I am having Paranoid Android on my One V from the moment I started making the rom for us, since August. From then onwards, I've only used this rom. I don't think that there are any kind of instability with it, because I test my roms before releasing them so if it was unstable, why should've I used it for more than 4 months now?

1ceb0x said:
Full wipe means:
Factory reset (this will delete cache and dalvik cache - this will also remove the .android_secure folder)
Wipe system
Flash rom
Flash the correct kernel in bootloader
Reboot your phone
why should've I used it for more than 4 months now?
Click to expand...
Click to collapse
1. I do all those. This is is my third android device. I used to have a galaxy tab 2 rom'd with cm10 and it was awesome. But even it had some problems with app compatibility. I got my learning in on that device. I nearly bricked it 3-4 times haha.
2. We use our phones differently. There are probably a ton of apps I use and a ton you don't. I know for sure that draw something is incompatible with JB itself.
I'll probably flash PA soon if some issues pop up with the cm9 build I'm using now.

Draw something is compatible with jellybean no doubt since I installed it on my HOV and it works.

[Q] Stable Android 4.0 ROM that can be used with Odin?

I'm looking for a stable Android 4.0 or above ROM which can be flashed using Odin. Any threads or links?

zacszy said:
I'm looking for a stable Android 4.0 or above ROM which can be flashed using Odin. Any threads or links?
Click to expand...
Click to collapse
Well I am not aware of any 4.0 or above ROMs that can be flashed via ODIN. I am sure if any developer wants, they may be able to do it but I really think that flashing via recovery is always a better choice compared to ODIN. I see no advantage for ODIN flash...
Do you mind telling me why do you need odin flash???

Well..
thearif said:
Well I am not aware of any 4.0 or above ROMs that can be flashed via ODIN. I am sure if any developer wants, they may be able to do it but I really think that flashing via recovery is always a better choice compared to ODIN. I see no advantage for ODIN flash...
Do you mind telling me why do you need odin flash???
Click to expand...
Click to collapse
Well, I'm more familiar with Odin flashing compared to recovery mode, and it's a whole lot easier compared to other flashing methods. I don't find that the recovery mode is easy to understand, so you mind to provide me the steps (better if they are easier to understand and follow) and also a link to a stable Android 4.0 Rom?

zacszy said:
Well, I'm more familiar with Odin flashing compared to recovery mode, and it's a whole lot easier compared to other flashing methods. I don't find that the recovery mode is easy to understand, so you mind to provide me the steps (better if they are easier to understand and follow) and also a link to a stable Android 4.0 Rom?
Click to expand...
Click to collapse
Do you have root access on your phone? Every step is actually quite easy to follow. There are really good guides on both general and development sections. But beforewe delve into howto's you should clarify what constitutes STABLE for you...
We have ICS (4.04) as well as JB ( 4.1.2 and 4.2.2) in the development section. All are pretty good but here and there they may have some bugs. Just go to their threads check them out. On the very first page of a ROM thread what works and what doesn't are listed. Decide whether you can live with one of them then we can talk about howto's.
I recommend CM9, CM10 and CM10.1 all from the developer arco68...
OHHH with a custom recovery, you don't even need a computer to flash a new ROM. That surely is a bonus...
Sent from my GT-I8150 using xda app-developers app

Okay..
thearif said:
Do you have root access on your phone? Every step is actually quite easy to follow. There are really good guides on both general and development sections. But beforewe delve into howto's you should clarify what constitutes STABLE for you...
We have ICS (4.04) as well as JB ( 4.1.2 and 4.2.2) in the development section. All are pretty good but here and there they may have some bugs. Just go to their threads check them out. On the very first page of a ROM thread what works and what doesn't are listed. Decide whether you can live with one of them then we can talk about howto's.
I recommend CM9, CM10 and CM10.1 all from the developer arco68...
OHHH with a custom recovery, you don't even need a computer to flash a new ROM. That surely is a bonus...
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
I have root access on my phone. Well, I don't see the ROM thread that you mentioned. Stable means that the ROM is not easy to crash or eats up my RAM even when I'm not using it, while common bugs are still acceptable if they can be fixed (I can't find threads from arco68, so I don't know what you mean by his CM9 and all those so...)
Hope you can enlighten me more about this recovery method and the difference between the CMs (if possible, also include any differences between ICS and JB b'coz I don't know which one to choose)

Recovery is super easy:
Download the zip and put it on your SD (internal or external, makes no difference)
Then turn of your phone
Press and hold Volume up + Power button + home button
Once the screen turns on, release the power button, but keep holding onto the other two
Then the recovery menu shows up
choose install zip from SD
select the zip and hit install
finished
Here are the links, with more detailed instruction on how to do it
CM10.1
http://forum.xda-developers.com/showthread.php?t=2214042
CM10
http://forum.xda-developers.com/showthread.php?t=1990795
CM9
http://forum.xda-developers.com/showthread.php?t=1576874

Ups and downs?
Are there any down sides regarding the CM9 mod? And can I change the shortcuts on the lockscreen if I install CM9?
And also, what is CWM actually? I don't understand from the FAQs in the forums or other sites, so can you tell me what CWM is (CWM5 or CWM6) and how to access or install that?
Sorry, I'm really considered a total newbie in this sort of stuff 8(>o<)8

zacszy said:
Are there any down sides regarding the CM9 mod? And can I change the shortcuts on the lockscreen if I install CM9?
And also, what is CWM actually? I don't understand from the FAQs in the forums or other sites, so can you tell me what CWM is (CWM5 or CWM6) and how to access or install that?
Sorry, I'm really considered a total newbie in this sort of stuff 8(>o<)8
Click to expand...
Click to collapse
Its a kind of recovery, called ClockworkMOD. Now its the 6.0.3.0 version if I'm not wrong...
Linky: here
Okay, the process of installation of a custom recovery is tedious. Link: here DO NOT USE THE FILES IN THIS PAGE. JUST THE INSTRUCTIONS.
Now, flash the ROM (any of the three is fine. I personally recommend CM9 or 10 cus its in its RC stages, which means Resource... something)
The instructions is on the ROM page itself. And you're done. I or arco are not held responsible if your phone is screwed up in the process (very little chance) or
if your heart fails because its loading for a longer period than it should be.
HAVE FUN!
Sent from my 4.1 running Galaxy W.

iDelta said:
Now its the 6.0.3.0 version if I'm not mistaken.
Click to expand...
Click to collapse
In CM9, I see that the ClockworkMod needed is 5.5.xxxx, so wouldn't CM9 crash if i use the 6.0.3.0 version instead of 5.5.xxxx?
And also, does the CM9 have any bugs? Because I saw some in the posts by people about CM10 but not CM9 (refer to links of above comments)
Anyway, it is a pleasure to receive help from you and the person above.

zacszy said:
In CM9, I see that the ClockworkMod needed is 5.5.xxxx, so wouldn't CM9 crash if i use the 6.0.3.0 version instead of 5.5.xxxx?
And also, does the CM9 have any bugs? Because I saw some in the posts by people about CM10 but not CM9 (refer to links of above comments)
Anyway, it is a pleasure to receive help from you and the person above.
Click to expand...
Click to collapse
Well obviously, since its a custom ROM, its bound to have bugs. There's no such thing as a "perfect" ROM. And I have 6.0.1.something CWM and I have flashed every single ROM, from 9-10.1. So it shouldn't be a problem.
Sent from my 4.1 running Galaxy W.

zacszy said:
In CM9, I see that the ClockworkMod needed is 5.5.xxxx, so wouldn't CM9 crash if i use the 6.0.3.0 version instead of 5.5.xxxx?
And also, does the CM9 have any bugs? Because I saw some in the posts by people about CM10 but not CM9 (refer to links of above comments)
Anyway, it is a pleasure to receive help from you and the person above.
Click to expand...
Click to collapse
Man, if you want a stable rom, buy another phone.

iDelta said:
Well obviously, since its a custom ROM, its bound to have bugs. There's no such thing as a "perfect" ROM.
Click to expand...
Click to collapse
I believe I have caused some misinterpretation here. What I mean is that I want to know if there is anything that's not working in CM9. The stuff below is found from the CM9 thread.
What's working:
Audio
Receiving and making calls
GPS
Compass
Proximity sensor
Wifi
Bluetooth
USB mass storage
HW accelerated gui
HW accelerated video
Camera
Torch
Wifi and USB tethering
There isn't anything that's not shown as "not working", so I'm asking you about it just for confirmation.
If there isn't anything, I will flash CM9 soon. :laugh:

zacszy said:
I believe I have caused some misinterpretation here. What I mean is that I want to know if there is anything that's not working in CM9. The stuff below is found from the CM9 thread.
What's working:
Audio
Receiving and making calls
GPS
Compass
Proximity sensor
Wifi
Bluetooth
USB mass storage
HW accelerated gui
HW accelerated video
Camera
Torch
Wifi and USB tethering
There isn't anything that's not shown as "not working", so I'm asking you about it just for confirmation.
If there isn't anything, I will flash CM9 soon. :laugh:
Click to expand...
Click to collapse
Everything works fine.
For CM9 for sure.

Madzix said:
Everything works fine.
For CM9 for sure.
Click to expand...
Click to collapse
Yeah, CM9 is like the most stable out of the three... hardly any bugs
Sent from my 4.1 running Galaxy W.

iDelta said:
Its a kind of recovery, called ClockworkMOD. Now its the 6.0.3.0 version if I'm not wrong...
Linky: here
Okay, the process of installation of a custom recovery is tedious. Link: here DO NOT USE THE FILES IN THIS PAGE. JUST THE INSTRUCTIONS.
Now, flash the ROM (any of the three is fine. I personally recommend CM9 or 10 cus its in its RC stages, which means Resource... something)
The instructions is on the ROM page itself. And you're done. I or arco are not held responsible if your phone is screwed up in the process (very little chance) or
if your heart fails because its loading for a longer period than it should be.
HAVE FUN!
Sent from my 4.1 running Galaxy W.
Click to expand...
Click to collapse
I just noticed something in your post. Just to clarify, RC mean "Release Candidate" not resource something... Just so you know. First alpha's come, then beta's, and right before a FINAL version is released in which most of the bugs are squashed, a release candidate comes to make sure everything is working. If for example, no bugs remain in a release candidate, it is renamed to FINAL as far as I know
However, there are different understanding of these names on the internet. For example, for some, once a product is in a BETA phase, no more new features added from there on. However, that may not be true for CM releases here, I am not sure.
and @zacszy, both CM9 and CM10 are pretty stable. I have not encountered any show stopping bugs but that maybe because of the way I use my phone, as I dont play games. I use it mostly for productivity, internet surfing, couple of youtube videos, music...
Try them all. I am sure you will pick one that suits your needs..

thearif said:
both CM9 and CM10 are pretty stable. I have not encountered any show stopping bugs but that maybe because of the way I use my phone, as I dont play games. I use it mostly for productivity, internet surfing, couple of youtube videos, music...
Click to expand...
Click to collapse
Really appreciate your help @thearif and I would definitely try them out before really settling in with the CM I want

thearif said:
I just noticed something in your post. Just to clarify, RC mean "Release Candidate" not resource something... Just so you know. First alpha's come, then beta's, and right before a FINAL version is released in which most of the bugs are squashed, a release candidate comes to make sure everything is working. If for example, no bugs remain in a release candidate, it is renamed to FINAL as far as I know
However, there are different understanding of these names on the internet. For example, for some, once a product is in a BETA phase, no more new features added from there on. However, that may not be true for CM releases here, I am not sure.
and @zacszy, both CM9 and CM10 are pretty stable. I have not encountered any show stopping bugs but that maybe because of the way I use my phone, as I dont play games. I use it mostly for productivity, internet surfing, couple of youtube videos, music...
Try them all. I am sure you will pick one that suits your needs..
Click to expand...
Click to collapse
Thanks for the definition. Just saying, you can't call it fully stable cuz .... well that's impossible. It is only nearly stable.... you may have not said it but I'm just saying. Haha
Can your single core run 4.1? My Galaxy W can! That's how I sent this!
---------- Post added at 11:30 PM ---------- Previous post was at 11:29 PM ----------
zacszy said:
Really appreciate your help @thearif and I would definitely try them out before really settling in with the CM I want
Click to expand...
Click to collapse
Good luck :thumbup:
Can your single core run 4.1? My Galaxy W can! That's how I sent this!

KitKat for Arc S ?

Can KitKat be ported onto our Arc S phones ????
Sent from my LT18a using xda app-developers app

Perhaps...
http://forum.xda-developers.com/showthread.php?t=2431179

17th_angel said:
Perhaps...
http://forum.xda-developers.com/showthread.php?t=2431179
Click to expand...
Click to collapse
That was just a discussion thread... and now some people think that just because it can run on 512MB RAM they can install it on their phones straight away... If kitkat ever comes to the Arc/S it will take a while for it to become stable enough for daily use. Also, the drivers we use are old since there have been no updates. If you guys want kitkat running successfully on this device, these old drivers need to be integrated with the new software, which is very tedious. Mike is already going to drown under 4.2 and 4.3, adding another OS to the pile will place him under more stress.
Don't assume the work we developers do is simple, just because an update came out that meets the system specifications means it can run just by downloading and installing it in recovery. If you ever tried to create a ROM by yourself, you'll find out that a lot of work needs to be done, along with many user complains and flooding your development thread with useless posts. That's how messed up the user community is nowadays. Jader's UHD ROM thread is one example of how users interact with the developer.
僕のLT18iから送られてきた

Im sorry, but which part of perhaps its a "definitely yes"?
I just point to that thread so he and anybody with the same question can see that it really going to depends on how google code it and how hard could be for the developers to bring that code to our devices...
I never declared that it will be a fact, but you have to admit that the 512 MB its a nice hope.

17th_angel said:
Im sorry, but which part of perhaps its a "definitely yes"?
I just point to that thread so he and anybody with the same question can see that it really going to depends on how google code it and how hard could be for the developers to bring that code to our devices...
I never declared that it will be a fact, but you have to admit that the 512 MB its a nice hope.
Click to expand...
Click to collapse
That reply was for that thread itself since some prick was like "hey Kitkat runs on 512MB devices"... I wasn't even referring to you in the first place.
Yes, it is hopeful but not promising, see Mike's reply at the thread itself
僕のLT18iから送られてきた

Yes, it's possible to port Android 4.4 for our device but it all really depends on if there will be any developer / developers who want to spend their time porting 4.4 for our device. Mike have started working on it for our devices, but we will see when or if he releases it or not.
I might see if I'm able to sync the sources, but the main problem on my end is that my PC is really bad and not suited for development.
Sent from my LT15i using Tapatalk

Yes, Harsh is developing the same, follow the link
http://forum.xda-developers.com/showthread.php?t=2134257&page=184

The fact that it can run, does not mean that it will run.
Either way, I am sure the devs will be porting it over in no time.
Sent from my Nexus 5 using xda app-developers app

Developers are trying hard, hope to see KK on Arc S soon

Fyi harsh isn't developing kitkat.. It's just a kitkat ui for his rom update...
Sent from my Xperia Neo V using Tapatalk 2

yes it is try to search if you wanna stable blasting fast rom with kitkat teme then flash super jelly bean by harsh with kitkat ui
---------- Post added at 08:02 PM ---------- Previous post was at 07:56 PM ----------
but kitkat based in my option is bet AORP kitkat rom try it

Just as a suggestion, I'm currently using VanirAOSP and it's pretty good. All I've to say is that right now one should get the vanir_anzu_4.4.2.012814 version, as the latest, vanir_anzu_4.4.2.022314, has a few additional bugs. On the mentioned good version WiFi works, everything is fairly smooth and you're left with enough space to actually install the apps you want, which seems to be an issue on many roms due to Arc's small internal memory.. Only real problem's the default browser lagging terribly, but I hear that's a general issue? Anyway, for anyone interested in kitkat on Arc it's definitely worth checking out.
Here's the thread: http://forum.xda-developers.com/showthread.php?t=2627083

If you want a good KK experiance I recomend carbon Rom just serach or let me doin' it for you her you are sir http://forum.xda-developers.com/showthread.php?t=2575425

AORP is stable for me.... you might wanna check
I m using AORP[anzu] from 2 weeks and it works awesome.
Scayris said:
Just as a suggestion, I'm currently using VanirAOSP and it's pretty good. All I've to say is that right now one should get the vanir_anzu_4.4.2.012814 version, as the latest, vanir_anzu_4.4.2.022314, has a few additional bugs. On the mentioned good version WiFi works, everything is fairly smooth and you're left with enough space to actually install the apps you want, which seems to be an issue on many roms due to Arc's small internal memory.. Only real problem's the default browser lagging terribly, but I hear that's a general issue? Anyway, for anyone interested in kitkat on Arc it's definitely worth checking out.
Here's the thread: http://forum.xda-developers.com/showthread.php?t=2627083
Click to expand...
Click to collapse
I will try VanirAOSP (out of curiosity), thanks for suggesting.
DuckyMomo said:
If you want a good KK experiance I recomend carbon Rom just serach or let me doin' it for you her you are sir http://forum.xda-developers.com/showthread.php?t=2575425
Click to expand...
Click to collapse
Tried it. Really cool ROM, some minor bugs but its OK

KitKat 4.4.2 AOKP and ART-runtime enabled
It is very well possible to use KitKat 4.4.2 on our phones. Even with ART-runtime enabled. I personally use AOKP (Android Open Kang Project)'s KitKat version, and I managed to get ART-runtime enabled and running very fast and smooth.
You can find the ROM here: http://forum.xda-developers.com/showthread.php?t=2624761
Of course you have to first install the kernel, which is given in the zip-file. Just unzip the kernel and Flashboot it to your device. Then go into CWM-recovery and go to Mounts and Storage and activate USB-mount. Locate the full AOKP-zip and place it on your SD-Card, as wel as the minimal Gapps for 4.4.2., found here : http://forum.xda-developers.com/showthread.php?t=2012857. Unmount the USB, and install the zip as usual through the menu for it. Then, after installing AOKP, install the minimal Gapps.
Reboot and let your device sit for a while, or play around with it a bit....
I proceeded with installing Mounts2SD from playstore, while before having prepared my class10 8 Gb sdcard into two partitions. One partition FAT32, size about 6Gb and one partition EXT2 size around 2 Gb. Move everything to SD-card through the menu of Mounts2sd, except Dalvik-cache. NEVER MOVE THIS!!! (Don't move dalvik-cache to SD...)
Reboot at least two times to let the script (Mounts2sd) settle in... After this I installed Pimp-my-Rom from playstore and activated the nav-bar and some other scripts to improve the experience. Also I odexed (after finishing all my modifications) the phone through this : http://forum.xda-developers.com/showthread.php?t=2527732
I then went to CWM-recovery through a reboot and made a full backup, which I advice you to do also, in case something goes horribly wrong.
Reboot to AOKP. As you can see, this ROM is awesome-fast beyond belief already. I had benchmarks in AnTuTu of around 6000, with NoFrills-CPU at 1401 Mhz. But, it can be faster if you choose to run ART-runtime instead of Dalvik. Be sure to remove all unwanted programs before switching to ART-runtime, because it'll take a lot of space in cache, and every program you don't need (system-programs that is) will reserve more space for ART.
Only and ONLY if your system is running smoothly on Dalvik, I advise you to go to your Phone-settings, (under Settings of course) and tap on 'Build-number' like 10 times. You will now become a developer. An extra menu will appear under Settings, where you can choose to run the ART-runtime library. Choose this and you will reboot.
Wait, wait and wait a long time for reboot. After initial booting everything has to be updated to ART-compiled apps. This will take a long time per app. Just wait and don't disturb your phone. If you get to the phone after booting, then you probably succeeded... You can check under the same settings-tab under Developer-options. If ART is selected, then you have it.
I strongly advice in case of mishaps regarding loss of network etc. to just reboot. Wait, wait and eventually you'll get there. Make a backup as soon as you have a stable working system under CWM-recovery.
I have been running stable ART under this AOKP-rom for about two weeks now and I'm really happy with it. Not only is the phone lightning-fast (6417 under AnTuTu, with CPU on my Arc LT15i on 1401 Mhz), but smooth as hell! Batterytime is amazing. This is as fast as it's gonna get! (I must have tried almost every ROM out there from stock 4.0.1 to 4.4.2...)
Hope you'll try and may it work for you too...!
(BTW my ultimate thanks to the guys from Open Kang Project!)
P.S. stock-browser is lagging... as usual under 4.4, but I use Dolphin and it is fast! Some toggles require reboot to function again. Some programs might fail you due to not being ready for ART. Facebook is a mess for instance, sometimes quitting unresponsice etc. Otherwise I have encountered no problems whatsoever.

Tried ION kernel and stuff and I can say that apart of one or two really minor bug the KK experience is just awesome and will be better within some months i suggest you to follow all the "Xperia Overlay" thing a I hope it gonna be amazing:laugh:

[AOSP Tamien 8.1 with OpenGapps]

I was able to use https://github.com/anestisb/android-prepare-vendor to prepare the vendor images to correctly build AOSP.
I submitted some changes to make it work with Pixel2-XL and they have been merged into main branch.
You have to wipe everything.
I dont know how to make proper zip images for TWRP so use fastboot
I use the fastboot script included in the zip after a full wipe and im all good
Thanks:
anestisb on Github
opengapps
not working:
pixel squeeze
AOSP 8.1 with google apps:
V3:
https://www.androidfilehost.com/?fid=889964283620776051
AOSP 8.1 stock (no gapps):
https://www.androidfilehost.com/?fid=817906626617955840
changelog:
v3:
Jan security update
v2:
updated camera
pixel launcher
updated wallpaper that was causing errors
fixed google setup errors during startup and boot
archive:
v2: https://www.androidfilehost.com/?fid=817906626617955877
V1:
https://www.androidfilehost.com/?fid=745849072291697825
During first boot google setup crashes a bit and I just skip it ...then on reboot I get complaints about stuff. but everything works. so......

deeproot said:
I built AOSP with OpenGapps and all I got was this forum thread
You have to wipe everything.
I dont know how to make proper images so use fastboot
I use the fastboot script included after a full wipe and im all good
Click to expand...
Click to collapse
Link?
Sent from my Pixel 2 XL using Tapatalk

yea, link?

?????

Don't tease us like this, lol. I'll flash anything at this point!
Sent from my Pixel 2 XL using Tapatalk

uplodz complete.

Interesting :good:

I've been doing my best to get my own build running for a few weeks now, and while everything else seems to work perfectly, I can't seem to figure out a way to get it to connect to mobile data. I'd be really interested to hear if there's something in addition to the build instructions provided by Google that you had to do to get it working!
I would just use your build, but my goal is to avoid gapps altogether. Hopefully the trick isn't to have gapps installed
Thanks!

prurigro said:
I've been doing my best to get my own build running for a few weeks now, and while everything else seems to work perfectly, I can't seem to figure out a way to get it to connect to mobile data. I'd be really interested to hear if there's something in addition to the build instructions provided by Google that you had to do to get it working!
I would just use your build, but my goal is to avoid gapps altogether. Hopefully the trick isn't to have gapps installed
Thanks!
Click to expand...
Click to collapse
I thought the whole point of gapps is Google *****es if you build a Rom with google apps installed already...

prurigro said:
I've been doing my best to get my own build running for a few weeks now, and while everything else seems to work perfectly, I can't seem to figure out a way to get it to connect to mobile data. I'd be really interested to hear if there's something in addition to the build instructions provided by Google that you had to do to get it working!
I would just use your build, but my goal is to avoid gapps altogether. Hopefully the trick isn't to have gapps installed
Thanks!
Click to expand...
Click to collapse
u did add in the propietary drivers i assume before u started making ur build?
this build is running smooth! i almost wanna say u couldve left gapps out n let ppl choose which they want to use but of cpurse this is only the beginning.. first thing i did was remove all those google hotword apks that fc, not had any issues yet and u already stated squeeze isnt on here but i nvr used that anyways
I was building from source today but my env has a ways to go before its useable.. it literally took all day to make aosp arm64 eng lol.. started gettin low mem stops towards the end so gonna look at it tom... i actually need to change it up and tweak settings cuz i only got 6gb ram
my set up tho is ur aosp, flash kernel 2.05 and magisk 15.1.. butter.. or shall i say vanilla??

prurigro said:
I've been doing my best to get my own build running for a few weeks now, and while everything else seems to work perfectly, I can't seem to figure out a way to get it to connect to mobile data. I'd be really interested to hear if there's something in addition to the build instructions provided by Google that you had to do to get it working!
I would just use your build, but my goal is to avoid gapps altogether. Hopefully the trick isn't to have gapps installed
Thanks!
Click to expand...
Click to collapse
aosp i dont think includes automatocally.. its runnin android web view n all lol instead of chrome that is

Now, I'm relatively new to the rooting world of Android. Is AOSP essentially custom ROMs? I know this is sort of a "if you don't know, you likely shouldn't be messing with it." I just love tweaking my phone!
So far only the squeeze doesn't work? Should the less advance user hold off until it's been tested a bit? Regardless, thanks for distributing your work to everyone on here! I love this community. Being able to share in the glory that is altering literally almost every aspect of your phone's software.

jgreen077 said:
Now, I'm relatively new to the rooting world of Android. Is AOSP essentially custom ROMs? I know this is sort of a "if you don't know, you likely shouldn't be messing with it." I just love tweaking my phone!
So far only the squeeze doesn't work? Should the less advance user hold off until it's been tested a bit? Regardless, thanks for distributing your work to everyone on here! I love this community. Being able to share in the glory that is altering literally almost every aspect of your phone's software.
Click to expand...
Click to collapse
for u id say hold off.. it works fine for me but it technically is a userdebug build.. AOSP =Android Open Source Project, Its basically Android built from Android source so typically devs can pull the source and make their own roms how they want them. Normally doesnt even have google apps like play store for example.
Its a very clean low lvl android OS and the dev controls every aspect of the build process.. its also been called Vanilla
this technically is "custom" but this initial build doesnt have many tweaks or customizations.. its merely a glimpse as to the possibilities
but hey, try it out if u got the itch, it wont hurt u lol plus the only real way to know the difference is to try it for yourself

jgreen077 said:
Now, I'm relatively new to the rooting world of Android. Is AOSP essentially custom ROMs? I know this is sort of a "if you don't know, you likely shouldn't be messing with it." I just love tweaking my phone!
So far only the squeeze doesn't work? Should the less advance user hold off until it's been tested a bit? Regardless, thanks for distributing your work to everyone on here! I love this community. Being able to share in the glory that is altering literally almost every aspect of your phone's software.
Click to expand...
Click to collapse
for u id say hold off.. it works fine for me but it technically is a userdebug build.. AOSP =Android Open Source Project, Its basically Android built from Android source so typically devs can pull the source and make their own roms how they want them. Normally doesnt even have google apps like play store for example.
Its a very clean low lvl android OS and the dev controls every aspect of the build process.. its also been called Vanilla
this technically is "custom" but this initial build doesnt have many tweaks or customizations.. its merely a glimpse as to the possibilities
but hey, try it out if u got the itch, it wont hurt u lol plus the only real way to know the difference is to try it for yourself

elliwigy said:
for u id say hold off.. it works fine for me but it technically is a userdebug build.. AOSP =Android Open Source Project, Its basically Android built from Android source so typically devs can pull the source and make their own roms how they want them. Normally doesnt even have google apps like play store for example.
Its a very clean low lvl android OS and the dev controls every aspect of the build process.. its also been called Vanilla
this technically is "custom" but this initial build doesnt have many tweaks or customizations.. its merely a glimpse as to the possibilities
but hey, try it out if u got the itch, it wont hurt u lol plus the only real way to know the difference is to try it for yourself
Click to expand...
Click to collapse
Honestly, I'd normally listen and hold off. But since I have a day off I think I'm gonna attempt it just for the sake of learning!
As long as it has the Play Store so I can download the apps I want, I'm good. If I can get all the apps I need to than I'll be a happy camper.
Say later on it's decided I want to go to another AOSP rom, am I going to have to wipe again? If I can get all my apps, won't have to wipe my device every other week, and can get my modules installed I should be good to do some good old fashioned experimentation.
I am not a smart man, at times. I'm gonna try it out. I have a few hours before anyone else is awake. Might as well use that time (un)wisely.
Plus I believe these "vanilla" ROMs, being what they are, can be modded to an even greater extent than the already pretty modifiable "stock" Pixel ones. Please correct me if I'm wrong.

prurigro said:
I've been doing my best to get my own build running for a few weeks now, and while everything else seems to work perfectly, I can't seem to figure out a way to get it to connect to mobile data. I'd be really interested to hear if there's something in addition to the build instructions provided by Google that you had to do to get it working!
I would just use your build, but my goal is to avoid gapps altogether. Hopefully the trick isn't to have gapps installed
Thanks!
Click to expand...
Click to collapse
I found this:
https://github.com/anestisb/android-prepare-vendor
I submitted my changes and they will update in a few days to the add tamien support.

I am going to hold off on this for now, as it's just a shell of what custom Android can be but just wanted to say thank you very much for getting the ball rolling. For giving us hope haha. I check the thread at least 4 times a day and my heart jumped when I saw this post! Good work!

Nice can we flash the Kernels that have been around here for a while on this rom?

patt2k said:
Nice can we flash the Kernels that have been around here for a while on this rom?
Click to expand...
Click to collapse
I flashed Elemental X and finger print stopped working.

deeproot said:
I found this:
https://github.com/anestisb/android-prepare-vendor
I submitted my changes and they will update in a few days to the add tamien support.
Click to expand...
Click to collapse
@deeproot
have you uploaded your WIP android_prepare_vendor anywhere? I would like to clone your changed repo and run this script if possible.
I attempted to manually add your changes in the pull request, but the script is breaking with a debugfs error
Thanks,
Edit: Found it, still getting same debugfs error.
Code:
[*] Extracting '/tmp/android_prepare_vendor.jlQiR6/taimen/opm1.171019.011/taimen-opm1.171019.011-factory-2df1c1cb.zip'
[*] Unzipping 'image-taimen-opm1.171019.011.zip'
[-] Symlinks have not been properly processed from /tmp/android_img_extract.FRWAOM/taimen-opm1.171019.011-factory-2df1c1cb/images/vendor.img.raw
[!] If you don't have a compatible debugfs version, modify 'execute-all.sh' to disable 'USE_DEBUGFS' flag
[-] Factory images data extract failed
[email protected] ~/Desktop/android-prepare-vendor $