• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM] Angry Bean / CM 10.1 [build 08.08.13]

Whenever I use 3g in my area (no 4g) my phone will get piping hot within minuets of it being used? Any ideas on this I'm under clocked and have had get around 2 signal bars constant.
 
Flashed this ROM last night. I want to thank you to the developer for putting out such a great ROM.

I have noticed a few issues though:
1. Audio playback does not switch to headphones when headphones are plugged in. (steps to reproduce below)
2. Audio seems to be pitch shifted, possibly with the center channel removed when playing through headphones (steps to reproduce below)
3. Lack of 4G icons and easy toggles.

How to reproduce issues 1 and 2:
- Plug headphones into phone
- Begin playing music through the Play Music app.
- While music is playing, do a google now voice search
- Notice music begins playing on phone speaker.
- Unplug headphones
- Press the play button in Play Music. Progress bar should indicate that music is playing, but no audio is coming from the speaker.
- Plug in headphones. If necessary, press the play button again.
- Music should start playing over headphones, but sounds odd (pitch shifting, minus center channel)
- Close the Play Music app
- Relaunch Play Music
- Begin playing song, sounds normal.

It seems that running a google now voice search with headphones plugged in messes with the headphone detection...
 
Does anyone know how to get the option to "restart into recovery" when holding down the power button? Just flashed and noticed it doesn't exist.
 
Great rom so far but I also have issues that others have reported. Bad signal for service and wifi, where it was good before on stock. MMS not being able to receive or send.
Hope these can be fixed soon so I can come back to it but for now I'll have to go back to Harmonia.
 
I also have trouble with mms, it will work if I use handcent though. Also the max cpu always resets to 1512 Mhz. Otherwise awesome Rom with good battery life, especially with an extended battery.
 
werewolfboy said:
First you said something about some posts. Also yes the gps is on.
Click to expand...

meh, there are some okay ones.

This post here was trying to determine how all of the location settings effected Google Now and battery life :

http://forum.xda-developers.com/showthread.php?t=2009614

It might be worth watching as more people start using Google now and documenting its battery usage with various settings.

Are you having issues with GPS locks? If so, it could be having issues getting your location when you move to a new area. If you open google maps does it know your location within a few seconds or does it take some time to properly locate you? Also, what application is showing that your location is way off?
 
StereoOverDose said:
I also have trouble with mms, it will work if I use handcent though. Also the max cpu always resets to 1512 Mhz. Otherwise awesome Rom with good battery life, especially with an extended battery.
Click to expand...

1st, I get excellent battery life also. 2nd, I don't know what the deal is with MMS because since the latest update I have had no problem sending or receiving if and only if I turn 3g on before I send the MMS. I also have to have whoever is sending me a MMS to let me know because it sends to only receive them if I have 3g on before they send them. Weird I know but it works.
 
Just want to start off by giving a huge thanks for this wonderful ROM. I had previously tried CM10 and AOKP a few months ago but found them too buggy to depend on, so I switched back to an ICS ROM. Been using it for two days and haven't ran into any issues yet.

Anyways, my only question is whether there's a way to make the volume control more precise (use smaller increments) for this ROM. When I used ICS this could be accomplished using LeeDroid tweaks.

Thanks
 
Sorry its been a hectic work week but wanted to at least post up with the fix for the wimax log space issue. Basically instead of applying Ramjet73's fix as part of the installing process added an init.d script so it is now applied on boot. Also synced up to pull in any changes made by CM and swapped out "libhtc_ril.so" & "libhtc_ril_switch.so" using the Harmonia libs. Will need to let me know if you notice any difference. I have been using them over the last week and they seem to be working out better then those used previously from the last Stock update and Sprint libs before that. For the most part have been trying to use as many of the proprietary files from Harmonia in place of the Sprint files ware I can. So far at this point we are using the Harmonia Bluetooth firmware, touchscreen drivers, DRM related blobs and now ril libs. Still working on audio and wimax blobs, a bit more challenging but would love to move away from using the hacked up Wimax app. Have a few ideas but overall on both the VM and Sprint side there are much more experienced devs who have been working on the device much longer then the 3 or 4 month I spent working with G60 on the Rom so if at all possible will be just a bit slow moving to say the least but I get excellent coverage and would love an icon and toggle option.

Haven't experienced issues with MMS but the same was true with the 5/10 build but to reconfirm sent and received about a dozen over the last week. Tested a few with wifi on and with multiple users before posting so feedback from those who had experienced issues would be appreciated. Also looking for testers if anyone is interested feel free to send me a PM.

Have a decent amount of time this weekend so will be looking into extending battery life and HDMI. Started with HDMI last weekend tracking down all the HDMI related code from the Stock Evo V Kernel and comparing the differences with the 8660 common Kernel we are using so going to start by applying those differences in the Kernel and see what we get and go from there.

Otherwise looks like I'm starting to rant so will leave it there. Not a big comment poster as I end up spending more time on the forums then the Rom but I do read all that's posted every night for feedback so I do look into whats being reported so feedback is again appreciated.

Almost forgot, will look into the volume increments also. Had done this pretty easily working on CM7 on the Triumph so hopefully not much has changed and will be a sooner then later adjustment.

So until next time P!
 
Recently flashed this as well, and I must say it feels very stable! Very fast and responsive, and without bugs. Thanks Chairshot for picking up development, can't wait to see what you do with this!
 
I am still having the problem with the storage. Is this gap ok?
 

Attachments

  • uploadfromtaptalk1368845678051.jpg
    uploadfromtaptalk1368845678051.jpg
    48.5 KB · Views: 105
werewolfboy said:
I am still having the problem with the storage. Is this gap ok?
Click to expand...


If you don't mind and have a file explorer installed take a look in "data/wimax/log" and check if the directory is empty?


Also just a general note for anyone who has not wiped data. The above directory may still contain leftover data.
 
I noticed a command in one of the folders that targets the wimax folder. I found it by accident when looking around for another file I misplaced in the system partion. For some reason I keep on getting an error about that file in the logs. When I looked at it, everything looked fine. Should I post the log or should I just ignore it?
 
werewolfboy said:
I noticed a command in one of the folders that targets the wimax folder. I found it by accident when looking around for another file I misplaced in the system partion. For some reason I keep on getting an error about that file in the logs. When I looked at it, everything looked fine. Should I post the log or should I just ignore it?
Click to expand...

Depending on the file I am honestly not sure. Have been looking at the wimax all day and from the looks of it all the current jellybean Roms for Sprint / VM including Angry Bean are using a Gingerbread WIMAX app patched up to work with CM9 & CM10. From the way it looks as long as we use the WIMAX app there is not much that can be done about most of the WIMAX errors on the log. Is why access to the WIMAX log directory needs to be blocked as it just keeps filling up with these errors. I would like to think we can get around using the app and in doing so will eliminate the current issues. Otherwise logs never hurt so if you have it available may as well.
 
You must log in or register to reply here.
Back
Top Bottom