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

Root [ROM][ICS] Paranoid Android Ver1.6 Beta from source (31JUL2013)

Day one with CM9 tester and its good GPS seemed fast too so far so good. Also no roaming issues yet. That's my day one let's see what day two will bring.
 
Been running the July 24th tester on my wife's phone and mine. Have a strange thing happening. When we use the camera to take a series of pictures (20 or more) the phone will behave normal until it falls to about 40% battery and then will say the battery is dead and turn off. If I try to restart it will boot and say 0% battery and turn off again. If I pull battery for a few min and restart it will boot with 40% battery. If it was only occurring with one phone I would say battery, but it is happening with both.

I'm not sure but I think this may be an issue with the phone itself. I have had this happen multiple times - as recently as last night, in fact - on multiple ROMs on the same phone. Hopefully someone else can shed some light on this...?
 
Bsydz, thank you for your relentless hard work, this rom is amazing. It's unbelievable how far you have taken this rom, we all owe you man!

I'm using your new CM9 tester, and so far it's been flawless. Noticeably quicker than the last version I used (June).

Text still gets screwed up (known problem, and not a big deal to me)

No roaming issues so far.

I'll be using the GPS extensively this weekend and will post my results.

I'm more than willing to test anything that would be beneficial, this rom seems pretty much complete in my mind though thanks to you.

Thanks again!
 
I'm seeing the garbled text a bit more with the 7/24 than I did with the 7/20. Otherwise, things are very comparable for my uses. The GPS seemed to lock a little faster with the new one. All in all, awesome ROM!
 
Been running July 24th tester since it was posted on both my wife's phone and mine. I Don't know if its the apps or the OS having an issue, but my wife has been experiencing force closes, and even a few hard reboots with Instagram and Facebook. As I don't use either app I can't attest as to if it is a problem with the apps or some other problem. She was experiencing the same problems while running CM7. Was hoping that updating the OS would fix the issues. I don't think its an issue with her phone though as when I installed the apps on my phone and had her test the apps out it did the same exact things.
 
I installed the July 24th tester yesterday along with the Symlinked Gapps and here's what I have to report...

First things first, this is noticeably quicker than any previous build/tester I have installed. HOWEVER, with all the previous versions I had been using the tablet UI instead of the phone UI. After installing this tester I also flashed the "BSydz-PA-Stock-CM9-Mode-Changer.zip" that can be found in the OP. So, that being said, I don't know if this tester actually IS quicker or if my lag problems in the past had been related to using the tablet mode.

With the previous testers (again, in Tablet UI mode) there was often a lag between when I would press an icon and when it would actually register the press and then open. This doesn't seem to be an issue at all here with this build. There is still quite a bit of lag (3 to 5 seconds) from when I exit an app to when the home screen icons and widgets reappear. This is not a major problem for me, just a minor annoyance.

The statusbar button for the Torch/Flashlight does not work at all and I've found nowhere to remove it. Not a big problem since I always keep the icon for Torch on one of my home screens. It seems that if I try to turn on the Torch with the statusbar button and then go into the app, it won't work at all. The only fix I've found is to kill the Torch app and clear data, followed by a reboot.

I've mostly been at home and on my Wi-Fi since I installed this. The Wi-Fi icon in the statusbar randomly goes grey for a few seconds as if the signal was lost, but then it switches back to blue fairly quickly.

I've not played around with the GPS yet, though I reckon I'll probably have the opportunity tomorrow depending on where work takes me for the day. I seem to be one of the lucky few who has had good results with the GPS on my MT, so I don't imagine there will be any complaints from me regarding its performance.

The garbled text seems to be back in full force, and more prominent than ever. It's rather irritating to have to close an app, reopen it, and then find my way back to what I was doing. But I'm willing to live with the irritation in return for a decent ROM.

One final thing... I have not had any of the random reboots while using Facebook that both I and cowboy44mag reported a few days ago. But the Messaging app seems to enjoy suddenly closing. It does this at completely random times, such as when I open it, when I go into a specific conversation, and sometimes when I hit the send button on a message that I was composing. No warning of any kind, just a rapid exit back out to my home screen.

I hope the feedback helps. It seems there's only a few of us stragglers hanging around and commenting these days, so if anyone needs any further details or specifics please don't hesitate to ask. I don't have the knowledge to do dev work but I'm more than happy to test and provide feedback. Thanks for keeping the MT alive and kicking!
 
I spent a few hours at my girlfriend's house today and had the same issue with the Wi-Fi dropping off randomly, so I now know that it's not a problem with the router at my house. Also, I am still getting random reboots, mainly when using the Facebook app, but also a couple other times. I don't know how the Android OS manages memory but it seems that when the RAM gets filled up using memory-intensive apps like Facebook or Twitter, and the phone slows down as a result, this is when the phone reboots. Things slow down to a crawl, then totally stop, and finally the phone resets itself.
 
I spent a few hours at my girlfriend's house today and had the same issue with the Wi-Fi dropping off randomly, so I now know that it's not a problem with the router at my house. Also, I am still getting random reboots, mainly when using the Facebook app, but also a couple other times. I don't know how the Android OS manages memory but it seems that when the RAM gets filled up using memory-intensive apps like Facebook or Twitter, and the phone slows down as a result, this is when the phone reboots. Things slow down to a crawl, then totally stop, and finally the phone resets itself.

Back in the day Tickerguy did some stuff for setting up RAM limits. He mentioned things about garbage collection. I wonder if that is what he was talking about.
 
Back in the day Tickerguy did some stuff for setting up RAM limits. He mentioned things about garbage collection. I wonder if that is what he was talking about.

I'm only taking a guess that these random reboots are memory-related. I could be talking out my a$$ for all I know LOL

Another thing I have noticed in relation to this is that if things start slowing down, a reboot of my own (instead of waiting for a "forced reboot") seems to clear things up for a while.
 
I spent a few hours at my girlfriend's house today and had the same issue with the Wi-Fi dropping off randomly, so I now know that it's not a problem with the router at my house. Also, I am still getting random reboots, mainly when using the Facebook app, but also a couple other times. I don't know how the Android OS manages memory but it seems that when the RAM gets filled up using memory-intensive apps like Facebook or Twitter, and the phone slows down as a result, this is when the phone reboots. Things slow down to a crawl, then totally stop, and finally the phone resets itself.

My wifi also randomly disconnects. Thought it was my router so its good to hear im not the only one.
 
I'm only taking a guess that these random reboots are memory-related. I could be talking out my a$$ for all I know LOL

Another thing I have noticed in relation to this is that if things start slowing down, a reboot of my own (instead of waiting for a "forced reboot") seems to clear things up for a while.

I think there is an option under development for listing the amount of RAM that's used. It might be a memory leak issue.
 
I too have issues with the WiFi dropping out. It's primarily noticeable when I'm using AirDroid to move files. I've also had a lot of random reboots while using Navigation. I used it for about 1.5 hours this morning and it rebooted three times.
 
I've been running the Jul 24th rom since it was posted. I too was having some issues with different things, ie sending a pic message would take forever or just never send at all, wifi disconnects, texting issue, force closings, hard reboots. They were never all that prevalent, but I experienced all the above issues. My phone seems to be running much better after setting allow purging of assets under memory management in performance settings and setting the back button long press kill app feature. I have found that the phone runs much smoother, much longer and if I kill messaging app when I exit I don't have texting issues even when sending pictures. When I see the phone starting to run a little slower I reboot and everything runs great again (usually only need to reboot once or twice a day). Doing these simple steps seems to help the stability of the phone a lot.
 
I think there is an option under development for listing the amount of RAM that's used. It might be a memory leak issue.

I may be wrong but I think we are pushing the hardware about as far as it can be pushed. Newer phones designed for ICS and JB are dual and quad core running 2x the RAM (or more). I have a real gut feeling that we are simply running out of assets to the point the phone will do a hard reboot to clear itself.

The Jul 24th tester works pretty well if you don't mind tweaking and playing with the phone a little to get the performance out of it. At any rate considering the phone is over 2 years old, and most of us are on the $25 month plan there really isn't anything to complain about. Considering the hardware limitations this ROM is totally awesome.
 
I'm running the July 24 tester, have to say this version has been pretty awesome, I'm consistently getting 20+ hours on the battery. The GPS is connecting consistently, though I have hit the jumbled text issue it hasn't shown up as often as previous builds. today I used my GPS cardio trainer for a run while backgrounding the music app to my bluetooth headset, this did not cause any issue, the phone worked seamlessly. I currently have been using this battery for 16+ hours of which 1 hour was using both bluetooth and GPS at the same time, and I still have more than 50% left on the battery. this build is just amazing. GREAT JOB
 
I'm not having any reboots on the april rom.

I do have to clear the memory once in awhile (it may get sluggish)
 
New release, this should be solid, in most all aspects. Let me know how it goes for you. Check the OP.

For anybody interested, these are the things that I believe were the issues.

Jumbled Text:
The EGL/GPU drivers, which were discussed earlier in the thread. While it is still using the zues .so files, the firmware in /system/etc, I reverted to Cherry ROM files. So I believe that was what was causing the text jumble.
The random crashing and rebooting and wifi disconnects:
This seems to be kernel related, I only changed a few things and will go back later to narrow it down. So after testing the may kernel it fixed the issues. So then I tried just the zImage from the may kernel, and all good, so then I pulled in the kernel from github and ended up building with that and all was good. So the kernel in the paranoid git is the most stable and fast that I have built to date, for any devs out there.

The new auto brightness code:
Stock auto brightness code:
[HIGH]config_autoBrightnessLevels
<item>12</item>
<item>17</item>
<item>20</item>
<item>23</item>

config_autoBrightnessLcdBacklightValues
<item>51</item>
<item>128</item>
<item>178</item>
<item>230</item>
<item>255</item>

[/HIGH]New auto brightness code:

[HIGH]config_autoBrightnessLevels
<item>0</item>
<item>1</item>
<item>2</item>
<item>3</item>
<item>4</item>
<item>5</item>
<item>6</item>
<item>7</item>
<item>8</item>
<item>9</item>
<item>10</item>
<item>11</item>
<item>12</item>
<item>13</item>
<item>16</item>
<item>17</item>

config_autoBrightnessLcdBacklightValues
<item>20</item>
<item>30</item>
<item>45</item>
<item>60</item>
<item>75</item>
<item>90</item>
<item>105</item>
<item>120</item>
<item>135</item>
<item>150</item>
<item>165</item>
<item>180</item>
<item>195</item>
<item>210</item>
<item>225</item>
<item>240</item>
<item>255</item>
[/HIGH]Please feel free to mess with these in the display settings, and if you get a good setup please share it. ;)


I have some ideas on the camera and hdmi, and am going to pursue them after I get this setup in to CM9 and the JB ROMs.

Enjoy!
 
I may be wrong but I think we are pushing the hardware about as far as it can be pushed. Newer phones designed for ICS and JB are dual and quad core running 2x the RAM (or more). I have a real gut feeling that we are simply running out of assets to the point the phone will do a hard reboot to clear itself.

The Jul 24th tester works pretty well if you don't mind tweaking and playing with the phone a little to get the performance out of it. At any rate considering the phone is over 2 years old, and most of us are on the $25 month plan there really isn't anything to complain about. Considering the hardware limitations this ROM is totally awesome.

I have an Epic which has the same RAM and similar processor, besides half the ROM space. I'm running CM10.2.2 buttery smooth with every thing working. I don't think it will make it to Key Lime Pie, but ICS and JB will work in theese small environments. Our problem seems to be mostly with the lack of real programming experiance. I do feel that if we had backrounds in programming this wouldn't be so hard. I know that most of the issues can be worked out. We have BSydz, who is like the HotRodder who makes things work when an engineer would say that it couldn't be done because he didn't know it couldn't be done.

I have hopes for this phone, even though I don't use mine and my wife doesn't care:D
 
If no one responds, I'd say it should work. It looks like some preset parts for the apps listed in it.

Thanks for the reply. I was thinking there should be no problem with it either and flashed it, I only became concerned because I didn't see it listed in the OP anymore.
 
Back
Top Bottom