[ROM] AngelRom Rhapsody v1.00 [ Abyss KERNEL v1.5]

[DeiphoneaAndroid]

Sorry to ask guys do i need to root phpne before installation and put cwm on or just download rom and flash

You need to root the phone and have CWM available.

 

[hkfriends]

This rom seems drain battery a lot

 

[The_Steph]

I used before this ROM, Sheep 1.2, and now that I moved to AngelRom 1.0 (with 1.1 Kernel), I couldn't agree more with hkfriends.

Despite the fact that I removed a lot of stuff from AngelRom to lighten it, I can only feel its speed which is unfortunately counterbalanced by a huge battery drain.

Please do note that this is not a complaint but just a warning.

Nevertheless, ROM is amazingly fast!

 

[piit79]

is the rom wipe/non wipe btw? thanks.

This ROM automatically wipes all user when installing. I was a bit surprised by that, lucky that I had a full backup which worked like a charm.

 

[Chris X.]

This rom seems drain battery a lot

Pls wipe the batstats via CWM.

How?

- charge to 100% when the phone is on
- then turn phone off and don't unplug the cable
- now charge again to 100%
- when its done, unplug the cable and go to CWM and wipe the batstatts
- reboot CWM
- reboot phone

 

[RiverSource]

Hello,

//EDIT: Please have a look in post #72 too!

I tried your Kernel (v1.1). I flashed it on my ROM, so there are no init.d scripts responsible for that.

It has the same problem, which I encountered in the beginning of my own tries. See the logcat:

<7>[20817.005234] usb 1-2: svn L2 p.s=1
<7>[20817.005853] ehci_hub_control:send Port suspend
<7>[20817.012675] modemctl modemctl: svn <HOST_WUP:0
<7>[20817.012701] usbsvn_request_resume:run time resume
<7>[20817.070160] usb_port_resume = 1283, 4
<7>[20817.070914] usb 1-2: svn L0 p.s=1
<7>[20817.071047] modemctl modemctl: svn <HOST_WUP:1
<7>[20817.071066] modemctl modemctl: svn >SLAV_WUP:0,0
<7>[20817.764439] IPC:RX size=16
<7>[20817.764583] buf:7F 0E 00 00  0B 00 FF 25  07 01 03 FF  04 00 05 7E
<7>[20818.005629] usb 1-2: svn L2 p.s=1
<7>[20818.007583] ehci_hub_control:send Port suspend
<7>[20818.014491] modemctl modemctl: svn <HOST_WUP:0
<7>[20818.014596] usbsvn_request_resume:run time resume
<7>[20818.070642] usb_port_resume = 1283, 4
<7>[20818.072157] usb 1-2: svn L0 p.s=1
<7>[20818.072685] modemctl modemctl: svn <HOST_WUP:1
<7>[20818.072776] modemctl modemctl: svn >SLAV_WUP:0,0
<6>[20818.129819] max17042 9-0036: max17042_get_soc : soc(4cf3)
<6>[20818.129931] max17042 9-0036: max17042_get_soc : use raw (76), soc (77)
<7>[20819.005547] usb 1-2: svn L2 p.s=1
<7>[20819.007157] ehci_hub_control:send Port suspend
<7>[20819.014134] modemctl modemctl: svn <HOST_WUP:0
<7>[20819.014242] usbsvn_request_resume:run time resume
<7>[20819.070433] usb_port_resume = 1283, 4
<7>[20819.071647] usb 1-2: svn L0 p.s=1
<7>[20819.072179] modemctl modemctl: svn <HOST_WUP:1
<7>[20819.072268] modemctl modemctl: svn >SLAV_WUP:0,0
<6>[20819.781138] sec-battery sec-battery: sec_bat_check_vf: Battery Health (1)
<6>[20819.782240] smb328-charger 19-0034: smb328_get_charging_health : charging status A(0x03)
<6>[20819.783275] smb328-charger 19-0034: smb328_get_charging_health : charging status B(0x00)
<6>[20819.784297] smb328-charger 19-0034: smb328_get_charging_health : charging status C(0x05)
<6>[20819.784419] smb328-charger 19-0034: smb328_get_property: smb328_get_property (2,1)
<7>[20820.005158] usb 1-2: svn L2 p.s=1
<7>[20820.005628] ehci_hub_control:send Port suspend
<7>[20820.012325] modemctl modemctl: svn <HOST_WUP:0
<7>[20820.012335] usbsvn_request_resume:run time resume
<7>[20820.070122] usb_port_resume = 1283, 4
<7>[20820.070734] usb 1-2: svn L0 p.s=1
<7>[20820.070785] modemctl modemctl: svn <HOST_WUP:1
<7>[20820.070793] modemctl modemctl: svn >SLAV_WUP:0,0
<7>[20821.005527] usb 1-2: svn L2 p.s=1
<7>[20821.007103] ehci_hub_control:send Port suspend
<7>[20821.014000] modemctl modemctl: svn <HOST_WUP:0
<7>[20821.014105] usbsvn_request_resume:run time resume
<7>[20821.070452] usb_port_resume = 1283, 4
<7>[20821.084406] usb 1-2: svn L0 p.s=1
<7>[20821.084936] modemctl modemctl: svn <HOST_WUP:1
<7>[20821.085027] modemctl modemctl: svn >SLAV_WUP:0,0
<7>[20822.005241] usb 1-2: svn L2 p.s=1
<7>[20822.005833] ehci_hub_control:send Port suspend
<7>[20822.012525] modemctl modemctl: svn <HOST_WUP:0
<7>[20822.012551] usbsvn_request_resume:run time resume
<7>[20822.070186] usb_port_resume = 1283, 4
<7>[20822.071040] usb 1-2: svn L0 p.s=1
<7>[20822.071176] modemctl modemctl: svn <HOST_WUP:1
<7>[20822.071196] modemctl modemctl: svn >SLAV_WUP:0,0
<7>[20823.005269] usb 1-2: svn L2 p.s=1
<7>[20823.005866] ehci_hub_control:send Port suspend
<7>[20823.012627] modemctl modemctl: svn <HOST_WUP:0
<7>[20823.012652] usbsvn_request_resume:run time resume
<7>[20823.070182] usb_port_resume = 1283, 4
<7>[20823.070911] usb 1-2: svn L0 p.s=1
<7>[20823.071045] modemctl modemctl: svn <HOST_WUP:1
<7>[20823.071065] modemctl modemctl: svn >SLAV_WUP:0,0
<7>[20824.005152] usb 1-2: svn L2 p.s=1
<7>[20824.005629] ehci_hub_control:send Port suspend
<7>[20824.012343] modemctl modemctl: svn <HOST_WUP:0
<7>[20824.012351] usbsvn_request_resume:run time resume
<7>[20824.070132] usb_port_resume = 1283, 4
<7>[20824.070737] usb 1-2: svn L0 p.s=1
<7>[20824.070782] modemctl modemctl: svn <HOST_WUP:1
<7>[20824.070788] modemctl modemctl: svn >SLAV_WUP:0,0
<6>[20824.880298] sec-battery sec-battery: sec_bat_check_vf: Battery Health (1)
<6>[20824.880764] smb328-charger 19-0034: smb328_get_charging_health : charging status A(0x03)
<6>[20824.881218] smb328-charger 19-0034: smb328_get_charging_health : charging status B(0x00)
<6>[20824.881671] smb328-charger 19-0034: smb328_get_charging_health : charging status C(0x05)
<6>[20824.881679] smb328-charger 19-0034: smb328_get_property: smb328_get_property (2,1)
<7>[20825.005135] usb 1-2: svn L2 p.s=1
<7>[20825.005630] ehci_hub_control:send Port suspend
<7>[20825.012331] modemctl modemctl: svn <HOST_WUP:0
<7>[20825.012339] usbsvn_request_resume:run time resume
<7>[20825.070126] usb_port_resume = 1283, 4
<7>[20825.070737] usb 1-2: svn L0 p.s=1
<7>[20825.070780] modemctl modemctl: svn <HOST_WUP:1
<7>[20825.070787] modemctl modemctl: svn >SLAV_WUP:0,0
<7>[20826.005535] usb 1-2: svn L2 p.s=1
<7>[20826.007621] ehci_hub_control:send Port suspend
<7>[20826.014583] modemctl modemctl: svn <HOST_WUP:0
<7>[20826.014689] usbsvn_request_resume:run time resume
<7>[20826.070421] usb_port_resume = 1283, 4
<7>[20826.071772] usb 1-2: svn L0 p.s=1
<7>[20826.072295] modemctl modemctl: svn <HOST_WUP:1
<7>[20826.072383] modemctl modemctl: svn >SLAV_WUP:0,0
<7>[20827.005199] usb 1-2: svn L2 p.s=1
<7>[20827.005789] ehci_hub_control:send Port suspend
<7>[20827.012551] modemctl modemctl: svn <HOST_WUP:0
<7>[20827.012566] usbsvn_request_resume:run time resume
<7>[20827.070156] usb_port_resume = 1283, 4
<7>[20827.070886] usb 1-2: svn L0 p.s=1
<7>[20827.070968] modemctl modemctl: svn <HOST_WUP:1
<7>[20827.070980] modemctl modemctl: svn >SLAV_WUP:0,0
<7>[20828.005596] usb 1-2: svn L2 p.s=1
<7>[20828.007258] ehci_hub_control:send Port suspend
<7>[20828.014262] modemctl modemctl: svn <HOST_WUP:0
<7>[20828.014372] usbsvn_request_resume:run time resume
<7>[20828.070371] usb_port_resume = 1283, 4
<7>[20828.071650] usb 1-2: svn L0 p.s=1
<7>[20828.072169] modemctl modemctl: svn <HOST_WUP:1
<7>[20828.072259] modemctl modemctl: svn >SLAV_WUP:0,0
<6>[20828.171045] max17042 9-0036: max17042_get_soc : soc(4cf3)
<6>[20828.171157] max17042 9-0036: max17042_get_soc : use raw (76), soc (77)
<7>[20829.005529] usb 1-2: svn L2 p.s=1
<7>[20829.007440] ehci_hub_control:send Port suspend
<7>[20829.014365] modemctl modemctl: svn <HOST_WUP:0
<7>[20829.014470] usbsvn_request_resume:run time resume
<7>[20829.070431] usb_port_resume = 1283, 4
<7>[20829.071764] usb 1-2: svn L0 p.s=1
<7>[20829.072276] modemctl modemctl: svn <HOST_WUP:1
<7>[20829.072367] modemctl modemctl: svn >SLAV_WUP:0,0
<6>[20829.981131] sec-battery sec-battery: sec_bat_check_vf: Battery Health (1)
<6>[20829.982230] smb328-charger 19-0034: smb328_get_charging_health : charging status A(0x03)
<6>[20829.983265] smb328-charger 19-0034: smb328_get_charging_health : charging status B(0x00)
<6>[20829.984291] smb328-charger 19-0034: smb328_get_charging_health : charging status C(0x05)
<6>[20829.984413] smb328-charger 19-0034: smb328_get_property: smb328_get_property (2,1)
<7>[20830.005506] usb 1-2: svn L2 p.s=1
<7>[20830.007480] ehci_hub_control:send Port suspend
<7>[20830.014342] modemctl modemctl: svn <HOST_WUP:0
<7>[20830.014446] usbsvn_request_resume:run time resume
<7>[20830.070449] usb_port_resume = 1283, 4
<7>[20830.072024] usb 1-2: svn L0 p.s=1
<7>[20830.072550] modemctl modemctl: svn <HOST_WUP:1
<7>[20830.072638] modemctl modemctl: svn >SLAV_WUP:0,0
<7>[20831.005240] usb 1-2: svn L2 p.s=1
<7>[20831.005985] ehci_hub_control:send Port suspend
<7>[20831.012778] modemctl modemctl: svn <HOST_WUP:0
<7>[20831.012804] usbsvn_request_resume:run time resume
<7>[20831.070181] usb_port_resume = 1283, 4
<7>[20831.070912] usb 1-2: svn L0 p.s=1
<7>[20831.071045] modemctl modemctl: svn <HOST_WUP:1
<7>[20831.071064] modemctl modemctl: svn >SLAV_WUP:0,0
<7>[20832.005554] usb 1-2: svn L2 p.s=1
<7>[20832.007470] ehci_hub_control:send Port suspend
<7>[20832.014358] modemctl modemctl: svn <HOST_WUP:0
<7>[20832.014465] usbsvn_request_resume:run time resume
<7>[20832.070441] usb_port_resume = 1283, 4
<7>[20832.071782] usb 1-2: svn L0 p.s=1
<7>[20832.072299] modemctl modemctl: svn <HOST_WUP:1
<7>[20832.072388] modemctl modemctl: svn >SLAV_WUP:0,0

I described it here in the first post:

I had a problem with endless USB Port Suspend / Resume cycles during testing, which caused the phone not to enter the deep sleep. Maybe the reason were to optimistic compiler options (it did not occur in the last 24 hours).

This error appears sporadic. I was not able to trigger it through a specific event (USB usage, charger connected/disconneted, flight mode, ...).

I'm also not sure, if it is really caused by compiler optimizations. Meanwhile I think, it were wrong applied fuzzy patches from the 2.6.35.14 patches. Maybe you should have a closer look at all fuzzy messages from patch.

 

[Chris X.]

@ RiverSource

Tried it also. No chance @ this moment.

 

[RiverSource]

By the way: Did you patch "your own" source, or did you start from my sources published in the FM kernel thread? This question is somehow important to me, since maybe the bug "sleeps" in my code, although it does not appear at the moment in my kernel.

If you patched your own sources, it is from my point of view likely a problem with patches. If you started from my source, we should try to analyse the problem deeper. Feel free to contact me, in case you would like to do so.

 

[joggie555]

There is some lag in the s memo.

Sent from my GT-N7000 using XDA App

 

[jason370]

Sorry don't mean to be Mr negative here but I just lost 47% battery in the six hours I slept. I get 6400 antutu scores from every rom I've flashed thus far, and considering how ugly the icons, fonts and themes are in this rom I'm a bit confused about what all the fuss is about here.

What am I missing?



Sent from my GT-N7000 using xda premium

 

[RiverSource]

Again its me.

Please have a look in your code at the following code fragment from drivers/usb/core/hub.c (Line 713):

		if (type == HUB_INIT) {
			delay = hub_power_on(hub, false);
			PREPARE_DELAYED_WORK(&hub->init_work, hub_init_func2);
			schedule_delayed_work(&hub->init_work,
					msecs_to_jiffies(delay));

			/* Suppress autosuspend until init is done */
			usb_autopm_get_interface_no_resume(
					to_usb_interface(hub->intfdev));
			return;		/* Continues at init2: below */
[COLOR="Green"]		} else if (type == HUB_RESET_RESUME) {
			/* The internal host controller state for the hub device
			 * may be gone after a host power loss on system resume.
			 * Update the device's info so the HW knows it's a hub.
			 */
			hcd = bus_to_hcd(hdev->bus);
			if (hcd->driver->update_hub_device) {
				ret = hcd->driver->update_hub_device(hcd, hdev,
						&hub->tt, GFP_NOIO);
				if (ret < 0) {
					dev_err(hub->intfdev, "Host not "
							"accepting hub info "
							"update.\n");
					dev_err(hub->intfdev, "LS/FS devices "
							"and hubs may not work "
							"under this hub\n.");
				}
			}
			hub_power_on(hub, true);
		} else {
[/COLOR]			hub_power_on(hub, true);
[COLOR="Red"]#if defined(CONFIG_SAMSUNG_PHONE_SVNET)
			if (type == HUB_RESET_RESUME) {
				struct usb_hcd *hcd = bus_to_hcd(hdev->bus);
				if (hcd->driver->wait_for_device)
					hcd->driver->wait_for_device(hcd);
			}
#endif[/COLOR]

The green part is added in 2.6.35.14, it is not available in 2.6.35.7. The red code is from Samsung. It is obvious, that the Samsung code will not be executed any more. This is one off the fuzzy patches I have mentioned. I think, that this could cause the problem, although I'm not completely sure.

As I said, I encountered the same problem. After I resolved every fuzzy patch by hand, the problem was gone. I could imagine, that this was the reason for this problem.

 

[marianoitalianoo]

and your point is ? Try it , do not like it ... flash back. This is not AA meeting nobody is interested in ur point of view.

chill dude

Sorry don't mean to be Mr negative here but I just lost 47% battery in the six hours I slept. I get 6400 antutu scores from every rom I've flashed thus far, and considering how ugly the icons, fonts and themes are in this rom I'm a bit confused about what all the fuss is about here.

What am I missing?



Sent from my GT-N7000 using xda premium

 

[rockky]

You forgot to insert the phrase 'in my opinion'. Many like the icons and fonts.....but if your the final ruling judge on all this..well my apologies.

QUOTE=jason370;19716648]Sorry don't mean to be Mr negative here but I just lost 47% battery in the six hours I slept. I get 6400 antutu scores from every rom I've flashed thus far, and considering how ugly the icons, fonts and themes are in this rom I'm a bit confused about what all the fuss is about here.

What am I missing?



Sent from my GT-N7000 using xda premium[/QUOTE]

 

[DominionZA]

So glad we are finally getting some custom ROMs
Of the ones available, this is the best IMO. But ye, battery drain a bit hectic. I will live with it until future updates sort it as my Note is sooooo smooth now.
Big thanks!

 

[marianoitalianoo]

Hello

I flashed this ROM with kernel [AbyssNote][v1.1]

Used Smartass gov with SetCpu

Performed batstat reset

as Chris X. wrote

- charge to 100% when the phone is on
- then turn phone off and don't unplug the cable
- now charge again to 100%
- when its done, unplug the cable and go to CWM and wipe the batstatts
- reboot CWM
- reboot phone

And it doesn't seem to drain battery so dramatically but anyway there will be a fix soon

Big thx to angelom

 

[rockky]

So guys....a little research on the governors just had my head swimming.
Can you recommend
1. An ideal governor for this rom (I'm using interactivex...not exactly sure why lol)
2. Are any SetCpU profiles recommended?
Thanks

 

[jason370]

and your point is ? Try it , do not like it ... flash back. This is not AA meeting nobody is interested in ur point of view.

chill dude

1) I did flash back, to KK1
2) you might consider taking your own advice as far as chilling is concerned

Look, it seems a perfectly fine rom, well aside from the worst battery drain I've ever experienced and you know.. .the icons. But let's be clear about one thing...

My battery drain comment was fact, not opinion. After reading thousands of posts on this site, in multiple forums, for multiple devices I can say with complete certitude that BATTERY DRAIN IS FAR AND AWAY THE NUMBER ONE ISSUE which concerns 99% of the people who read this forum.

I asked what am I missing, in earnest because I don't see it, and I'm quite qualified TO see it. Then you reply with YOUR opinion, which I'd argue nobody wants to hear, since it has absolutely nothing to do with the workings of this rom.

At least I directed my comments toward the rom.

Respectfully,
Jason

Sent from my GT-N7000 using xda premium

 

[ampelift]

Very fast and stable
Horrible battery drain

 

[angelom]

Again its me.

Please have a look in your code at the following code fragment from drivers/usb/core/hub.c (Line 713):

		if (type == HUB_INIT) {
			delay = hub_power_on(hub, false);
			PREPARE_DELAYED_WORK(&hub->init_work, hub_init_func2);
			schedule_delayed_work(&hub->init_work,
					msecs_to_jiffies(delay));

			/* Suppress autosuspend until init is done */
			usb_autopm_get_interface_no_resume(
					to_usb_interface(hub->intfdev));
			return;		/* Continues at init2: below */
[COLOR="Green"]		} else if (type == HUB_RESET_RESUME) {
			/* The internal host controller state for the hub device
			 * may be gone after a host power loss on system resume.
			 * Update the device's info so the HW knows it's a hub.
			 */
			hcd = bus_to_hcd(hdev->bus);
			if (hcd->driver->update_hub_device) {
				ret = hcd->driver->update_hub_device(hcd, hdev,
						&hub->tt, GFP_NOIO);
				if (ret < 0) {
					dev_err(hub->intfdev, "Host not "
							"accepting hub info "
							"update.\n");
					dev_err(hub->intfdev, "LS/FS devices "
							"and hubs may not work "
							"under this hub\n.");
				}
			}
			hub_power_on(hub, true);
		} else {
[/COLOR]			hub_power_on(hub, true);
[COLOR="Red"]#if defined(CONFIG_SAMSUNG_PHONE_SVNET)
			if (type == HUB_RESET_RESUME) {
				struct usb_hcd *hcd = bus_to_hcd(hdev->bus);
				if (hcd->driver->wait_for_device)
					hcd->driver->wait_for_device(hcd);
			}
#endif[/COLOR]

The green part is added in 2.6.35.14, it is not available in 2.6.35.7. The red code is from Samsung. It is obvious, that the Samsung code will not be executed any more. This is one off the fuzzy patches I have mentioned. I think, that this could cause the problem, although I'm not completely sure.

As I said, I encountered the same problem. After I resolved every fuzzy patch by hand, the problem was gone. I could imagine, that this was the reason for this problem.

Yes, this is the reason of the problem. With a fix the kernel go into deep sleep very well now. Many thanks RiverSource

 

[airbillion]

Yes, this is the reason of the problem. With a fix the kernel go into deep sleep very well now. Many thanks RiverSource

Angel,

Are you going to post the fixed kernel any time soon?

I hope so because this kernel is great except for the battery drain.

Thanks