Develop Bugs

CM7.0.2.1 not stable.....

CM7.0.2.1....... sucks battery and app. Problems after update.... ??

Crans said:
CM7.0.2.1....... sucks battery and app. Problems after update.... ??
Click to expand...
Click to collapse
naw... running smooth as ever for me. maybe something went wrong with your install

Have you tried a different kernel? Make sure your screen brightness isn't up all the way also, big battery killer.
CM7 nightly

I dont think this belongs in development. try Q/A they might be able to help you out.

I am also having issues mainly with you tube all the videos are jittery as hell and tried a different rom and issue was gone.
Sent from my ADR6300 using XDA App

The difference. between 7.0.2 and 7.0.2.1 has been like night and day .....my batt. After taking off the charger today went from 100 to 95 in less that 10 seconds and I'm not getting fc's. But my display apps try and open than dissapear giving me no access...... I am running dual boot sooooo... that may be the cause but 7.0.2 worked great when I updated to it..... just didn't know if I was the only one

If its a well known major problem with development of a rom that is supposed to be stable than yes if no than Q/A with people whom aren't even rooted....... hmmmmm hard choice,I know it was for me....... please move this post if it's not in the right section...

You could check the threads for CM7 and see if it its a "development issue"...searching works from time to time
CM7 nightly

Just don't know why 7.0.2 to 7.0.2.1 would be so drastic.... understand nightlys but not stable

Crans said:
If its a well known major problem with development of a rom that is supposed to be stable than yes if no than Q/A with people whom aren't even rooted....... hmmmmm hard choice,I know it was for me....... please move this post if it's not in the right section...
Click to expand...
Click to collapse
Opening a new thread about a ROM rather than posting in that ROM's thread, running it in a non standard configuration, AND having an attitude when someone points out a Q doesn't belong in dev? Yeah, I see no problem at all. /sarcasm

You guys are getting sarcasm and straight forward confused thanks for any input that actually pertained to my question... to others.... think before you speak or ask ... done... Please close this thread ASAP

Crans said:
The difference. between 7.0.2 and 7.0.2.1 has been like night and day .....my batt. After taking off the charger today went from 100 to 95 in less that 10 seconds and I'm not getting fc's. But my display apps try and open than dissapear giving me no access...... I am running dual boot sooooo... that may be the cause but 7.0.2 worked great when I updated to it..... just didn't know if I was the only one
Click to expand...
Click to collapse
um, the only thing they fixed from .2 to .2.1 was the camera.
To many people here post issues that aren't from a clean wipe.
No issues, move along.

Thank you for your reply..... as stated before...done

Remove this Thread
Please remove this thread. We don't need the negativity. There are too many people spending they're own time to make CM7 what it is.

morrisdan said:
Please remove this thread. We don't need the negativity. There are too many people spending they're own time to make CM7 what it is.
Click to expand...
Click to collapse
Why, so people can go on downloading a supposed "stable" release only to find out it wasn't so "stable" to begin with?
I LOVE the CM crew and all they do for the scene, but I had a very terrible experience with 7.0.0 on the DINC. First it was jittery video (which I lived with for over a week) and then all my installed apps just suddenly quit working.
masully1984 said:
Have you tried a different kernel?
Click to expand...
Click to collapse
A "stable" ROM should never require an end user to try a different kernel.
Anyway, I ended up back on OMGB and couldn't be happier. The only FC I can find is due to installed software (Astro SMB Module).

I love using CM7 ... bugs or not please save your ignorance.morrisdan

Crans said:
If its a well known major problem with development of a rom that is supposed to be stable than yes if no than Q/A with people whom aren't even rooted....... hmmmmm hard choice,I know it was for me....... please move this post if it's not in the right section...
Click to expand...
Click to collapse
Just because someone posts something in Q&A doesn't mean they aren't rooted. Your attitude sucks man. My personal opinion would be to reflash and wipe I have been running the latest stable release for as long as its been out and been updating to the latest version asap and have had zero problems other than those cause by user error. Perhaps you did something. Gotta release 9/10 problems are user generated.

skyblaster said:
Why, so people can go on downloading a supposed "stable" release only to find out it wasn't so "stable" to begin with?
I LOVE the CM crew and all they do for the scene, but I had a very terrible experience with 7.0.0 on the DINC. First it was jittery video (which I lived with for over a week) and then all my installed apps just suddenly quit working.
A "stable" ROM should never require an end user to try a different kernel.
Anyway, I ended up back on OMGB and couldn't be happier. The only FC I can find is due to installed software (Astro SMB Module).
Click to expand...
Click to collapse
Dude you should always try different kernals with roms. You must be new. It is stable I've had zero problems. As stated previously 9/10s of problems are user error and with the ignorance you are displaying I'm gonna say you did something. Just a tip when you wipe you should multiple times becayse 3.X wipes like a dirty person.

cstrife999 said:
Dude you should always try different kernals with roms. You must be new.
Click to expand...
Click to collapse
Don't let my post count fool you. I've been around since the beginning with the G1. Final, Stable, these words suggest newbie usage. Final builds should come with a final kernel. Unless you're a dev, tester, or need something specific for a certain application then you shouldn't need to kernel hack.
cstrife999 said:
As stated previously 9/10s of problems are user error and with the ignorance you are displaying I'm gonna say you did something. Just a tip when you wipe you should multiple times becayse 3.X wipes like a dirty person.
Click to expand...
Click to collapse
I understand how memory wipes work, so I don't believe the multiple wipe requirement. However, if it is an issue with ClockworkMod 3.x then I do apologize for any nay say here against CM. However, that doesn't really explain why 7.0.2 and 7.0.2.1 came out so soon after 7.0.0, and I wasn't the only one with video troubles in 7.0.0.

/deleted
10char

[ROM][GSM][JB 4.1.1] Monster AOSP [Beta][DeOdexed]

Hello everyone,
This is a pure-AOSP ROM with very little CM-style modifications. These modifications are designed to address all Galaxy Nexus users. I have modified Android only to improve the usability with minimum impact on the stock JB look. Please note that this ROM is a beta and I hadn't had a chance to test it, so you are my testers. When testers are happy, I will erase the word beta.
CREDITS
Um.. I am the only dev working on this ROM. PM me if you want to help out. Any help is very much appreciated. Find me @tommrazek
FranciscoFranco For a very nice running kernel with some GPU overclocking which a lot of people will like.
The creator of this app for a great app improving the usability of our phones.
The AOSP Project, Samsung and Google.
CHANGELOG
Version Beta:
Speed Tweaks
Notification Toggles
CM9 Torch App...
Modified Settings.apk strings by me
Franco.Kernel with GPU overclocking. (For now at 384mhz, there will be an experimental 512mhz version coming too.)
Advanced Power menu
Click to expand...
Click to collapse
DOWNLOADS
The 384mhz GPU Version with speed tweaks HERE.
SCREENSHOTS
You post screenshots, I put them here.

Bump. Posted new changelog and download links. Enjoy! :}

reserved

Why would you call it MONSTER AOSP if the ROM is close to stock with very minimal modifications?

CADude said:
Why would you call it MONSTER AOSP if the ROM is close to stock with very minimal modifications?
Click to expand...
Click to collapse
its beta and its his rom? that could be it...

you dont even know if this rom will boot or not ???
funny...

It will boot. That is for sure. There could be one or two fcs but probably not. Be quiet and flash. This wont brick your phone

I dont have problems in brick or not my phone and no thanks, i will not flash

Getting a db error from DL host.
Sent from my Galaxy Nexus using Tapatalk 2

CADude said:
Why would you call it MONSTER AOSP if the ROM is close to stock with very minimal modifications?
Click to expand...
Click to collapse
It's a work in progress. It's not a final ROM. If you don't like the ROM... then move onto the next thread, not bash the thread.
I dont have problems in brick or not my phone and no thanks, i will not flash
Click to expand...
Click to collapse
Pretty much what I said above.... if u dont like the ROM, move on, dont bash the thread.
@OP: Thanks for the ROM. Nice to see new developers on the scene, best of luck! Ignore these people who are causing negativity, looking forward to what you bring to the scene.
But generally speaking.. people need to stop going into dev's threads and bashing their ROM which is obviously a thing they do as a hobby and doesn't charge their users. Bashing someone's ROM when you haven't even tried it causes ROM developers to not make ROMs.

Bootloop: (

zephiK said:
It's a work in progress. It's not a final ROM. If you don't like the ROM... then move onto the next thread, not bash the thread.
Pretty much what I said above.... if u dont like the ROM, move on, dont bash the thread.
@OP: Thanks for the ROM. Nice to see new developers on the scene, best of luck! Ignore these people who are causing negativity, looking forward to what you bring to the scene.
But generally speaking.. people need to stop going into dev's threads and bashing their ROM which is obviously a thing they do as a hobby and doesn't charge their users. Bashing someone's ROM when you haven't even tried it causes ROM developers to not make ROMs.
Click to expand...
Click to collapse
Thank you for the kind words. You are completely right.
@JosepiOT I will look into your problem. It seems to work fine, maybe a location error? I will provide an alternative link.

Cornma said:
Bootloop: (
Click to expand...
Click to collapse
Did you wipe?

loll... i`m not bashing anything :silly:
sorry for whatever
bye and good luck with your hobby

guys please install what you want and let devs cook their rooms. It is a free world but nobody wants to know about what you install and do not install.
@tommrazek01
thanks for your rom. pls provide screenshoots...thnx again.

thank you very much. I will provide screenshots as soon as i can get to my Galaxy nexus.

Don't give in to the hate. I've done two Roms, a theme, and an app and I'm surprised at how nasty people can be over FREE software!
Anyway... I recommend you add Trackball Alert compatibility from lilHermit and AppWidgetPicker. Both are really useful and blend very well with AOSP.
Keep up the good work and keep having fun.

Thanks a lot. Can anyone give feedback please? I mean, you kind people are my testers. I will be able to test it after tomorrow at best...

[ROM][14-02-13][Flinny] Andromadus - AOSP4.2.2[9]

Andromadus - Test Builds
To start with here you will find test versions of ROMs built by me from the Andromadus github repo http://github.com/Andromadus, think of them along the same concept as nightly builds just not every night These are development ROM's, if you want to run bleeding edge development ROM's and at least know how to use adb and logcat then you might find something of interest here. If you require something that works 100% of the time all of the time then this might not be for you. That said you can always give it a try and if it doesn't work restore your previous nandroid backup!
What IS Andromadus?
Initially it was a group of people who got together to make ICS work on the HTC Desire Z because nobody else seemed to want to support devices with physical hardware keyboards/trackpads. Whilst the idea stays the same It has grown slightly to support some other hardware and some of the work we have done is now used in many other devices. Andromadus builds of CM10 or CM10.1 are basically CM sources with a few additional tweaks or additions to support our phones.
1. New versions will be added as and when I feel there are enough changes to warrant one, don’t ask when the next version is coming.
2. If we decide to release a "Stable" version of these roms they will be published in another Andromadus thread.
Direct all your queries with release versions to that thread and in the same vain do not discuss these releases anywhere but here.
3. I will do as best I can to answer questions but if you don't get an answer from me I'm sure somebody else will be along to help. Help each other and I have more time to spend fixing things!
4. Don't ask for what's changed since the previous version, have a look at the recent submits on the Andromadus github if you want to know or wait for the mini changelogs when I post a new release.
5. If there is something in particular to test it'll be mentioned!
6. As always if you didn't wipe between installations then at least verify that the problem exists on a clean install before posting here. Nandroid/superwipe/install/check at the end of the day you can always restore your nandroid if the problem is reproducible on a clean installation. If you can't be bothered to try this then I really can't be bothered to try to help you :>
7. All that said ensure you make a nandroid/backup before hand. I take no responsibility for what you do to your phone with these ROM.
8. Whilst I can't stop you I would rather these builds were not used as a base for any ROM/MOD/ETC. The source is all available if you want to do your own builds with which you can do whatever you like.
9. Tell us what works/what's worse/what's better but don't ***** when something breaks or isn't fixed yet, report it and move on.
10. Sometimes people forget that we do this for fun, for ourselves, and sometimes your super important issue is way down on our personal list of things to be fixed.
If you ignore any of the above you will in turn be ignored.
Now that's all out of the way as always have fun
As usual you need to flash the ROM then GAPPS.
Checkout http://andromadus.flinny.org for links/files/changelog's
This a team/community effort, I'll not list everyone who has helped along the way here that list is in the beta thread but I will say thanks to all of them again and obviously anyone that has been missed.

Reserved

Hi Flinny, great job on the AOSP builds they are running perfect. I only had one satback sins build 4. Suddenly my gallery stopt working and dropbox to. Because of the gallery problem my camera won't boot either. I flashed build 5 but I had the same problem. Build 4 was flashed with a full wipe and build 5 was flashed as update that the reason of course why the problem didn't left but sometimes it helps Does this sound familiar? Greetz Munky

I tested it last evening but have many FC message about "aosp keyboard" even with the physical keyboard
I wiped all but still the same message going back to cm10.1

Ok I'm a little rusty on the details at the moment but: AOSP means that you want it to get as close as stock experience as you can get right? (I'm really looking for a G-lite thing but then with ICS/Jelly Bean, sort of Nexus feel but then for our Desire Z)

What's everyone's opinion on these AOSP builds? To me they seem more stable and faster than CM. I kinda miss CM a little though, but not the lag.
Sent from my HTC Vision using xda app-developers app

I know that this is a dumb question and the answer is probably within the other thread, but... Ah heck, now it's just that I'm too lazy to look for the solution LOL...
But I installed AOSP 4.2 v6 last night and so far I'm not experiencing any major problems (except for FCing when I edit a picture and a bit of confusion adjusting to some new features LOL)... But when is this project going to be merged with CM? There are LOTS of creature comforts (e.g. silence during night hours, T9-style contact search, etc.) that I'm used to with the CM-optimized version that I kinda miss and only noticed that it was gone when I flashed it (I was under the impression that those features were all standard?)
Sorry to pester and thanks in advance.

EdWaRdW818:
Here you've got CM10.1 which is based on AOSP 4.2
http://forum.xda-developers.com/showthread.php?t=2031678
Flinny:
Could you add init.d support to the rom or fix it? I see that there is a placeholder for scripts and there is one script, but it's not executed on boot (with 755 permissions).

Eddy130306 said:
What's everyone's opinion on these AOSP builds? To me they seem more stable and faster than CM. I kinda miss CM a little though, but not the lag.
Click to expand...
Click to collapse
Have you tried Flinny's CM 10.1?
(I haven't - I'm just curious as to what you think)

google ears
EDIT: Sorry wrong thread
BTW: how can I delete my post?

I can't find changelog in your site flinny can you link it ?!
Inviato dal mio HTC Vision con Tapatalk 2

zofox said:
I can't find changelog in your site flinny can you link it ?!
Inviato dal mio HTC Vision con Tapatalk 2
Click to expand...
Click to collapse
http://andromadus.flinny.org/?q=node/2

This is absolutely the smoothest 4.0+ ROM I have ever used. Might switch to CM10.1 though for more features.

adamz667 said:
EdWaRdW818:
Here you've got CM10.1 which is based on AOSP 4.2
http://forum.xda-developers.com/showthread.php?t=2031678
Flinny:
Could you add init.d support to the rom or fix it? I see that there is a placeholder for scripts and there is one script, but it's not executed on boot (with 755 permissions).
Click to expand...
Click to collapse
catachresistant said:
Have you tried Flinny's CM 10.1?
(I haven't - I'm just curious as to what you think)
Click to expand...
Click to collapse
Oh jeez... Either I had a total brain fart and completely missed the link or it got posted anywhere from the time I posted it to the catching up of 14+ hours of sleep (I only slept 7 hours across 3 days LOL), but I guess CM10.1 is already posted. I'll download it and see what's up. Thanks for not flaming me guys. I would've gotten the N4 but I'm not a big fan of LG (had countless bad hardware experiences) and my phone is somewhat last on my "to upgrade list", so thanks for everybody's help and keep up the good work! There's some top quality Münchner Bier mit your name on it once I get some disposable income

catachresistant said:
Have you tried Flinny's CM 10.1?
(I haven't - I'm just curious as to what you think)
Click to expand...
Click to collapse
No I have not.
Sent from my HTC Vision using xda app-developers app
---------- Post added at 02:11 PM ---------- Previous post was at 02:00 PM ----------
LAMER_CZ
That is strange. Which recovery are you using? Don't use clockworkmod as they're always full of glitches and bugs. Don't use ROM Manager to flash ROMs either as they as well have glitches. I recommend doing everything in recovery. If you do have clockworkmod I recommend flashing 4ext as it has more features and can make your phone a little faster
Sent from my HTC Vision using xda app-developers app

Ok I just went ahead and installed it. This is exactly what I need for a ROM on my Desire Z! Thanks Flinny, and keep up the good work!
Now my experience with this ROM:
- I just fly trough my home screens and menu's, it runs fluently!
- When at stock speeds (so 1Ghz) I sometime run into problems booting up the settings. I just hangs there for 4+ seconds untill it actually shows the settings. Setting clockspeeds to 1,8Ghz fixes this most of the times, but it's something you might want to look into (Or don't, it's your ROM)
- The above also happens with some apps.
I don't run swap or any other optimization, so I don't know if it's my problem or a ROM problem, but if you want me to do some more testing just tell me what I need to do

Boot Loop
Thanks for the work, this is a great ROM, just thought I would pitch my issue I had.
Im currently testing an app and set the device to use 2g only as I wanted so see how quickly it pulled in my data on a slower connection. If you leave it in 2g mode and reboot it appears to get stuck in a boot loop.
Hope this is helpful.
Cheers

usc911 said:
Thanks for the work, this is a great ROM, just thought I would pitch my issue I had.
Im currently testing an app and set the device to use 2g only as I wanted so see how quickly it pulled in my data on a slower connection. If you leave it in 2g mode and reboot it appears to get stuck in a boot loop.
Hope this is helpful.
Cheers
Click to expand...
Click to collapse
I doubt that has anything to do with the "2g" setting since the radio doesn't come on until after it is booted up. Maybe that application you're testing screwed something up?

Authorita said:
I doubt that has anything to do with the "2g" setting since the radio doesn't come on until after it is booted up. Maybe that application you're testing screwed something up?
Click to expand...
Click to collapse
The app is fine, I have been building it for a few weeks and runds fine on a nexus one, and a sapphire. I have tried flashing the 4.2.1 AOSP build and the CM10 build and exactly the same is happening.
Guess I'm just missing something :s

usc911 said:
The app is fine, I have been building it for a few weeks and runds fine on a nexus one, and a sapphire. I have tried flashing the 4.2.1 AOSP build and the CM10 build and exactly the same is happening.
Guess I'm just missing something :s
Click to expand...
Click to collapse
Do you think you could get a log of the reboot? Might help in figuring out why it is rebooting like that.

MIUI 2.12.28/29 with CM9 base

Hello guys, I'm starting to port latest MIUI using as base the great job made by Arco with his CM9 port (Arco you're great!). Now, you might ask, why use CM9? well... cause I think is the best rom out there or, at least, the most stable and reliable. It's the one I'm using right now... but I really like the new features in the latest MIUI builds.
I'll try to port using the patchrom tool, right now I'm synching the git repository, as soon as it has finished and in my spare time, I'll start to work on it!
I'm an experienced linux user and a developer with some experience, though this is my first work on a mobile phone, and my goal is to make a stable and usable rom :fingers-crossed:
In a future, maybe, I might help improving kernel and fixing some bugs
So, should you have any useful suggestions, I'd like to hear them cause, as I said, it's my first port! otherwise wish me good luck
EDIT 01/06
Ok, I managed to sync and compile, though I got bootloop. Now I'm doing some deeper analysis of conflicts and manually applying rejected patches. It's my first time with smali code, but I guess I'm understanding something

This is great news! I really like MIUI! I have a suggestion, though I don't know if it will be useful. XD
There was an old MIUI ROM here, developed by utingbato. Although, it was based on CM9 Beta 4 and MIUI 2.8.10. But, as far I'm using it now, it's really kind of smooth and only the [system updates] and sometimes, the [theme manager] on crashes. The file manager there is kinda buggy, when I tried to move some of my files, it doesn't really move them, but says that the operation was completed. Same goes with deleting files. He applied some tweaks and stuff on the ROM too, I guess that's why its really smooth. The english language in the ROM is also not translated properly. Some of the buttons (specifically, the reboot options in power menu) is not translated properly.
I don't really know how any of the procedures of creating a ROM really, but I hope you can port some of his tweaks, to make the ROM smooth too. I don't think he has any github though, and he is kind of inactive lately. LINK: http://forum.xda-developers.com/showthread.php?t=1963421
I hope the best for MIUI!

madpausa said:
Hello guys, I'm starting to port latest MIUI using as base the great job made by Arco with his CM9 port (Arco you're great!). Now, you might ask, why use CM9? well... cause I think is the best rom out there or, at least, the most stable and reliable. It's the one I'm using right now... but I really like the new features in the latest MIUI builds.
I'll try to port using the patchrom tool, right now I'm synching the git repository, as soon as it has finished and in my spare time, I'll start to work on it!
I'm an experienced linux user and a developer with some experience, though this is my first work on a mobile phone, and my goal is to make a stable and usable rom :fingers-crossed:
In a future, maybe, I might help improving kernel and fixing some bugs
So, should you have any useful suggestions, I'd like to hear them cause, as I said, it's my first port! otherwise wish me good luck
Click to expand...
Click to collapse
Although the outcome is not certain, but said Thanks for your effort!
Good luck in it. We will be waiting for anything good to result. And keeping our devices alive!

Mbacc u mastr a cavc è tost!
English: Good luck mad! XD

glad to hear that and thank you.
well, im not good in suggestions,,just try to make it smooth and fast for multitasking
Sent using Tapatalk 2

really glad to see more devs are coming to this phone

guess I'll switch to AOSP ICS as a base, should give less conflict issues than CM

+ langague french please!!!!! :thumbup:
Sent from my GT-I8150 using xda app-developers app

Hi, i'm is user of rom miui 2.8.10 by utingbato and i'll waiting for your miui rom release. I'll try it and using because i'm is fans of miui
I hope the release is as soon as possible.
Thanks.
*sorry about my english*
Sent from my GT-I8150

AOSP Rom

Hello! This is my first post and i want to know if anyone is making an AOSP rom for this device? It appears that this device is really laggy and stutters here and there. The Geodev rom is based on AOSP i think but don't know how the rom is doing right now and i can't comment on it because this is only my first post. MAY I KNOW WHO HERE IS TRYING TO GET AOSP FOR OUR DEVICE BECAUSE THAT IS THE ONLY WAY OF MAKING THIS SMOOTH. Thanks everyone! Cheers!

Sarmiento_Luise said:
Hello! This is my first post and i want to know if anyone is making an AOSP rom for this device? It appears that this device is really laggy and stutters here and there. The Geodev rom is based on AOSP i think but don't know how the rom is doing right now and i can't comment on it because this is only my first post. MAY I KNOW WHO HERE IS TRYING TO GET AOSP FOR OUR DEVICE BECAUSE THAT IS THE ONLY WAY OF MAKING THIS SMOOTH. Thanks everyone! Cheers!
Click to expand...
Click to collapse
As of now, Geodev is the only one in development. If you're trying to get your post count up, go to the XDA General section and post in the new members forum or the off topic lounge.

postcount++
imho that geodev thing sounds shady at best.
If you would decide to port a custom rom to a new device, would you really start by porting KitKat if the device
currently only runs jellybean? Wouldn't it be easier to use the stock kernel for now to get cm10 running
and then wait paitiently until htc releases the kernel src to make it a full unofficial cm10 build.
Instead this sounds more like taking the existing source of a hopefully hardware compatible build
and bending it until it brea.. ehm works.
I may be biased, but if you plan to make any kind of release you usually don't go and announce it to the world.
This only encourages the rather impatient endusers to come up with many variations of the same old:
"i need my rls now!", "I am entitled to a release because I found this thread","GIMME RLS!!!11oneeleven"
posts that will just annoy the crap out of every dev I've ever met. Also there is absolutely no point in asking for
beta testers before you even have a working build ready.
Combine that with the recent e-begging post and draw your own conclusions.
DroidTwe4kz said:
[...] I can't continue developing until someone gift me new computer (or motherboard only). [...]
Click to expand...
Click to collapse
In any case, for the time being it might be a good idea to check if there are some services you could deactivate
in order to get a little bit more speed out of your phone. I personally have no problems with lags, but maybe
it's because I don't expect the phone to run every app ever made at the same time since it has only 512MB RAM.