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

The back button issue is a hardware issue, as far as I can tell. It is the same on all ROMs and kernels. It even happens in recovery.

I have been doing some reading on touchscreen implementation and have reworked the touch drivers. I have put together 2 versions. Nothing has changed from 06MAY build except touch screen drivers.

BSydz_Pa-Touch2-kernel-CM9.zip

BSydz_Pa-Touch3-kernel-CM9.zip

I need detailed comparisons between touch1 kernel included in 06MAY ROM, touch2 kernel, and touch3 kernel. Please only provide relevant info pertaining to the touch screen please. This is not gonna break GPS or make your favorite app fc, only one thing has changed and that is touchscreen.

I did all this from my phone, I'll clean it up when I get on a PC.

Touch 3 seems smoother than touch 1. I have not flashed touch 2 yet. I'll continue to use touch 3 today and report back with more detailed results.
 
So doing a factory reset, formatting cache, and wiping Dalvik on EVERY attempt is not good enough? Would be nice if anyone had actually mentioned a need for unusual procedures on this install.
Well usually do all those 2 times when coming from another ROM.Some people say you don't have to do it twice but I always do it twice.
 
Hey, everything seems to be working good, just one thing though. When im in a phone call my screen keeps flashing on and off, Does anyone else have this problem?
 
When pressing the wifi button in the status bar, it takes longer than usual to toggle off wifi. I also got the roaming issue once this afternoon.
 
I'm on this ROM and it was working fine yesterday. Does anyone know a reason why mobile data would stop working today? Heidi's VM phone works fine on mobile data. Text and phone still seem to work for me, and so does WiFi, but mobile data isn't working today. ...
Fixed: I called VM (after trying a few ROMS with no luck), and they said my account had no data and it is a known issue for some users, and that they "are running a script every day to work around the issue until a permanent fix could be put in place" [but my data has been down for more than 1 day, so it apparently wasn't helping me]. The fix they used to get my phone data working was for them to add $25 to my account and to restart my month for me [my month had started just 2 days ago anyway].
 
Repeated flashes haven't helped, and the keyboard finally got its act together for me with CM9, so I don't think it's a device issue at this stage (and yes, I do know how to flash a ROM).

Bad download is a possibility, granted.

Are you restoring apps?

The first thing I would do is load the ROM and gapps. Then try to use it for a day or two. Then try adding app you know (for sure) are safe. Finally your "wanted" apps. It seems to be an app interruption as it happens across ROMs
 
Are you restoring apps?

The first thing I would do is load the ROM and gapps. Then try to use it for a day or two. Then try adding app you know (for sure) are safe. Finally your "wanted" apps. It seems to be an app interruption as it happens across ROMs

Problem was that I had a couple of apps I needed to use pretty much right away. As you know, I did manage to sort that out, though.
 
Fixed: I called VM (after trying a few ROMS with no luck), and they said my account had no data and it is a known issue for some users, and that they "are running a script every day to work around the issue until a permanent fix could be put in place" [but my data has been down for more than 1 day, so it apparently wasn't helping me]. The fix they used to get my phone data working was for them to add $25 to my account and to restart my month for me [my month had started just 2 days ago anyway].

I posted a thread about this exact thing its called looping
 
If you don't wipe the phone correctly coming from CM7 to PA then the libs for the CM7 keyboard can still be there which will cause the libs for the keyboard for PA to not work.Now if you do the same for PA to CM9 then it's not going to affect it that much.Yes there will be issues if you don't wipe correctly but less if you are staying with same android version (2.3 to 2.3 or 4.0 to 4.0).When you change from like a 2.2 or 2.3 to a 4.0 you are making MAJOR changes.I'm just putting out there what I KNOW will cause the issue seeing NO ONE else has reported this.Keyboard works flawless on everything I use(Skype,KiK,Texting,Words with friends,ooVoo,GMail,TextNow,Facebook,and Maps all have working keyboard)

Okay, I studied and worried for nearly two weeks before my (successful) attempt at switching from stock ROM to CM7- and now I'm nervous about switching from CM7 to PA.
Can someone explain it step-by-step....as if you were talking to a 12 year-old? :o

.....Yes there will be issues if you don't wipe correctly.....

Yes, my mommy taught me that when I was potty trained. :rolleyes:
 
would be nice if we could have a ROM that we can make into a stable release on the triumph.

besides camera issues,


one of my problems I am having is trying to change my governor settings. it's stuck on interactive. However I want to switch it to smoothass.

whenever I do try to change the governor settings, I lose the functionality to change my min/max clock speeds.

also, would it be possible to bring up the RTN menu within the ROM?

I know I can gain access via stock rom by entering on the dial pad: ##RTN#

Hope this helps, good luck on cracking the Triumph
 
Hey there! Just wanted to say this rom is AMAZING! I have the may 6 version installed and its super smooth and more responsive than the April version. It's perfect as my daily. It's great that you guys were able to get both cameras working even if its just for taking pictures! A great accomplishment! :) if I may ask though, can anyone help me on how to get the auto-brightness to work? I have it set for auto but the screen doesn't light up that bright in the sun. Is something wrong with the default values? Thanks in advance! :)

Here is what I did to make my auto-brightness work. I based this on a previous post that said it only seemed to register levels of 1-50 instead of 1-1000.

Go into System Settings -> Display.
Select 'Automatic backlight'
Select 'Edit other levels...'
Go through each of the entries in the first column of the table and divide the number by 20. Round to the closest number. So it goes '0,1,2,4,5,7,8,10,11,13,14,16,18,22,25,29,34,38,43,45'.

I've been happy with my automatic brightness after that.

Regards,
M.
 
Yeah, I did the same thing earlier based on tamasaurus' suggestion. I wanted the numbers to be evenly divided, so my values were slightly different (2,5,7,10,12,15, 17,20, etc.), but I can't imagine it makes much of a difference. It was a huge improvement, though. Previously with auto brightness on I couldn't see anything outside or even in my car. Now it's much better.
 
I'm not sure what changed, because I'm sure the light meter was reading on the full scale (or at least pretty close to it) on previous builds. Glad my suggestions is helping though :)
 
...
I have been doing some reading on touchscreen implementation and have reworked the touch drivers. I have put together 2 versions. Nothing has changed from 06MAY build except touch screen drivers.

BSydz_Pa-Touch2-kernel-CM9.zip

BSydz_Pa-Touch3-kernel-CM9.zip
...
I've been using Touch2 for 2 days (though not heavily), and haven't noticed any significant difference. I'll probably flash Touch3 now and give that a try too.
 
Okay, I studied and worried for nearly two weeks before my (successful) attempt at switching from stock ROM to CM7- and now I'm nervous about switching from CM7 to PA.
Can someone explain it step-by-step....as if you were talking to a 12 year-old? :o



Yes, my mommy taught me that when I was potty trained. :rolleyes:

Put the ROM and the ics gapps files on your SD card....go to CWM recovery and wipe data/factory reset, wipe system, wipe dalvik....install the ROM and install the gapps right after...reboot
 
I tried both kernels and I have not seen much of a difference in touch reponse. I tried Touch3 first and that seemed to kill my 3G. I thought it might have been an issue with Virgin Mobile, but I could not get 3G anywhere. I tried restarting the phone several times, turning off WiFi and turning off and on the phones data, nothing helped.

I gave Touch2 a try and still no 3G. I restarted the phone a second time and bingo, my 3G worked fine. I cannot say for sure that this has anything to do with these kernels. I guess you could talk to 50 different testers and get 50 types of results.

If anyone has an idea why my 3G quit, please share.
 
So doing a factory reset, formatting cache, and wiping Dalvik on EVERY attempt is not good enough? Would be nice if anyone had actually mentioned a need for unusual procedures on this install.

I had some weird issues previously and fixed it by mounting and formatting /system in addition to doing the normal factory reset, cache & dalvik wipes. Couldn't hurt to try that, too, in case some code isn't getting wiped correctly.
 
If anyone has an idea why my 3G quit, please share.
It might be the same issue I had (see my posts above), which was not related to any flashing of ROMS: It was a problem with Virgin Mobile, and supposedly they have a daily script in place to work around the issue, so maybe their script fixed your issue, and the timing was just a coincidence.

3G is working for me with Touch3.
 
I left the Galaxy 2 and came back to myTruimph....I don't ever remember my 3G being as fast as it is now and I'm on touch 3.. ... can't figure out why locksceen weather not working though.
 
I left the Galaxy 2 and came back to myTruimph....I don't ever remember my 3G being as fast as it is now and I'm on touch 3.. ... can't figure out why locksceen weather not working though.

Touchscreen kernels don't change the speeds..

Anyone here considering the Google S4?
 
Back
Top Bottom