[ROM] Paranoid Android 1.5a [CM9 HYBRID] [v3]

Alunduyn

Senior Member
Mar 23, 2012
260
112
0
Why its unusable? Thanks for accepted me as a tester. I'll do my best. ;)

Ok here it is my first look at this rom:

Wiped all the cache/data+dalvik then i proceed to flash the rom, once it was done i've flash the Gaps zip. First boot took like 2 minutes (i guess it would be more but fine) Once got in the launcher, i've followed the wizard. Nice smoothness, nice response.

The only issue that I found is i got the same problem that i had when i flashed the zeubea's CM9 to my legend, it was that the home/search/back and menu buttons didn't light up. What will be causing this because it doesn't happend when flashed another rom, just when using ICS? :confused: And how can i got the masstorage option appear on the status bar?

I've flashed again and everthing seems to be ok, if any issue arise (despite my un-lighted menu -.- ) i'll let you know, by now everthing is Ok.
For testing, I can give you the compiled ROM, but unusable literally means "unusable". I just took a first look and a lot of texts were wrong ( instead of "restart" there was a "lock screen" by example ), a lot of things for MDPI were missing ( like overflow effect : only an orange field saying "add something for this event" were shown ). Settings didn't work : when I selected a category for options (like "security") the app crashed and sent me back to launcher. Also phone didn't shut down, I had to remove battery. The GNex ROM is too different for Legend, I think no port can be done from that.

:eek: I see credit for me in 1st post, not sure how I contributed to "this" project but thanks Alex :D

Sent from my Legend using xda app-developers app
Your hint for rebuilding apks was very useful for the project, so I wanted to mention you :)

PHONE PROCESS ,force close :I can't use the phone
If you changed Phone DPI the problem will appear, in this and in zeubea's ROM. You can easily solve that replacing phone.apk in system/app with the one modified that feed3 shared. If the one who made that can grant me permissions, in next releases I'll replace original phone.apk with that.

Edit : I feed3 solved the keyboard problem. Just replace LatinIME.apk with the one in his MIUIv4. I'll directly include it in next release.
 
Last edited:

nafnist

Senior Member
Nov 18, 2007
202
16
0
I am currently using cm9beta4 with 133dpi and apex launcher.
There are a few issues with the dpi change.

This sounds like just the rom for me, so Thanks for this!
 
Why do restarting the phone takes longer? Well i'm currently copying the phone.apk to system/app with root explorer to use the phone itself...

Edition: I can't make a call still i've followed the feed3 instructions... I must say that i couldn't find the phone.odex app in these folder (system/app) and yes i gave w/r-r-r permissions.


If you changed Phone DPI the problem will appear, in this and in zeubea's ROM. You can easily solve that replacing phone.apk in system/app with the one modified that feed3 shared. If the one who made that can grant me permissions, in next releases I'll replace original phone.apk with that.

Edit : I feed3 solved the keyboard problem. Just replace LatinIME.apk with the one in his MIUIv4. I'll directly include it in next release.
The LatinIME.apk needs to be taken from the system/app folder of MIUIv4 rom?...
 

Alunduyn

Senior Member
Mar 23, 2012
260
112
0
I am currently using cm9beta4 with 133dpi and apex launcher.
There are a few issues with the dpi change.

This sounds like just the rom for me, so Thanks for this!
Not just DPI changes :)

Why do restarting the phone takes longer? Well i'm currently copying the phone.apk to system/app with root explorer to use the phone itself...

Edition: I can't make a call still i've followed the feed3 instructions... I must say that i couldn't find the phone.odex app in these folder (system/app) and yes i gave w/r-r-r permissions.




The LatinIME.apk needs to be taken from the system/app folder of MIUIv4 rom?...
Longer restart may be caused by the need to calculate DPIs.

Have you changed the DPI of Phone? If you set it to Phone mode and 160 DPI it will work fine. I don't know why even with modified apk it FCs. Can you provide more details? Which DPI do you use? Tablet or Phone mode? Thanks for reporting.

You can't find odex because this ROM is deodexed. You don't need any odex file. Maybe it still FCs because the apk given by feed3 is odexed. I'll try deodexing it and uploading tomorrow.

Yes. But you don't need to worry, v1 has it already inside, so you have just to flash it.

_________________________________________________________________________________
v1 Released
Changelog
Fixed Tablet Mode ( Now Working )
Fixed Keyboard ( Now Working on Standard DPI )
_________________________________________________________________________________​
 
Last edited:
Not just DPI changes :)

Longer restart may be caused by the need to calculate DPIs.

Have you changed the DPI of Phone? If you set it to Phone mode and 160 DPI it will work fine. I don't know why even with modified apk it FCs. Can you provide more details? Which DPI do you use? Tablet or Phone mode? Thanks for reporting.

You can't find odex because this ROM is deodexed. You don't need any odex file. Maybe it still FCs because the apk given by feed3 is odexed. I'll try deodexing it and uploading tomorrow.

Yes. But you don't need to worry, v1 has it already inside, so you have just to flash it.

Ah and BTW, v1 download link is now up, I'm uploading also on Mediafire now.
Ok. Basically i made the following changes:

Before update - After update
1) Configuration: Set to Phone mode (Optimized) -Changed to Tablet Mode (Optimized)
2) User dafault DPI: Stock DPI (Phone)
3) User dafault UI: TAble UI
4) Framework-res: Stock DPI(Phone) - Then I've followed your instructions
5) SystemUI DPI: Default DPI
6) List of apps: Just changed the camera to 160 DPI and the Native keyboard to 130.

After i did a restart to make the changes on... The restar was so smooth -different from the first time booting- everthing seem ok by now...
Now i'm trying to make all steps again check them one by one to make clear if i did or not a mistake...

I've flashed the update and everthing except the phone itself works... :crying: What i did wrong? Do i have to set another DPI? Sorry if i'm disturbing/annoying you with this but i don't know what i am doing wrong.... :eek:

---------- Post added at 03:21 AM ---------- Previous post was at 02:35 AM ----------

Just to confirm, if you use the attached file here? Might need to clear dalvik after replacing the file.
Yes brother, i've used that file but i didn't know that dalvik should be wiped after instalation,... Thanks for the guide! I'll see what's happend now, Ok an "Android is upgrading" message appear and after upgrading i went off the phone to try a call and the message now was different "Unfortunately. contacs app has stopped"... Hmm... i think i must change the contacs DPI.

I'll try it out tomorrow... by now, many thanks, its changed something at least.
 

Alunduyn

Senior Member
Mar 23, 2012
260
112
0
For phone FCs, you can try to manually set phone to PhoneUI and customDPI 160 (just to be more sure). With that I have no problems. For changing Phone DPI I can't give you any hint right now, I'll try all these solutions and report when I'll have a sec.

Alex, could you guide to config like what we see in the pictures you post, please? I try but i can not.
I'll do some images when I'll get back to my PC. Right now I can tell you that you have to open settings - Paranoid Settings - Configuration - Tablet Mode (Optimized) for the tablet UI. If you want to change single apps Paranoid Settings - List of apps - *navigate to your app* - select tabletUI and customDPI (120 is good) / phoneUI and StockDPI (phone). TabletUI for the 2columns view, phoneUI for the single column.

Enjoy

Sent from my Legend using xda app-developers app
 

quannv_vp

Senior Member
Aug 18, 2010
57
1
28
Hanoi
For phone FCs, you can try to manually set phone to PhoneUI and customDPI 160 (just to be more sure). With that I have no problems. For changing Phone DPI I can't give you any hint right now, I'll try all these solutions and report when I'll have a sec.



I'll do some images when I'll get back to my PC. Right now I can tell you that you have to open settings - Paranoid Settings - Configuration - Tablet Mode (Optimized) for the tablet UI. If you want to change single apps Paranoid Settings - List of apps - *navigate to your app* - select tabletUI and customDPI (120 is good) / phoneUI and StockDPI (phone). TabletUI for the 2columns view, phoneUI for the single column.

Enjoy

Sent from my Legend using xda app-developers app
Thanks so much, i will try now.
 

Alunduyn

Senior Member
Mar 23, 2012
260
112
0
_________________________________________________________________________________
v2 Released
Changelog
Fixed Automatic Brightness ( now works without problems )
Fixed Keys Backlight ( with Automatic Brightness it works )
Fixed "Reboot to Bootloader" ( Removed option "Download" from reboot menu and added "Bootloader" )
_________________________________________________________________________________​
 
I'm not in PA right now so i cant test it and dont know if these apk will make any different but no harm to try right? :) download the files from HERE (ContactsProvider.apk) and HERE (Contacts.apk), copy/push to /system/app/, reboot into cwm and clear dalvik-cache in advance.
Well i've followed step by step and i got the following:

The launcher shows without the phone and contacs icons even their were still on the system/app folder:


This 2nd image is a representation about the apps permission and once i tried to fix the permission, the apk rejected the changes:


I'm getting mad with this... anybody else has this problem or just its me? :eek: Did someone fixed that? :confused:

---------- Post added at 06:26 PM ---------- Previous post was at 06:18 PM ----------

_________________________________________________________________________________
v2 Released
Changelog
Fixed Automatic Brightness ( now works without problems )
Fixed Keys Backlight ( with Automatic Brightness it works )
Fixed "Reboot to Bootloader" ( Removed option "Download" from reboot menu and added "Bootloader" )
_________________________________________________________________________________​
Hi Alex brother! I'm currently downloading this rom to flash it later (like in one hour) but unfortunately i'm sock yet with the phone issue... :crying:

I'll see what can i do for fix that... :fingers-crossed:
 

feed3

Senior Member
Nov 17, 2011
1,040
727
0
The Land of Hornbill...
Well i've followed step by step and i got the following:

The launcher shows without the phone and contacs icons even their were still on the system/app folder:

This 2nd image is a representation about the apps permission and once i tried to fix the permission, the apk rejected the changes:


I'm getting mad with this... anybody else has this problem or just its me? :eek: Did someone fixed that? :confused:


You need to mount r/w that /system partition. if you are using root explorer, it is just a matter of tapping that little button at the top with "Mount R/W" words.

Some people able to fix the issue just by using the phone.apk from my other thread, so i don't know why it is so different with yours but my guess would be you missed out some step (changing permission is one of them)
 
You need to mount r/w that /system partition. if you are using root explorer, it is just a matter of tapping that little button at the top with "Mount R/W" words.

Some people able to fix the issue just by using the phone.apk from my other thread, so i don't know why it is so different with yours but my guess would be you missed out some step (changing permission is one of them)
:crying: Ok let me explain you guys what exactly i'm doing, i mean, the way that i used to install this rom.

(I most say that i cleared my sd card just in case some folder/file was causing this, which is not what i suspected :( )

Thats the way i've had flash it from the begining (and i have done the following steps after cleared my sd card)

Recovery mode -> install zip from sd card -> choosed the paranoid zip -> choosed yes = Succesfuly installed

Then flashed the gapps the same way as the paranoid = Succesfuly installed

Rebooting system -> paranoid boot image -> follow the wizard as well ->settings -> paranoid settings ->configuration: set as Phone mode ->User default dpi (non touched) -> user dafault ui (non touched= -> framwork-res dpi (non touched) ->systemui dpi (non touched) List of apps (I've just changed the keyboard dpi at 130)

Now using your guide to change the phone apk:

Installed Root Explorer and copyied the 1.8 mb phone.apk to the sd -> opened R.E. -> mounted W/R since the begining -> open sdcard folder -> selected "move" for the phone.apk -> selected "sysetm" folder -> selected "/system/app" -> selected "paste" -> went out and restarting in recovery -> wiped dalvik cache -> rebooting system -> applying changes and the result is!!"

Nothing gain with it!! :crying: But wait, there is something that we're skipping!! What?? The app permissions itself!! I remembered that once i was moving the app to system/app from my sd the permissions that it had its was similar to the image i posted here which dissagree with the system/app permissions, don't get it yet? Ok this image could help to understand better what i mean.

Thats the permissions of the apk for default;


So all i have done was change it as showing; e.g.


Alhamdulila!! Eureka amicus!! :cool:

Now i'm enjoying the rom as a kid with new toy!! :victory: The only that i missing is the ability to select "mass storage" as usual but i'll keep in touch!! By now many thanks to you guys, Alex and Feed3 for your hints!! See you in few days, i'm going outside the city for a while after facing all this... :good: Hopefuly this will be a key to anothers users!... :D
 
  • Like
Reactions: jazib360

Alunduyn

Senior Member
Mar 23, 2012
260
112
0
I'm happy to hear you finally did it. :) I'll link to your post in main thread, so everyone can fix the problem easily.

Note that with v1 and v2 changing DPI for keyboard is no more needed :)

For the mass storage problem, I don't know what the problem could be, I'll logcat a lot during my holidays hoping to return home with a solution (and maybe v3)

I'm happy you all guys like my work, I never even imagined to do such a thing. Thanks to everyone for support, reports, help and help to others.

Sent from my Legend using xda app-developers app