KitKat for Arc S ? - Xperia Arc Q&A, Help & Troubleshooting

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:

Related

new to the g2...best ics rom?

i see there's been other threads that have asked the same thing....however, things like this change on a daily basis....just wanted to get an idea of where to start on an ics rom for the g2. thanks in advance for those who respond
also, if you do recommend something, any heads up on what trouble you've had with it.
They're all good honestly. For AOSP, Virtuous Quattro is heavily outdated, and the rest perform (very) similarly. Camera works, but it hasn't been completely figured out yet. Other than that, it seems like most of the issues have been figured out. In my experience with Andromadus I had absolutely no issues.
For Sense, again, they all perform similarly. They are somewhat faster when compared to the AOSP counterparts, but the camera doesn't work at all. Atm I'm running Sensewich B6 and it's very smooth/fast. No issues so far.
If you're happy with a possible buggy Rom go for andro test. It is far smoother than the stable release (B2).
Sent from my HTC Desire Z using xda premium
MarkyG82 said:
If you're happy with a possible buggy Rom go for andro test. It is far smoother than the stable release (B2).
Sent from my HTC Desire Z using xda premium
Click to expand...
Click to collapse
lol, stable release (Beta 2)
As crestofawave said there's only minor differences about performances from one to another and there are only few issues left.
I'm running CM9 Unofficial and i'm really happy with it. People seem to be happy with the lastest Andromadus too. And if you want Sense, don't hesitate, Sensewich B6 is really good.
where can i download andromadus v11 from?? i'm running GB 2.3 on my G2 and its acting up now for some reason.
i'm new to this whole thing and i have no idea what to do.
If anyone can help me out, it'll be greatly appreciated
Rafter581 said:
where can i download andromadus v11 from?? i'm running GB 2.3 on my G2 and its acting up now for some reason.
i'm new to this whole thing and i have no idea what to do.
If anyone can help me out, it'll be greatly appreciated
Click to expand...
Click to collapse
there's beta 5 now...take a look in development section!
Rafter581 said:
where can i download andromadus v11 from?? i'm running GB 2.3 on my G2 and its acting up now for some reason.
i'm new to this whole thing and i have no idea what to do.
If anyone can help me out, it'll be greatly appreciated
Click to expand...
Click to collapse
Go to development area & just find the rom you want to try. As far as not knowing what to do, how lost are you? I see youre new here. Backing up? Flashing? Let me know
Are there any miui ics roms out there suitable for use as a daily driver? I'm currently using strawmetals miui rom.
I use the one in my signature and I much enjoy it, it's fast, it's stable the camera/camcorder works, and the dataswap mod makes multitasking very smooth.
ics roms are too laggy once u add more apps on cuz you run out of ram fast. it sucks ive tried cm9/andro/mimicry. Its what you have to give up inorder to have ics on your phone.
tvdang7 said:
ics roms are too laggy once u add more apps on cuz you run out of ram fast. it sucks ive tried cm9/andro/mimicry. Its what you have to give up inorder to have ics on your phone.
Click to expand...
Click to collapse
Not the case with the ICS Rom I'm using in my signature, and I have 150 apps installed (as per the 'optimizing # of 150' when I clear the dalvik cache and have zip align feature enabled). Though it seems to *need* the latest *.19 radio to use, but you don't need the DZ hboot since it's quite a light rom in comparison to other ICS roms. Works best with sd-ext and 64/96 dataswap option.
mimicry was the fastest for me, but i couldn't record audio in some apps like evernote. what i did was flash quadsense and THEN mimicry w/o formatting partitions. don't know why but this solves the problem. like the user above said, the new radio is necessary--i saw instant increase in performance after the flash.
---------- Post added at 09:14 PM ---------- Previous post was at 09:09 PM ----------
kbeezie said:
Not the case with the ICS Rom I'm using in my signature, and I have 150 apps installed (as per the 'optimizing # of 150' when I clear the dalvik cache and have zip align feature enabled). Though it seems to *need* the latest *.19 radio to use, but you don't need the DZ hboot since it's quite a light rom in comparison to other ICS roms. Works best with sd-ext and 64/96 dataswap option.
Click to expand...
Click to collapse
what does sd-ext and 64/96 dataswap do and what audience is it ideally for? do you have to reinstall your apps after a flash of a different rom? btw, do you have problems with the launcher app drawer taking long to load? i tried both nova and apex, but both are plagued by the same problems. i tried the tweak to keep launcher in memory and it helped but i still have a slow down with initial opening the app drawer.
crimsonpham said:
what does sd-ext and 64/96 dataswap do and what audience is it ideally for? do you have to reinstall your apps after a flash of a different rom? btw, do you have problems with the launcher app drawer taking long to load? i tried both nova and apex, but both are plagued by the same problems. i tried the tweak to keep launcher in memory and it helped but i still have a slow down with initial opening the app drawer.
Click to expand...
Click to collapse
DataSwap compliments SD-Ext, with his rom if an sd-ext partition exists on the SD card it'll automatically move the content of /data/app and /data/app-private to /sd-ext/app and /sd-ext/app-private. Unlike most sd-ext apps it does not move the cache/dalvik-cache to the SD Card as that would only slow things down.
With DataSwap it places a swapfile on the /data partition (hence using the space freed up by sd-ext and splitting the usage between two devices rather than all on the /data partition), which is much faster than using swap on the SD card, although it will still use swap on the SD card if present, will just add it to the total swap (but will rarely be used as ~54MB seems to be the sweet spot with Eliterom). 96MB is used for people who tend to be heavy multi-taskers for extra smoothness.
I do not have a problem with the apex loader taking too long to load with at least the 64MB DataSwap mod applied, and the app list is quick in the drawer as well.
IF you switch to a different rom, then naturally you're going to want to wipe everything before flashing a brand new rom, as not wiping between different kernels/roms/systems is just asking for trouble (though upgrading to a new EliteMod Rom or Kernel usually does not require a wipe unless he specifies it in the change log).
PS: With sd-ext used, you DO NOT move your apps to SD card, as /data/app* is mapped to /sd-ext/app* and you are already using that partition on the SD card for your non-system apps, moving to SD card will instead move it to the FAT32 portion of the card and performance would be noticeably degraded.
The G2/DZ isn't exactly ram friendly for ICS so swapping, whether it be with a mod like DataSwap or a swap partition on your SD card is advised for the best performance, otherwise you run into the sluggishness or forced closes you described when memory starts to cap out.

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!

CyanogenMod versions for Wildfire S

Hi,
I am really full of compliments about the good work of some guys that have done a good job in building the actual CyanogenMod versions for Wildfire S.
Thank you sooo much!!
But what I currently do not completly understand...
Why are most of the CM users really happy about version 10.2 or version 11.0 (like orig. CyanogenMod or WFSY) when those versions - last version of CM 9.2.2 included - do not even have GooglePlay/PlayStore and Data2SD (or Link2SD) installed?...
The last (and obviously most advanced CM version) CM9 (alpha9, v.9.2.2) would already be a wonderful solution for the WFS phone (I tested it!!) and it is said to be nearly finished (even video camera is working now at the version of Olivier) BUT both mentioned, absolutly necessary components are missing (and nobody mentioned it yet). Or what can I do with a phone where I cannot install new apps at all?..
So what is it that I misunderstand?...
I would be very happy if anybody could inform me about how I can find a version that has a complete set of system apps or how/where I can find both missing components to complete them by myself. (and even more happy if the cyanogenmod update function would still find some updates)
Otherwise I would guess that not any of the existing CM-based versions for Wildfire S can be used at all...
Should all the past work for creating a CM version (Android 4.x !!) for the (unfortunately!) one and only COMPACT smartphone on the world, 'Wildfire S' (I must admit, it is in fact!!) should have been completly in vain ???... I couldn't believe it.
Thank you guys very much for your nice explanations!
All the best to this wonderful community,
from Falk
CyanogenMod said:
Google Apps are the proprietary Google-branded applications that come pre-installed with most Android devices, such as the Play Store, Gmail, Maps, etc. Due to licensing restrictions, these apps cannot come pre-installed with CyanogenMod and must be installed separately.
Click to expand...
Click to collapse
Gesendet von meinem Xperia Z mit Tapatalk
Hi Olivier,
many thanks for your tip. You did not mention the point directly but I could answer most of my questions by mayself then.
Now I installed CM9 'cm-9-20140720-Olivier-marvel' together with 'CronMod-INT2EXT+_signed'. Works pretty fine!
Only little questions have been left now...
1.) How can I sort my app icons by subjects/folders (s. HTC Sense)? This Trebuchet launcher does not seem to support anything like that. If there is no chance, which launcher would you suggest instead?
2.) There is no really 'useful' version of CM10 or CM11 for WFS yet, is there? I couldn't find. Do you think there will be s.o. still working for a final version next time?... (why is Wildfire but not Wildfire S an official CM development?)
2b.) At your current version CM9, is there any problem left that should still be fixed? Everything works fine here yet...
3.) Therefore the OTA updater for CM would be a fine feature like in CM9 vers. 9.1.0 (but no updates found yet!). But your current CM9 version does not support it any more. Any reason for that?
3a.) Are updates possible anyway without flashing the whole ROM?
3b.) Is there anybody managing OTA any update of CM (v. 9..11) for WFS?
3c.) Are OTA updates from cm9 to cm11 possible?
4.) Skype does not react when clicking the icon to start it. Any idea what is the problem?...
5.) Some system programs (e.g. contacts or call manager) do not have that nice design than before. There is no chance/choice to exchange them?... (if yes, how and where to find alternatives?)
Thank you again for your final responses!
First of all this really does not belong in the development section, in Q&A perhaps.
And you just can't ask every single think that comes up in your mind, you gotta search a little bit and try it out for yourself.
Now, 1. Trebuchet does support folders but not auto-arranging. Most of the popular launchers support this.
2. The current CM10 and CM11 are perfectly functional and working. Though they lag a bit (which is fair considering our old device). And the wildfire only had an official CM7 which is very old now.
2b. If you don't have a problem it does not contain a problem.
3. OTA is working for CM11. But for CM9 a OTA makes less sense considering that its stable now.
4. No idea.
5. Again you have to look for yourself, nobody can babysit you all the time.
thanks very much!
Okay, maybe question 1 might belong to Q&A. That's it. Sorry.
To make you understanding (sorry to write again so much!)...
to 1.) Did not expect that it would support it. So I did not even search for!... Thanks, this drag/drop solution is more than perfect!!
to 2.) Sorry, then I am not able to find them. I searched a lot and found actual version like 'WFSY11.0-WFS-V5.5, 20140723' or 'cm-11-20140726-NIGHTLY-marvel' where not even back button or Android option menu worked. Lots of functions are missing. I did not try 'cm-11-20140810-NIGHTLY-marvel' but do not expect more within one month. The same with cm version 10.2. In a thread I read that it was give up because cm11 is already working better.
**** So would you please give me the link to the finished versions of cm10 and cm11, please? ****
(a patch for the video camera problem seems to be existing shortly now...)
to 2b.) My first problem I saw was missing updater in cm9 for version 10 and 11. And the strange Skype problem. And video problem was fixed JUST before!! BT seems to have restrictions as well. So there is good reason to ask this question!?..
to 3.) It seems as if simple updating from Android 4.0 to 4.2 (cm10) and 4.4 (cm11) isn't possible!?... Officially it seems to work. E.g. OTA of Samsung offered update from 4.2.2 to 4.4. Strange!... How/why does it work here?...
Remark: So I suppose it is CyanogenMod which does not support it... It will not work without 'Titanium Backup' here...
to 4.) I suppose you will have the same problem!? Maybe you have opportunity to try out quickly!?... Skype really does not seem to run on WFS cm9+INT2EXT+. Isn't that strange?... (I reinstalled it already. No chance.)
to 5.) I asked this HERE because it belongs to SYSTEM apps (contacts or call manager) that cannot easily be exchanged, as far as I know!... Can they?...
There is one thing I would like to add, after your remarks to my point 2... Maybe I could not find the right sources. But this is because there is no resource pool (about WFS at XDA anywhere. Instead there just appear 'lonely' links in some threads. And instead of telling/explaining the systematics (if there is one) you guys generally just mention the fact (e.g. a link). So this makes it hard for non-insiders. You understand what I mean?...
(so e.g. I will have to ask (in another thread) how I can find the 'FM radio' app (no streaming!) which is missing in CM9 - instead of just looking at the right page where they are collected)
I would be really happy to get to know at least where you guys have found the informations for all what you do when 'cooking' new versions, etc.!...
Cause then I would have read about all that much more!... Instead of blaming me. Sorry, if I do not have that general info that you got already.
Maybe you understand better now!?... Would be fine.
Anyway, thanks a lot for your short repsonses. Have a nice day!
Again only things that are directly related to development are to be placed in development section. And NO if you have a problem with a rom you have to ask it in Q&A. Read the development forum rules in the stickies attached to the top of the section.
And you could also try reading through the stickies in the general section. It will give you some understanding.
Now CM10 and CM11 works, the threads are pretty high in the development section, you can find them if you look. The version of CM11 you used is the right one (the NIGHTLY) and back button does work. Try the later versions. Officially updating to a higher version is different and large corporations can spend time and money to make it work. But it just is not possible (or rather safe) with the variety of unofficial roms. You could try but most probably fail. You can install different apps for call and messaging and they will work. Search for those apps. CM9/10 works fine and have very less amount of problems. Now remember that this is a very old device and the devs are doing it NOT as a profession. So every single thing will never work.
Now as a last your largest problem is you think everything will be written somewhere in front of your eyes. It will not be. You have to use Google before asking a question. And also you just have to calm down and fix your attitude.
aWFSuser said:
First of all this really does not belong in the development section, in Q&A perhaps.
Click to expand...
Click to collapse
That was my fault, I'd moved this out of a thread and mistakenly put it in the Development section. All sorted now.
thanks again for your time to answer!!
I know, I sound as if I would not know which hard work you guys do. But I do, aWF Suser. And I mentioned that already in the beginning.
And I have heard already from your collegues that it would be a good idea if things could be organised some better. The official cm versions e.g have a central resource pool. Or the android-Wiki and CM-Wiki notes are all out-dated (from 2012) !!... Etc.
But PLEASE understand this more as a suggestion than a criticism - from a user that in your eyes only expects and criticises but cannot give. This is not the case!
Thank you!
I know it is an old smartphone I have. And I would have bought a new one already a long time ago. But even Samsung Galaxy Mini is too big in size and some important functions you will only find in the big version. Why is that so? Nobody can explain!... (i would pay the same price for a small phone!!! Handy devices must not be worse and more expensive than big ones!!)
The WFS is just the only really COMPACT smartphone all over. And I am sad that the industry detected a trend to bigger displays. The opposite is the trueth. Nearly all my friends e.g. like to have a compact phone but those always a beginner versions/hardware which cannot be understood at all.
Really sad. It is a big strange hole in products on market, isn't it?...
Unfortunately you did not give me tips how I could find a way to get more familiar with what and how you guys are doing. Is it a secret? I could imagine to do some work here as well. I am very interested in how you are doing your development work!...
Thank you again...
Now it is sure...
Olivier's last CM9 version still has bugs, not only the problem with lgCamera and Skype but also at the akku loading status.
It seems as if it is not correctly refreshing. The loading curve (s. settings) slows down a lot and shows e.g. after 4 hours loading still 43%. But after rebooting it changed to the right value finally: 100%.
So again my question before, as Olivier unfortunately put away the OTA update function (but ment that it is not necessary anymore):
How can this version be fixed?
As far as I know you don't offer patches but only complete ROMs...
Okay first sorry for being rude as posting in the development section was not your fault.
Now the main problem with our device is not that its old but that it has a armv6 cpu which is not supported by later android versions. So development for developers is tougher and bugs will remain. I mentioned the general stickies before there you can find some useful guides.
And have you installed GAPPS in CM9 because some apps depend on it and won't work without it.
And just to be clear, I'm not really a developer but just a user like you.
I never said CM9 doesn't have bugs. It's is clearly stated in its OP that:
modpunk said:
This ROM is not meant for daily use!
Click to expand...
Click to collapse
Hallo Olivier,
never mind. But I just understood it like that. As you gave the reason for the OTA non-support in your ROM.
So if I misunderstood you... what is your reason then?...
In fact it would bring us forward if you could please comment my questions and/or give tips to solve the mentioned problem.
@so please give me a chance to fix the akku status bug. This is really annoying.
Can you confirm that problem? And if so will you fix it?
And if so how can I update it by OTA updater? Or alternatively at least by a patch but not by a new complete ROM !?...
@TO the Skype problem...
First of all: can you confirm my problem?...
To your question: I used your ROM from 20th Aug. (119.518 KB) This one contains already gapps, I suppose. Cause Google Play and the other stuff was already installed!...
@TO lgCamera...
This wonderful camera app worked fine with EQDKP (v.2.3.5) but now it is too slow and hops a lot. Can you confirm that?
And if so do you have any idea why this is a problem?...
@how can I add FM Radio (analog) support?...
Thank you very much for your feedback!
PS: So if the last version of CM9 is not ment for daily use... which CMx version is it then? Is there none?...
Currently your cm9 works fine. Only those three problems so far...
Do you care for my bug messages?... (or where can I post them?)
Hallo aWF Suser,
yes, I know the problem with the arm version. You must not excuse for any bug in CM.
I do not have problems with bugs. I have more problems when they cannot be fixed easily (missing OTA updater) or errors are not heard or cared for so that bugfixes will not be available at all...
By the way the phone Wildfire (without 'S') is supported by Standard CyanogenMod and also has an ArmV6 processor!...
You mean I should read again the forum rules?... What is it that is is still annoying you in my style of writing?...
Olivier's ROM I used (s. previous message) obviously contained GAPPs already. GooglePlay atc. was already installed. So this should not be the reason, should it?...
First of all: can you confirm my Skype problem, aWF Suser?... I expect it to be in each CM9 version!...
Thank you very much for your support!
PS: By the way, I have compatibility problems when flashing ROMs. For nearly each ROM I have to change the recovery. Is there any that can read all 'formats' of zip files?...
Falk2 said:
Hallo aWF Suser,
yes, I know the problem with the arm version. So you must not excuse for any bug in CM.
I do not have problems with bugs. I have more problems when they cannot be fixed easily (missing OTA updater) or bugfixes are not available at all...
By the way the phone Wildfire (without 'S') is normally supported at CyanogenMod and also has an ArmV6 processor!...
You mean I should read again the forum rules?... What is it that is is still annoying you in my style of writing?...
Olivier's ROM I used (s. next message) obviously contained GAPPs already. GooglePlay atc. was already installed.
So this should not be the reason, should it?...
First of all: can you confirm my Skype problem, aWF Suser?... I expect it to be in each CM9 version!...
Thank you very much for your support!
PS: By the way, I have compatibility problems with ROMs. For every second ROM I have to change the Recovery. Is there any that can read all 'formats' of zip files?...
Click to expand...
Click to collapse
The Wildfire is listed officially only for CM7 (gingerbread) . After that it has not been supported. I am not asking you to read the rules, in the stickies in general section there is a thread that lists some guides to some useful things. And is OTA that necessary because in most cases a dirty flash is enough to upgrade from one version to another as long as its the same android version. Upgrades between different android version would not be possible even with OTA (as lots of things change, it will probably end in a bootloop). I am not using CM9 currently so can't speak for that.
So then which CM version are you using on your WFS? And why?
I flashed cm11 shortly but it still has too many problems. E.g. the camera app crashes after successfully recording a video, the launcher only has two pages, launcher does not seem to support folders, etc.
Do you know where I can find the actual todo list? (AndroidWiki unfortunately is not maintained anymore!)
I will give Paranoid 4.45 a try yet. Maybe this is better!?...
Otherwise I will keep cm9 and hope that we can find out why Skype is not running.
Oooh, that is important... I can make a 'dirt flash'? This is very fine!! Then OTA is not that necessary, of course. But there is still no reason to left it away, is it? Especially because all this observing and searching for the update is NOT necessary! Can't understand Olivier here...
Could you comment my PS as well, please?...
(error log: "cannot load volume /misc. Can't partition non-vfat: /sto .. (vfat)")
http://forum.xda-developers.com/htc-wildfire-s/development/cyanogenmod-10-t2908631
is there any better rom than this rom? how can i improve battery life with screen on? i want it for daily driver, i do not use bluetooth ad2p but i dont know what armv7 features means...
for me its affordable atm and give a new life to the oldie and shiny wfs
Which rom is the most stable for everyday use?
(With working wi-fi tethering)

[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 $

Categories

Resources