i was wondering if ay developer working on a Rom with the new cyanogen vertion 7.1?
already out, try typhoon rom.
android 2.3.7?yes but not cyanogen 7.1!
v3.7.0: Updated to cm_bravo v7.1.0 base. Updated to Market v3.2.0.
Click to expand...
Click to collapse
This is from Typhoon changelog...just read!
icke said:
This is from Typhoon changelog...just read!
Click to expand...
Click to collapse
amen Brother
but most are to lazy to read ..they want others to do it for them
im not talking abouth android market!!domn asses!!!CYANEGEN 7.1 !!IDIOTS!!
arsc1 said:
im not talking abouth android market!!domn asses!!!CYANEGEN 7.1 !!IDIOTS!!
Click to expand...
Click to collapse
WTF!!!???
v3.7.0: Updated to cm_bravo v7.1.0 base. Updated to Market v3.2.0.
Click to expand...
Click to collapse
I HAVE THAT MARKET VERTION!!im talking abouth this http://www.cyanogenmod.com/blog/cyanogenmod-7-1-released....wich has nothing 2 do with the android base!!!
cyanogenmod 7 its been from android 2.2 all the way 2 android 2.3.7 has the vertion change?cyanogen before a week ago?no!!but they just realese it!!its now cyanogen 7.1!!it may not have a lots of diferese sense i havent have the chanse 2 check on the changelog, n even if i did i rather taste it my self!!!
First...your link doesn't work!
Second...changelog says that his rom is updated to CyanogenMod 7.1.0 (cm_bravo v7.1.0 base) AND market v3.2.0.
Please do not flash anything to your phone to preserve us from other stupid post of you!
where u at smart ass?
can u post the link to that changelog?i will probive u with pics.i dont now why the link doesnt work but u can always go 2 cyanagenmod.com n check t ur self!!!
v3.7.1: Updated to cm_bravo 227 base. Updated to Market v3.2.0 (redundant, but I know somebody is going to ask if the new market is in v3.7.1).
v3.7.0: Updated to cm_bravo v7.1.0 base. Updated to Market v3.2.0.
v3.6.9: Updated to cm_bravo_220 base. Updated 98cpu_voltage script to include 128mhz.
v3.6.8: Updated to cm_bravo_216 base. Updated to tytung r12.4. Now Android base 2.3.7.
v3.6.7: Updated to cm_bravo_213 base. Updated to tytung r12.3. Updated to drizztje libaudio.so v5.
v3.6.6: Updated to cm_bravo_212 base. Updated to Market v3.1.5.
v3.6.5: Updated to cm_bravo_206 base. Fixed boot loop thanks to securecrt.
v3.6.4: Updated GAPPS to 08/28. Updated to Tytung r12 kernel.
v3.6.3: Updated to cm_bravo_183 base. Updated to Market 3.1.3.
v3.6.2: Updated to cm_bravo_182 base. Changed default mic_levels to 400/600. Updated libaudio.so to compatible libaudio.so for "mic fix".
v3.6.1: Updated to cm_bravo_181 base. Updated GAPPS. Changed kernel to tytung r12 beta 1 kernel. Removed htcleo.acdb. Included tytung's GPS v2.1 NMEA.
v3.6.0: Updated to cm_bravo_172 base. Updated media_profiles.xml. Included tytung r11 final. Updated initrd to tytung's initrd with modifications for CPU performance settings. Fixed cLK data issue. tytung's initrd seems to increase boot speed for me, let me know your results with this.
v3.5.9: Updated to cm_bravo_171 base. Updated gps.conf. Included tytung r11 beta 2 kernel. Updated to latest wifi firmware.
v3.5.8: Updated to cm_bravo_166 base. Added 5th mirror thanks to Rofela!
v3.5.7: Updated to cm_bravo_159 base. Included tytung's GPS lib v2.0 NMEA.
v3.5.6: Updated to cm_bravo_157 base. Included jan-willem3's ril tweaks via build.prop.
v3.5.5: Updated to cm_bravo_151 base.
v3.5.4: Updated to cm_bravo_147 base. Updated to tytung's GPS lib v1.9 NMEA.
v3.5.3. Updated to cm_bravo_146 base. Removed tablet tweaks yet again because of bootloop issues.
v3.5.2: Updated to cm_bravo_145 base (Android 2.3.5)! Updated Google Talk to AV chat
just in case what does bravo_145 base (android 2.3.5)means 2 u?
btw 3.7.1 is out domn ass...n its not cyanogenmod 7.1!!!great rom i cant say anything bad abouth it!!
here it is!!
btw..theres something wrong with the date on what ever ur running!!
its 2011 bro not 2010!!
If you've flashed typhoons latest version go to cyanogenmod settings and read changelog!
icke said:
First...your link doesn't work!
Second...changelog says that his rom is updated to CyanogenMod 7.1.0 (cm_bravo v7.1.0 base) AND market v3.2.0.
Please do not flash anything to your phone to preserve us from other stupid post of you!
Click to expand...
Click to collapse
AMEN 7.1 is 7.1.0 but i guess he is too dumb to realize the difference.
---------- Post added at 01:09 PM ---------- Previous post was at 01:06 PM ----------
arsc1 said:
here it is!!
Click to expand...
Click to collapse
And to answer your question concerning the thumb nail you posted that is CM 8 HoneyComb for tablets which the source was not released in accordance with google since they didnt release the source due to the incompatibity with Mobile phones.
Ok guy i sure have to apologise 2 all of u!!not sure why but on my phone,the changelog does says cm7.1 but not on my pc!!not sure whats up with my pc!!sorry again for waisting ur time!!
Related
Hi guys,
Just have a quick question- wondering if anyone is running into the same problem. I just installed Cyanogen 7 rc1, and it is force closing between the load screen and the welcome screen (for the first time).
I'm not sure if this is the correct place to post this, but any help would be great.
Thanks
Based off what I've read in the development threads, the RC does't seem to be too much of an RC. I'd restore and wait.
you have to flash RC1 over a nightly build.
Nowak4G said:
you have to flash RC1 over a nightly build.
Click to expand...
Click to collapse
Yep! Its was a known issue with the first build of RC1. Something was botched. I recommend you either flash RC1 over nightly build #38, or you just flash nightly build #39 (which already includes fixes that were left out of RC1).
Cheers!
Hi
Found this tweet
LoxDev ⓁⓄⓧ
Here is an early build of CM7 based on android 2.3.5 (just merged) for HTC Hero: ubuntuone.com/p/16QE/
Just seems to download the zip file anyone tested yet?
tfn said:
Hi
Found this tweet
LoxDev ⓁⓄⓧ
Here is an early build of CM7 based on android 2.3.5 (just merged) for HTC Hero: ubuntuone.com/p/16QE/
Just seems to download the zip file anyone tested yet?
Click to expand...
Click to collapse
downloaded and installed. works well. Thank you for the information and the download link.
Elelinux 7.1 also on 2.3.5 now!
jonathanljs said:
Elelinux 7.1 also on 2.3.5 now!
Click to expand...
Click to collapse
yeah I believe He did mention somewhere that He was waiting for it to release so he could release His updated phone.
THis is Raw CM7 obviously not tweaked like Elelinux's
CM7 nightly build also 2.3.5 starting on built 137
I am currently trying to get full battery of my defy+ to work under MIUI. Being CM based i assumed it would work with the CM battery patch. It doesn't however. I know which files need to be replaced, would it be a good idea to just grab the files from the CM9 defy+ build and replace them?
For those that are interested doesn't work = battery only showing full with question mark icon.
Having same problem and seems there is total silence in all forums concerning this issue. If you manage to solve it please let me know !
Hey, guys I'm using MIUI Pikachu Edition by einsteinno1 and it has full DEFY+ support (battery charges up to 100%)
It's overall an awesome ROM, after trying CM7.2, latest WIUI and MS2G v3, Pikachu is the best one for me.
My DEFY+ was on 2.3.5, so I flashed it down to Froyo before flashing Pikachu
Cheers!
I have the same Defy 2.3.5 but I don't know how to install a diffrent ROM/interface ...
iceguy0585 said:
I have the same Defy 2.3.5 but I don't know how to install a diffrent ROM/interface ...
Click to expand...
Click to collapse
Search this wonderful Forum - There are many threads telling you how to install a new ROM / interface
Well then I will definitely give Miui Pikachu edition a try As far as I understand Froyo version is the best to use to flash Miui right ?
Hi all,
About the Defy+ battery. This battery is only support by GB kernel. So nevermind the patch you applied, you'll always have a bad result. This patch works on CM 7.2 Defy + because this rom doesn't incluse the kernel and use the GB one of your phone.
So the only solution is what nisky+ said... Flash before the 2.3.6 SBF on the dev forum who allow you to flash a Froyo kernel first...
http://forum.xda-developers.com/forumdisplay.php?f=855
DeanSebastian said:
Well then I will definitely give Miui Pikachu edition a try As far as I understand Froyo version is the best to use to flash Miui right ?
Click to expand...
Click to collapse
Froyo is the safest way, yes, and it will work without problems. It should work when flashed over 2.3.4, too, but I haven't tried that, myself.
@mdt24 Then how come I don't have battery problems now when Froyo's kernel is used
P.S. It's niksy, not nisky
Hi niksy ;-)
It's because I think this rom doesn't incluse kernel, so you always run a 2.3.4 GB Kernel...
quote from Miui Pikachu edition : IMPORANT!!! this Rom works only on Defy or Defy+ with Froyo Kernel or Gingerbread 2.3.4/5 Kernel. All with 2.3.6 Kernel have to downgrade to Froyo Kernel, because the new Motorola Kernel won't work with MIUI. Just use this Tutorial on XDA Developers
But I could be wrong in my deduction, so Please, can you give us the number of the kernel you have with this pikachu rom ?...
What I did before was downgrade from 2.3.6 using the sbf the dev provided that allows you to downgrade to froyo then I flashed Miui official rom and still had problems with battery. Kernel version currently is : 2.6.32.9gb08c3c8 if that makes any sense to you cause I personally just don't know anything bout kernels... I just downloaded pikachu Miui and will give a try soon and share the results with you
Hey all, thanks for the replies. I already know about the limitations of the patch and which versions the driver works with. That is why i flashed the 2.3.4 kernel before using MIUI and therefore the defy + patch. I just don't get why it doesn't work, do i need to use a defy+ kernel?
I will grab the files used in the working MIUI Defy+ rom and package them as a flashable .zip for other users.
mdt24 said:
Hi niksy ;-)
It's because I think this rom doesn't incluse kernel, so you always run a 2.3.4 GB Kernel...
quote from Miui Pikachu edition : IMPORANT!!! this Rom works only on Defy or Defy+ with Froyo Kernel or Gingerbread 2.3.4/5 Kernel. All with 2.3.6 Kernel have to downgrade to Froyo Kernel, because the new Motorola Kernel won't work with MIUI. Just use this Tutorial on XDA Developers
But I could be wrong in my deduction, so Please, can you give us the number of the kernel you have with this pikachu rom ?...
Click to expand...
Click to collapse
Mate, you are right about the ROM, it doesn't include any kernel, but I said that I flashed that special version 6 Froyo (that's a full sbf) before flashing Pikachu!
DeanSebastian said:
What I did before was downgrade from 2.3.6 using the sbf the dev provided that allows you to downgrade to froyo then I flashed Miui official rom and still had problems with battery. Kernel version currently is : 2.6.32.9gb08c3c8 if that makes any sense to you cause I personally just don't know anything bout kernels... I just downloaded pikachu Miui and will give a try soon and share the results with you
Click to expand...
Click to collapse
The kernel you mentionned is a froyo kernel...
As you all I try to understand why it's possible that the defy+'s battery works or not with the patch. It's sure it works with a 2.3.6 GB kernel and a patch for the system (battd, lib) used by the rom if the new rom doesn't include a kernel.
It seems that if the rom include a froyo kernel the patch doesn't work...
So... may be a way to understand
---------- Post added at 03:56 PM ---------- Previous post was at 03:43 PM ----------
niksy+ said:
Mate, you are right about the ROM, it doesn't include any kernel, but I said that I flashed that special version 6 Froyo (that's a full sbf) before flashing Pikachu!
Click to expand...
Click to collapse
Yes but I'm pretty sure than this special version has a GB kernel. It's just the bootloader who accept all kind of kernel...
Check your Kernel number, I think you must have something like this 2.6.32.9-gbdd614e...
Ok after some testing I can tell you that the battery charged to 100% only the first time I booted.Since then it has only charged till 90%. I also did calibrate the battery the first time I flashed the Rom but no results
mdt24 said:
Yes but I'm pretty sure than this special version has a GB kernel. It's just the bootloader who accept all kind of kernel...
Check your Kernel number, I think you must have something like this 2.6.32.9-gbdd614e...
Click to expand...
Click to collapse
It's 2.6.32.9-gb08c3c8 - the one you said it's Froyo Just checked!
And for the battery... First time it charged to 100%, this time it stuck at 90%. Quite weird... But, that is with Froyo kernel, as we've come to conclude.
But, on the other hand, my bro's got a DEFY+, too, with CM7.2 on it and with Gingerbread kernel (27th January DEFY+ nightly) and the battery goes to 100% every time. I will test Pikachu on a Gingerbread kernel, cause I can't really live with this bug :-/ Will let you know how it went, now I'm off to find a 2.3.4 sbf!
I had the same idea and have already downloaded a full 2.3.4 GB sbf to check just that !
i wish a 2.3.4 GB kernel can fix that, although I think the only kernel able to fix this is 2.3.5 and above
Hi.. I m new to android... I just want to ask how can I add music contol to notification toogle bar like that in cm mod..... I m using pikachu edition on my defy plus and its really great ... I haven't faced any problem till now.. thank u dev for such a beautiful rom...
hey buddy....i was runing on 2.3.5 than i tried a rom called [Retail British] here ; http://sbf.droid-developers.org/umts_jordanplus/list.php
then
i upgreade it by automatic update so it became 2.3.6
then i again flash it through [Retail British] after that my device not able to power on just with white led light but i'm able to flash the device ..so can u suggest me a suitable rom for my device [Motorola defy+] ??
HELP pls
Thanks !!
mdt24 said:
Hi niksy
It's because I think this rom doesn't incluse kernel, so you always run a 2.3.4 GB Kernel...
quote from Miui Pikachu edition : IMPORANT!!! this Rom works only on Defy or Defy+ with Froyo Kernel or Gingerbread 2.3.4/5 Kernel. All with 2.3.6 Kernel have to downgrade to Froyo Kernel, because the new Motorola Kernel won't work with MIUI. Just use this Tutorial on XDA Developers
But I could be wrong in my deduction, so Please, can you give us the number of the kernel you have with this pikachu rom ?...
Click to expand...
Click to collapse
Thanks for ur Info.. tried to install Pikachu edition on my Defy+ 2.3.6 nd failed. But now using CM10..
Along time ago I used a MIUI rom, and it was awesome. Rock solid stable and easy to use. I think it was MIUI.us 1.11.18, or at least that is the rom I found in my U8800 folder.
I want to go back to MIUI again, but stability is of the utmost importance. I tried Miui V3 2.4.20 [2.6.35 & 2.6.32] [U8800], the .35 version, over in developer forum. I've had a lot of task bar crashes, and a couple of other weird things happen. I'm downloading the .32 version now to try, and I also went to MIUI.us and downloaded the latest version there (1.12.9).
I see there are a lot MIUI roms in the forums. Does anyone know of any other ones that near perfection in their stability. I don't need the latest and greatest updates, I need stability. I use my phone for work related stuff a lot, and a crash can cause some problems.
Thanks for the help.
EDIT: Just realized this isn't the Q&A section. If a mod wants to move it, please do.
Very strange things about notify bar you say. I've using sbasil's miui v3 and it's very stable for me. No reboots, no crashes, everything working. Maybe you just didn't updated to 35kernel (installed official 2.3) and that's why this happens. If did, try to do 3 wipes, flash rom, 3 wipes and install it again.
yeah, I thought it pretty strange too. I'm on B136, which is 2.3, so I'll try wiping/flashing it again.
typci said:
yeah, I thought it pretty strange too. I'm on B136, which is 2.3, so I'll try wiping/flashing it again.
Click to expand...
Click to collapse
fyi b136 is not 2.3. you have to use a 2.6.32.9 kernel based rom.
Moved To Q&A
Please post questions in the Q&A section
ezet said:
fyi b136 is not 2.3. you have to use a 2.6.32.9 kernel based rom.
Click to expand...
Click to collapse
Typo, sorry. I'm on B526. not sure why I typed b136.
Im giving away my Defy to my brother, who is not good at ROM hacking thus I want to install him a ROM that is as stable as possible. I've installed one of Quarx's 4.3 ROM to it (2 months ago), but after a few days it refused to boot (guess it was the data corruption bug). So I wiped everything, now it has stock 2.2 ROM.
Any recommendations on a newer ROM, that has as few issues as possible?
syddd said:
Im giving away my Defy to my brother, who is not good at ROM hacking thus I want to install him a ROM that is as stable as possible. I've installed one of Quarx's 4.3 ROM to it (2 months ago), but after a few days it refused to boot (guess it was the data corruption bug). So I wiped everything, now it has stock 2.2 ROM.
Any recommendations on a newer ROM, that has as few issues as possible?
Click to expand...
Click to collapse
I suggest trying MS2Ginger or CM7.
hotdog125 said:
I suggest trying MS2Ginger or CM7.
Click to expand...
Click to collapse
Why not cm11? i think it's the only one stable since cm9, and almost everything works.
Android_74 said:
Why not cm11? i think it's the only one stable since cm9, and almost everything works.
Click to expand...
Click to collapse
CM11 is not yet ready fully and it's not fully stable.
SlimBean 4.3.1
GB ROMs: MS2Ginger or CM7, already mentioned.
JB ROM: STABLE SlimBean 4.3.1 (final) build2.2.
Absroid said:
GB ROMs: MS2Ginger or CM7, already mentioned.
JB ROM: STABLE SlimBean 4.3.1 (final) build2.2.
Click to expand...
Click to collapse
Do not install Slimbean for someone who doesn't flash his phone. Slimbean uses a customized version of the playstore, which means that the playstore won't work if google updates it.
There's nothing like CM7 for stability. I thought 4.1.2 was robust but it's starting to behave strangely after a couple of weeks of use.
Nemado said:
Slimbean uses a customized version of the playstore, which means that the playstore won't work if google updates it.
Click to expand...
Click to collapse
Good point, but correct and incorrect.
Google Play Store 4.4.22 still working fine. It shouldn't be a problem to replace or manually update it to the latest 4.5.10.
Just download com.android.vending-4.5.10.apk and install the update.
Absroid said:
GB ROMs: MS2Ginger or CM7, already mentioned.
JB ROM: STABLE SlimBean 4.3.1 (final) build2.2.
Click to expand...
Click to collapse
Is Slimybean based on Quarx's 4.3 ROM? Cause that has several bugs - one of them is, that a partition gets corrupted rendering the phone unable to boot.
Is there a buglist for Slimbean 4.3.1?
syddd said:
Is Slimybean based on Quarx's 4.3 ROM? Cause that has several bugs - one of them is, that a partition gets corrupted rendering the phone unable to boot.
Click to expand...
Click to collapse
Check the link for sources. If you mean Master Quarx's kernel, then yes. But if you want to use another one in JB, your choises are very limited..
This build is too an unofficial port, so only Slim-parts can be called stable, to be more accurate.
Is there a buglist for Slimbean 4.3.1?
Click to expand...
Click to collapse
Changelog stable build 2
If you have time, you should test these suggested GB and JB builds.
Absroid said:
Good point, but correct and incorrect.
Google Play Store 4.4.22 still working fine. It shouldn't be a problem to replace or manually update it to the latest 4.5.10.
Just download com.android.vending-4.5.10.apk and install the update.
Click to expand...
Click to collapse
Bottom line is, the playstore has a convenient auto update feature which Slimroms disables. His brother would have to go to slimroms.net to download further playstore updates. Besides, Slimroms.net could stop supporting the ROM at any time and he would be "stuck" with an outdated playstore. It would work but he would have to pass on any new features or fixes. That's something to consider.
Second thing to consider, every ROM is based on Quarx ROMs. This means that every custom ROM is likely to have Quarx's bugs AND the bugs of the cutomized ROM.
4.3 performs well but it is not 100% functional. I've read they had troubles with bluetooth and I found that some options don't work (adding APN for instance).
4.1.2 is mostly functional but it's not 100% stable. I had several reboots on a fresh install.
Epsylon's latest 4.0.4 is still a good pick. I just installed it and it performs better than JB on Kingdom Rush (it stuttered, crashed and reboot on JB and worked flawlessly on ICS!)
CM7.2 is awesome in every aspects BUT it doesn't have HWA, which means he won't be able to use some of the latest app. Of course, it doesn't mean much since the Defy is not very powerful. But there are some good HWA only apps that still work on the Defy.
I'll say Xperia D3.4 for Defy/Defy+ based on Quarx's CM10 (20130117). It's fast, clutter free, and stable. A very good music player, stable camera, and lots of other addons. Battery life is also not bad.
Because AndroidOS is a chopped/adapted Linux for every hardware (it doesn't contain large drivers library for space economy) is per se a not very stable OS. Even the original firmware isn't "very" stable so the various kind of mods is unstable either. Every mod ROMs is made to cover some aspects and for this cause you must pick the most appropriate for your needs. For beginner try to accomodate with original firmware first, after that try a CM7.x and if you wanna adventure pick a JB or a KK mod. Enjoy.