Develop Bugs

Desire build for Kaiser (SENSE)

Here is a desire build I have been tinkering around with for a long while. There are several several issues still in need of work so I am going to leave it to the community to help me out.
I failed to mention this is a full NAND install
I will get some screen shots up as soon as I can get time.
Much faster and much more responsive in my opinion than the legend / hero / mytouch builds
Here it is in a nutshell
- I am not a hardcore developer I have just been using existing files and putting something together that works most optimal. This build has a lot of polymod, and mssmison mixed.
- Hardware keyboard does not work correctly while using Rosie, disable Touch Input to correct this issue. Also speeds up system somewhat.
- clock.sh is in /system/bin use at your own risk It is only there for those that wish to use it is not enabled at boot. Modify sysinit.rc for this
- Disable vibrate on ring and quiet when phone is moved helps with incoming calls
- This build will leave approximately 37mb of free space for data, I do store apps on SD but it is a little unorthodox maybe someone can do better than me. I create an app folder on sdcard and symlink to it. I do not recommend this but I will be upgrading soon and could careless about damaging my cards they are old.
- Livewallpapers are questionable I don't use them or like them If they dont work and you want them then you are welcome to work on their developement.
- Bluetooth not working Help Please
- Wifi not working Help Please
- Widgets may need influenced to work just go to applications / manage applications / Find HTC Sense and Force stop and Clear Data if widgets do not load on boot.
- First boot takes an extreme amount of time.
- CompCache is disabled use it if you will I find that it causes stability issues try to keep the mem size down to 28 or less if you use it.
- Media folder is not built into this system it is included in the download just add it to your sdcard should look like this /sdcard/media
ONCE AGAIN I AM NOT A DEVELOPER I WILL WORK ON WHAT IS OUTSTANDING AS I GET TIME. I MAY OR MAY NOT MAINTAIN THIS BUILD IF YOU HAVE A FIX FOR ISSUES PLEASE PM ME I WILL UPDATE FIRST POST TO REFLECT THE FIX AND BY WHO.
DOWNLOAD
USE ONE OF THE 320x480 NBH FILES FOR YOUR KAISER

Why you name it Desire build.. android on desire looks differently

Michga said:
Why you name it Desire build.. android on desire looks differently
Click to expand...
Click to collapse
This is an old build, mssmison put it out as a sdcard install on the vogue a long time ago before the legend builds were put out. I kept hold of it and tweaked it to work on my kaisers nand. That is why it looks much different than the most recent builds

Post it in the vogue forum. They get more attention so easier chance of a wifi/bluetooth update.

kallt_kaffe can probably help you with the wifi.

Dukenukemx said:
kallt_kaffe can probably help you with the wifi.
Click to expand...
Click to collapse
Try this (NOT TESTED!). I actually think just putting the correct wlan.ko in /system/lib/modules might be all it takes but I included the usual stuff just in case.

does anyone have a mirror for this build. I would like to try it out

Does anyone have market problem. I can't even enter the market, it just kick me out

crackeyes said:
does anyone have a mirror for this build. I would like to try it out
Click to expand...
Click to collapse
It should download for you I just checked it to make sure it was still validwhat issue are you having

[BUILD] **Complete FroYo Bundle** FRX07.1 - Maintenance Release

FRX07.1 is here!!
This is a maintenance release - basically taking the newest components to make a completely up-to-date (as of Sept. 1).
Quite a lot has changed since FRX06 - the install process hasn't really, but be sure to read the changelog in the next post and the caveats in post #3!
<<<This is a link to the... FAQ Click it!!>>>​
I have created a complete bundle of FroYo with a stable kernel from GIT (August 19 / 1348), and rootfs from GIT (Sept. 2).
Please, feel free to DONATE to the XDAndroid project!
Every little bit helps!
Directions:
1. Download the full bundle (zip). (Updated September 1 2011)
If instead you just want the system.ext2 (zip) (Updated July 15 2011) file by itself... Don't download this if you're not sure! Grab the full bundle!
2. Extract it. You’ll see a folder, FRX07.1, copy its contents to the root of your SD card. If you want to run Android from a folder instead of all the files on the root of the card, follow the steps below.
3. Go into the STARTUPS folder. Grab the appropriate startup.txt for your device (if you don't know what device you have, you should read the FAQ), and move it to the root of the card (or where you run haret.exe from. If you want to change the location of the build, put a rel_path= statement in the cmdline section of the startup.txt. Mine is located two folders deep on the SD, so my rel_path=Androids/TP2Ref)
4. Screen calibration - you have three choices:
Re-use an old ts-calibration file if you have it and you know it's good.
Download the ts-calibration.zip file and extract it to where you put the rest of the files (root of SD or in a folder - make sure it all stays together!)
Manually calibrate - boot with no ts-calibration file and watch the boot process - you'll be asked to hit 5 points to calibrate the screen. If you have issues calibrating, try an older kernel (1225 works well) Once you have the calibration file hold on to it (make 15 copies if it's a good one ), reboot & go back to the newest kernel!
6. Run haret.exe.. Profit!
Let it settle out on the first boot. Many have reported they had to reboot basically because it was so slow - if you let it sit for about 10 mins so the media scanner can go thru everything, etc. it will be much more pleasurable experience. If you want adb in and watch the processes via top, you'll see why the phone seems so slow - there's lots of background processes cranking because this is the first boot .
Troubleshooting:
Please read the... FAQ
If you have any issues with the kernel, feel free to change it:
There are some devices that are having issues with the newest kernels. Please see the kernel autobuild service to get archived kernels. Once you download a replacement kernel, go to where you run haret.exe from - remove your old zImage/modules-xxxxx.tar.gz. Take the new zImage/modules-xxxxx.tar.gz and replace the old ones, same folder - where you run haret.exe from. Make sure the ‘zImage’ is named just that. Do not rename the modules file, do not extract it - should be in .tar.gz format.
See Incremental Updates for more information on updating the kernel and other components.
Random issues can often be solved by forcing the system to create a new data.img. If you're worried about losing data (all user data is stored in the data.img!!), Titanium Backup works quite well. If you wish, you can rename the data.img to something else, and let the system create a new one - just to see if it resolves your problem.
Similarly, if you wish try formatting your SD card - I prefer to use the HP Tool - do a full format, FAT32.
Even though this build is considered fairly stable, you are more than likely going to run into issues. The next post will address issues particular to this build - PLEASE READ THESE before asking questions! Feel free to post questions in this thread, I will do my best to address them. Big thanks to stinebd for releasing the system image, and of course the other developers for their hard work on making these kernels available.

stinebd's Changelog:​
stinebd said:
Here’s a new release for you, folks. This is a major release with a ton of changes, new features, and fixes. Our friend hyc/highlandsun did most of the heavy lifting for this release. Highlights include a rewritten RIL with support for world phones and greatly improved CDMA support; fixes for the media codecs; fixes for MMS on Sprint; increased security with the Superuser app.
A list of changes is included below. The FRX07 system image is available for download now, and will require the use of a new rootfs image, also available now. Additionally, we have a new bundle containing everything needed to enjoy a full FRX07 system.
Note: Due to the incredibly long list of changes, this is a somewhat condensed, terse changelog describing only the overall scope of the changes.
FRX07:
frameworks/base:
Major frameworks changes for CDMA/GSM dual-mode worldphone support. (hyc)
Fixes for data connection handling to improve startup time. (hyc)
Fixes for wifi handling to avoid issues on hanged drivers. (hyc)
Stagefreight (media codecs) fixes. (hyc/viruscrazy)
Fixes for Sprint’s wonky MMS markup structure. (hyc)
Fix MediaScanner not finding audio files (including ringtones) in system.ext2
hardware/libhardware_legacy:
Minor GPS driver fixes. (Alex[sp3dev])
Rename wifi interfaces to wlan0 on all devices (hyc)
hardware/xdandroid-ril: Major RIL refactoring for improved performance on all devices, and added CDMA/GSM dual-mode worldphone support. (hyc)
packages/apps/Gallery3D: Switched back to Gallery3D as the gallery app (closes bug #111)
packages/apps/Mms: Fixes for Sprint’s wonky MMS markup structure. (hyc)
packages/apps/Phone: Fixes for CDMA/GSM dual-mode worldphone support. (hyc)
packages/apps/Superuser: Added the Superuser package for authorizing su privileges. This, along with our signed builds, provides greatly increased security for the end user (mostly against malicious apps from the Market).
system/extras/su: Added as a dependency for the Superuser package
vendor/qcom/android-open: Include missing stagefright codec symbols. (hyc/viruscrazy)
To coincide with the FRX07 system image, the following rootfs changes have been made:
init.froyo.rc modifications...
Adjust wpa_supplicant service for the new abstraction provided by libhardware_legacy, as well as interface rename
Abstract the hciattach service to provide bluetooth support on both chipsets
Rename wifi interface to wlan0 on all devices
apns-conf.xml updated
keymaps completely reorganized, and RHOD end-call key has been remapped to be the Home key in Android.
default.prop: set ro.secure=1 to lock down the adb shell - su can be used with the Superuser app to authorize root access in adb if needed.
Click to expand...
Click to collapse

Layman's Changelog​
(As in, the changelog I wrote )​
FRX07.1 Changelog:
RHOD - all buttons on the front no longer wake the device. Only the power button wakes the device now.
Updated to the newest RIL
hyc's modified libs for video now baked in - *most* HQ YouTube videos (and other HQ videos) should finally work!
RHOD & TOPA - Userland (Android) now controls the LED by default now. If you need to debug sleep, you will have to change the behavior manually. See Detule's post on this topic.
Facebook sync should now work, out-of-box.
FRX07 Changelog:
Updated RIL (thanks hyc!) - this covers many different bugs that were in the old RIL - I'm only going to cover the major ones...
CDMA now works correctly (for the most part). force_cdma (and north_am_dialing) is now deprecated (not needed/ignored!)
You can boot with a SIM in on a CDMA device and choose your GSM or CDMA on the fly under Settings.
Location based on towers now works on CDMA.
1xRTT now displays correctly, but I never seem to get EVDO Rev.a... I always get 0. This is represented by a 3g icon, as this is what the Android framework provides.
Full MMS support! Please see this page for configuration instructions. Will need help fleshing out the list of carriers folks!
Spotty service, switching towers, etc should no longer cause the dreaded SoD (Sleep of Death) condition!
(Basic audio) 3.5mm support for RHOD400/500
Droidwall works out of the box now
Keyboard backlight now fades in/out
Gallery3D back in! Picasa Web Sync comes with it
A couple new apps added to AndroidApps folder:
rpierce99's app GetLogs
Titanium Backup

Caveats:​
BT - works now! But audio doesn't route. See this thread if you're feeling adventurous and want to play with/don't mind using some unstable/incomplete code...
NOTE: BT must be disabled in WinMo before booting Android or else you'll run into all sorts of odd issues...
WEP on wifi doesn't work. I heard an app called 'wifi-ace' (on the Market) fixes WEP!
If auto-brightness is enabled, the keyboard/button lights will fail at random. See this post for more scant details .

Yay! No more "when is FRX07 coming out?" posts!

highlandsun said:
Yay! No more "when is FRX07 coming out?" posts!
Click to expand...
Click to collapse
And to that effect, I would like to personally apologize to everyone for how long it took. Life has been crazy busy the past couple months. Hopefully we'll get GRX01 out in a more timely manner.

Woooohooooo!!! Thanks to all of the dev's on this, Stine, Hyc, Emwe, Arrrghhh (for putting up with all the BS!), and anyone else involved.

Can't wait to try this out. Thanks to all who contributed =)
highlandsun said:
Yay! No more "when is FRX07 coming out?" posts!
Click to expand...
Click to collapse
Just to get a sense of things, is it too soon for a "when is FRX08 coming out" post?

Diam 500 endlessly repeats smd-tty buffer mismatch on first boot (same as last 2? Kernels). Thanks for your work on this aargh and xda team.
Sent from my LG-P999 using Tapatalk

bluenote73 said:
Diam 500 endlessly repeats smd-tty buffer mismatch on first boot (same as last 2? Kernels). Thanks for your work on this aargh and xda team.
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
Ah yea... I need to test this on a RAPH800 I just got my hands on, thanks for reminding me!

Quick question. Prior to right now I've been running Hyc's 5/30 build very successfully and very happily. With that build, sound was working when recording a video. With the new FRX07, no sound comes when recording a video. Any ideas on how to get the sound to work with recording video on FRX07?

wmg316 said:
Quick question. Prior to right now I've been running Hyc's 5/30 build very successfully and very happily. With that build, sound was working when recording a video. With the new FRX07, no sound comes when recording a video. Any ideas on how to get the sound to work with recording video on FRX07?
Click to expand...
Click to collapse
His build has the new acoustic code seen here. It routes audio in a much better fashion, for sure... but it's not stable. Still needs some work, so it's not in FRX07...

arrrghhh said:
His build has the new acoustic code seen here. It routes audio in a much better fashion, for sure... but it's not stable. Still needs some work, so it's not in FRX07...
Click to expand...
Click to collapse
Thank you sir!

Big thanks to every one on the dev team for FRX07. You guys are awesome.
Just extracted FRX07 on to a newly formatted sdcard, copied startup & calib from FRX06 and when I launch haret, i get the following error.
"Error reading file. Expected 4096 got 0"
Anyone know what it means? Search did not turn up many useful hits.

webxplore said:
Big thanks to every one on the dev team for FRX07. You guys are awesome.
Just extracted FRX07 on to a newly formatted sdcard, copied startup & calib from FRX06 and when I launch haret, i get the following error.
"Error reading file. Expected 4096 got 0"
Anyone know what it means? Search did not turn up many useful hits.
Click to expand...
Click to collapse
Figured out...Had a corrupt zimage file. Able to launch now.

After a few hours of testing, great job!
The battery status actually tracks really close to where windows mobile says it should be. It also seems to go to sleep, and stay sleeping!
The only thing that's keeping me from using it full time is the phone and speaker phone have noticeable static that windows mobile doesn't have. Does the beta audio routing fix this, or are there some new settings I can try?
I also love the recent apps on end long press, fancy

First Impressions
Coming from FroyoB Hercules, this is a step up in my opinion. A HUGE step up.
I am running the Tilt2 with a 2GB Class 2 SD card and the provided FRX07 package .zip.
The build is running smooth and silky (making me have more faith in looped builds heh heh) with slight overclocking (633.600MHz). Had one hot reboot while accessing the Notification bar at the same time Market was updating Google apps, but after that the updates proceeded without issue. Everything else has yet to be tested, but I'm sure I won't run into anything major.
I'm 110% satisfied running the build. Accessing menus is quick and not laggy at all. To me, that's what's important: user functionality. You guys nailed it big time, and for that I thank you all very much. I won't be using CWM for a looong while
EDIT: Figured I'd list what is and isn't working for me. Again, I'm using all the default components like kernel and whatnot on the Tilt2 and have the phone overclocked to 710.400MHz now:
WiFi - Works
Data - Works (most stable I've experienced)
Bluetooth - Works (haven't tried headset)
WiFi HotSpot - Buggy; Turns on, but disabling keeps the notification icon and enabling again causes reboot. Different kernel doesn't fix.
USB Tethering - Works/Turns On (Don't have the driver to test quite yet )
Camera/Camcorder - Works (Camcorder doesn't record sound.. known issue?)
Phone - Works flawlessly
MMS - Incoming/Outgoing Works

maff1989 said:
Coming from FroyoB Hercules, this is a step up in my opinion. A HUGE step up.
I am running the Tilt2 with a 2GB Class 2 SD card and the provided FRX07 package .zip.
The build is running smooth and silky (making me have more faith in looped builds heh heh) with slight overclocking (633.600MHz). Had one hot reboot while accessing the Notification bar at the same time Market was updating Google apps, but after that the updates proceeded without issue. Everything else has yet to be tested, but I'm sure I won't run into anything major.
I'm 110% satisfied running the build. Accessing menus is quick and not laggy at all. To me, that's what's important: user functionality. You guys nailed it big time, and for that I thank you all very much. I won't be using CWM for a looong while
Click to expand...
Click to collapse
+1
Come from FroyoB Hercules v2.
Any possible to run FRX07 on CWM?

FRX07 on cwm is being worked on by Eodun,wich sadly yesterday released FRX06 for cwm

rtrip said:
After a few hours of testing, great job!
The battery status actually tracks really close to where windows mobile says it should be. It also seems to go to sleep, and stay sleeping!
The only thing that's keeping me from using it full time is the phone and speaker phone have noticeable static that windows mobile doesn't have. Does the beta audio routing fix this, or are there some new settings I can try?
I also love the recent apps on end long press, fancy
Click to expand...
Click to collapse
I would bet that the new audio routing stuff fixes the static problems. It definitely cleaned things up for me. But at this point I think we need a newer kernel in addition to the new audio libraries, the stuff in that audio routing thread is rather out of date at the moment.
I've been running most of this stuff for more than a month without issues. It's definitely going to be a lot more solid than any previous builds...

2/2 {rom} cm9 4.0.3 (WIP) icedBOCA Prequel /gsm\

In celebration of almost 1/2 a MILLION BOCA Downloads!
I proudly present the XDA release of:
The SGT7's *original & first GSM CM9 port:
>click pic to begin<
or; http://magrathearoms.weebly.com/
image created by supagforce
*first icedBOCA went out to testers 11/30 in heimdall form. V2 went out: 12/16
Original in no way describes quality of performance or relate to updates or features.
First relates to public availability.
if my timeline is wrong, please pm.
FEATURES​
Partial addition list:
*Added CombinedBar (statusbar) Auto on/off, upon fullscreen option.
*Fixed SystemUI FC when disabling Notifications
*Additional options and toggles
*Improved caller id.
*Car charging
*Touch outside a notification window to shove to background. Without halting install actions! Really helps with installing multiple side loaded apps. You don't have to wait for each to finish.
*contacts picture and name fix for incomming/outgoing calls
*6 new drawer and screen transitions (cm9 launcher)
*Smoother/faster rotations
*Screenshots fixed
*Long press menu soft key (3/4 seconds) for persistent back-lights lights on/off
*Recent apps view rotation fixed
*Tablet screen fling (Action to change screen or scroll shortened to fit a tablet screen size)
*Smoother volume adjustment - more steps
*Scrollable Tablet Settings Bar
*Power Widget added to Combined Bar
*More Tablet Settings Bar options
*Better performance and battery life
*Smoother scrolling
*Working init.d scripts
*Smoother audio level adjustment
*3g
*Auto zip align at boot
*Messaging
*Ability to script inject
*New/more browser options
*New/more settings options
*Working Bluetooth audio
*New performance options
*More options through out the entire system
*Auto Ext4 conversion (check sdcard for icedBOCA.log)
*Ability to use Zram (compress memory for increased virtual capacity) and also choose compression level!
*Dalvic tweaks
*BMLwrite
*Carrier/Voicemail identification fix
*JIT (Just In Time compiler)]
*Quicker screen rotation
*UI improvements
*Game play improvements.
*Ps3 Bluetooth controllers
*Bluetooth upgrades
*Faster responces
*much much more!!
*Hot Reboot
*BOCA extra screen timeouts
*A few of the new settings
dont comply yet,
basically awaiting
merge/development/& build.
* All claims, or suggestions
of improvements or updates,
are only held in claim over
previous versions of icedBOCA​BROKEN​
*Camera (lol dont even open it!)
*True HW accel
*USB Computer mounting (use supplied USB Storage app)
*Global Action Recovery/Download mode (use supplied rootbooter)
*Hot Reboot???
*Phone?? I remember there was a simple fix in other ics thread, Ill research it and apply it
KERNEL​
Some things that I contributed directly to this kernel were suggestions about voltages, tips on recovery, showed changed the bootclass path (to make it an ICS kernel. From original ics boot spilt thread, but modded to build from source, as ours doesn't split) some other small things, alot of random work(as it is based off BOCA kernel - we used to share sources) and I ported/patched the following: SIO, VR NOOP, INTERACTIVEX, SAVEDZEN, GREASEDLIGHTNING, DARKSIDE, ONDEMANDX, SCARY, SMARTASSV2, SUPERBAD. Maybe a bit more, but nothing else comes to mind, directly.
Therefore I feel that I have contributed enough to include this kernel in my release.
If you notice, I didnt "spiff" the recovery up to its usual vibrant self this time.
Maybe next time, if users liked it in BOCA RC1.
ROM​
This creation was ported and built by me.
I did get various ideas and configurations from developers around the web. And shared oh-so-many ideas also.
PLEASE DO NOT DISTRIBUTE BOCA IN WHOLE OR PART. NOR RE-UPLOAD​
TREBUCHET
This version of the launcher uses hardware accel.
In can also upload a version that uses cpu /software accel.
Let me know.
Feel free to distribute the link (when uploaded) Its cyanogens product, but VERY heavily modded by me. Others on different devices (if it'll install) may appreciate it. Just kindly give me credit.
Info to read about the future:
http://forum.xda-developers.com/showthread.php?p=22086399#post22086399
post 286 down
THANKS​
Its truely impossible to thank everyone, so I chose a very few who stood out in my short development stint.
spacemoose1
Koxudaxi
Ultramag
nobleskill
Fattire
reborn
Ronis
Alroger
Reborn
jt1134
Humbertos
tecknomancer
google
github
xda galaxyTab section developers
cyanogen and its gerit system
my users
Every single person who added to the development of ics for the sgt7..........
.......................................and every single android developer!
If I have missed anyone, it was not intentional. Please, PM me, and I will add you.
Thank you!!
As per request i have supplied a link that goes directly to rom.
DOWNLOAD link~ http://www.4shared.com/zip/7bZNGPJh/icedBOCA_prequel_2-2.html

NOTES
**FIRSTLY before posting, READ THE THREAD
**Replies requesting help, or reporting UNREPORTED bugs must include the following information:
Carrier
Country
Original device branding (sgh-t849, P1000L ect)
ROM you came from
BE HONEST in the steps you took to get here
If possible, include a link to patsebin, where you have uploaded your LOGCAT of the error
The more info the better
-IF YOU CAN NOT DO THESE SIMPLE THINGS, IT WILL BE DIFFICULT TO CORRECT THE PROBLEM-
As a user, you are very important to me, as is my quality of work and enjoyment of such work.
But if you cant be bothered to offer up some very simple info, Then I can hardly be bothered to beg you for it, just to help you.
*The red boarder still persists, infequently
*THERE IS NO HARDWARE ACCEL!!
*NOT EVERYTHING WORKS!!!!!!!!!!!!!!!
This is a DEVELOPMENT site, not a polished product site. DONT COMPLAIN!! Be helpful instead!
*We (all sgt7 cm9 ports) use the wrong graphics driver and graphics resolution. (its all thats available) So some video may not react up to your standards.
*This is a WORK IN PROGRESS!!!!!
I am a ONE PERSON development team.
I do this all in my free time, for the pure joy of it. Dont kill my joy by being a "GIMMIE-GIMMIE" or a Complainer
I (and every single developer here) am nice enough to share our work with you, be gratefull.
Or build it yourself.
*Doing things like porting and building a source code (especially an unfinished VERY alpha one) IS VERY TIME CONSUMING.
Each new build takes two full days to compile. Ive learned how to wait.
Total time ive spent doing this, added up probely equals over 700,000 hours. Again, for the joy of it.
So be patient on updates, or mistakes. There is never, ever an ETA. Dont ask.

About the download link
Its 4shared ;(
My server went down last night.
After I complete repairs, All my work will be uploaded to it.

Hi diz, just to let you know the image at the top is not clickable, and can only be viewed when users are logged in. Also there is a version of the image with (CM9) added to it in the boca rc1 post, you might want to copy these to your hosting and link them from there.
Gonna give this rom a try NOW!! thanks again for all your hard work.

supagforce said:
Hi diz, just to let you know the image at the top is not clickable, and can only be viewed when users are logged in. Also there is a version of the image with (CM9) added to it in the boca rc1 post, you might want to copy these to your hosting and link them from there.
Gonna give this rom a try NOW!! thanks again for all your hard work.
Click to expand...
Click to collapse
thanks for the headsup.
wierdly now it wont even show up while loged in.
but does when i go to edit post.
ill take a look at it.
Thanks again for the great artwork

hey diz, top work on releasing a new version of icedBOCA, looks like you put a lot of work into it
ive been kinda quiet for the last week (got a new computer from work which ive turned into a media centre and it was a pain to get the old clunker of a video card working in it)
i know what you meant in your other thread by the other one taking off the way it has, i was gonna try to manually add all their added stuff to your AOSEP version just to see how it went, but it wouldve taken forever just to get it to where they have, and keeping up with the updates would be hard (although i still want to do it just to learn more).
anyway, i thought id thank you yet again for your AOSEP idea and all behind it, even though i started fiddling before you had the idea, it pushed me to take it further.
with that, id thought id offer up one piece of information i learnt from another thread that fixes the red borders completely, on top of:
Code:
persist.sys.strictmode.visual=0
the other line that ive found that removes it completely is:
Code:
ro.build.type=user
so if the build type is set to user it seems to get rid of the red borders completely. hope this helps in some way and best of luck in the future.

just when i'm gonna download this ROM i found out that phone is broken, too bad >.<
gonna taste it when it fixed. great job diz!

Thank you mate! Like allways a great job!
Just experienced a small bug.
When rom installs I got allways a FC of a chineese aplication.
Thanks again, performance is very good.

Changing default keyboard and laguage to English in settings (Language & input) helped stop this for me. No need to freeze the launcher.
testadeferro said:
Thank you mate! Like allways a great job!
Just experienced a small bug.
When rom installs I got allways a FC of a chineese aplication.
I´ve frozed the launcher with titanium backup and its fine.
Thanks again, performance is very good.
Click to expand...
Click to collapse

Use the fix from the cm9 thread.
Sent from my GT-P1000 using Tapatalk

Download link
Would the Chef be kind enough and put in post 1 or 2 in bold letters where we could all DOWNLOAD the Rom. Thank you for your hardwork and sleepless nights. More people will follow you!

Derrian said:
Use the fix from the cm9 thread.
Sent from my GT-P1000 using Tapatalk
Click to expand...
Click to collapse
Could you be more precise? cm9 thread is quite long.... which fix?
thanks in advance

dabrowsk said:
Could you be more precise? cm9 thread is quite long.... which fix?
thanks in advance
Click to expand...
Click to collapse
You need to alter a couple of lines in the build prop and swap the phone. Apk for the one in cm 9
Sent from my GT-P1000 using Tapatalk

hey diz
hey i am a member on ur site i am the guy with the riffbox and stuff and if there is anyway i can help u i have a new quad core desktop that i compile with and at the most my compile times are 3 hours.i also thought i hear u say that u needed some ram i have some old ddr and ddr3 ur welcome to ...maybe i can help u compile or something andf i would like to pick ur brain on some stuff

my device is p1000 and I'm on overcome android 2.3 . due to hardware problems (my device crashed) I can't access recovery. can you make a flashable (via odin) TAR instead of ZIP please? if not say why it's impossible

Derrian said:
You need to alter a couple of lines in the build prop and swap the phone. Apk for the one in cm 9
Sent from my GT-P1000 using Tapatalk
Click to expand...
Click to collapse
ahh, the one with RIL thing
back then when i was on alpha 3 i used the method to solve the phone's FC but no good. Im on red rebel's now and its all working fine
If I pull the one from red rebel's , would it be as good as the phone.apk posted there or it's gonna be different?

hummy15 said:
Would the Chef be kind enough and put in post 1 or 2 in bold letters where we could all DOWNLOAD the Rom. Thank you for your hardwork and sleepless nights. More people will follow you!
Click to expand...
Click to collapse
im in talks with the mod about it.
a thread restructuring may be comming soon.

As per moderator request i have supply a link that goes directly to rom.
op has been updated to comply.

thank you for your work -
I`ve flashed it on clean safe gb from overcome with overcome kernel
battey drain is significantly better in your rom, although its unstable.
sometimes its 9 mah per minite )radio off, screen off
sometimes its 120.
Killing apps in backgroung helps though
I`m using battery monitor widget for monitoring
all my video players seem to work better than in cm9 build
the browser is very slow to render and load, cm9 is way better
but 3g is more than 1.5 times faster
other glithches
the mentioned red border, scrolling stutters sometimes, application names in all application screen sometimes are not displayed fully, its get choped and the rest is shown at the side of the screen.

Dizgustipated, Thank you so much, for making it easier to download your Rom. More grease to your elbows.

Roll-iphon

Roll-iphon download: Mod edit: Link removed. <- this is the one best Google Play Edition 5.1 ROM!
The launcher animations with real iPhone.
To use animation rendering engine Project Butter.
Smooth and fast animation.
Very simple and clean design.
Put the camera, gallery, sms, street view, calendar, extended menu restart button, the screen went out.
My job icons live living clock, calendar, оriginal sounds.
Installation Instructions:
- install a custom recovery...
- download Roll-iphon rom zip
- reboot recovery
- Install Roll-iphon with Full Wipe
- reboot device
Thanks Based on Danvdh
Google Project Butter accomplished its “buttery smooth” responsiveness and “speed infusion” improvements via three main additions: triple buffering, which improves coordination and animation synchronization between the CPU, GPU and display; VSync, which improves graphical performance and increases frame rates to 60fps (frames per second); and touch responsiveness, which predicts a user’s upcoming actions of the screen in order to improve load times for those actions.new technology Project Butter, aimed at making the entire UI fast, fluid and enjoyable — one of the complaints against Android was that the interface is sometimes slow even on powerful machines. The technology includes triple buffering the graphics pipeline in order to ensure the absence of jumps in the frame rate in the animation interface, as well as technology enabled vertical sync.
XDA:DevDB Information
Roll-iphon, ROM for the Samsung Galaxy S 4
Contributors
rullert
ROM OS Version: 5.1.x Lollipop
Version Information
Status: Stable
Created 2015-10-25
Last Updated 2015-10-25

Is it a GPE rom with a launcher right? ?

This guy is trolling.
Need someone to close the thread.

Razov said:
Is it a GPE rom with a launcher right?
Click to expand...
Click to collapse
Yes, of course only the rest of the shell is almost original GPE -10-21 -2015 .

ImChoey said:
This guy is trolling.
Need someone to close the thread.
Click to expand...
Click to collapse
Since I'm not a fan of the ordinary made extraordinary 5.1

The only thing you 'made' is catch the zip and put an apk inside there and now there is a new rom?

Razov said:
The only thing you 'made' is catch the zip and put an apk inside there and now there is a new rom?
Click to expand...
Click to collapse
Yes, a new not old.

:laugh: :laugh: :laugh: cool

need to theme settings, statusbar and add control center to make it look like iphone...good idea, something completeley different, but need a lot of work

beafraid88 said:
need to theme settings, statusbar and add control center to make it look like iphone...good idea, something completeley different, but need a lot of work
Click to expand...
Click to collapse
I tried already, but it turns out worse than the original short I could not get who can give the necessary files here. Although so good to me personally.

Thread closed.
12. Using the work of others.
If you are developing something that is based on the work of another Member, you MUST first seek their permission and you must give credit to the member whose work you used. If a dispute occurs about who developed / created a piece of work, first try to settle the matter by private message and NOT in open forum. If this fails, you may then contact a Moderator and provide clear evidence that the work was created by you.
Convincing evidence will result in the copied work being removed. If there is no clear evidence that it was you who created the work, then in the spirit of sharing, all work will remain posted on the forums.
As an addition, developers have the right to hold exclusivity over their work for as long as it is deemed necessary by that developer. However, if the work is claimed as exclusive, it must remain as such. No selective sharing will be allowed (ie, allowing certain people to use it and not others). If the developer decides to start sharing the work with others, the work automatically becomes available for all to use, albeit with the relevant credit displayed.
When permission has already been given, unless there is a very valid reason, it cannot be revoked (same applies to major updates on the work). Under that same premise, permissions cannot be denied unless the work is exclusive or under extreme circumstances.
In plain English: If you want to keep your work exclusive, go for it. However, if you are going to share your work, do it fairly.
Reposted content, derivative or maintaned works based on that of former or banned members may be removed at our discretion.
These rules apply to all software posted on XDA (including but not limited to ROMs, RUUs, apps, games, kernels, themes, icons, etc) unless that software comes with a license that waives these rules.
Regards,
The_Merovingian
Forum Moderator

CM13 Z3+ Ivy E6553 Alpha -- Secondary Testing

This is a no-frills thread.
I am looking for additional competent testers to provide proper feedback.
Testers are assumed to be experienced. Thank you.
Okay here it is.
Flash in order of appearance. Required.
cm_ivy-test_rebuild.zip
cm13_ivy_updater_system-etc.zip <--Fixes audio.
cm13_ivy_updater_bootimage_ round1.zip <-- Fixes external storage
Thanks @MotexT for initial testing and feedback.
So, working:
All CM apps; RIL; WiFi, Bluetooth; Theme Engine, Audio, Bluetooth/WiFI Hotspot work confirmed
Buggy:
Bluetooth (crashes of Bluetooth Share);
Camera (color bugs, frontal camera take photos with glitches);
Initial load/Load after reboot (glitches, performance loss - solving easy with locking/unlocking device);
AutoBrightness (small delay when switching brightness levels on the fly)
Screen Recorder
Not working:
NFC;
External SD Card;
OTG
Click to expand...
Click to collapse
Again this is alpha. This is for sinlge sim, you are welcome to test on dsds, i would be very interested in the results.
Cyanogenmod Source
Thanks to/for
@CTXz Sources and convincing me to get a Z5P instead of another Sammy device.
Sony Kitakami Platform Developer Organization
@zacharias.maladroit For answering questions, many questions. [ still have more... xD ]
Those of you without a sense of humor, go away.
Okay current features i'm working on and stuff that works/doesn't work
UVC support enabled in kernel. probably need to build rom-side support still. libuvc avutils etc.
- This is for plugging in camera devices in conjuction with apps like LegitDashcam.
USB Gadget functionality as per pelya's work ,
- pelya/android-keyboard-gadget
I am working my kernel source here toward net-huntery goodness.
The rest you tell me, and you tell me properly. Messages like
"waahhh my whatchamhoozit is all floompy"
are not acceptable.
This is not a random discussion thread either. Idle chatter belongs in general.
This is also NOT a discussion thread for Xposed,Viper, etc..
Thank you.
m

Notes and Updates
NOTE
SELinux is COMPLETELY disabled on this build. If You want security go back to stock.
SELinux enforcing is the goal though.
I strongly recommend using a "traditional" root os SuperSU over systemless-root.
Reasons:
Opengapps requires a factory-reset or fresh install to set up correctly!
Privacy Guard based root sucks. It forgets alot of permissions granted.
Use BETA-SuperSU-v2.52
Would have posted earlier but needed a smoke break *>cough<*
NOTE: this initial offering is in 3 parts due to limited bandwidth issues.
When i have resolved external storage i will upload a new build.
NFC may take a little longer.

Breathing Room
Reserved 2
@MotexT will be posting screens, as time permits, in post number 4.
Trolls will be burned.

Screenshots
Here we have some screenshots. If you need more - PM me, will add them ASAP. Also include the type of screenshot.

I'm using a single SIM version.
Please continue the work. I'll start testing by the weekend.

lukeaddison said:
I'm using a single SIM version.
Please continue the work. I'll start testing by the weekend.
Click to expand...
Click to collapse
Thanks,
If i can get you to specifically test and log screen recorder that would be great. [including during playback]
Currently it appears to function but when it comes to playback of the recorded file, playback breaks.
Thanks.
m

Hy well this thread need a clean start
And I will test it this weekend
(single sim) hopefully it works like a charm and till then i hope you fix some little bugs you mention
BTW cause I have a SmartWatch (moto360)
Does the Bluetooth restart or dont work like it should be?
Sent from my E6553 using XDA-Developers mobile app

So, a small report about this ROM. For now I'm using it two days in a row, and it's pretty stable - you can use main functions without any troubles: WiFi, RIL, Themes Engine etc. Bluetooth works great, crashes sometimes and automatically restarts - not a big deal. It's a really smooth for alpha build and could be used even as daily driver if you close your eyes on some small bugs with not so important stuff. Anyways, testers are welcome

KOALAaufPILLEN said:
Hy well this thread need a clean start
And I will test it this weekend
(single sim) hopefully it works like a charm and till then i hope you fix some little bugs you mention
BTW cause I have a SmartWatch (moto360)
Does the Bluetooth restart or dont work like it should be?
Click to expand...
Click to collapse
K, actually i don't know. But it's cool that you have a smart watch, would you mind be a tester/logger for that function in particular?
That would be great.
Thanks
m

Single sim
How to solve this？:crying:
Full selinux support is present.
MTP Enabled
installing '/sdcard/cm_ivy-test_rebuild.zip'...
checking for MD5 file...
Skipping MD5 check: no md5 file found
target:sony/cm_ivy/ivy:6.0.1/Nega_spork/76b3bfd6c4:user debug/test-keys
could not detect filesystem for /dev/block/bootdevice/by-name/system,assuming ext4
mount:failed to mount /dev/block/bootdevice/by-name/system at /system failed;no such volume
E:Error executing updater binary in zip '/sdcard/cm_ivy-test_rebuild.zip'
Error flashing zip '/sdcard/cm_ivy-test_rebuild.zip'
updarting partition details...
......done

Hi , you are most likely using the wrong recovery for your device
See here and get a correct recovery
http://forum.xda-developers.com/xperia-z4/development/twrp-xperia-z3-fota-recovery-t3346298

moonbutt74 said:
Hi , you are most likely using the wrong recovery for your device
See here and get a correct recovery
http://forum.xda-developers.com/xperia-z4/development/twrp-xperia-z3-fota-recovery-t3346298
Click to expand...
Click to collapse
it really works!Thank you

Ok cleaned this up a bit.
I don't really have much issue with discussion on GIT etiquette, and tips to keep your "house clean" as it were. I think that's a good thing with devs working together on things like that.
Here's the bottom line. If you are merging commits into a kernel you have to keep the original authorship, period. To do otherwise is kang. We all know this.
Now if some dude has some private repo where during personal testing authorship is removed, but anything merged into the public kernel or the release repo/binary maintains proper authorship, then that is a bit gray, but the user is not clearly attempting to claim authorship at all.
If anyone sees a blatant kang, or attempt to hide/claim authorship, please report to the mods for handling. If this particular point needs more discussion, please open up a thread about it and have a non flame war discussion about it.
@moonbutt74 - I do ask that you make it very blatantly sure what your public release repo is, and that your authorship is maintained, and I actually recommend you do not link your personal playground repo to avoid situations.
Thanks guys.

After looking thru all and speaking with the OP, I am closing this thread.