• 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]

ron scubadiver said:
Mirage kernel produces outstanding battery life at default settings on any ROM that it is compatible with. It was developed for stock ROM's.
Click to expand...
I concur, but have you been successful running MiRaGe with the current Angry Bean? If so I'd be very interested to know which kernel version you're using and what you did to get it working.

For me installing MiRaGe over any post-4/03 Angry Bean causes a hang at the white HTC boot screen, and any post-5/08 MiRaGe installed over Angry Bean 4/03 causes a bootloop early in the "Android is upgrading" process.
 
I have not tried Angry Bean. My reason for posting was someone had asked if a program like Kernel Tuner was used, and I knew that with Mirage the default settings were good.

I don't know if it will work, but Mac kernel also gives very good battery life.
 
I couldn't get mac kernel to boot. I have had no issues with kernel tuner with it although I mostly put it on for sweep to wake.
 
ron scubadiver said:
I have not tried Angry Bean. My reason for posting was someone had asked if a program like Kernel Tuner was used, and I knew that with Mirage the default settings were good.

I don't know if it will work, but Mac kernel also gives very good battery life.
Click to expand...

I'm not using kernel tuner or anything like that. Came from harmonia to this and couldn't be happier with battery life. Wi-Fi is on all the time to.
 
Because of new commits to Cyanogenmod and how fast they make changes, Kondik made a statement that third party kernels would break things. That's why this won't boot MAC or Mirage, I believe. Used to have a link to it, but don't know where it is anymore.
 
I wanted to use this rom with Anthrax kernel because it supports the mhl cable. I tried to flash anthrax, but after flashing it my phone could not get past the boot animation. Then I tired buttered toast and had the same problem. Why does anthrax and buttered toast not work with this rom? Is there any way I can get mhl working?

My main goal is to get mhl working with a jb rom. This is the best jb rom that I have tried out, so I was hoping that someone could help.
 
asdfjkljkl5 said:
Why does anthrax and buttered toast not work with this rom?
Click to expand...
This whole thread is worth a read... your question was answered two posts above yours.

Unless a kernel dev magnanimously decides to bite the bullet and branch one of these kernels to actively chase AOSP development, this will not happen. To date none of the primary players have had the bandwidth to do more than the very occasional AOSP 4.2 test build... I've not seen any recent examples on the threads I follow, and some of those test builds had multiple reports of problems.

As I've mentioned a couple of times here, Angry Bean 04/03 was the last version that seemed to work with most custom kernels... chairshot, perhaps you could also provide that version in the OP & repo, with a YMMV caveat for those who would rather have a custom kernel than the latest ROM? I can provide it if you (chairshot) don't have it.
 
I just took Angry Bean for a test drive.

It was a bit inconvenient for me to make the switch because my customized deodexed stock 2.95 rom will not boot on 1.50 or 1.04. After flashing hboot I had to remove the battery and delete the hboot from the root of my sdcard. It would have been easier if I had used fastboot. After some messing around, it did boot.

WiFi tethering worked via the built in app. 4G worked, but it is not convenient to enable. The led stayed green all the time, I don't know why. I could not change the dates in the data usage area of settings. It seemed stuck on 30 days ending with today. No Frills CPU reported 1512 Mhz, reducing the need for a kernel swap.

I guess now I know why some of the launchers look the way that they do since they all must have copied the look of 4.2. I can't say that I am a big fan of sense, but it doesn't bother me either.

Since my stock based ROM gets great battery life with Mirage kernel and it has some crucial mods that I like (30 step volume control, dim led's, hyperlinks) it is difficult to get me to budge off of it, so I reverted.

However, I have tried many ROM's and Angry Bean looks like one of the better choices out there. It would particularly appeal to those who don't like Sense, want a version of Google Now that is not crippled, or just want the latest thing.
 
mrbenji said:
I concur, but have you been successful running MiRaGe with the current Angry Bean? If so I'd be very interested to know which kernel version you're using and what you did to get it working.

For me installing MiRaGe over any post-4/03 Angry Bean causes a hang at the white HTC boot screen, and any post-5/08 MiRaGe installed over Angry Bean 4/03 causes a bootloop early in the "Android is upgrading" process.
Click to expand...


I had answered a similar question at XDA thread.
http://forum.xda-developers.com/showpost.php?p=41806156&postcount=444
 
Does anyone else get issues with all cell service not working? I get points where texts don't send and it requires a reboot to send and receive as well as calls. All in all that's annoying to no end. Other than that rock solid ROM except for mediocre battery life.
 
landonh12 said:
Does anyone else get issues with all cell service not working? I get points where texts don't send and it requires a reboot to send and receive as well as calls. All in all that's annoying to no end. Other than that rock solid ROM except for mediocre battery life.
Click to expand...

Only problem is when I am making a call or getting a call while on Bluetooth the call crashes and hard reboot occurs.
 
mrg666 said:
Edit: Also, I wouldn't release a kernel for any of the JB ROMs unless coordinated with the ROM devs since this will make fixing bugs much more complicated for both sides.
Click to expand...

Would most definitely concur. Prior to the last release was syncing to use the Team Hydra Kernel but after the 5/2 build it would no longer boot. Have been playing around the last few month but am far from a Kernel dev and have been at this point learning by looking at differences between the stock and other Kernels and see what either shows improvement or blows something up. Kinda got a crash course after breaking apart from the Hydra Kernel and needed to revert a few commits to get things working again and regain some stability including the Ion commits. Still with that said Angry Bean is kinda its own monster compared to some of the other JB Roms for Sprint/VM in that allot of the Vendor Blobs and other proprietary files used are coming from Stock Evo V and is being developed with VM users in mind. In doing this a few changes needed to be made in the Kernel or Ramdisk. Nothing major but for example needed an edit in the "init.shooter.rc" for the new DRM Blobs and an additional line in the "shooter_deconfig" for the change in BT firmware. So in other words at this point there are a few specific things that separate Angry Bean from the other JB Roms developed for both Sprint and VM.
 
Chairshot215 said:
Would most definitely concur. Prior to the last release was syncing to use the Team Hydra Kernel but after the 5/2 build it would no longer boot. Have been playing around the last few month but am far from a Kernel dev and have been at this point learning by looking at differences between the stock and other Kernels and see what either shows improvement or blows something up. Kinda got a crash course after breaking apart from the Hydra Kernel and needed to revert a few commits to get things working again and regain some stability including the Ion commits. Still with that said Angry Bean is kinda its own monster compared to some of the other JB Roms for Sprint/VM in that allot of the Vendor Blobs and other proprietary files used are coming from Stock Evo V and is being developed with VM users in mind. In doing this a few changes needed to be made in the Kernel or Ramdisk. Nothing major but for example needed an edit in the "init.shooter.rc" for the new DRM Blobs and an additional line in the "shooter_deconfig" for the change in BT firmware. So in other words at this point there are a few specific things that separate Angry Bean from the other JB Roms developed for both Sprint and VM.
Click to expand...

Have you reverted ION back to PMEM both in kernel and ROM? I would be happy to see your changes if you have a repo. I am testing MiRaGe (the same kernel for ICS/Sense) with AOKP 4.2.2 right now, it works just fine when the ROM and kernel are built for each other. I had to upgrade the bluetooth stack but this didn't break the compatibility with ICS/Sense.
 
mrg666 said:
Have you reverted ION back to PMEM both in kernel and ROM? I would be happy to see your changes if you have a repo. I am testing MiRaGe (the same kernel for ICS/Sense) with AOKP 4.2.2 right now, it works just fine when the ROM and kernel are built for each other. I had to upgrade the bluetooth stack but this didn't break the compatibility with ICS/Sense.
Click to expand...
Ok, *now* I'm getting excited. The dev for my favorite kernel is talking to the dev for my favorite ROM! Woo-hoo! Angry Bean would so benefit from MiRaGe. :D
 
I always set the display intensity on auto brightness, so it's very low in low light conditions. It helps tremendously. Just configure starting at about 13% then gradually increase. Just fiddle with it and you'll get a more rounded response. Also, I drop the max CPU speed to about 1400Mhz which also helps.
 
mrg666 said:
Have you reverted ION back to PMEM both in kernel and ROM? I would be happy to see your changes if you have a repo. I am testing MiRaGe (the same kernel for ICS/Sense) with AOKP 4.2.2 right now, it works just fine when the ROM and kernel are built for each other. I had to upgrade the bluetooth stack but this didn't break the compatibility with ICS/Sense.
Click to expand...

For the most part at the time they had been making the ion commits and reversing them the next day for about a week. It had looked like at the time they were having issues getting it to work correctly so what I did was fork the Kernel and then did a rebase for those commits and then figured when they had settled down I would check them out later. They had added Ion into the shooter Team Hydra device files.

https://github.com/Team-Hydra/andro...mmit/bac6fe8ff41af865ab3ee6fb3aa8f2573246a3e4

but I had never made the changes in the Angry Bean shootervm device files. These are the Angry Bean repository's.

https://github.com/HTCCM10
 
Chairshot215 said:
For the most part at the time they had been making the ion commits and reversing them the next day for about a week. It had looked like at the time they were having issues getting it to work correctly so what I did was fork the Kernel and then did a rebase for those commits and then figured when they had settled down I would check them out later. They had added Ion into the shooter Team Hydra device files.

https://github.com/Team-Hydra/andro...mmit/bac6fe8ff41af865ab3ee6fb3aa8f2573246a3e4

but I had never made the changes in the Angry Bean shootervm device files. These are the Angry Bean repository's.

https://github.com/HTCCM10
Click to expand...

Thanks! I will check the repo. ION is a tricky transition for a device like EVO3D that was released with PMEM. Since the stock kernel and ROM were not developed by HTC with ION, the KGSL driver and other media drivers in the EVO 3D kernel source need to be updated. Some of the user-space libraries will also require update due to incompatibilities after the drivers updated ... I think your decision to rebase was a good one.
 
MtDewFella said:
I can't get wimax to connect, anyone else having this problem?
Click to expand...
WiMax is very fussy on this ROM, but I've been able to work out a routine that works in most cases.

For starters, I always fiddle with WiMax using the full WiMax settings screen, not by trying to toggle the Power Widget or Power Toggles icons. I've never been able to get those toggles to work reliably. I do have both icons enabled, though: the Power Widget icon so I can long-press it to go to the WiMax settings directly, and the Power Toggles icon because it accurately displays WiMax status (grey=off, green=on, yellow=connection issue).

My best results have come by disabling 4G when I know I'm going to be in a WiFi area for a while (ex. at home), then enabling it once I've left the WiFi area.

Sometimes I'll find 4G enabled but failing to connect... usually that's when I had failed to disable it at home. This is usually fixed by waiting until the checkbox is selectable, disabling it, waiting until it says "disconnected," then reconnecting.

Every once in a while that doesn't work either, but I'm always able to get it working again after a system reboot.

Hope this helps.
 
You must log in or register to reply here.
Back
Top Bottom