Related
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.
Few n00b questions.
Firstly, how do i flash a nightly on my phone? lets say im running ofw 2.2 SEA edition? Do i follow the same procedure as if to flash RC1... do i also need to flash gapps similarly.
Secondly, are the links on quarxs' CM7 for defy thread up-to-date? or are there newer versions of gapps and nightlies floating around somewhere
Third, i have noticed that there is an issue with network and wi-fi when i flash cm7 RC1 over the nordic sbf. when i go back to official 2.2 SEA there is no hassle at all. Since i live in india i was wondering if that was the issue. I can easily take care of the network problem using "baseband switcher for defy" but it still doesnt help the wi-fi problem.
My question is.. will using the new BOOTSEA nightly solve this problem. I am assuming from the name is boot"SEA" im assuming its built southeastasia specific.
Fourth, ive used CM7 RC1 for a while and apart from the wifi issue i got problems with camera and video... it absolutely doesnt work, wether it be in potrait or landscape or whatever setting... the app just force closes. Any fixes for that.. ive got green lens.
please help!!! and i hope other similar questions can be added by members here so as to make this thread an FAQ for distressed users like me.
Thanks
deathw15h said:
Few n00b questions.
Firstly, how do i flash a nightly on my phone? lets say im running ofw 2.2 SEA edition? Do i follow the same procedure as if to flash RC1... do i also need to flash gapps similarly.
--> I'd say install RC1 and gapps first, then try a nightly by just wiping cache and Dalvik - no need to install gapps again since they're on your phone now. If you install a BOOT version and want to go back to an earlier CM7 nightly, then you might want to start from scratch, reflash froyo and install RC1 + gapps again.
Secondly, are the links on quarxs' CM7 for defy thread up-to-date? or are there newer versions of gapps and nightlies floating around somewhere
--> mostly up to date, but I don't worry about gapps too much as I believe that the Market gets updated automatically anyway (but I might be wrong about that). On the OP, the link to the gapps should show you up to date versions; but read the comments on there - very important.
Third, i have noticed that there is an issue with network and wi-fi when i flash cm7 RC1 over the nordic sbf. when i go back to official 2.2 SEA there is no hassle at all. Since i live in india i was wondering if that was the issue. I can easily take care of the network problem using "baseband switcher for defy" but it still doesnt help the wi-fi problem. My question is.. will using the new BOOTSEA nightly solve this problem. I am assuming from the name is boot"SEA" im assuming its built southeastasia specific.
---> same here my wifi DL speed was really bad for the last month or so on CM7; only after BOOT179-4 install, my wifi speed somewhat got back to normal.
Fourth, ive used CM7 RC1 for a while and apart from the wifi issue i got problems with camera and video... it absolutely doesnt work, wether it be in potrait or landscape or whatever setting... the app just force closes. Any fixes for that.. ive got green lens.
---> My camera and video worked on RC1 (and earlier) but video recording had some chopiness at times. Around July 11th nightly, Quarx released a camera fix (in that nightly) that solved the problem for me. But then days later, on newer nightly builds, I got the FC problem on video camera (same as you but red lens here). Then with BOOT179-4, camera was fine again and so the wifi speed; so all good for me.
--------> I really don't know what's going on with the video camera: many poeple have problems and many have it working on every nightly builds. It has been a problem from day one for Quarx on CM7-jordan... You have to try and see which build works for you I guess. And like you said, BOOT-SEA definitely looks like something you should try - many people liked it and many people say yesterday nightly is the best for them so far... so go on and have fun with testing
---> Before you do more testing though, you can always do a backup from the custom recovery so it will be easy for you to restore your current phone state -if nothing improves. I do this all the time: stock recovery factory reset, nordic flashing, RC1 install then restore my (BOOT179-4 now) backup.
Please help!!! and i hope other similar questions can be added by members here so as to make this thread an FAQ for distressed users like me.
---> I did try to help - I hope I did! If so, you can use that "Thanks" button - hehe!
---> Not sure that a thread entitled "nightly doubts" will become a very popular
FAQ thread though
Thanks
Click to expand...
Click to collapse
........................
[] AL [] said:
........................
Click to expand...
Click to collapse
thanks for all the help
There is a FAQ for flashing cm7 go and read it There is no need for threats like This
Send from my brain using Tapatalk
dumrul said:
There is a FAQ for flashing cm7 go and read it There is no need for threats like This
Send from my brain using Tapatalk
Click to expand...
Click to collapse
i went thru the whole FAQ but my doubts are regarding the nightlies which it doesnt address hence the thread.
thx for the concern though.
downloaded the BOOTSEA, but there is another file "cm7-110726-0018-BOOTSEA-Jordan.zip.md5sum" mentioned below it. ( there are similar md5sum files for all nightlies...) are they essential ? and how do i use them.
wanted to clarify before proceeding.
deathw15h said:
downloaded the BOOTSEA, but there is another file "cm7-110726-0018-BOOTSEA-Jordan.zip.md5sum" mentioned below it. ( there are similar md5sum files for all nightlies...) are they essential ? and how do i use them.
wanted to clarify before proceeding.
Click to expand...
Click to collapse
Md5 files are to verify your download is not corrupted one. Which you can compare the md5 after downloading the zip file and regenerating the md5 of downloaded file and check against the one in the server.
Sent from my MB525 using XDA App
deathw15h said:
thanks for all the help
Click to expand...
Click to collapse
No problem.
Go read here on the official CM7-jordan thread: http://forum.xda-developers.com/showthread.php?t=1033654&page=943
And from post 9429 particularily; pretty much goes in the same direction I was pointing at regarding the wifi and video camera...
How's the BOOTSEA doing for you?
The nightly ones is just the output that the ones who are working on the rom ups to us. Normally have all that part on topic that say "next version:..."
If you wanna try the nightly one, use as the *.zip that you download when got the "rc1 v2" for exemple. So wipe the phone, choose install from a zip of the sdcard and choose the *.zip, been it the rc1 or the nightly build.
The md5sum file is the one that contains the 5sum from the file. Its nornaly given when you have to download a big file and have fear to corrupt the file. If you use linux, go on terminal and type "5sum file" when file is the name of any file that you have. It will give you a big number. This is the 5sum. The *.md5sum have the 5sum of the respective *.zip nightly rom.
Sent from my MB525 using XDA App
how is the battery life with the nightly builds?
what android version is the 27/7 nightly build using? is it 2.3.5?
yup..its 2.3.5
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!
Hey everyone, this might be a total noob question, but I'm relatively new to the whole custom rom thing, so bear with me.
I've been recently messing around with many roms just to see what I've liked and disliked. So far my favorite has been Paranoid Android. Today I flashed the beta of the 4.4.x release and have been very pleased with it. The only issue is that the OTA update apk doesn't seem to be anywhere. I've re-flashed the rom, but that hasn't helped. Any advice?
AnTiDoWn3r said:
Hey everyone, this might be a total noob question, but I'm relatively new to the whole custom rom thing, so bear with me.
I've been recently messing around with many roms just to see what I've liked and disliked. So far my favorite has been Paranoid Android. Today I flashed the beta of the 4.4.x release and have been very pleased with it. The only issue is that the OTA update apk doesn't seem to be anywhere. I've re-flashed the rom, but that hasn't helped. Any advice?
Click to expand...
Click to collapse
Device?
Verizion GS3.
Sent from my SCH-I535.
AnTiDoWn3r said:
Verizion GS3.
Sent from my SCH-I535.
Click to expand...
Click to collapse
I'm not sure if non-nexus device maintainers build with PA OTA by default...they can include it but they would have to make some changes and upload their files to Goo.im
You'd have to contact your maintainer to see if it's included or not.
Ah that makes a lot of sense. The ROM turned out to be pretty unstable all around (at least for me) so I'm now running a CM 11 nightly. Once a stable release is made for PA, I'll flash that and if the app isn't included, I'll ask. Thank you for your time and help.
Sent from my SCH-I535 using xda app-developers app
The app won't do any good unless the maintainer puts their builds on goo and modifies the ota app to point to it. The standard ota app only works for the devices the team has listed on their site
Sent from my Nexus 5
I extracted the latest ParanoidOTA.apk from PA 4 beta 3. Just install it like any other apk and grant it SU permissions. Take it.
cezarvrabie said:
I extracted the latest ParanoidOTA.apk from PA 4 beta 3. Just install it like any other apk and grant it SU permissions. Take it.
Click to expand...
Click to collapse
There is no point in this unless your device is hosted on the official servers or the app is modified to look at some other server which hosts your device builds.
The only thing installing this would provide is updates for GApps
Q&A for [ROM] [Alpha] Unoffcial CM12 for d2tmo
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] [Alpha] Unoffcial CM12 for d2tmo. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
CM12 for D2tmo
i installed CM12 but it does not detect my simcard PLZ help
Cant wait for new Lollipop roms!!!
Do you know if any time soon there will be a fix for mobile data?
thanks for effort
menace211 said:
Cant wait for new Lollipop roms!!!
Click to expand...
Click to collapse
Yeah, if they turn out like KitKat Roms I'm heading back to touchwiz jellybean, stock.
Liquidsmooth lollipop for S3
Hi,
Here are some builds for the S3, including the d2tmo. I've loaded the but had to go back to backup , there is a bug (black screen) with lollipop that i could not stay with it.
Sorry .. they did not allow me to put in the message an outside link to the downloads
Adam
fully functional work around to get lollipop on s3 d2tmo t999l
after doing a lot of research i have sucsesfully installed lollipop onto my s3 and got the camera to work with the camera for android app from the play store. the data also works the build i installed is the 12-20141125-unofficial-d2att after changing the script file to include d2tmo instead of the d2att. works great no real bugs except the time stamp on hangout mesages which is fixed by setting the time on the phone to network but turning of the reginal time set. thought this would be nice to share.
ps: stock camera and google camera still do not work but everything else does so this can be used as a daily driver links below to camera and build:
camera: https://play.google.com/store/apps/details?id=com.photo.android.camera&hl=en
build: http://forum.xda-developers.com/galaxy-s3-att/orig-development/cyanogenmod-12-t2944071
Added screen shots of apps used speed test and the edit that needs to be made to script file to make installable
lollipop for d2tmo install instructions
WHAT YOU NEED
the build location:
12-20141125-unofficial-d2att link: http://forum.xda-developers.com/galaxy-s3-att/orig-development/cyanogenmod-12-t2944071
in the same link is superSU
also will need gapps 5.0 lollipop
"camera for android" ( stock camera and google camera DOES NOT work)
link: https://play.google.com/store/apps/details?id=com.photo.android.camera&hl=en
total commander
instructions to exit the updater-script file to make the build installable on your d2tmo
1. open the file in total commander
2. META-INF> COM>GOOGLE>ANDROID
3. open and edit the updater-script by long pressing the file choosing unpack+edit
4. change d2att to d2tmo in the first line P.s. theres two words change both
5. go back and the editing is done now just wipe everything and flash just like any other rom the boot up takes about 8 to 9mins so dont worry about it being stuck in a loop, it isn't
do not forget to download superSU from the same link as the build and have gapps 5.0 when you flash
flash in this order: rom, gapps, superSU
important things that do work :
4g YES
bluetooth with android wear YES
gps YES
camera for android YES( stock camera NO google camera NO)
wifi YES
flash light YES
time needs to be adjusted(settings > date & time > check atumatic date & time (use network-provided time) uncheck automatic time zone, select time zone to finish time set)
sound YES
dsp YES
security YES unlocks only with power button (home button will not unlock your phone takes some getting use to)
keyboard YES
what was used to set up my phone: philz recovery, rescripted 12-20141125-UNOFFICIAL-d2att, superSU beta app,gapps 5.0, latest modem from xda for d2tmo t999L
leonid002 said:
after doing a lot of research i have sucsesfully installed lollipop onto my s3 and got the camera to work with the camera for android app from the play store. the data also works the build i installed is the 12-20141125-unofficial-d2att after changing the script file to include d2tmo instead of the d2att. works great no real bugs except the time stamp on hangout mesages which is fixed by setting the time on the phone to network but turning of the reginal time set. thought this would be nice to share.
ps: stock camera and google camera still do not work but everything else does so this can be used as a daily driver links below to camera and build:
camera: https://play.google.com/store/apps/details?id=com.photo.android.camera&hl=en
build: http://forum.xda-developers.com/galaxy-s3-att/orig-development/cyanogenmod-12-t2944071
Click to expand...
Click to collapse
Is it possible that you could upload d2att rom with changed script?
leonid002 said:
after doing a lot of research i have sucsesfully installed lollipop onto my s3 and got the camera to work with the camera for android app from the play store. the data also works the build i installed is the 12-20141125-unofficial-d2att after changing the script file to include d2tmo instead of the d2att. works great no real bugs except the time stamp on hangout mesages which is fixed by setting the time on the phone to network but turning of the reginal time set. thought this would be nice to share.
ps: stock camera and google camera still do not work but everything else does so this can be used as a daily driver links below to camera and build:
camera: https://play.google.com/store/apps/details?id=com.photo.android.camera&hl=en
build: http://forum.xda-developers.com/galaxy-s3-att/orig-development/cyanogenmod-12-t2944071
Added screen shots of apps used speed test and the edit that needs to be made to script file to make installable
Click to expand...
Click to collapse
Wiwee said:
Is it possible that you could upload d2att rom with changed script?
Click to expand...
Click to collapse
it looks like the file is too big to upload, here are the steps to edit the file manually, if you follow these you wont screw up
1. open the file in total comander
2. META-INF> COM>GOOGLE>ANDROID
3. open and edit the updater-script by long pressing the file choosing unpack+edit
4. change d2att to d2tmo in the first line P.s. theres two words change both
5. go back and the editing is done now just wipe everything and flash just like any other rom the boot up takes about 8 to 9mins so dont worry about it being stuck in a loop, it isnt
do not forget to download superSU from the same link as the build and have gapps 5.0 when you flash
flash in this order: rom, gapps, superSU
Wiwee said:
Is it possible that you could upload d2att rom with changed script?
Click to expand...
Click to collapse
files not uploading still sorry
leonid002 said:
files not uploading still sorry
Click to expand...
Click to collapse
I have determined I am an idiot. I downloaded the rom and tried to change the stuff you have listed and no love. If you have a chance to get it uploaded ( mega.co.nz with a public link maybe.....) please share would love to give it a shot.
PHP:
alarmdude9 said:
I have determined I am an idiot. I downloaded the rom and tried to change the stuff you have listed and no love. If you have a chance to get it uploaded ( mega.co.nz with a public link maybe.....) please share would love to give it a shot.
Click to expand...
Click to collapse
I'll get right on it thanks for the response,did it not let you flash it and say it's not compatible?
leonid002 said:
PHP:
I'll get right on it thanks for the response
Click to expand...
Click to collapse
No thank you for trying to help idiots like me. that is correct says not compatable
alarmdude9 said:
No thank you for trying to help idiots like me.
Click to expand...
Click to collapse
I got it to work at 3 in the morning so if I forgot something I'm sorry in advanced it's halfway uploaded right now with the changes in the script. Hope this helps. I also flashed with Philz recovery if that makes any difference
leonid002 said:
I got it to work at 3 in the morning so if I forgot something I'm sorry in advanced it's halfway uploaded right now with the changes in the script. Hope this helps. I also flashed with Philz recovery if that makes any difference
Click to expand...
Click to collapse
No apologies needed at all. Don't know if one version of the recovery matters or not. I know it did way back in the days of the CLIQ but I'm hoping not this far along
leonid002 said:
after doing a lot of research i have sucsesfully installed lollipop onto my s3 and got the camera to work with the camera for android app from the play store. the data also works the build i installed is the 12-20141125-unofficial-d2att after changing the script file to include d2tmo instead of the d2att. works great no real bugs except the time stamp on hangout mesages which is fixed by setting the time on the phone to network but turning of the reginal time set. thought this would be nice to share.
ps: stock camera and google camera still do not work but everything else does so this can be used as a daily driver links below to camera and build:
camera: https://play.google.com/store/apps/details?id=com.photo.android.camera&hl=en
build: http://forum.xda-developers.com/galaxy-s3-att/orig-development/cyanogenmod-12-t2944071
Added screen shots of apps used speed test and the edit that needs to be made to script file to make installable
lollipop for d2tmo install instructions
WHAT YOU NEED
the build location:
12-20141125-unofficial-d2att link: http://forum.xda-developers.com/galaxy-s3-att/orig-development/cyanogenmod-12-t2944071
in the same link is superSU
also will need gapps 5.0 lollipop
"camera for android" ( stock camera and google camera DOES NOT work)
link: https://play.google.com/store/apps/details?id=com.photo.android.camera&hl=en
total commander
instructions to exit the updater-script file to make the build installable on your d2tmo
1. open the file in total commander
2. META-INF> COM>GOOGLE>ANDROID
3. open and edit the updater-script by long pressing the file choosing unpack+edit
4. change d2att to d2tmo in the first line P.s. theres two words change both
5. go back and the editing is done now just wipe everything and flash just like any other rom the boot up takes about 8 to 9mins so dont worry about it being stuck in a loop, it isn't
do not forget to download superSU from the same link as the build and have gapps 5.0 when you flash
flash in this order: rom, gapps, superSU
Click to expand...
Click to collapse
alarmdude9 said:
No apologies needed at all. Don't know if one version of the recovery matters or not. I know it did way back in the days of the CLIQ but I'm hoping not this far along
Click to expand...
Click to collapse
https://mega.co.nz/#!8wdyVICK!ORYZsTOTdnXvgpEYVA6mJr9JbQJ0MCz_wFh8sA_xPNk
Try this I checked the file to make sure it was edited
leonid002 said:
https://mega.co.nz/#!8wdyVICK!ORYZsTOTdnXvgpEYVA6mJr9JbQJ0MCz_wFh8sA_xPNk
Try this I checked the file to make sure it was edited
Click to expand...
Click to collapse
awesome bringing it down now.
alarmdude9 said:
awesome bringing it down now.
Click to expand...
Click to collapse
so when you flash there should be a small error but it will continue flashing. let me know it goes
leonid002 said:
so when you flash there should be a small error but it will continue flashing. let me know it goes
Click to expand...
Click to collapse
Will do. Besides the camera everything else is working? Can't test it a lot tonight, just got called into work, but want to get it set up and a nandroid then play with it after work tomorrow.
alarmdude9 said:
Will do. Besides the camera everything else is working? Can't test it a lot tonight, just got called into work, but want to get it set up and a nandroid then play with it after work tomorrow.
Click to expand...
Click to collapse
when I first flashed the time for some reason was off but its pretty easy to fix, as for the camera install camera for android in the play store so you have some kind of working camera if that matters to you . everything else works perfectly a lot faster than the carbon ROM I had