CM7 and battery - Desire General

Hi,
I find battery usage a bit high on CM 7(RC1 and nighly).
Batter Montor widget or CurrentWidget shows values from 6-12 mAh.
With same radio i have 3-5 mA when using default HTC Sense ROM.
I did full wipe factory reset, dalvik, cache etc..
I need some tips how to diagnose the problem and eventually file a bug report.
I am using lates radio 32.54.00.32U_5.14.05.17, but the problem is the same with older one 32.49.00.32U_5.11.05.27
I don't think the problem is with the radio itself, because it will be problematic with all ROMs (?)

You do realise that you can post in the CM7 thread. You also realise that RC and nightly builds arn't stable releases?

You also realise that RC and nightly builds arn't stable releases?
Click to expand...
Click to collapse
ofc i know that . I also know that if it is a bug, someone will have to report it. That's the goal of RC after all . May be you should read the whole post after all.

I seem to be having a similar experience with oxygen rom so would be interested in investigating what is causing this. Tried looking at all the usual stuff in QSI to weed out programs that may be causing this problem but nothing jumps out at me. Plus, i'm having the problem with completely clean rom without any apps installed.
j0r01 said:
ofc i know that . I also know that if it is a bug, someone will have to report it. That's the goal of RC after all . May be you should read the whole post after all.
Click to expand...
Click to collapse
Don't think that sort of response if going to help your cause tbh

I also know that if it is a bug, someone will have to report it. That's the goal of RC after all . May be you should read the whole post after all.

p5x said:
I seem to be having a similar experience with oxygen rom so would be interested in investigating what is causing this. Tried looking at all the usual stuff in QSI to weed out programs that may be causing this problem but nothing jumps out at me. Plus, i'm having the problem with completely clean rom without any apps installed.
Don't think that sort of response if going to help your cause tbh
Click to expand...
Click to collapse
same here. battery just runs dry very fast! (after playing a song on youtube, battery goes down for about 6%)

Try a different kernel. I recommend ManU kernel (the CFS-HAVS-AXI-version).

Same comments in spanish forum:
http://www.htcmania.com/showthread.php?t=303281&page=21#402
This guy is recommending aEVViollet (..35) kernell.
I'm thinking about changing into Oxygen.
Best regards

It is getting better, isn't it?

Related

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

HTC One X custom rom - Screen Flicker Fix...

Hello everyone one,
I had an international HTC One X locked to the ThreeUK network (1.28). They were rubbish releasing updates namely 1.29.701.11
I get the screen flicker issue, and last night I rooted and installed Revolution HD 9.1.0 (sense 4.1) rom onto my phone.
The phone is soooo much snappier and faster, plus scores 700-800 more on antutu.
My question is, will this custom firmwire update I have done also fix the screen flicker issue and lost memory card data I was experiencing with 1.28 4.0.3??
Thanks.
New here and looking to stay
ben-fisher-bro said:
Hello everyone one,
I had an international HTC One X locked to the ThreeUK network (1.28). They were rubbish releasing updates namely 1.29.701.11
I get the screen flicker issue, and last night I rooted and installed Revolution HD 9.1.0 (sense 4.1) rom onto my phone.
The phone is soooo much snappier and faster, plus scores 700-800 more on antutu.
My question is, will this custom firmwire update I have done also fix the screen flicker issue and lost memory card data I was experiencing with 1.28 4.0.3??
Thanks.
New here and looking to stay
Click to expand...
Click to collapse
It should do, wait a couple of weeks for the screen flicker fix to fully implement.
ste1164 said:
It should do, wait a couple of weeks for the screen flicker fix to fully implement.
Click to expand...
Click to collapse
Thanks for the reply.
I'm getting conflicting reports that the screen flicker won't be fixed as I need that specific update and a custom rom will not fix it as it's more to do with the binary and not with the rom side?
Any other ideas ?
Cheers
ben-fisher-bro said:
Thanks for the reply.
I'm getting conflicting reports that the screen flicker won't be fixed as I need that specific update and a custom rom will not fix it as it's more to do with the binary and not with the rom side?
Any other ideas ?
Cheers
Click to expand...
Click to collapse
Can you reference these conflicting reports?
I firmly believe that the cusotm ROM you have will include the fix (ask the author) but it is fair to say that a few people found the fix didn't work but the majority of handsets were fixed by 1.29.xxx.11.
I cannot reference no. If I find the thread again i'll link it here.
So what's the best route of it being fixed? Maximum brightness?
farnsbarns said:
Can you reference these conflicting reports?
I firmly believe that the cusotm ROM you have will include the fix (ask the author) but it is fair to say that a few people found the fix didn't work but the majority of handsets were fixed by 1.29.xxx.11.
Click to expand...
Click to collapse
farnsbarns
Hmm, this is what I always wanted to know. Maybe you can shed light on this for me (getting ignored in custom kernel, or CM threads)
The custom kernels are made from the source right? I mean compiled?
Whats the latest one there is? Last time I was on custom kernel there was the official source only from the 0.7 version without the flicker fix.
Or is there already a new source? Or no source needed, they can just hack into the kernel without it?
Also the modded roms, they have their own kernels right? Also a new source with the flicker fix?
Also I didn't have flicker with .11 (got the phone shipped with it) and when I tested custom kernels = flickers, back to stock = no flicker.
On this OTA, it flickers, hoping it will settle, but I can already tell it was faster "fixed" for me on the .11
Maybe there was the data, which will it have to gather from new on as I am now after RUU etc.
I'm having the exact same issue on CM10. I know it's still an alpha build, so I'm willing to wait. But I've asked one of the developers directly, but he/she won't respond.
It is a big problem for some of us, yet it's being ignored. That alone doesn't sit right with me. Does that mean that it's not easy to fix or that it's not in the pipeline (yet)?
jvlmp said:
I'm having the exact same issue on CM10. I know it's still an alpha build, so I'm willing to wait. But I've asked one of the developers directly, but he/she won't respond.
It is a big problem for some of us, yet it's being ignored. That alone doesn't sit right with me. Does that mean that it's not easy to fix or that it's not in the pipeline (yet)?
Click to expand...
Click to collapse
You know, I wouldn't mind the flickering as much I am now, if someone of them would at least say something to it. Like "not possible" or "working on it" but ignoring the questions just made me abandon CM for now and I am back to stock.
PAGOT said:
You know, I wouldn't mind the flickering as much I am now, if someone of them would at least say something to it. Like "not possible" or "working on it" but ignoring the questions just made me abandon CM for now and I am back to stock.
Click to expand...
Click to collapse
I totally agree! I'm playing with the same idea of going back to the stock ROM, but I truly don't like Sense. But I ike it more than the flickering though.
jvlmp said:
I totally agree! I'm playing with the same idea of going back to the stock ROM, but I truly don't like Sense. But I ike it more than the flickering though.
Click to expand...
Click to collapse
I hate sense too . Thats why I have most of it deactivated and use Nova launcher. There is even a sense cleaner here in the forum. But I just frozen the aps I don't like. Should help a bit with deactivating most of the sense stuffs.
I would go for CM, but there were few issues, I had with it besides the flickering.
It's been a while, but did anyone have any luck in fixing the screen flickering in CM10?

High battery drain when using a 3.0 kernel

Flashed the ROM from http://forum.xda-developers.com/showthread.php?t=1492461 which uses a 3.0 kernel. It runs smooth on my device. However, if I use my phone to listen to music, my battery drains very fast (about 40%/h) although I'm not doing anything else with the device. It also gets quite warm as if it had a high CPU load. However, the CPU load is low as you'd expect. The CPU clock is also OK, most of the time it runs at 245Mhz.
I then downloaded the very same RO with a 2.6 kernel. This time, battery was good when listening to music (1%/15m) and the device stays at a normal temperature so I assume there is a problem with the 3.0 kernel. Did anybody else also encounter this? What can I do to help debugging this problem?
Personally I'd suggest to move over to a similar but better/more stable ROM. Two that come to mind are mimicry and elitemod ICS, both are great and have far less bugs than the ROM you are using. But to each there own... I'd suggest contacting the developer, either within the thread or via pm and ask him why he implemented the 3.0 kernel when it is just far to buggy to use as a daily driver? I'm not hating on him just seems as it was put in his ROM and well... not supported much thereafter.
Sent from my Nexus 7 using xda premium
The 3.0 kernel isn't as stable as 2.6. If the battery drain issue is that bad then I would suggest moving onto a rom that still uses 2.6. Or if you feel lucky, go test out Andromadus JB which also has the 3.0 kernel. It might be better there. Considering you're testing this with a music app, why not try another application? Try changing the overclock settings. The unofficial CM9.1 and Andromadus are mostly in testing right now. You'd have to be willing to deal with these problems if you use those roms, and report the bugs to the authors.
I would suggest using Mimicry. It may not have all the new bells and whistles like 3.0 kernel, but at least it's stable.
For the record, the 2.6 kernel that Mimicry uses has a *ton* of 3.0 kernel patches merged into it.
Sent from my HTC Vision using xda premium
Thanks for the replies! Forgot to mention that I first also blamed the audio player (Apollo) and changed to the app I used with the stock ROM but the battery drain was just as bad. So: sorry Apollo
My intention was to help the author of the ROM to track down that issue. But since I'm new to these forums I wasn't allow to reply to the original thread so I wanted to ask first if this is a known general issue of the 3.0 kernel. I'll PM the author and point him to the thread. If anybody knows a good thread on debugging battery drain issues or knows how to do this, please feel free to post links here, I'll also search further.
Madthrillhouse said:
Thanks for the replies! Forgot to mention that I first also blamed the audio player (Apollo) and changed to the app I used with the stock ROM but the battery drain was just as bad. So: sorry Apollo
My intention was to help the author of the ROM to track down that issue. But since I'm new to these forums I wasn't allow to reply to the original thread so I wanted to ask first if this is a known general issue of the 3.0 kernel. I'll PM the author and point him to the thread. If anybody knows a good thread on debugging battery drain issues or knows how to do this, please feel free to post links here, I'll also search further.
Click to expand...
Click to collapse
I have the same problem. 40%/h drainage, with either poweramp or apollo. I use CM9.1-vision-3.0-V4
Any news on this?
TIA
Frank
i think 3.x.43 is high battery drain,but 3.x.40 is better than 3.x.43
GaardenZwerch said:
I have the same problem. 40%/h drainage, with either poweramp or apollo. I use CM9.1-vision-3.0-V4
Any news on this?
TIA
Frank
Click to expand...
Click to collapse
I sent the developer a PM offering help on this but didn't get a reply. I then reverted back to the 2.6 kernel which works just fine in terms of battery usage.
Still in CM9.1.0 Final
Madthrillhouse said:
I sent the developer a PM offering help on this but didn't get a reply. I then reverted back to the 2.6 kernel which works just fine in terms of battery usage.
Click to expand...
Click to collapse
Hi,
just to let you know
this behaviour is still there with the "CyanogenMod 9.1.0 - 3.x Kernel - Final" ROM.
Thanks
Frank
GaardenZwerch said:
Hi,
just to let you know
this behaviour is still there with the "CyanogenMod 9.1.0 - 3.x Kernel - Final" ROM.
Thanks
Frank
Click to expand...
Click to collapse
the problem still persist...
my phone battery runs out to fast...
Use mimicry it avoids the problematic kernel and it is the original code
Sent from my HTC Vision using xda app-developers app

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

any completely stable finished roms available?

hi, just wondering if there are any roms available that are completely stable and finished for this phone?
if not, (as i have not found any), is the original stock rom (rojers) available to download anymore?
thanks guys..
jmpcrx said:
hi, just wondering if there are any roms available that are completely stable and finished for this phone?
if not, (as i have not found any), is the original stock rom (rojers) available to download anymore?
thanks guys..
Click to expand...
Click to collapse
After reading a lot, I believe I can confirm that only GB, and stock ICS are stable, as with no issues, some little glitches but no deal breakers. As for Rogers, there's only Osimod GB ROM based of Rogers. The rest are based of UCLJ3
lasuazo said:
After reading a lot, I believe I can confirm that only GB, and stock ICS are stable, as with no issues, some little glitches but no deal breakers. As for Rogers, there's only Osimod GB ROM based of Rogers. The rest are based of UCLJ3
Click to expand...
Click to collapse
ok thanks lasuazo ;--)
I guess omni and cm11
jmpcrx said:
hi, just wondering if there are any roms available that are completely stable and finished for this phone?
if not, (as i have not found any), is the original stock rom (rojers) available to download anymore?
thanks guys..
Click to expand...
Click to collapse
I may be off base here but I guess the [4.4] cyanogenmod 11 and omni ROM are pretty much stable ...
Though the pretty much is still a while away from complete the following are the general bugs with bubor's amazing Roms:
There is an audio bug when making VoIP calls which gives audio latency ..
There is fixed camera rotation which means all the pictures are in landscape
There is no Wi-Fi direct
Google experience launcher is not that Good looking (I know I am complaining)
Google maps 7 has issues but can be dual loaded with maps 6 so they work
Backlight,PPI, lag all have fixes though
Battery drain is a bit more
But as far as performance goes... They are pretty smooth..
So I guess make your choice
thefusor said:
I may be off base here but I guess the [4.4] cyanogenmod 11 and omni ROM are pretty much stable ...
Though the pretty much is still a while away from complete the following are the general bugs with bubor's amazing Roms:
There is an audio bug when making VoIP calls which gives audio latency ..
There is fixed camera rotation which means all the pictures are in landscape
There is no Wi-Fi direct
Google experience launcher is not that Good looking (I know I am complaining)
Google maps 7 has issues but can be dual loaded with maps 6 so they work
Backlight,PPI, lag all have fixes though
Battery drain is a bit more
But as far as performance goes... They are pretty smooth..
So I guess make your choice
Click to expand...
Click to collapse
i wish i could agree with you.. im running kitkat crdroid, and like every rom i have flashed over the years, has plenty of bugs that make it very annoying as a daily rom. phone switching off twice a day, icons/widgets dissapearing after rebooting, becomes laggy after a week or so of usig the rom, laggy browsing on all browsers, trebucket crashing regurly etc etc, thats on top of the bugs you list.. the only roms that are stable are completely finished official cm or miui roms (which there are none for this fone..). the stock rom is the only one that has not given me trouble. with the greatest respect to those that put their time i to make these roms, im sure people who flash them make them out to be more stable than they really are unfortunatelly.
Maybe we have developer aura or something like that? I'm sure I just used 4.4 PAC ROM for a week without reboot or any crashes. Bluetooth, fixed camera rotation and VoIP - yes, these are issues we can't fix, the same is with google maps v.7 (we just have no hardware NEON support that uses v.7 of maps). There is also issue with wi-fi: if you turn it off, it sometimes don't turns on until reboot. As for myself, I just never turn it off.
Besides of these issues, everything is smooth and stable. Really is. But I got sometimes trebuchet crashes - this was a time when I flashed dirty and didn't make a factory reset - the new trebuchet version sometimes conflicts with the data from old version. I just went to Settings - Apps, found Trebuchet (or Launcher3 if old version) and tapped Erase Data. And the issue was gone! But I recommend to always make a factory reset with new ROM. That's really important.
And even if you have those constant trebuchet bugs whatever you do (icons disappearing is also a trebuchet bug, I never encountered it though), just install a different launcher. Google now launcher is the basic, and is like trebuchet in many ways, miui one is also good, and others, they are many!
I had problems with some icons disappearing when the system reboots. I found that the icons that disappeared were for applications which were installed on the SD card. When I moved them to the system, they stopped disappearing.
Makshow said:
Maybe we have developer aura or something like that? I'm sure I just used 4.4 PAC ROM for a week without reboot or any crashes. Bluetooth, fixed camera rotation and VoIP - yes, these are issues we can't fix, the same is with google maps v.7 (we just have no hardware NEON support that uses v.7 of maps). There is also issue with wi-fi: if you turn it off, it sometimes don't turns on until reboot. As for myself, I just never turn it off.
Besides of these issues, everything is smooth and stable. Really is. But I got sometimes trebuchet crashes - this was a time when I flashed dirty and didn't make a factory reset - the new trebuchet version sometimes conflicts with the data from old version. I just went to Settings - Apps, found Trebuchet (or Launcher3 if old version) and tapped Erase Data. And the issue was gone! But I recommend to always make a factory reset with new ROM. That's really important.
And even if you have those constant trebuchet bugs whatever you do (icons disappearing is also a trebuchet bug, I never encountered it though), just install a different launcher. Google now launcher is the basic, and is like trebuchet in many ways, miui one is also good, and others, they are many!
Click to expand...
Click to collapse
like i said in my first post, i do really appriciate the fact that people spend Alot of time cooking theese roms, and it easy for me to come along and moan about them, but i have found over the years that after using a custom rom for a couple of weeks or so, its like the ram seems to gradually get eaten away, the device gradually slows down, becomes laggy and ultimately unuseable (not just this fone, and not just me that says this). im not saying all are like this, just many i have used, mainly because they never get finished.
i am very open though to people suggesting that i am doing something wrong, and maybe you have picked up on that something.. you say you do a factory reset, can i ask, do you mean a factory reset in the fone settings, or are you referring to a full wipe using cwm/twrp? as when i flash, i wipe everything accept what i dont want wiped on the external sd.. i dont factory reset, is this after you have flashed the new rom? or before you flash a new rom?
also thank you for the erase data tip for trebucket, i will try that.. i have not used the google now launcher yet, but i tried using miui launcher but when i went back to trebucket the lockscreen stayed as the miui lockscreen, which has happened on past cm roms, so i just deleted it.
just gets a bit frustrating when you spend hours getting everything working/setting up personalisation, then the phone just seems to start getting worse day by day, but maybe like you say, its cos i "dirty flashed"?
linuxguy42 said:
I had problems with some icons disappearing when the system reboots. I found that the icons that disappeared were for applications which were installed on the SD card. When I moved them to the system, they stopped disappearing.
Click to expand...
Click to collapse
i did think that, and im sure you are right, but i have had every app/folder/widget dissappear twice now, then, randomly over several restarts, some widgets/apps will replace themselves over the top of the new ones i have just newly placed there.. strange, but i have came across this before on cm roms, so im sure there is a bug there somewhere, even if it is not too common..
jmpcrx said:
you say you do a factory reset, can i ask, do you mean a factory reset in the fone settings, or are you referring to a full wipe using cwm/twrp? as when i flash, i wipe everything accept what i dont want wiped on the external sd.. i dont factory reset, is this after you have flashed the new rom? or before you flash a new rom?
Click to expand...
Click to collapse
Yes, what you do should suffice. I meant cwm/twrp wipe (boot, system, data, cache, android.secure). SD card is not touched. So you are doing fine with that, but anyway, there has to be something make those issues... Can you look at /system/addon.d folder? There is stored info about files that will be preserved even if you install a new ROM with a wipe. If there are many leftovers from ROMs or programs you tried earlier, then you should try to manually clear this folder before new ROM install.
the device gradually slows down, becomes laggy and ultimately unuseable
Click to expand...
Click to collapse
That was the point with pre-4.2 ROMs, and even with 4.2 there was a bug with gallery thumbnails which made it to eat gigabyte and more of storage after some time. That was fixed in CM 10.1.3. Also a Lite-Kernel used by earlier ROMs is very great, but has its issues, for example, systemui crashes when camera launch after some phone use and sleep of death.
I used CM 10.1.3 for a a three months and still keeping a backup of it for a some case. There was no slowing or lagging, it was almost perfect (if you don't use VoIP or BT handset) even after those months of use. Strangely, but I didn't have even "settings -> about crash" issue bubor listed!
Welll here are some tip which have helped me
jmpcrx said:
i wish i could agree with you.. im running kitkat crdroid, and like every rom i have flashed over the years, has plenty of bugs that make it very annoying as a daily rom. phone switching off twice a day, icons/widgets dissapearing after rebooting, becomes laggy after a week or so of usig the rom, laggy browsing on all browsers, trebucket crashing regurly etc etc, thats on top of the bugs you list.. the only roms that are stable are completely finished official cm or miui roms (which there are none for this fone..). the stock rom is the only one that has not given me trouble. with the greatest respect to those that put their time i to make these roms, im sure people who flash them make them out to be more stable than they really are unfortunatelly.
Click to expand...
Click to collapse
i .. umm.. well i agree that as of now they have issues but they will get better .. ours is an old device... so i guess we should tread slowly . which is exactly what the developers are doing .. .
and i agree on the ram hungry part but there are ways for that too . .
funny i have been messaging people to help me post this stuff through them . . but well thats the prob with being a junior member .
My personal tested suggestions for omni rom which have really incremented to the performace some of which are :
- using one of the lightest launchers as i find trebuchet and even google launcher RAM hungry is 'Lightning Launcher' the bloody app itself is in BYTES!!
-also i use link2sd with ext4 that helps in storage and also use sd maid for regular clean up.
-also i have been testing memory swapping using linux swap partition on sd card (class 10 ) and yeah i know it degrades sd card but oh well like Glados testing testing testing
-i have also switch off startup at boot for certain apps
and i apologize for posting what maybe well known tricks or improvs but i really dont know where else to post these (still have the ten post ban from posting )
and if these dont help then sorry to waste your time . .
PS anyone think an F2FS file system like for the nexus7 would\might help ?
tl;dr use the given tips maybe they might help . . and with custom roms i guess you have to spend time to keep them running well .
Makshow said:
Yes, what you do should suffice. I meant cwm/twrp wipe (boot, system, data, cache, android.secure). SD card is not touched. So you are doing fine with that, but anyway, there has to be something make those issues... Can you look at /system/addon.d folder? There is stored info about files that will be preserved even if you install a new ROM with a wipe. If there are many leftovers from ROMs or programs you tried earlier, then you should try to manually clear this folder before new ROM install.
That was the point with pre-4.2 ROMs, and even with 4.2 there was a bug with gallery thumbnails which made it to eat gigabyte and more of storage after some time. That was fixed in CM 10.1.3. Also a Lite-Kernel used by earlier ROMs is very great, but has its issues, for example, systemui crashes when camera launch after some phone use and sleep of death.
I used CM 10.1.3 for a a three months and still keeping a backup of it for a some case. There was no slowing or lagging, it was almost perfect (if you don't use VoIP or BT handset) even after those months of use. Strangely, but I didn't have even "settings -> about crash" issue bubor listed!
Click to expand...
Click to collapse
ok thanks, i cleared the data in trebucket, and started again with placing apps/widgets on home screen, and i also have deleted the hacked version of adobe flash that you install with dolphin browser, and, supprisingly after a couple of days of testing, my apps/widgets are not deleting themselves, the phone is significantly less laggy, and i have had no switch offs, so, im very pleased with that! so id suggest against downloading that version of flash player with this rom..
thefusor said:
i .. umm.. well i agree that as of now they have issues but they will get better .. ours is an old device... so i guess we should tread slowly . which is exactly what the developers are doing .. .
and i agree on the ram hungry part but there are ways for that too . .
funny i have been messaging people to help me post this stuff through them . . but well thats the prob with being a junior member .
My personal tested suggestions for omni rom which have really incremented to the performace some of which are :
- using one of the lightest launchers as i find trebuchet and even google launcher RAM hungry is 'Lightning Launcher' the bloody app itself is in BYTES!!
-also i use link2sd with ext4 that helps in storage and also use sd maid for regular clean up.
-also i have been testing memory swapping using linux swap partition on sd card (class 10 ) and yeah i know it degrades sd card but oh well like Glados testing testing testing
-i have also switch off startup at boot for certain apps
and i apologize for posting what maybe well known tricks or improvs but i really dont know where else to post these (still have the ten post ban from posting )
and if these dont help then sorry to waste your time . .
PS anyone think an F2FS file system like for the nexus7 would\might help ?
tl;dr use the given tips maybe they might help . . and with custom roms i guess you have to spend time to keep them running well .
Click to expand...
Click to collapse
some good tips there, thankyou, i havent tried any of them yet, but i will have a go at some of them and see what happens.. thanks thfusor..
jmpcrx said:
hi, just wondering if there are any roms available that are completely stable and finished for this phone?
if not, (as i have not found any), is the original stock rom (rojers) available to download anymore?
thanks guys..
Click to expand...
Click to collapse
For what it's worth, I recently had to reflash and decided to use dman325's stock UCLJ3. (He has two versions, stock and one with the aosp lockscreen. If you decide to use either, use the stock one. dman325 had to resign the aosp one with a test signing key that, recently, got invalidated or declined and it prevents Google Play from updating past 3.7.15 and Google Play Services wont install at all because of a shared_uid fault due to certificate conflict, etc.)
I got frustrated with the amount of bloat in an otherwise vendor fun-packed rom, so I went in and hacked out lots of crap. Largely relying on either "what is safe to get rid of" lists for similar samsung phones and my own poking around/guestimation using dex2jar and jd-gui. I really, honestly don't understand what InputEventApp.apk was meant to do. Seriously. But, getting rid of it reduced the logcat spam tremendously. Also, the wsslcm* apks are somewhat frightening in appearance.
I've gone a few steps further, I modified android.policy.jar smali to prevent the emergency dial option from showing up on the lock screen - I accidentally pocket dialed 911 a year ago and am not about to do that again. I also modified the kernel ramdisk image to set ro.debuggable=1 and ro.secure=0. I tried, while I was at it, to replace /dev/random with /dev/urandom, but I'll have to do some experimenting.
I've added a few static binaries for proper gnu utilities. bash, ls, grep, sort, du, etc. It surprises me that a functional shell environment doesn't get more attention on phones with keyboards.
So, that's my $0.02. Try the stock UCLJ3 and fiddle with it a bit. Good luck.
etherfish said:
For what it's worth, I recently had to reflash and decided to use dman325's stock UCLJ3. (He has two versions, stock and one with the aosp lockscreen. If you decide to use either, use the stock one. dman325 had to resign the aosp one with a test signing key that, recently, got invalidated or declined and it prevents Google Play from updating past 3.7.15 and Google Play Services wont install at all because of a shared_uid fault due to certificate conflict, etc.)
I got frustrated with the amount of bloat in an otherwise vendor fun-packed rom, so I went in and hacked out lots of crap. Largely relying on either "what is safe to get rid of" lists for similar samsung phones and my own poking around/guestimation using dex2jar and jd-gui. I really, honestly don't understand what InputEventApp.apk was meant to do. Seriously. But, getting rid of it reduced the logcat spam tremendously. Also, the wsslcm* apks are somewhat frightening in appearance.
I've gone a few steps further, I modified android.policy.jar smali to prevent the emergency dial option from showing up on the lock screen - I accidentally pocket dialed 911 a year ago and am not about to do that again. I also modified the kernel ramdisk image to set ro.debuggable=1 and ro.secure=0. I tried, while I was at it, to replace /dev/random with /dev/urandom, but I'll have to do some experimenting.
I've added a few static binaries for proper gnu utilities. bash, ls, grep, sort, du, etc. It surprises me that a functional shell environment doesn't get more attention on phones with keyboards.
So, that's my $0.02. Try the stock UCLJ3 and fiddle with it a bit. Good luck.
Click to expand...
Click to collapse
thanks etherfish, if i continue to have probs i may well do that, i was thinking about going back to stock. dont think i have the confidence to fiddle like you have though as im more of a windows man than linux, but thanks for the great advice
jmpcrx said:
thanks etherfish, if i continue to have probs i may well do that, i was thinking about going back to stock. dont think i have the confidence to fiddle like you have though as im more of a windows man than linux, but thanks for the great advice
Click to expand...
Click to collapse
Well, you learn by doing, I believe. Also, I have a classy - for a flip phone - Motorola Razr2 v8 kicking around I can always put my SIM into if I've managed to hose my captivate glide. Also, I'm replying because I can't post in the rom development forum until I have 10 posts. Hurray for well founded, but nonetheless arbitrary restrictions. So, a number of things have piqued my curiosity.
So, first of all, this surprised me in the logs:
Code:
I/Launcher( 2263): onCreate(): product model family:U1 product model : GT-I9221
I'd always wondered why I had an SGH-I927 when other phones, like the remarkably similar Galaxy R, are GT-I9103. Is/was GT-I9221 an internal reference?
Also, there are other inconsistencies, for example:
Code:
D/RILJ ( 426): [1718]> REQUEST_GET_NEIGHBORING_CELL_IDS
D/RILJ ( 426): [1718]< REQUEST_GET_NEIGHBORING_CELL_IDS error: com.android.internal.telephony.CommandException: REQUEST_NOT_SUPPORTED
If you jump into the debug/field test menu system, (dial *#*#197328640#*#* ) you can bring up the list of neighboring cells in both GSM and WCDMA modes... So, why is the request marked not supported? Furthermore, why didn't samsung disable the request in the first place if they went to the trouble of disabling it from working. I imagine this has a reason, but I doubt it's a terribly great one.
And the FM receiver? I do believe our broadcom BCM4329 is a bluetooth+wifi_in_an_sdcard (well, SDIO really, but still, not pci-e and not usb.) and has an FM receiver built in, but it's omitted and hidden?
Code:
W/AudioPolicyManager( 112): FM radio recording off
Oh, the conspiracy theories. And then there's the weird lines you discover if you dump the string identifiers from /system/bin/drexe!
For example, these lines are all sequential:
Code:
broadcast -a android.provider.Telephony.SECRET_CODE android_secret_code://767*3855
InvokeOemRequestHookRaw broadcast factorst OK
InvokeOemRequestHookRaw factorst fail %d
/system/.configure.txt
(what's with /system/.configure.txt???)
Do not type 767*3855 into your phone. It's the factory wipe code or possibly part of it. I do believe drexe is the DataRouter you often see spamming the logs with:
Code:
E/DataRouter( 107): usb connection is true
E/DataRouter( 107): DSR is ON. Don't send DTR ON.
And we find these strings in drexe:
Code:
__initialize_usb_ipc
/data/.usb_stream
usb connection is true
InvokeOemRequestHookRaw usbstatus true is success
oh, and:
Code:
pipe failed (%s)
fork failed (%s)
child pid = %d.
execute sh.
system/bin/sh
execl fail %d
What do you think? Why does drexe seem to have code to support and start a shell? Well, if nothing else, thank you for reading.
P.S. I don't suspect anything the least bit conspiracy like, malicious, or devious. I've worked for some huge companies; i don't think it'd be likely.
etherfish said:
Also, I'm replying because I can't post in the rom development forum until I have 10 posts. Hurray for well founded, but nonetheless arbitrary restrictions.
Click to expand...
Click to collapse
Technically, you can post in cappy dev forums started from 3 posts. I saw someone posting there his fourth post.
As for other things you listed... Well, I'll be glad to have an FM receiver in our glide. But I really think that reason for all this staff can be as simply as hands growing from wrong place or restricted development time...
Makshow said:
Technically, you can post in cappy dev forums started from 3 posts. I saw someone posting there his fourth post.
As for other things you listed... Well, I'll be glad to have an FM receiver in our glide. But I really think that reason for all this staff can be as simply as hands growing from wrong place or restricted development time...
Click to expand...
Click to collapse
I recently, after some research, also installed dans stock (i decided to go complete stock since i didnt know what the lock screen thing meant).
I havent had any trouble with being outdated. Only thing i noticed (unless im doing it wrong, im new to this phone) was that screencaps dont work. its power button and volume down, right?
Other things id like to customize are data being in the top drawer instead of bluetooth (since i never use it), and id like to be able to see who texted me on the lock screen, but while still using the stock messaging app, and without an app having to constantly run.
Other than those couple of things its been great!
im HOPING down the road for an un-buggy or at least minimally buggy version of 4.4. well see what happens with that i guess.
Some help
Pawprints1986 said:
I recently, after some research, also installed dans stock (i decided to go complete stock since i didnt know what the lock screen thing meant).
I havent had any trouble with being outdated. Only thing i noticed (unless im doing it wrong, im new to this phone) was that screencaps dont work. its power button and volume down, right?
Other things id like to customize are data being in the top drawer instead of bluetooth (since i never use it), and id like to be able to see who texted me on the lock screen, but while still using the stock messaging app, and without an app having to constantly run.
.
Click to expand...
Click to collapse
well i always say stock is best cause it IS optimized however there are things like keep and total Google integration that i like so i updated to kit kat
for screen caps if they dont work i could maybe suggest an application called super manager its pretty loaded it has screen cap and may even give you prox sense wake up for device.
also customizing the drawer hmm.. i guess you could try xposed framework but please be careful and make a backup before
as for who texts you and the content of the text you could try dash clock its able to do a lot
hello guys I was just wondering if I could get some help since I returned back to fully Ice Cream Sandwich Stock. I completely removed all the system bloat with link2sd, uninstalled all att crap. Can anyone recommend me something since I feel the ram consuption still to high... battery so far is doing kind of good almost as in crdroid
But i believe it can be improved. Any recommended settings or something else i can do? Already tried lite kernel but it gave me some issues. Rather keep stock. Any recommendations please guys. Also if you know a "ok google" like app or something as a swifty assistant would be nice. Please recommend. Thanks in advance
jmpcrx said:
hi, just wondering if there are any roms available that are completely stable and finished for this phone?
if not, (as i have not found any), is the original stock rom (rojers) available to download anymore?
thanks guys..
Click to expand...
Click to collapse
Hi,
well that depends.. on what you mean with "finished"
I have tested all (3 months ago) available ROMs for the Glide. IMO the best available ROM is PACman but as said it depends. I used pac_i927-milestone.1.RC1.4.zip for a long time (months) without having any issues besides Bluetooth Headset which is a general problem in JB and higher version). I have tried other PACMan ROM versions as well but the above one was the best of stability and battery life (in my case).
So it depends what features you really need or are a must-have for you. If you do not have bluetooth headsets I would recommend the above otherwise .. well I would recommend sediROM
Regards
xdajog
---------- Post added at 02:39 PM ---------- Previous post was at 02:33 PM ----------
lasuazo said:
hello guys I was just wondering if I could get some help since I returned back to fully Ice Cream Sandwich Stock.
Click to expand...
Click to collapse
Haven't done that before but would be rooted ICS stock also ok for you?
If so:
--> search for thread ID 1994902 or search for: [ROM] Stock UCLJ3 Rooted, Deodexed, Zipaligned
(sorry not allowed to post links..)
Regards
xdajog

Categories

Resources